agentleFS
Sign inStart free
first-flukefirst-fluke/fullstack-starter/AGENTS.md

fullstack-starter

AGENTS.md223 starsChanged 28 days agoMITView on GitHub

Follow .agents/skills/_shared/core/execution-policy.md for authorization, clarification, verification, and completion. System/developer instructions and the user's request take precedence over OMA defaults. Never build, compile, bundle, or package software unless the user explicitly requests a build. Resolve each agent from .agents/oma-config.cue or .agents/oma-config.yaml, overlaid by .agents/oma-config.local.cue or .agents/oma-config.local.yaml when present. With modelpreset: free, always use oma agent spawn so the subprocess receives the FreeLLMAPI route; free.model replaces per-agent model pins. Otherwise, explicit agents: overrides take priority. With modelpreset: auto, follow the current vendor's…

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

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

  • 6

    Very specific

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

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

    Follow .agents/skills/_shared/core/execution-policy.md for authorization, clarification, verification, and completion.

    line 5
  2. Very specific:

    SSOT: Do not modify .agents/ definitions (skills, workflows, rules, agents, config) directly.

    line 7
  3. Very specific:

    Response language: Follow language in .agents/oma-config.yaml.

    line 8
  4. Very specific:

    Skills: Read the relevant .agents/skills/{name}/SKILL.md when needed.

    line 9
  5. Distinctive:

    Write non-ASCII tool-call parameters as literal UTF-8, not Unicode escapes.

    line 16
  6. Very specific:

    Run workflows only when explicitly requested or detected by a hook.

    line 28
  7. Very specific:

    Read the relevant file from .agents/rules/ when working on matching code.

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 36,368 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
<!-- OMA:START — managed by oh-my-agent. Do not edit this block manually. -->

oh-my-agent

Follow .agents/skills/_shared/core/execution-policy.md for authorization, clarification, verification, and completion. System/developer instructions and the user's request take precedence over OMA defaults. Never build, compile, bundle, or package software unless the user explicitly requests a build.

  • SSOT: Do not modify .agents/ definitions (skills, workflows, rules, agents, config) directly. Run outputs under .agents/results/ and .agents/state/ are generated artifacts and may be written.
  • Response language: Follow language in .agents/oma-config.yaml.
  • Skills: Read the relevant .agents/skills/{name}/SKILL.md when needed.
  • Subagents:
    • claude: Same-vendor native dispatch via Claude Code Agent tool with .claude/agents/{name}.md; cross-vendor fallback via oma agent spawn
    • codex: Same-vendor native dispatch via Codex custom agents in .codex/agents/{name}.toml; cross-vendor fallback via oma agent spawn
    • cursor: @agent-name (defined in .cursor/agents/)
    • qwen: Same-vendor native dispatch via Qwen Code subagents in .qwen/agents/{name}.md; cross-vendor fallback via oma agent spawn
    • pi: pi has no native subagent API; use oma agent spawn {agent} {prompt} {sessionId} --vendor pi for CLI subprocess dispatch
  • Write non-ASCII tool-call parameters as literal UTF-8, not Unicode escapes.

Per-Agent Dispatch

Resolve each agent from .agents/oma-config.cue or .agents/oma-config.yaml, overlaid by .agents/oma-config.local.cue or .agents/oma-config.local.yaml when present. With model_preset: free, always use oma agent spawn so the subprocess receives the FreeLLMAPI route; free.model replaces per-agent model pins. Otherwise, explicit agents: overrides take priority. With model_preset: auto, follow the current vendor's native agent/model settings; use default_cli only when the runtime is unknown. Use native subagents when the target matches the current runtime; otherwise, or when native dispatch is unavailable, use oma agent spawn.

Code Search

Serena MCP is required for code search and discovery. Load deferred tools before use. Use find_file for paths, search_for_pattern for content, and find_symbol / get_symbols_overview for symbols. Native search is only for paths outside this project, ignored paths, or plain non-code content. The PreToolUse guard already allows searches confined to confirmed provider exclusions or paths outside this project.

Workflows

Run workflows only when explicitly requested or detected by a hook; never self-initiate. Read and follow .agents/workflows/{name}.md. Continue active workflows until complete or explicitly cancelled.

Project Rules

Read the relevant file from .agents/rules/ when working on matching code.

RuleFileScope
backend.agents/rules/backend.mdon request
branching-strategy.agents/rules/branching-strategy.mdon request
build-guide.agents/rules/build-guide.mdon request
commit.agents/rules/commit.mdon request
database.agents/rules/database.md**/*.{sql,prisma}
debug.agents/rules/debug.mdon request
design-tokens-guide.agents/rules/design-tokens-guide.mdon request
design.agents/rules/design.mdon request
dev-workflow.agents/rules/dev-workflow.mdon request
frontend.agents/rules/frontend.md**/*.{tsx,jsx,css,scss}
i18n-arb.agents/rules/i18n-arb.md**/*.arb
i18n-guide.agents/rules/i18n-guide.mdalways
infrastructure.agents/rules/infrastructure.md**/*.{tf,tfvars,hcl}
lint-format-guide.agents/rules/lint-format-guide.mdon request
market.agents/rules/market.mdon request
mobile.agents/rules/mobile.md**/*.{dart,swift,kt}
preferred-editing-tools.agents/rules/preferred-editing-tools.mdon request
quality.agents/rules/quality.mdon request
test-guide.agents/rules/test-guide.mdon request
<!-- OMA:END -->

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.

Check your setup, free