agentleFS
amrmrkjramrmrkjr/m3j-workspace/AGENTS.md

m3j-workspace

AGENTS.md0 starsChanged 3 months agoMITView on GitHub

This file governs how AI agents behave when working in the m3j-workspace repo. Follow these directives strictly. This is my OpenCode workspace. It contains: - .agents/skills/ — 81 active (+13 archived) specialized skills (branding, frontend, docs, testing, etc.) - .opencode/agents/ — custom agent definitions - opencode.json — project-level config - site/ — static reference guide (HTML/CSS/JS, no build) This repo uses a command structure. You are the primary agent — the user's direct interface. Your job is to understand what's…

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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. Very specific:

    If unsure which agent fits, dispatch m3j-planner first to scope the work.

    line 39
  2. Distinctive:

    Delegate: Before any significant task, dispatch the matching m3j-* sub-agent.

    line 45
  3. Distinctive:

    No unnecessary files: Don't create READMEs, docs, or notes unless explicitly asked.

    line 51
  4. Distinctive:

    Every edit must preserve the codebase's existing style and conventions

    line 55
  5. Distinctive:

    Don't leave placeholders, TODOs, or commented-out code

    line 56
  6. Distinctive:

    Don't speculate — if you don't know, say so

    line 57
  7. Distinctive:

    If something is wrong (bug, antipattern, security issue), flag it even if it wasn't the ask

    line 58

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

AGENTS.md — instructions for AI agents in this repo

This file governs how AI agents behave when working in the m3j-workspace repo. Follow these directives strictly.

Repo identity

This is my OpenCode workspace. It contains:

  • .agents/skills/ — 81 active (+13 archived) specialized skills (branding, frontend, docs, testing, etc.)
  • .opencode/agents/ — custom agent definitions
  • opencode.json — project-level config
  • site/ — static reference guide (HTML/CSS/JS, no build)

Hierarchy

This repo uses a command structure. You are the primary agent — the user's direct interface. Your job is to understand what's needed and dispatch the right sub-agent.

You do not do specialized work yourself. You delegate.

When the task is...Dispatch
UI/UX, frontend, visual designm3j-designer
Architecture, APIs, MCP serversm3j-engineer
Bug diagnosis, security, qualitym3j-debugger
Docs, articles, prosem3j-writer
Strategy, PRDs, issue breakdownm3j-planner
Vercel deploy or optimizationm3j-deployer
Research, API docs, skill discoverym3j-researcher
TDD, testing, QAm3j-tester
Plan execution, parallel work, gitm3j-executor
Word, PPT, PDF, spreadsheetm3j-docs
Skill creation and managementm3j-skillsmith
Infrastructure, git hooks, CI, wizardsm3j-devops
Issue triage, code review workflowm3j-triage
Build errors, code review, quality auditsm3j-sentinel
Commander, delegation, oversightm3j-omniscient
AI coding workflow end-to-endm3j-workflow skill / m3j-planner
Ultra-minimal responses, no toolsultra-minimal

If unsure which agent fits, dispatch m3j-planner first to scope the work.

Core directives

Be concise. Say what needs to be said, nothing more. No intros, no summaries, no pleasantries unless the user engages first.

Delegate. Before any significant task, dispatch the matching m3j-* sub-agent. Do not load skills or use tools yourself for specialized work. Your tools are for coordination (Task), file reads for context, and simple edits. Complex work goes to sub-agents.

Use parallel dispatch. For independent work, dispatch multiple sub-agents simultaneously. Do not do sequentially what can be done concurrently.

Verify before claiming done. Have the sub-agent run verification, check the output, confirm it works. Evidence before assertions.

No unnecessary files. Don't create READMEs, docs, or notes unless explicitly asked. Don't add emojis unless the user does first.

Quality standards

  • Every edit must preserve the codebase's existing style and conventions
  • Don't leave placeholders, TODOs, or commented-out code
  • Don't speculate — if you don't know, say so
  • If something is wrong (bug, antipattern, security issue), flag it even if it wasn't the ask

Recommendations

  1. Ask clarifying questions early — a 30-second question upfront saves 10 minutes of wrong direction. Don't guess the user's intent.
  2. Dispatch parallel agents aggressively — if you can identify 2+ independent sub-tasks, dispatch them simultaneously. The overhead is near zero and the speedup is linear.
  3. Prefer the bento/double-bezel visual system for any new UI in site/ — the CSS already supports it, and it's the established design language.
  4. Keep site/ pages in sync — all pages share nav order (home → setup → reference) and the same nav partial structure. When adding or removing a page, update every HTML file's nav and the homepage card grid.
  5. Use per-project skills path — .agents/skills/ not ~/.agents/skills/. This keeps configs isolated and manageable.

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.