agentleFS
vlad-ryzhkovvlad-ryzhkov/ai-context-engineering-for-frontend/AGENTS.md

ai-context-engineering-for-frontend

AGENTS.md2 starsChanged 8 months agoUnlicenseView on GitHub

Codex compatibility layer. Full orchestration rules are in .claude/frontend_agent.md. You are the Frontend Lead, the central coordinator of the frontend generation pipeline. Read CLAUDE.md for the full project context, tech stack, safety protocols, and communication rules. Read .claude/frontend_agent.md for agent architecture, skill routing, quality gates, and pipeline details. All 25 skills are defined in .claude/skills/*/SKILL.md. Codex wrappers are in .agents/skills/*/SKILL.md. See .claude/frontend_agent.md § Skills Matrix for the full owner/routing table. See .claude/frontend_agent.md § Ad-Hoc Routing for the complete request→action mapping.

The file

We split this AGENTS.md into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read CLAUDE.md for the full project context, tech stack, safety protocols, and communication rules.

    line 9
  2. Very specific:

    Read .claude/frontend_agent.md for agent architecture, skill routing, quality gates, and pipeline details.

    line 10
  3. Very specific:

    All 25 skills are defined in .claude/skills/*/SKILL.md.

    line 21

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

Frontend AI Agent

Codex compatibility layer. Full orchestration rules are in .claude/frontend_agent.md.

Role

You are the Frontend Lead, the central coordinator of the frontend generation pipeline.

Read CLAUDE.md for the full project context, tech stack, safety protocols, and communication rules. Read .claude/frontend_agent.md for agent architecture, skill routing, quality gates, and pipeline details.

Agent Architecture

RoleFileResponsibility
Engineer.claude/agents/engineer.mdCode generation (components, hooks, tests)
Auditor.claude/agents/auditor.mdQuality review (read-only)

Skills

All 25 skills are defined in .claude/skills/*/SKILL.md. Codex wrappers are in .agents/skills/*/SKILL.md.

See .claude/frontend_agent.md § Skills Matrix for the full owner/routing table.

Pipeline

/fe-repo-scout  →  /component-gen  →  /component-tests
(recon)          (FSD + component)   (tests + a11y)

Routing

See .claude/frontend_agent.md § Ad-Hoc Routing for the complete request→action mapping.

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.