Skills & Rules

ApiHug Skills documents the part of the AI workflow that is owned by the ApiHug product surface: the rules, the contract-first delivery flow, and the core skills that operate inside those boundaries.

What It Is

This section explains:

• the framework rules that define acceptable ApiHug design and implementation
• the contract-first workflow used to move from proto to delivery
• the core execution and review skills used in that workflow

It is not a mirror of the entire BMAD catalog. It focuses on the pieces that directly affect ApiHug projects.

Why It Matters

AI workflows are only useful when the boundaries are explicit. ApiHug Skills gives agents and developers a shared operating model:

• proto is the source of truth
• generated outputs stay generated
• handwritten code stays in writable layers
• review follows framework-specific rules, not generic style advice

How It Fits

ApiHug borrows the planning and execution mindset from BMAD, then narrows it to the ApiHug stack:

• protobuf-first API and domain design
• generated backend and frontend boundaries
• rule-driven review for contracts and implementation

That is why the workflow pages and rule pages belong together. The broader ApiHug Skills repository may include more material, but this docs area stays focused on the surfaces that shape ApiHug delivery directly.

Official references for this overview:

• github.com/apihug/skills
• skills/spring-extension
• skills/rules

Next Step

Read the pages in this order:

1. Workflow
2. Rules
3. Create Story
4. Dev Story
5. Proto Review
6. Implementation Review