agentleFS
Pearl1531Pearl1531/Archetype-talk/.github/copilot-instructions.md

Archetype-talk

Copilot instructions2 starsChanged 47 days agoMITView on GitHub

This repo has one ruleset for every AI agent and model. It is not Claude-specific: the .claude/ folder name is historical, not a scope. If you are Cline, Roo, Continue, Copilot, Qwen, Codex, Gemini or anything else, all of it applies to you. 1. Read AGENTS.md — the cross-tool entry point. 2. Then CLAUDE.md — the full working rules: grounding and Levels, Signal vs Evidence, never inventing quotes/statistics/sources, demo-data isolation, link changes only after the user approves them. 3. Workflows…

The file

We split this copilot-instructions.md into the rules it gives an agent

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

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read AGENTS.md — the cross-tool entry point.

    line 8
  2. Very specific:

    Never read or edit app/index.html or app/src/embedded-graph.html — 300 KB+ generated build artifacts.

    line 27

≈ “Common” is an estimate: at least 1 in 5 of the 3,779 Copilot instructions 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
copilot-instructions.md

Archetype Talk — read this before doing anything

This repo has one ruleset for every AI agent and model. It is not Claude-specific: the .claude/ folder name is historical, not a scope. If you are Cline, Roo, Continue, Copilot, Qwen, Codex, Gemini or anything else, all of it applies to you.

  1. Read AGENTS.md — the cross-tool entry point.
  2. Then CLAUDE.md — the full working rules: grounding and Levels, Signal vs Evidence, never inventing quotes/statistics/sources, demo-data isolation, link changes only after the user approves them.
  3. Workflows are plain instructions in .claude/skills/<name>/SKILL.md; the index is .claude/skills/INDEX.md. Claude Code, Copilot and Cursor list them as slash-commands (/persona-talk); Codex and Gemini CLI find the same files through .agents/skills/ (Codex: $persona-talk). In any other agent, open the matching SKILL.md and follow its steps by hand. Same result.
  4. Follow a skill silently — never narrate it. The user gets the result in the format that skill defines: not your plan, not your step numbers, not a summary of what a file held before you used it. VS Code custom modes and local reasoning models emit <think>/<reasoning> tags as plain text the client does not strip — in persona-talk that prints the persona's cheat sheet above her own answer and the interview is over. Can't hide the tags? Keep what is inside them to a few words.
  5. Fresh checkout, first session: no other tool runs Claude Code's SessionStart hook, so do its job yourself — check Inbox/ for unprocessed files, and if .claude/onboarded.local is missing, follow .claude/skills/welcome/SKILL.md.
  6. Never read or edit app/index.html or app/src/embedded-graph.html — 300 KB+ generated build artifacts. Edit the partials in app/src/ (map: app/src/README.md) and rebuild with python3 scripts/build_app.py.

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.