agentleFS
jnsfhrmnnjnsfhrmnn/jf-agentic-coding-starter-kit/AGENTS.md

jf-agentic-coding-starter-kit

AGENTS.md1 starsChanged 4 months agoMITView on GitHub

This starter kit supports both Codex and Claude. CLAUDE.md and the repository rules define the shared workflow; these instructions add the Codex entry point. 1. Inspect the skills and tools currently available. 2. Prefer an applicable skill when one exists. Use deterministic tools for mechanical checks and LLM judgment for semantic, contextual, or non-deterministic decisions. 3. Read CLAUDE.md and relevant .claude/rules/. 4. Run $csk-start before selecting work. It validates the tracked first-use decision in .csk/project-state.json, routes adopted repositories to $csk-adopt-plan-scaffold,…

The file

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

11 rules. About 0 are common, 5 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Prefer an applicable skill when one exists.

    line 11
  2. Very specific:

    Read CLAUDE.md and relevant .claude/rules/.

    line 14
  3. Very specific:

    Run $csk-start before selecting work.

    line 15
  4. Very specific:

    Follow .claude/rules/workflow-state.md as the routing and transition SSOT.

    line 18
  5. Distinctive:

    Never install, copy, or synchronize kit skills into a user's global Claude or Codex directories.

    line 25
  6. Very specific:

    Run $claude-skill-proxy-sync after adding, renaming, moving, or removing a canonical skill, or after changing its frontmatter trigger/UI …

    line 27
  7. Very specific:

    Use source-of-truth files instead of duplicating state.

    line 41
  8. Distinctive:

    Create task rows only for work that survives the current session, is blocked or deferred, or is a verified interruption point.

    line 44
  9. Very specific:

    After verified work on a non-default branch, use $finish-branch.

    line 46
  10. Distinctive:

    Read files before modifying them, preserve unrelated user changes, and verify edits and tests before claiming completion.

    line 48
  11. Distinctive:

    Keep all generated proxy paths repository-relative and reject global fallbacks.

    line 51

≈ “Common” is an estimate: at least 1 in 5 of the 41,581 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

Codex Repository Instructions

<!-- CODEX_CLAUDE_COMPATIBILITY -->

This starter kit supports both Codex and Claude. CLAUDE.md and the repository rules define the shared workflow; these instructions add the Codex entry point.

Session Start

  1. Inspect the skills and tools currently available.
  2. Prefer an applicable skill when one exists. Use deterministic tools for mechanical checks and LLM judgment for semantic, contextual, or non-deterministic decisions.
  3. Read CLAUDE.md and relevant .claude/rules/.
  4. Run $csk-start before selecting work. It validates the tracked first-use decision in .csk/project-state.json, routes adopted repositories to $csk-adopt-plan-scaffold, and then reads tasks/INDEX.md plus live Git state.
  5. Follow .claude/rules/workflow-state.md as the routing and transition SSOT.

Claude And Codex Skills

  • Canonical skills live only in .claude/skills/.
  • Ready-to-use Codex proxies live only in .codex/skills/ and load their canonical Claude skill at runtime.
  • Never install, copy, or synchronize kit skills into a user's global Claude or Codex directories.
  • Run $claude-skill-proxy-sync after adding, renaming, moving, or removing a canonical skill, or after changing its frontmatter trigger/UI metadata.
  • Ordinary canonical skill body and resource changes do not require a sync.
  • /csk-adopt-plan-scaffold / $csk-adopt-plan-scaffold is required and must remain bundled.
  • /finish-branch / $finish-branch, /audit-plan-loop / $audit-plan-loop, and /review-loop / $review-loop are required and must remain bundled.
  • /create-worker-worktree / $create-worker-worktree and /pull-main-ff / $pull-main-ff own parallel-session worktrees and safe default-branch updates; docs/git-basics.md is the beginner reference for both.

Work Rules

  • Codex may perform productive repository work; it is not restricted to review.
  • Use source-of-truth files instead of duplicating state. features/INDEX.md and feature specs own feature state; tasks/INDEX.md owns immediate open or blocked durable continuation work; .csk/project-state.json owns onboarding state.
  • Create task rows only for work that survives the current session, is blocked or deferred, or is a verified interruption point.
  • After verified work on a non-default branch, use $finish-branch; Git and external mutations still require explicit authority.
  • Read files before modifying them, preserve unrelated user changes, and verify edits and tests before claiming completion.
  • Change CLAUDE.md only with concrete user authorization for that change.
  • Keep all generated proxy paths repository-relative and reject global fallbacks.

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.