Context & Token Efficiency
Shorter instructions leave room for the task. These examples do not claim a token-savings percentage. Load the file that matches the task, and leave the rest out.
Project map
UI implementation rules are in Standards & Best Practices. Agent workflows are in Skills & Workflows.
Focused context
AGENTS.md contains every button rule, every token, and every component API.
AGENTS.md names the project, the Next.js version, and the paths of scoped rules and skills.
Codex stops at its configured instruction size. A short root file leaves room for a nested file when a task is inside one folder.One always-on rule mixes UI tokens, authorization, and rendering advice into every prompt.
Three skills each have a name and description. The longer note stays in references/ and is read when that subject is in the task.
Cursor, Codex, and OpenCode can show the description first and load the body later.The prompt tells the agent to read node_modules/next/dist/docs/ and call /_next/mcp.
The prompt says this install is Next.js 15.5.27 and those paths are not present.
An agent that opens a missing path spends the turn on a file that this version does not ship.A generated .cursor/mcp.json enables GitHub, filesystem, and a browser with a copied token.
The generator writes a review note under examples/ and does not create .cursor/mcp.json.
An enabled server is a permission. A note can be read without granting that permission.Reusable prompts
Each prompt is generated from the published rules for one component or one UI guideline. Proposed CSC standards are not approved policy, and the prompt does not claim a WCAG audit.
Loading prompts…