agentleFS
int2t05int2t05/engineering-skills/AGENTS.md

engineering-skills

AGENTS.md3 starsChanged 28 days agoMITView on GitHub

Universal entry point for AI coding agents working with this skill pack — Claude Code, Codex, OpenCode, Cline, Continue, Cursor (agents mode), and any agent that reads AGENTS.md. Scope: This file orients agents using the engineering-skills pack. The reusable assets are the skills under skills/; this file routes work to them and loads the shared discipline. Skills organized by the software development lifecycle, including a meta router. Each skill is a folder skills/<phase>/<name>/SKILL.md with YAML frontmatter (name, description, optional disable-model-invocation)…

The file

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

5 rules. About 0 are common, 1 is distinctive, and 4 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.

  • 4

    Very specific

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

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

    Verify / References. Encyclopedic data lives in per-skill references/ (progressive disclosure).

    line 16
  2. Very specific:

    When a task arrives, identify the phase and reach for the matching skill.

    line 29
  3. Very specific:

    Every skill's ## When to use states a negative boundary (NOT for → the adjacent skill it isn't), so adjacent tasks route to the right skill …

    line 93
  4. Distinctive:

    Every skill is either model-invoked (default — the agent reaches for it autonomously on trigger match) or user-invoked (only fires when the …

    line 99
  5. Very specific:

    Every skill's ## References links the shared engineering principles (source-relative links.

    line 119

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

AGENTS.md

Universal entry point for AI coding agents working with this skill pack — Claude Code, Codex, OpenCode, Cline, Continue, Cursor (agents mode), and any agent that reads AGENTS.md.

Scope: This file orients agents using the engineering-skills pack. The reusable assets are the skills under skills/; this file routes work to them and loads the shared discipline.

What this pack is

Skills organized by the software development lifecycle, including a meta router. Each skill is a folder skills/<phase>/<name>/SKILL.md with YAML frontmatter (name, description, optional disable-model-invocation) and four sections: When to use / Steps / Verify / References. Encyclopedic data lives in per-skill references/ (progressive disclosure).

Read the engineering principles first

Once per session, unless these rules are already loaded, read references/engineering-principles.md (repo-relative path — resolves in every framework). It defines shared decision boundaries, scope discipline, verification, document consent and publication control.

Claude Code gets these injected automatically at session start (SessionStart hook). Other frameworks — read the file above once per session.

Intent → skill routing

When a task arrives, identify the phase and reach for the matching skill. If unsure, the using-skills skill (in skills/meta/) maps the task to a phase.

PhaseSkillTriggers on
metaskill-authoring"写技能", "改技能", "技能评估", write/edit/eval a skill
productbrainstormunderspecified ask, "refine this idea", "头脑风暴" (user-typed)
productspecnew project/feature/change, "write spec", "create prd", "写需求文档", refactor/update a PRD for readability, "精简 PRD", "重构 PRD", "更新 PRD", "要做什么", "需求是什么"
productoss-strategyOSS business model, COSS, "开源策略", "开源商业模式"
researchresearchdeep web research, cited report, "深度检索", "调研报告"
researchresearch"deep research", "市场调研", "竞品分析", "技术选型", "选哪个" (general/market/tech-selection modes)
designarchitecturesystem design, "架构设计", "系统设计", ADR, evidence-based tech decisions, design audit, "这个技术方案怎么审计"
designdomain-modelingdomain model, ubiquitous language, "领域模型", CONTEXT.md
designapi-designREST/GraphQL contracts, "接口设计", "API 契约"
designcodebase-designdeep modules, "深化模块", "重构架构"
designfrontend-designUI, "界面设计", "前端设计", production-grade frontend
designimage-to-code"设计图转代码", "图片实现", image-first frontend pipeline
designimagegen"品牌识别", "logo 设计", "网站设计图", "移动端设计图", brand/web/mobile design reference images
designdesign-research"设计参考", "真实设计参考", "找设计灵感", free public design galleries
designschema-design"数据模型", "表结构设计", data model, schema design
designprompt-engineering"提示词工程", "LLM 特性", prompt design, eval harness
designprototypethrowaway prototype, "原型", "试这个方案", "build a demo"
developimplementimplement spec/tickets, "实现", "编码", "改这个配置", "搭项目骨架", "改一下这个", "加个功能"
developmulti-agent-orchestration"并行 agent", "子代理执行", "派发任务", parallel/sequenced subagents
developbreakdownbreak work into tickets, "拆解任务", "拆票", decision map
developcontext-engineeringagent needs context, "解释这段代码", "带我过一遍代码库"
developi18n"国际化", "本地化", "多语言", i18n, RTL, localization
developauth-implementation"implement auth", "实现认证", "实现登录", "OAuth 集成", "password hashing", "token 轮换", JWT, RBAC
developerror-handling"error handling", "错误处理", "重试策略", "熔断", "降级", retry strategy, circuit breaker, error propagation
tunecost-optimization"成本优化", "云账单", "费用", cloud bill, FinOps, spend
tuneperformance"性能优化", "性能调优", "太慢了", "卡顿", profile, bottlenecks
tunesimplify"too complex", "简化", "重构求清晰", refactor for clarity
tunerefactoring"refactor structure", "提取模块", "拆分文件", extract/move/split/merge
testtdd"测试驱动开发", "红绿重构", red-green-refactor
testtest-generation"生成测试", "补测试", generate test files
testapi-testingcontract testing, "API 测试", "接口测试", REST/GraphQL
teste2e-testinge2e, browser test, "端到端测试", "浏览器测试"
testload-testing"压测", "压力测试", "容量测试", load/stress test, capacity
verifya11y-review"无障碍", "可访问性", accessibility, a11y, WCAG, screen reader
verifycode-reviewreview before merge, "代码审查", "合并前审查", "帮我看看这代码", "能合并吗"
verifydebuggingbug, "调试", "排查 bug", "读日志", "排查错误日志", "为什么返回 null", "跑不通"
verifysecurity-reviewsecurity review, "安全审查", "安全审计", secrets, injection
verifylinting"lint", "lint 修复", "静态分析", eslint/ruff/clippy
shipshippingdeploy, launch, "上线", "发布", "部署到生产"
shipgit-workflowcommit, merge conflict, "提交", "合并冲突", pre-commit
shipci-cdCI pipeline, GitHub Actions, "流水线", "持续集成"
shipdeprecation-migrationdeprecate, migrate, "迁移", "升级依赖", "更新这个库"
shiposs-polish"开源项目美化", "优化项目展示", README/topics polish
operateobservabilitylogs, metrics, "可观测性", "监控告警", instrumentation
operatedocumentation-auditdocs drift, "写文档", "写 README", "文档化这个功能", sync docs
operatepurity-audit"纯净审计", "残留审计", files read like edited many times, historical residue
operatehandoffhand off to another session, "交接" (user-typed)
operateincident-response"事故响应", "线上故障", "复盘", incident, on-call, postmortem

Several skills carry sub-task references for focused scenarios — the main SKILL.md links a references/ file for depth:

  • context-engineering → explains existing code / codebase tours (references/code-explanation.md)
  • debugging → log triage without full reproduction (references/log-triage.md)
  • implement → lightweight changes: small edits, renames, scaffolding (references/lightweight-changes.md)
  • documentation-audit → writing new docs from scratch (references/writing-docs.md)
  • purity-audit → per-category auditor subagent dispatch (references/subagent-dispatch.md)
  • deprecation-migration → dependency upgrades (references/dependency-upgrade.md)

Every skill's ## When to use states a negative boundary (NOT for → the adjacent skill it isn't), so adjacent tasks route to the right skill instead of two firing at once.

Invocation model — user-invoked vs model-invoked

Every skill is either model-invoked (default — the agent reaches for it autonomously on trigger match) or user-invoked (only fires when the human types its name). Two skills are user-typed: brainstorm and handoff (set disable-model-invocation: true). The rest are model-invoked. See .agents/invocation.md for the full model and how it syncs across Claude Code (disable-model-invocation) and Codex (agents/openai.yaml → policy.allow_implicit_invocation).

Planning

Scale planning to the task. Use the harness planning facility when available, otherwise an inline plan. Use breakdown when durable dependency-aware tasks are useful. Do not force clear small edits through formal specifications.

Install

See .agents/install-block.md for the canonical install commands (Claude Code plugin, Codex, and other agents).

Conventions

  • Skills live under skills/<phase>/<name>/SKILL.md (uppercase SKILL.md).
  • Frontmatter: name + description (+ optional disable-model-invocation). Nothing else.
  • Every skill's ## References links the shared engineering principles (source-relative links; standalone installation bundles shared resources). PM-side skills also link references/product-principles.md; UIUX skills also link references/design-principles.md.
  • Doc-producing skills declare **Output:** (see references/skill-anatomy.md). Artifact paths are suggestions until confirmed. PRD/TECH/PLAN normally have one owner; separate release detail only when independently maintained scopes justify it. Human review uses references/human-audit.md.
  • Validate: bash scripts/validate-skills.sh; installation: python -m unittest discover -s test -v.

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.