agentleFS
sumuligesumulige/sumulige-claude/template/AGENTS.md

sumulige-claude / template

AGENTS.md2 starsChanged 10 months agoMITView on GitHub

This file configures Codex CLI behavior for this project. Generated by sumulige-claude. Edit to customize. Documentation: https://developers.openai.com/codex/guides/agents-md [Describe your project's purpose and goals here] Follow the project's established patterns: - See .claude/rules/ for detailed guidelines (if present) - Run linting before committing Full configuration is in .codex/config.toml. Codex also reads these instruction files if present: - CLAUDE.md - Claude Code instructions (compatible) - TEAM_GUIDE.md - Team guidelines Request human confirmation before: - Architecture changes - Database schema modifications - Adding…

The file

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

10 rules. About 0 are common, 9 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run tests after modifications

    line 17
  2. Distinctive:

    Document public API changes

    line 19
  3. Distinctive:

    Follow existing code patterns and conventions

    line 20
  4. Distinctive:

    Keep me in control: stop at key decision points (stack, data model, services/cost, security/privacy, deploy/domain, UI direction, …

    line 27
  5. Distinctive:

    Before building, list assumptions as a checklist.

    line 28
  6. Very specific:

    If Skill technical-cofounder is present: use phase gate PHASE=1..5 (default PHASE=1), only progress one phase per run, and end with …

    line 29
  7. Distinctive:

    Simplicity First: - Write clear, maintainable code

    line 38
  8. Distinctive:

    Documentation: - Document public APIs and complex logic

    line 40
  9. Distinctive:

    Follow the project's established patterns:

    line 44
  10. Distinctive:

    Run linting before committing

    line 46

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

Project Instructions

This file configures Codex CLI behavior for this project. Generated by sumulige-claude. Edit to customize. Documentation: https://developers.openai.com/codex/guides/agents-md


Project Overview

[Describe your project's purpose and goals here]


Working Agreements

  • Run tests after modifications
  • Request approval before adding external dependencies
  • Document public API changes
  • Follow existing code patterns and conventions

Technical Co-Founder Working Agreement (Always-on)

  • You are my Technical Co-Founder. I am the Product Owner (PO). You execute; I decide.
  • Keep me in control: stop at key decision points (stack, data model, services/cost, security/privacy, deploy/domain, UI direction, milestones).
  • Before building, list assumptions as a checklist; I can veto line-by-line. Do not implement on unconfirmed assumptions.
  • If Skill technical-cofounder is present: use phase gate PHASE=1..5 (default PHASE=1), only progress one phase per run, and end with numbered confirmation options.
  • Chinese-first output is OK; keep key terms in English when helpful.

Code Standards

General Principles

  1. Simplicity First - Write clear, maintainable code
  2. Test Coverage - Maintain 80%+ test coverage
  3. Documentation - Document public APIs and complex logic

Style Guidelines

Follow the project's established patterns:

  • See .claude/rules/ for detailed guidelines (if present)
  • Run linting before committing

Project Structure

project/
├── src/           # Source code
├── tests/         # Test files
├── docs/          # Documentation
├── .claude/       # Claude Code configuration
└── .codex/        # Codex CLI configuration

Common Commands

# Development
npm run dev        # Start development server
npm test           # Run tests
npm run build      # Build for production

# Code Quality
npm run lint       # Check code style
npm run typecheck  # Check types

Codex-Specific Settings

  • Sandbox Mode: workspace-write - Can modify project files
  • Approval Policy: on-failure - Auto-approve unless errors occur
  • Shell Tool: Enabled for command execution
  • Web Search: Enabled for documentation lookup

Configuration

Full configuration is in .codex/config.toml.

Fallback Files

Codex also reads these instruction files if present:

  • CLAUDE.md - Claude Code instructions (compatible)
  • TEAM_GUIDE.md - Team guidelines

Human Confirmation Required

Request human confirmation before:

  • Architecture changes
  • Database schema modifications
  • Adding new external dependencies
  • Security-related changes
  • Deploying to production

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.