Your AI Knows Forge Before You Start

Every AI session starts from zero. You describe your setup, correct the first three guesses, and get somewhere useful twenty minutes later. The next session starts over.

The gap is not the AI. The gap is that the AI does not know your system.

Forge ships with the manual already written. Four skill files, one directory. Each one is written for AI agents to load, not for humans to read. Copy what fits your setup and the AI arrives informed.

For developers building with Forge

One file covers everything needed to work with Forge correctly: how content moves through its lifecycle, what actions are available at each stage, permissions, and the things that are easy to get subtly wrong. Add it to a project and every session starts with the right knowledge already in place.

For the team managing content

The operator skill turns Claude.ai into a content management interface for your site. It defines what the AI can do and how it speaks. The voice is specified so the AI sounds like a capable colleague, not a help desk. The person running the site does not need to understand the system underneath. They tell the AI what they want and the AI handles it.

For anyone designing a new page

Two design skills guide the process of building a new page layout: one for developers working from an existing content structure, one for non-technical users describing what a page should look like in plain terms. Both produce a structured brief that any AI design tool can turn into ready-to-use HTML and CSS.

You own all four files. They live in the public repository. Read them, edit them, extend them. No black box. No intermediary platform. Your AI understands your site the way you want it to.

The technical details are in the devlog: forge-cms.dev/devlog/forge-skill-public.