fullstackhero ships agent-ready. The conventions, footguns, and step-by-step recipes that normally live in a senior engineer’s head are written down in a form AI coding tools read on demand — so an agent scaffolds a feature, adds a module, or writes a migration the same way you would, without breaking the architecture.
Two pieces make this work:
- AGENTS.md — the single, tool-neutral guide at the repo root. CLAUDE.md and GEMINI.md are thin bridges that import it, so every tool reads the same source of truth.
- .agents/ — a folder of rules (conventions, read on demand), skills (task recipes), and workflows (review/orchestration playbooks).
- 01/03
AGENTS.md & the .agents Folder
The canonical AGENTS.md guide, the CLAUDE.md/GEMINI.md bridges, the .agents folder structure, and the on-demand rule files that encode every convention.
- 02/03
Skills & Workflows
The catalog of .agents skills (task recipes like add-feature, add-module, create-migration) and workflows (review and orchestration playbooks) that ship…
- 03/03
Developing with Claude Code
A practical guide to building on fullstackhero with Claude Code — how it loads AGENTS.md, invokes skills, runs review workflows, and the build/test loop to follow.