agentleFS
Sign inStart free
FqihFqih/.mycc-setup/rules/agents.md

.mycc-setup / rules

AGENTS.md2 starsChanged 2 months agoMITView on GitHub

Located in ~/.claude/agents/: No user prompt needed: 1. Complex feature requests - Use planner agent 2. Code just written/modified - Use code-reviewer agent 3. Bug fix or new feature - Use tdd-guide agent 4. Architectural decision - Use architect agent ALWAYS use parallel Task execution for independent operations: For complex problems, use split role sub-agents: - Factual reviewer - Senior engineer - Security expert - Consistency reviewer - Redundancy checker

9 other projects use a version of this.

Adopted by

Most recently taken up by

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No user prompt needed:

    line 21
  2. Distinctive:

    ALWAYS use parallel Task execution for independent operations:

    line 29

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

Agent Orchestration

Available Agents

Located in ~/.claude/agents/:

AgentPurposeWhen to Use
plannerImplementation planningComplex features, refactoring
architectSystem designArchitectural decisions
tdd-guideTest-driven developmentNew features, bug fixes
code-reviewerCode reviewAfter writing code
security-reviewerSecurity analysisBefore commits
build-error-resolverFix build errorsWhen build fails
e2e-runnerE2E testingCritical user flows
refactor-cleanerDead code cleanupCode maintenance
doc-updaterDocumentationUpdating docs

Immediate Agent Usage

No user prompt needed:

  1. Complex feature requests - Use planner agent
  2. Code just written/modified - Use code-reviewer agent
  3. Bug fix or new feature - Use tdd-guide agent
  4. Architectural decision - Use architect agent

Parallel Task Execution

ALWAYS use parallel Task execution for independent operations:

# GOOD: Parallel execution
Launch 3 agents in parallel:
1. Agent 1: Security analysis of auth.ts
2. Agent 2: Performance review of cache system
3. Agent 3: Type checking of utils.ts

# BAD: Sequential when unnecessary
First agent 1, then agent 2, then agent 3

Multi-Perspective Analysis

For complex problems, use split role sub-agents:

  • Factual reviewer
  • Senior engineer
  • Security expert
  • Consistency reviewer
  • Redundancy checker

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