Guides system design decisions using docs/ARCHITECTURE.md and related docs. Use for cross-service flows, module boundaries, deployment, or when adding features that touch frontend, API, database, or external integrations.
Applies BMAD-style agent workflow: break down goals, model requirements, analyze risks, and deliver in small verifiable steps. Use when planning features, writing specs, or structuring multi-phase implementation.
Code quality bar for implementation work: linting, formatting, tests, and test coverage for new features and bug fixes. Use when frontend-developer or backend-developer (or PM) delegates or reviews implementation.
Orients agents to this repository: product goals, stack, docs index, UI language, and layout. Read this first for any task in this repository. Fill in the placeholders when adopting this template in a new project.
Security review checklist: auth, secrets, API boundaries, data handling, and infra. Use with security-reviewer subagent after architect (design) and after QA pass (implementation).
SEO, social sharing metadata, sitemap/robots, heading/keyword structure, analytics attribution (gclid, utm), and Lighthouse performance — primarily public marketing surfaces. Use when building or reviewing metadata or analytics hooks.
TypeScript conventions: strict mode, ESLint, explicit types, node: imports, string enums, complexity limits, and ESM readiness. Use when writing or reviewing TypeScript anywhere in the repository.
UX/UI usability checklist: user flows, forms, wireframe alignment, accessibility, and mobile. Use with ux-reviewer subagent after QA pass on user-facing features.
Visual design system, brand tokens, and SVG illustration. Defines colors, illustration style, and produces optimized SVG assets for marketing surfaces. Use with visual-designer subagent when illustrations, brand refresh, or OG visuals are needed.
System architect. Use proactively when designing cross-cutting features, API or schema changes, auth flows, or recording technical decisions before FE/BE implementation.
Requirements and process analyst. Use proactively when a new requirement arrives, scope is unclear, or user stories and process mapping are needed before product shaping.
Product owner for scope and acceptance criteria. Use proactively when shaping features, prioritizing backlog items, or validating that work fits current boundaries before architecture or implementation.
Security reviewer. Use after architect completes design review, and again after QA passes to review implemented code and infra. Works with architect on design refinements; sends implementation back for rework when security issues are found.
UX/UI reviewer. Use after QA passes on user-facing features to validate usability, visual clarity, copy presentation, accessibility, and alignment with wireframes/design. Routes rework to frontend or marketing.
Visual designer for brand system and SVG illustrations. Use when landing illustrations, OG images, logo/icon work, or design-system updates are needed.
★not rated 3▲
+1 2mo agoA32 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: