Create professional, dark-themed architecture diagrams as standalone HTML files with SVG graphics. Use when the user asks for system architecture diagrams, infrastructure diagrams, cloud architecture visualizations, security diagrams, network topology diagrams, or any technical diagram showing system components and…
A project-documentation tool that reads an existing codebase and produces a structured specification, or SPEC, describing what it does and how it is built.
Graph engineering for parallel task execution: convert a task, PRD, SPEC, or issue set into a dependency graph (DAG), layer it into supersteps, then implement each independent node concurrently with subagents — each node runs /goal → /review-it → /ship-it in an isolated git worktree, with a fan-in barrier between…
A project-analysis tool that creates UML diagrams, architecture diagrams, and flowcharts from a codebase. UML is a standard way to draw software structure and behavior.
Automated issue loop with checkpoint/resume: fetch open GitHub issues → dependency-aware topological sort → implement each issue end-to-end → review with /review-it → document with /note-it → ship with /ship-it → repeat. Persists state to .loop-state.json for crash recovery. Triggers on: loop-it, loop issues, auto…
A note-taking step for recording how a feature was implemented compared with its written requirements. It saves design choices, differences, tradeoffs, and unanswered questions in an HTML file.
A process for turning a PRD, or Product Requirements Document describing what to build, into a technical specification describing how to build it. The result covers architecture, APIs, data, errors, and implementation agreements.
Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. After PRD is confirmed, use /prd-to-spec (optional) for technical design, then /to-issues to create implementable tickets. Triggers on: create a prd, write prd for, plan…
Detect software architecture bad smells, algorithmic complexity hotspots, and anti-patterns in a codebase. Produces a detailed markdown report identifying violations of architectural principles, design patterns, code quality, and performance complexity. Triggers on: smell, code smell, architecture smell, find…
A design document made from a PRD, or product requirements document, explaining how a software change could be built and why that approach was chosen. It follows the structure of official Go design proposals.
Connect to remote ACP server and execute commands via imclaw-cli.
★not rated 50 6mo agoC19 tokens
originalMIT
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: