Comprehensive security analysis against OWASP Top 10. If given code files — audits code for vulnerabilities. If given tech-spec — reviews security decisions in architecture. Orchestrator specifies what to check and provides file paths.
Verifies factual claims in tech-spec or tasks against actual codebase. Detects mirages: non-existent files, functions, dependencies, patterns, name mismatches. Orchestrator specifies feature path. Agent reads documents and checks every claim in code. Use during tech-spec validation (phase 2, step 5) and task…
Creates task files from tech-spec Implementation Tasks section. Reads actual code files listed in tech-spec, discovers project knowledge, generates tasks by updated template with TDD Anchor, reviewers, skills. Use when: generating task/.md files after tech-spec is approved, during /decompose-tech-spec or manual task…
Validates task files against task template and task-creator rules. Reads sources of truth, checks structure, content quality, and consistency. Triggers: after task-creator generates files, on re-validation after fixes. Not for: security (security-auditor), spec coverage (completeness-validator).
Prescriptive test quality analysis: finds problems and provides concrete fixes. Analyzes written test code, test strategy from tech-spec, or both. Orchestrator specifies what to check and provides file paths.
Validates user-spec for adequacy and feasibility — not document quality, but whether the proposed solution is reasonable, buildable with current stack, right-sized, and not over/under-engineered. Does not check document quality (template compliance, section completeness, acceptance criteria wording) — that is…
Use when you need information about this project's architecture, tech stack, coding patterns, data model, deployment setup, git workflow, or UX guidelines. Contains comprehensive project documentation including design decisions, technical specifications, and development standards.
A code-review method with a structured process, quality standards, and 11 areas for examining code. Code review means checking changes for correctness, maintainability, and related risks.
A coding workflow for planning changes, writing tests before or alongside code, and reviewing the result. TDD, or test-driven development, means using tests to guide the implementation.
A design tool that creates HTML/CSS pages and static SVG mockups from text descriptions using a project’s design system. It can choose among layout patterns, apply design tokens, use screenshots for iteration, and create a before-and-after collage after approval.
A design review process that turns feedback from a design session into documented lessons, principles, and a reusable description of the project's visual preferences.
A small style review that compares changed user-interface code with the project’s design tokens, which are shared values for colours, spacing, and other visual choices.
A work-session finalization process that compares documentation with recent Git changes, updates project knowledge, and can optionally archive a completed feature. Git is a system for tracking changes to code and related files.
A setup guide for preparing a new software project, including its folders, framework, Docker files, tests, and commit checks.
★not rated 1 4mo agoA78 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: