Source of truth for ADD doc rules, depth floors, IDs, refs, validation gate. Load before any doc write.
Database layer: entities, repos, migrations, multi-tenancy. Stack-agnostic. Consult CLAUDE.md for ORM.
Git global cfg setup — colors, performance, merge conflicts, aliases for new machines
Backend API architecture: Clean Architecture, SOLID, DTOs, Services, Repositories, RESTful — stack-agnostic.
Use when generating or updating CLAUDE.md files — defines what belongs vs. what stays in skills/docs, format rules (JSON for data, markdown for rules/instructions), and line…
Create/update plan.md with sequenced tasks, file mapping, dependencies and S/M/L estimates
Use when analyzing codebase for a specific feature - creates/updates discovery.md with technical analysis, patterns, files mapping and caches for future sessions
Document feature requirements - creates/updates about.md with business rules, scope, decisions
Use when building, styling, or theming UI components, pages, layouts, dashboards, charts, tables, or forms for SaaS products.
Use when writing commands or skills that reference other commands, skills, or scripts — ensures paths resolve correctly across all providers after installation
Code review: IoC, RESTful, Contracts, Security (OWASP), Clean Architecture, SOLID.
Use when user mentions Stripe, billing, subscriptions, plans, or payments - patterns for Stripe with price versioning and grandfathering
Use when executing implementation plans via dispatched subagents with code review between tasks.
Use when creating commands, skills, or docs — defines generic compression patterns (minified JSON, abbreviations, glob patterns, single breaks).
Frontend architecture consultant for project structure, folder organization, feature boundaries, and scaling decisions. Framework-aware (React, Vue, Angular).
Tech health check: documentation, security, architecture, data analysis. Use when user requests project audit, tech debt review, or health check.
Use when documenting project architecture — generates Technical Spec section in CLAUDE.md
Use when starting a new project — discovers founder profile and product blueprint, writes docs/owner.md + docs/product.md
Use when adding plan-gated features, flags, limits, or validating plan access via IPlanService
Security audit: OWASP Top 10, multi-tenancy, injection, auth, XSS, dependencies.
Consolidated view of the add-pro ecosystem - commands, skills, relationships and dependencies. Loaded by /add as source of truth.
Frontend architecture: state, data fetching, components, forms, routing. Stack-agnostic.
Guide Node.js project scaffolding — Starter monolith, Scale monorepo, Starter→Scale migration.
Use when reviewing a just-written ADD doc as a fresh stakeholder — surfaces gaps, clarity, and scope questions.
Use when bash/git/jq/gh CLI are missing or VS Code terminal is not WSL — detects OS, diagnoses gaps, installs missing tools.
Product validation: Requirements 100% implemented, prerequisites exist, acceptance criteria pass.
Guides backend architecture decisions — over-engineering, folder structure, slices, layers, feature organization, where code goes.
Use when investigating vague symptoms or information-flow bugs requiring differential diagnosis before fixes. Applies to hotfix triage, audit deep-dive, review follow-up.
Use when committing changes mid-workflow with smart message generation. Triggers: commit, git commit, salvar progresso, checkpoint, conventional commits, push changes, commitar,…
Use when allocating feature/hotfix/refactor/chore/docs IDs or creating branches — canonical `[NNNN][L]` format that the scripts (next-id.sh, get-branch-metadata.sh, done.sh) expect
Internal skill for developing ADD framework artefacts (commands, skills, agents, scripts). Use when add.plan analyzes viability of new framework features, when add.build…
Use when creating, updating, or improving agent skills.
Schema and tick rules for tasks.md across plan/build/review.