Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a…
Write and fix Claude Code Prompts — skills, agents, commands, hooks, rules files, Claude.md, and plugin distribution. TRIGGER when the task says "cc"/"claude code"/"claude-code", or asks to build, edit, test, or share a skill/agent/hook/command, tune a description's triggering, write or prune a Claude.md, or cut…
Autonomous async Execution. The Architect hands off and walks away; the Agent drives the Task to done — makes every Architectural call by tracing the code and finding every option with /discover, executes through /delegate, verifies from each implementing Subagent's Evidence (they exercise their own flows, real…
Mandatory contract for every commit. The classifier names it when it authorizes a commit — it injects "Skills to execute: /commit" whenever the Architect asks to commit ("/commit", "commit this", "create a commit"). Holds the whole commit job: commit your own changes, write the message, commit, verify, then suggest…
Process for changes with a large blast radius — files with many callers or repo-p95 complexity, and actions that are destructive, hard to reverse, or visible outside the repo. TRIGGER before editing a file whose enrichment context shows callers ≥ 20 or complexity at the repo p95, and before any delete, force-push…
Run N independent architect Agents debating Architectural options through rounds. TRIGGER when the Architect wants multiple competing Solutions evaluated, when 3+ distinct approaches need comparison, or when the Prompt says "debate", "competing solutions", "run architects", "architecture debate", or /debate [count]…
Framework for dispatching one-shot Subagents that complete a Task and return. Covers Prompting (WHY -> WHAT -> HOW), the Story/Business/Goal/Verification/Process Prompt Template, and Evidence directories. TRIGGER when dispatching or resuming Subagents, when Orchestration needs the dispatch Prompt Template, or when the…
TRIGGER when building UI components, styling pages, or making visual/interaction Decisions. Guides design thinking, anti-patterns, CSS Architecture, and responsive patterns.
Build or sharpen a project's Domain.md and Decisions. Use when the Architect wants to pin down project language, record a Decision, or when another Skill needs to change Domain.md.
Mandatory contract for every executing-state turn. The classifier names it when the Architect types /execute, and every 30 turns after that while the session is executing. Implements the work the Architect approved; when that work needs an Architectural change, stop and escalate instead of deciding. TRIGGER on every…
Create or update GitHub issues. Writes the durable context an Agent cannot rediscover — the Problem, the WHY, the systems it crosses, the impact — and leaves the tactical HOW to the Agent that picks it up. Use when the Architect says "create an issue", "file an issue", "gh issue", "update the issue", or wants to turn…
Run N identical parallel Subagents on the same Task for independent Verification. Use when the Architect wants consensus through redundancy — multiple Subagents independently analyze, review, or test the same thing, then the combined returns are triaged with /triage. Invocation /independent-review [count] "task".
Interview the Architect to plan complex Architectural work before any code is written. Use when the Architect asks for an interview, or a Plan or Proposal needs his Decisions before Execution.
An Agent merges two branches one file at a time and checks each file against its two parents, so both sides' code survives while one side's feature stops working and no file-level check sees it. This Skill merges the branches and proves every behaviour each side committed still runs afterward. TRIGGER when merging two…
Transform Shaping output into a concrete Modeling artifact — database schema, User experience, and Architecture. TRIGGER between Shaping and Slicing, or when the Architect asks to model an existing system before Execution.
Name a code identifier, or review the names code already has — variable, function, class, file, folder, database column, route, CSS class, enum case, attribute. TRIGGER when introducing or changing an identifier, on /naming, "rename", "what should I call", "naming ideas", or "review the naming". DO NOT TRIGGER when…
The orchestrate mode's contract. You own the Architecture and spend your whole capacity on it — Subagents make every change, and you validate what they return with read-only checks. TRIGGER when the session enters orchestrate mode, on the /orchestrate command, and when orchestrate mode is re-injected after compaction.…
Keep engineering boring and complete. TRIGGER when the Architect says KISS, pragmatic, don't overengineer, ship it, keep it simple, or asks for a pragmatic read on a Proposal, Plan, code review, or Architectural Decision. DO NOT TRIGGER when the Architect asks for maximum rigor over shipping pressure.
Present information to the Architect so he can act on it. TRIGGER on every reply that carries a Decision, a finding, or an Architectural discussion, and on /present. DO NOT TRIGGER for drawing one diagram; that is /show-me.
★not rated 22
changed 1mo agoA52 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: