skills/ancplua/working-on-ancplua-plugins/SKILL.md
Primary instruction manual for working within the ancplua-claude-plugins monorepo. Use when creating, modifying, or debugging plugins in this repository.
npx skillsauth add aiskillstore/marketplace working-on-ancplua-pluginsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This is the primary instruction manual for an agent working within the
ancplua-claude-plugins monorepo. It defines the mandatory conventions, architectural patterns,
and workflows required to contribute safely and effectively.
Use this skill when:
publishing.md guide to scaffold correctly.conventions.md to ensure you don't break architecture.testing.md to verify JSON syntax, permissions, and paths.testing.md.| Resource | Description | |----------|-------------| | Conventions | Critical rules, naming, directory layout, Git flow | | Publishing | Step-by-step guide to create and release plugins | | Testing | Validation commands and debugging steps |
| Topic | Link | |-------|------| | Plugins | code.claude.com/docs/en/plugins | | Skills | code.claude.com/docs/en/skills | | Hooks | code.claude.com/docs/en/hooks | | Marketplaces | code.claude.com/docs/en/plugin-marketplaces |
Validate everything:
./tooling/scripts/local-validate.sh
Check marketplace sync:
./tooling/scripts/sync-marketplace.sh
Validate single plugin:
claude plugin validate plugins/<plugin-name>
ancplua-claude-plugins/
├── plugins/ # Individual plugins live here
│ └── <plugin-name>/
│ ├── .claude-plugin/plugin.json
│ ├── skills/
│ ├── commands/
│ ├── agents/
│ ├── hooks/
│ └── README.md
├── agents/ # Repo-level Agent SDK experiments
├── skills/ # Repo-level shared skills (like this one)
├── .claude-plugin/ # Marketplace manifest
├── tooling/ # Validation scripts, templates
└── docs/ # Architecture, specs, ADRs
development
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about charts component, collection view, image view, web view, color well, image well, activity view, lockup, data visualization, content display, displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says how should I display charts, what's the best way to show images, should I use a web view, how do I build a grid of items, what component shows media, or how do I present a share sheet. Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.
tools
Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.
testing
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
tools
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.