Development plugins that enforce standards and guide scoping and research
翻譯準備中
AI 摘要 · README
外掛Shell · PythonGitHub @camoa自行安裝營運者未確認
試用過了嗎? 點一下就好,不需要登入。
尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
安裝型專案無需部署網域也可驗證。個人儲存庫可透過 GitHub 登入驗證,組織儲存庫可使用上方的儲存庫驗證檔案。
正在載入完整 README。 以下為已儲存的摘錄。
A marketplace of Claude Code plugins built on one idea: AI is fast; these tools make the parts it likes to skip hard to skip. The gates enforce your standards, the guides keep the AI working from current best practice instead of stale training data, and you make every decision. The reasoning behind that is in PHILOSOPHY.md.
The flagship, aida, run on a single task:檢視完整 README ↗A marketplace of Claude Code plugins built on one idea: AI is fast; these tools make the parts it likes to skip hard to skip. The gates enforce your standards, the guides keep the AI working from current best practice instead of stale training data, and you make every decision. The reasoning behind that is in PHILOSOPHY.md.
The flagship, aida, run on a single task:
$ /aida:scope rss_feed # you write the contract: goal, non-goals, the criteria that prove it
$ /aida:research rss_feed # finds drupal/views_rss already covers most of it: reuse, do not rebuild
$ /aida:design rss_feed # work orders with owned files, a diff budget, and tests for code with logic
$ /aida:implement rss_feed # for code with logic: tests first, frozen, then the code against them
$ /aida:review rss_feed # every criterion answered, the checks run from the stack's recipe
$ /aida:completion rss_feed # closes on the verdict, writes the pull request body from the records
It never picked your architecture for you. It just refused to skip the scope, the existing-solution check, the tests, or the review, and it left everything it did on disk, so a decision that later looks wrong is a file you open. That is the idea behind all of these plugins.
None of it is perfect. The AI still slips a step past us now and then, and when it does, that gap becomes the next gate we add. See PHILOSOPHY.md for the fuller picture.
# Add the marketplace
/plugin marketplace add https://github.com/camoa/claude-skills
# Install the plugins you want
/plugin install aida@camoa-skills # pulls dev-guides-navigator automatically
/plugin install dev-guides-navigator@camoa-skills
/plugin install claude-plugin-checks@camoa-skills
/plugin install code-quality-tools@camoa-skills
/plugin install code-paper-test@camoa-skills
/plugin install drupal-ai-contrib@camoa-skills
/plugin install drupal-htmx@camoa-skills
/plugin install brand-content-design@camoa-skills
Each plugin's README has its own requirements, worked examples, and a docs/usage.md. Versions and component counts live there and in each CHANGELOG.md, not here, so this page does not go stale.
The skills conform to the open agentskills.io standard and work in Cursor, Codex CLI, VS Code Copilot, Gemini CLI, Cline, OpenCode, and more. Commands, agents, and hooks are Claude-Code-specific by format but can be emulated. See PORTABILITY.md for the full guide and CURSOR.md for the highest-fidelity option.
aida: The AI jumps straight to code: it skips understanding the problem, misses a library that already exists, drifts from your standards, and forgets the tests. Runs any coding task through a contract, then research, design, implementation against frozen tests, review, and completion. The checks are scripts reading records, not the model judging its own work. Works on any stack (process recipes carry the framework specifics) and on Claude Code plugin work too. This is the flagship; version 6 of what was ai-dev-assistant.
dev-guides-navigator: The model writes code from whatever it remembered at training time, which is often out of date. Routes each task to the current best-practice guide from a catalog of 1200+ atomic decision guides, hash-cached so nothing is re-fetched. Required by aida; useful on its own.
claude-plugin-checks: Checking a Claude Code plugin means remembering which of five tools to run, and none of them opens the component files the manifest points at. One command that runs them all and prints what each said, plus three checks nothing else performs: the external component files, a file that contradicts itself, and leaked home paths or credentials.
code-quality-tools: Is this code actually safe and sound, or does it just run? TDD, SOLID, and DRY checks plus multi-layer security scanning (Semgrep, Trivy, Gitleaks, and more) for Drupal and Next.js. Version 5 of the flagship delegated its quality gates here; version 6 runs the tools from the stack's recipe instead.
code-paper-test: Does this code, skill, or config actually do what it claims, before you run it in anger? Mental-execution testing that traces logic line by line with concrete values, plus an adversarial test-team, to surface bugs, edge cases, and AI hallucinations. Part of the review method for plugin work.
drupal-ai-contrib: AI-assisted Drupal.org contributions get bounced for unverified claims and policy misses. Evidence-over-assertion gates that mirror the drupalci pipeline locally at CI strictness and check the AI-contribution policy, so a contribution passes only on a produced artifact, never an assertion.
drupal-htmx: Migrating Drupal AJAX to HTMX by hand is fiddly and easy to get wrong. HTMX patterns and an AJAX-to-HTMX migration path for Drupal 11.3+.
brand-content-design: Every deck, carousel, and one-pager drifts a little further from the brand. Branded presentations, carousels, infographics, and HTML pages generated from one shared brand and design system.
I started building what I called "frameworks" over a year before Claude officially released Skills. Same concept, different name. The idea came from frustration: I was tired of repeating the same instructions every conversation, so I asked AI to analyze our successful interactions and capture the recurring requirements and preferences as reusable project knowledge. That produced real work: 3 published Drupal contrib modules, 17+ blog articles, automated social campaigns, and phase-based editorial workflows. When Claude released Skills officially, I recognized what I had been building, and this repository translates those frameworks into proper Skills with tooling. More on the methodology: My Journey with AI Tools.
Conventions, plugin structure, and the review bar are in CONTRIBUTING.md and CODE_OF_CONDUCT.md. In short: CONVENTIONS.md at each plugin root (not a plugin-root CLAUDE.md, which Claude Code does not load), path-scoped .claude/rules/, version and model routing in frontmatter, and progressive disclosure (SKILL.md lean, detail in references/).
| Tool | Purpose | Install |
|---|---|---|
| Anthropic skill-creator | Official skill creator | /plugin install example-skills@anthropic-agent-skills |
| Superpowers | TDD skill development | /plugin marketplace add obra/superpowers-marketplace |
Built collaboratively by Carlos Ospina and Claude (Anthropic). The methodology, frameworks, and domain expertise came from Carlos; Claude contributed code generation, research synthesis, documentation structure, and pattern implementation. Patterns and insights drawn from:
MIT