agentleFS
ytvee-devytvee-dev/webdev-agent-kit/AGENTS.md

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;…

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
  1. Distinctive:

    Run relevant existing checks, bound retries, change failed approaches and report blocked checks.

    line 97

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

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:

  1. common/core/runtime-core-policy.md.
  2. The matching adapters/** file only when client behavior affects the task.
  3. profiles/react-typescript/PROFILE.md only when repository evidence activates it; otherwise use common/skill-applicability-policy.md and local conventions.
  4. Verified project instructions and only the affected project/** facts.
  5. The smallest matching skills/**/SKILL.md and 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-planner defines goals; execution-plan-manager manages slices; loop-workflow-planner governs cycles.
  • Design: design-screenshot-spec converts supplied visual evidence; frontend-design-intelligence grounds product patterns; frontend-design-director sets visual direction; frontend-prototype-explorer tests unresolved UI or state decisions.
  • Build: frontend-architecture-planner defines ownership; greenfield-project-builder plans a first vertical slice; frontend-layout-implementer implements an approved spec in its target stack.
  • Quality: frontend-bugfix-debugger fixes defects; frontend-refactor-surgeon preserves behavior; frontend-linter-manager runs or repairs scoped lint; frontend-visual-qa checks rendering; frontend-quality-reviewer reviews independently.
  • Context and tooling: project-onboarding-adapter initializes pointers and local facts; project-context-adapter refreshes them; mcp-toolchain-manager maps tool capabilities; pattern-library-manager maintains reusable patterns; agent-rules-skill-author maintains this bundle.
  • Learning: agent-self-improvement saves explicitly requested experience to the learning database, including natural-language requests. Never substitute project-rule edits.
  • Feedback: webdev-feedback files requested issues. Updates: webdev-kit-updater preserves 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.