AGENT → COMMAND

There was a chat window here. Now there is a command.

The hosted agent has been retired. Asking for a component is now something you do from the editor you already work in, with the same execution cycle and one command instead of another tab to keep open. It builds, and it also plans, answers, reviews and edits.

Ask for a token

Access is invite-only while the knowledge base settles.

THE COMMAND, END TO END

01
Install the skill
Writes one skill file and a gitignored config into your project. No dependency is added, and nothing else is touched.
npx create-frontendag --token=<token>
02
Ask, in plain language
Your editor session collects the assembled context and answers on your own subscription. Open with a verb — think, structure, ask, review — to get a brief, a page plan, an answer or findings instead of a file.
/frontendag "a combobox for picking a country"
03
Grade what came back
Syntax, accessibility, Tailwind and motion rules. It also records what the file was built on, so a follow-up keeps that grounding.
frontendag check components/ui/combobox.tsx

Install once per project. After that, a request in plain language is the whole interface.

SIX THINGS IT CAN BE ASKED

buildthe default
One production-quality React file, checked before it lands.
a combobox for picking a country
think
A design brief first: the job, the states, one composition, the contract.
think a quantity stepper for a cart line
structure
A page broken into components, with what owns which state.
structure an account settings page
askinferred from a question
One answer, grounded in the same verified knowledge a build gets.
should this be a dialog or a drawer?
review
Findings on a component you already have, worst first.
review components/ui/pricing-card.tsx
iterateinferred after a build
The same file, changed only where you asked.
make it denser

One request, one verb. Every one of them is assembled from the same verified component knowledge, so a plan promises only what a build can deliver.

Runs where your code is

The component is written in the session that already has your project open, so it lands against your real imports and conventions.

No API key to hand over

Generation happens on your own subscription. Nothing here holds a key on your behalf and nothing meters your requests.

Same verified knowledge

The specs, guidance and design anchors behind a request are assembled and served from here, exactly as the hosted agent used them.

WHAT STANDS BEHIND ONE REQUEST

Verified

component guidance grounded in supported APIs

Project-aware

code checked against your types and conventions

Accessible

interaction requirements kept in scope throughout

Reviewed

compiled output checked again after improvements

Focused by design. Each request draws on the component guidance and design standards it needs, keeping the result relevant to the brief.

Checked before delivery. Generated code is validated against the project and supported component APIs, then reviewed again after improvements.

Still a brief in, validated code out.

Only the surface changed. See the execution cycle.