brabos-ai
Organization📋 The Spec-Driven Development framework. Define the what, AI handles the how.
Categories
Indexed Skills (54)
add-skill-creator
Use when creating, updating, or improving agent skills.
add-feature-readback
Use when a feature's docs are closed and you need a cold reader to say back what they understood before anyone builds — catches docs that pass every review and still make the reader build the wrong thing.
add-qa-migration
Use when a project already runs a QA/test flow (Cypress, Jest, Vitest, custom) and wants to adopt the code-addiction QA pipeline instead of starting over — defines the autonomous dogfooding sequence (add.new → add.plan → add.build → add.review) and its checkpoints. Consumed by /add.qa-setup when migration is detected and confirmed.
add-gitnexus
Use when a task needs structural/relational code navigation — call graph, references, blast-radius, trace flows, safe refactors — and the GitNexus plugin is enabled. Routes intent to the native gitnexus-* skills.
add-architecture-discovery
Use when documenting project architecture — generates Technical Spec section in AGENTS.md
add-backend-development
Backend API architecture: Clean Architecture, SOLID, DTOs, Services, Repositories, RESTful — stack-agnostic.
add-code-review
Code review: IoC, RESTful, Contracts, Security (OWASP), Clean Architecture, SOLID.
add-commit
Use when committing changes mid-workflow with smart message generation. Triggers: commit, git commit, salvar progresso, checkpoint, conventional commits, push changes, commitar, fazer commit.
add-cross-sf-consistency
Use when judging contract consistency across an epic's subfeature plans — the five-dimension rubric, dedupe rules, and finding routes.
add-database-development
Database layer: entities, repos, migrations, multi-tenancy. Stack-agnostic. Consult AGENTS.md for ORM.
add-delivery-validation
Product validation: Requirements 100% implemented, prerequisites exist, acceptance criteria pass.
code-addiction-ecosystem
Consolidated view of the add-pro ecosystem - commands, skills, relationships and dependencies. Loaded by /add as source of truth.
add-feature-discovery
Use when analyzing codebase for a specific feature - creates/updates discovery.md with technical analysis, patterns, files mapping and caches for future sessions
add-feature-specification
Single writer of about.md — reads the brainstorm intent file, extracts the objective and the closed decisions without asking, and asks only what is still open. Loaded by /add.new.
add-final-report
Use at a command's closing step, in the internal layer — the seven blocks every finishing command reports in, the banned phrasings, and the self-check. Load at the last step, not at the first.
add-frontend-development
Frontend architecture: state, data fetching, components, forms, routing. Stack-agnostic.
add-health-check
Tech health check: documentation, security, architecture, data analysis. Use when user requests project audit, tech debt review, or health check.
add-id-convention
Use when allocating feature/hotfix/refactor/chore/docs/backlog IDs or creating branches — canonical `[NNNN][L]` format that the scripts (next-id.sh, get-branch-metadata.sh, build-setup.sh, done.sh) expect
add-knowledge-discovery
Use at the context/discovery step of add.plan, add.hotfix, add.new, add.diagnose, add.review, add.brainstorm — consult the delivery index, then the project wiki (and code knowledge graph), for minimal token cost before dispatching agents.
add-plan-review
Pre-delivery executability review for freshly generated about.md and plan.md — verdict (ok / fix-then-ok / blocked) plus required fixes, not questions. Load before dispatching plan-reviewer-agent, or when applying its rubric inline as a fallback.
add-project-scaffolding
Guide Node.js project scaffolding — Starter monolith, Scale monorepo, Starter→Scale migration.
add-qa
Use when running agent-judged QA validation (read-PNG by default; the playwright plugin adds live driving) — the Level C judge rubric, severity taxonomy, dual-judge (@ux-agent review ∥ @qa-agent) method, report schema/template, and the config.json/screens.json formats. Consumed by /add.review and both judges.
add-resource-path-convention
Use when writing commands or skills that reference other commands, skills, or scripts — ensures paths resolve correctly across all providers after installation
add-security-audit
Security audit: OWASP Top 10, multi-tenancy, injection, auth, XSS, dependencies.
add-subagent-driven-development
Use when executing implementation plans via dispatched subagents with code review between tasks.
add-tasks-checklist
Schema and tick rules for tasks.md across plan/build/review.
add-tdd
RED-GREEN-REFACTOR execution discipline for AI agents. Use when implementing any feature or bugfix that has (or should have) tests — forces a failing test confirmed for the right reason before any production code. Loaded by add.build.
add-token-efficiency
Use when creating commands, skills, or docs — defines generic compression patterns (minified JSON, abbreviations, glob patterns, single breaks). Load before any write where token density matters.
add-review-discipline
Use when a command dispatches a reviewer, a cold reader or the prompt reviewer over a document or a delivery — how many times each runs, why none of them writes a file, and the rule that a finding is judged before it is applied.
add-agents-md-style
Use when generating or updating the project's AGENTS.md — migrates any legacy context file into it first, then defines what belongs vs. what stays in skills/docs, format rules (JSON for data, markdown for rules/instructions), and line budget. Load before any AGENTS.md write.
add-delivery-mode
Use when a pipeline command reaches a stop or its closing handoff — the two delivery modes and where each is carried, which stops wait in each mode, how one command hands off to the next, and where the automatic path ends.
add-ux-design
Use when building, styling, or theming UI components, pages, layouts, dashboards, charts, tables, or forms for SaaS products.
add-wiki-maintenance
Use for incremental project-wiki updates — loaded by /add.wiki update (manual drift) and add.done STEP 4.9 (pre-merge, automatic). Diff-driven surgical edits only, never full rewrites.
add-artefact-graph
Use when a command, skill or agent needs to ask what an artefact relates to — resolving a stated question to the verb that answers it, the eleven verbs, the two interfaces that answer them identically, the case of an agent with no route at all, and the standing list of what the graph still cannot see.
add-build-ledger
Use when executing a plan's F-blocks — the build ledger, the resume rule, one commit per F-block, the ruling format, and the four hard stops. Load before the first F-block of any planned build.
add-doc-schemas
Source of truth for ADD doc rules, depth floors, IDs, refs, validation gate. Load before any doc write.
add-backlog
Use when something should be done later but not now — record it as a ticket on the project backlog, or read, reprioritise, comment on and close what is already there. Works mid-flow, inside another command's run, without derailing it. Triggers: backlog, ticket, anota isso pra depois, note this for later, record for later, not now, todo, fica pra depois, what's on the backlog, list the backlog, search the backlog, prioritise, drop this ticket.
add-framework--brainstorm
Use when an idea for the framework itself needs shaping before any plan — explores it with the user, classifies it spike, bounded or architectural, writes the design and intent files, and ends on one approval that can start the rest of the internal pipeline. First stage of brainstorm → plan → build → done.
add-framework-development
Internal skill for developing ADD framework artefacts (commands, skills, agents, scripts). Use when add-framework--plan analyzes viability of new framework features, when add-framework--build implements framework artefacts, or when creating/modifying commands, skills, or agents. Always use this skill before proposing or implementing changes to the framework itself.
add-framework-internal-layer
Use when an F-block touches the internal layer — .claude/, scripts/, CLAUDE.md or the repo root. Coherence and dependency checks, the rename/remove sweep, and why the graph gates still apply.
add-framework-product-layer
Use when an F-block touches the product layer — framwork/.codeadd/, provider-map.json or cli/. Registration, build.js, the cli test suite and artefact structures.
add-plan-authoring
Use when writing or revising a plan document — file naming, F-block layer tags, the Produces/Consumes rule, the review dispatch and its verdicts, and Continue/List mode resolution.
building-commands
Use when designing command workflows or refactoring existing commands — applies prompting best practices to ensure agents execute intended logic instead of skipping steps or rationalizing. Use this skill whenever creating new commands, reviewing why a command skipped steps or executed out of order, fixing agent compliance issues, converting Phase-based commands to STEP-based, or when /add-framework--build or /add.build needs to generate a command. Also use when the user mentions "o agente pulou", "agent skipped", "command não funciona", or asks to improve prompt quality of any .md command file.
add-backend-architecture
Guides backend architecture decisions — over-engineering, folder structure, slices, layers, feature organization, where code goes.
add-claude-md-style
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 budget. Load before any CLAUDE.md write.
add-dev-environment-setup
Use when bash/git/jq/gh CLI are missing or VS Code terminal is not WSL — detects OS, diagnoses gaps, installs missing tools.
add-frontend-architecture
Frontend architecture consultant for project structure, folder organization, feature boundaries, and scaling decisions. Framework-aware (React, Vue, Angular). Use when user asks about frontend folder structure, "components folder is a mess", "where should this go", over-engineering, slices, feature folders, or starting/refactoring a frontend project. Guides decisions only — does not implement (use add-frontend-development) or design UI (use ux-design).
add-investigation
Use when investigating vague symptoms or information-flow bugs requiring differential diagnosis before fixes. Applies to hotfix triage, audit deep-dive, review follow-up. Consumed by add.diagnose.
add-plan-based-features
Use when adding plan-gated features, flags, limits, or validating plan access via IPlanService
add-product-discovery
Use when starting a new project — discovers founder profile and product blueprint, writes docs/owner.md + docs/product.md
add-setup-contract
Use when a state-materializing command starts — compare the receipt setup-shape to the shipped sidecar shape and route FIRST-RUN / CURRENT / STALE. Consumed by /add.qa-setup STEP 1.5 and STEP 12.
add-stripe
Use when user mentions Stripe, billing, subscriptions, plans, or payments - patterns for Stripe with price versioning and grandfathering
add-optimizing-git-workflow
Git global cfg setup — colors, performance, merge conflicts, aliases for new machines
add-test-specification
Generate contract test cases from feature requirements (RFs/RNs) and technical contracts. Use when add.plan needs to produce plan-test-spec.md mapping each requirement to testable cases before implementation.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.