Your AI does not know Forge. The first time you open a project and ask it to wire a new module, it guesses. It gets the struct tags wrong, it invents options that do not exist, it forgets that archived items cannot be reverted. Then you correct it, and the next session starts from zero again.
We wrote down everything an AI agent needs to know about Forge and put it in a file. We have been using it internally for months. It is called forge.md and it is now in the skills/ directory of the Forge repository.
What is in it
The complete working reference for building with Forge: how to define a content type, how to wire a module, routing variants, the signal bus, every MCP tool with its required role, the upload token flow, forge-social, and forge-agent. The things that are easy to get subtly wrong are called out explicitly.
Add it to your project and your AI knows the API before you type your first message.
.claude/skills/forge.mdFour skills now ship with Forge
forge.md joins three skills we released earlier this week:
forge-design.md: generatesforge-pattern.mdfrom your Go struct for AI-assisted page designforge-design-assistant.md: guides non-technical users through design intent via conversationforge-operator.md: Claude.ai project instructions for content operators managing a live site
All four are in skills/ with a README. Copy what fits your setup.
The full design workflow guide is at forge-cms.dev/docs/ai-design.
Read the full story at forge-cms.dev/solved/forge-ships-the-manual.