AI prompts and generated files
Building a house-standards file for your project, and pointing every AI coding tool at it in one step.
FEWD Studio is built for a workflow where some of the code was written by a model. The AI Prompt tab in the project panel is the half of that which happens before the code.
The problem it solves
A model given no standards writes reasonable code that is not your reasonable
code — utility classes where you use BEM, hardcoded hex values where you have
tokens, a <div> where you wanted a <section>.
Correcting that after the fact, every time, is most of what makes AI-assisted work feel slower than it should.
Snippets
Sixteen buttons, each appending a block of house standards to your project’s
FEWD-PROMPT.md:
Architecture — BEM · Selectors · Components · Props · One source · No utilities · Component architecture Astro — Astro · Astro pages · Repo build · Flex pages Design — CSS tokens · Responsive · Animations · Semantics & A11y SEO — SEO · Astro SEO
Add the ones that match how you work. There is a free-text field for everything particular to this project.
They are cumulative and editable — the file is plain markdown in your project root, and Open file in panel opens it in a coding pane like anything else.
Generate AI files
One click writes AGENTS.md, CLAUDE.md and GEMINI.md at the project root,
each pointing at FEWD-PROMPT.md.
AGENTS.md is the cross-tool standard — Codex, Cursor, Copilot and opencode all
read it. CLAUDE.md and GEMINI.md are for the two that look for their own.
One set of standards, read by whichever tool you happen to be using, edited in one place.
A file that already has content is left alone. FEWD tells you which it skipped so you can add the reference by hand rather than having your own instructions silently replaced.
And afterwards
The other half of the workflow is what happens when the model gets something wrong: click the element, see the rule responsible, fix it.