What is Fireskills?

Fireskills is the spec-driven method that comes inside Nuxfire. You describe what you want in your IDE agent's chat; the agent follows a fixed flow (capture, refine, specify, prove, implement, document) and works from a set of technical specialists that already know this codebase.

Instead of loose prompts, every change goes through one normative file, quality gates and evidence. When code and documentation disagree, the code wins.

New here? Start with the Quick Start: it lists what to type in your IDE for each thing you may want to do.

Core pillars

1. One normative specification per slice

Every feature, fix or change lives in exactly one file: specs/<state>/<NNNN>-<slug>/spec.md. Requirements, Gherkin scenarios, tasks, checklists, test evidence and gates are all in it. There is no plan.md, tasks.md or research.md.

2. Three acts, three gates

• Act I, Define (Inbox, Backlog, Specify, Validate) ends with the Definition Gate.
• Act II, Design & Prove (Tasks, TDD/BDD) ends with the Plan Gate: tasks exist and the tests fail for the right reason (RED).
• Act III, Deliver (Implement, Documentator) ends with the Delivery Gate: tests green, types checked, evidence recorded, context documents current.

3. 38 technical specialists

Loaded by the agent before it touches code in their area:

• 15 Nuxfire stack specialists: Nuxt 4, @nuxt/ui v4, Nuxfire layers, tRPC v10, Drizzle, nuxt-authorization, OpenAuth.js, Pinia, Billing (Stripe and Paddle), Cloudflare Workers, SST 4, content and SEO (blog, docs, translations), web performance, search engine requirements (Google, Bing) and copywriting. Each has a references/nuxfire-*.md with what exists in the code and what does not.
• 23 engineering specialists: TypeScript, PostgreSQL, Tailwind, architecture, API design, security, performance, observability, debugging, code review, accessibility, UX/UI, versioning, git and more.

4. A small CLI for the mechanical parts

bun run fireskill (code in fireskills/cli/, Bun and TypeScript) moves specs between states, sets the effort score, validates a spec with a quick linter, shows progress, syncs milestones and manages lessons learned. See the CLI reference.

5. Persistent context in .fireskills/

PROJECT.md, STACK.md, RULES.md, DATABASE.md, INTERFACE.md, DESIGNSYSTEM.MD, PACKAGES.md, USER-PROFILE.md, and LESSONS.md/lessons.json. Agents read them before they ask you anything. See Project Context.

6. Safety around the database and irreversible actions

Server code runs on Cloudflare Workers via SST. The flow never deploys, deletes data or runs a destructive database command on its own; a guard script classifies commands (drizzle-kit push --force, db:wipe, DROP, TRUNCATE and others are refused even with your approval), and tests that reach PostgreSQL need a separate test database.

Where to go next

• Quick Start: what to type in the IDE, by goal.
• Workflow & Governance: how the agent asks and hands off.
• The Three Acts and Quality Gates.
• Skills Catalog and Technical Specialists.
• CLI Reference.