An index of coding commands for a staged workflow, from interviewing and planning through implementation, testing, review, and debugging. It also lists commands for project analysis, automation, quality checks, and team work.
A coding assistant persona for a full-stack developer, meaning someone who works across both the visible app and its server-side code. It supports test-driven development, or TDD, where tests are written before implementation and then used to guide changes.
A debugging assistant for analysing error messages, stack traces, logs, inputs, and environments. A stack trace is the list of code calls showing how an error was reached.
A Chinese-language requirements interview assistant that asks detailed questions about a proposed software project. It helps define the problem, boundaries, technical limits, and first usable version.
A planning command that breaks a specification into small tasks, maps their dependencies, identifies risks, sets priorities, and defines acceptance checks.
A code-review command whose reviewer checks whether changes work correctly, stay secure, remain maintainable, perform acceptably, and have suitable tests.
A command that runs a debate between a product manager focused on user and business value and an architect focused on technical design and feasibility.
An automatic task-running command with five stages: expanding the request, planning the work, executing it, checking quality, and validating the result. It repeats the work cycle when the goal has not yet been reached.
A code-review command that asks four separate reviewers to inspect security, performance, maintainability, and architecture. It combines their findings into one report ordered by severity.
A command that repeatedly has one agent improve a web page while another agent scores it against measurable criteria. It uses agent-browser to inspect the page.
A command that assigns GitHub Issue labels by looking for keywords in the issue title and description. It uses GitHub CLI to apply labels for priority, issue type, complexity, and affected component.
A command for coordinating work across multiple isolated sessions or containers. It can run tasks in parallel, one after another, or according to a dependency graph, where a task waits for the tasks it depends on.
A command that reviews project specification documents from both a business and a software-architecture perspective, then improves the documents. It uses separate reviewers for business concerns and technical concerns, followed by a product manager who combines their feedback.
An agent that diagnoses software bugs, finds their underlying cause, makes a focused code fix, and checks it with a regression test.
★not rated 4 4mo agoA35 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: