webdev-agent-kit
AGENTS.md7 starsChanged 21 days agoApache-2.0View on GitHub
Route work to portable policy, applicable profiles, verified project facts and the matching skill. Load detailed rules only when relevant. Bundle paths are rooted at the installed bundle: .agents for project targets or the native plugin root. Generated dist/** output is never source truth. Only approved project-onboarding-adapter work may replace the host-root instruction pointer. Resolve conflicts through common/policy-precedence.md: system, client security, and sandbox restrictions; current user request; confirmed scope and approvals; host-project instructions; verified project/** facts; selected skill; active profile;…
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,774 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository23 other files it gives its agents.
- agent-rules-skill-authorSkill
- agent-self-improvementSkill
- design-screenshot-specSkill
- execution-plan-managerSkill
- frontend-architecture-plannerSkill
- frontend-bugfix-debuggerSkill
- frontend-design-directorSkill
- frontend-design-intelligenceSkill
- frontend-layout-implementerSkill
- frontend-linter-managerSkill
- frontend-prototype-explorerSkill
- frontend-quality-reviewerSkill
- frontend-refactor-surgeonSkill
- frontend-visual-qaSkill
- goal-plannerSkill
- greenfield-project-builderSkill
- loop-workflow-plannerSkill
- mcp-toolchain-managerSkill
- pattern-library-managerSkill
- project-context-adapterSkill
- project-onboarding-adapterSkill
- webdev-feedbackSkill
- webdev-kit-updaterSkill
The file
We split this AGENTS.md into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 97
Run relevant existing checks, bound retries, change failed approaches and report blocked checks.
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
WebDev Agent Kit Runtime Policy
Purpose
Route work to portable policy, applicable profiles, verified project facts and the matching skill. Load detailed rules only when relevant.
Bundle paths are rooted at the installed bundle: .agents for project targets or the native plugin root. Generated dist/** output is never source truth. Only approved project-onboarding-adapter work may replace the host-root instruction pointer.
Precedence And Approvals
Resolve conflicts through common/policy-precedence.md: system, client security, and sandbox restrictions; current user request; confirmed scope and approvals; host-project instructions; verified project/** facts; selected skill; active profile; generic defaults.
Require explicit approval before installing packages or tools, changing configuration outside scope, adding test infrastructure, replacing project instructions, performing irreversible actions, or contacting external people or systems. New tests require an explicit current request; relevant existing-test maintenance follows common/test-policy.md.
README.md may be read only when relevant under common/readme-policy.md, never as sole technical evidence or runtime authority. Reading never authorizes editing. Do not create or change an existing README unless the current user explicitly requests that README change.
Context Loading And Workflow Scale
In Codex, when a local model-routing profile exists, consult
common/codex-model-routing-policy.md before broad reading or delegation.
In Claude Code, consult common/claude-agent-routing-policy.md when delegation
is relevant; use verified native roles and preserve single-agent fallback.
Classify before reading broadly:
Fast Lookup: narrow question, file location, or code explanation; search and read only decisive snippets.Lightweight Workflow: one obvious, low-risk local change; avoid planning and toolchain overhead.Standard Workflow: multi-file work, unclear root cause, refactor boundary, or bounded verification.Deep Workflow: new project, architecture or migration, broad redesign, repeated failure, or resumable work.
Load in this order, stopping when the next safe action is clear:
common/core/runtime-core-policy.md.- The matching
adapters/**file only when client behavior affects the task. profiles/react-typescript/PROFILE.mdonly when repository evidence activates it; otherwise usecommon/skill-applicability-policy.mdand local conventions.- Verified project instructions and only the affected
project/**facts. - The smallest matching
skills/**/SKILL.mdand only references it requires for the active slice.
Load narrowly. Use common/prompt-intent-routing-rules.md for unclear intent.
tool-capabilities-manifest.json defines needs; callable tools, not names or
configuration, establish availability.
Skill Discovery
For explicit WebDev role selection, use common/webdev-role-selection.md.
Select skills by name and description; explicit invocation is optional. Each SKILL.md owns triggers, exclusions, workflow and validation. Keep lightweight work free of planning, design, MCP, loop, review and onboarding overhead unless scope escalates.
Compact Skill Index
- Plan:
goal-plannerdefines goals;execution-plan-managermanages slices;loop-workflow-plannergoverns cycles. - Design:
design-screenshot-specconverts supplied visual evidence;frontend-design-intelligencegrounds product patterns;frontend-design-directorsets visual direction;frontend-prototype-explorertests unresolved UI or state decisions. - Build:
frontend-architecture-plannerdefines ownership;greenfield-project-builderplans a first vertical slice;frontend-layout-implementerimplements an approved spec in its target stack. - Quality:
frontend-bugfix-debuggerfixes defects;frontend-refactor-surgeonpreserves behavior;frontend-linter-managerruns or repairs scoped lint;frontend-visual-qachecks rendering;frontend-quality-reviewerreviews independently. - Context and tooling:
project-onboarding-adapterinitializes pointers and local facts;project-context-adapterrefreshes them;mcp-toolchain-managermaps tool capabilities;pattern-library-managermaintains reusable patterns;agent-rules-skill-authormaintains this bundle. - Learning:
agent-self-improvementsaves explicitly requested experience to the learning database, including natural-language requests. Never substitute project-rule edits. - Feedback:
webdev-feedbackfiles requested issues. Updates:webdev-kit-updaterpreserves local changes.
Change Boundaries
Preserve unrelated user work. Reuse verified project architecture, components, styles, tokens, data boundaries, and commands. Make the smallest coherent change; keep profile defaults subordinate to local evidence. Do not add dependencies, scaffolds, migrations, styling systems, UI libraries, global tokens, broad cleanup, or generated infrastructure outside approved scope.
Use targeted source or platform documentation only when current facts affect the decision. For active OpenAI API, ChatGPT Apps SDK, or Codex questions, route openai_platform_docs to the callable official OpenAI Developer Docs MCP first, then its official web fallback. Skip that lookup for generic frontend or local repository facts. Follow declared capability fallbacks and report the confidence impact when required evidence is unavailable. Keep durable host facts local in project/**.
Verification And Output
Omit routine model/version/effort announcements; include only on request or for model diagnostics. Preserve verified trace/evaluation metadata.
Run relevant existing checks, bound retries, change failed approaches and report blocked checks. Never claim tools, screenshots or results without evidence.
Apply common/token-economy-rules.md. Return only facts that affect understanding, confidence, or the next action. For changed work, default to Changed, Verified, and Blocked when applicable; lightweight final answers stay within 180 words. Omit request echo, skill names, workflow narration, empty sections, raw logs, and irrelevant skipped-work notes; never hide errors, unknowns, blocked verification, or approval needs.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

