no-slop / adapters
CLAUDE.md1 starsChanged 11 days agoMITView on GitHub
Integrate the no-slop workflow into Claude (Claude Projects, Claude Code CLI, or Claude Web). When initiating a coding request in Claude, reference the workflow: Claude functions primarily as a single-turn conversational agent or sequential tool runner. The orchestrator will automatically fall back to sequential execution: - Execute prompt-optimizer -> planner -> (UI: design-taste). - Execute each chunk in TASKS.md sequentially. - Enforce diff-guard on all edits. - Run reviewer self-audit. - Record teach-mode entry in LEARNING.md.
In this repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- rules/AGENTS.mdAGENTS.md
- asset-intakeSkill
- client-collabSkill
- design-tasteSkill
- diff-guardSkill
- motion-craftSkill
- no-slop-startSkill
- orchestratorSkill
- plannerSkill
- prompt-optimizerSkill
- reference-teardownSkill
- reviewerSkill
- scene-3dSkill
- storyboardSkill
- teach-modeSkill
- visual-qaSkill
The file
We split this claude.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
- Very specific: line 19
Place no-slop in your project root or in a .claude/ configuration folder:
- Distinctive: line 29
When initiating a coding request in Claude, reference the workflow:
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.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.
Files
Claude Setup Adapter
Integrate the no-slop workflow into Claude (Claude Projects, Claude Code CLI, or Claude Web).
1. Installation Locations
Claude Projects (Web)
- In your Claude Project, go to the Project Knowledge pane.
- Upload the
no-slopdirectory or the following core files:AGENTS.mdskills/directory (allSKILL.mdfiles)roles/directory (all role.mdfiles)
- In Custom Instructions, add:
Follow the instructions in AGENTS.md for all coding and refactoring tasks. Adhere strictly to the no-slop protocol, skills, and role constraints.
Claude Code (CLI)
- Place
no-slopin your project root or in a.claude/configuration folder:cp -r /path/to/no-slop/skills ./skills cp -r /path/to/no-slop/roles ./roles cp /path/to/no-slop/AGENTS.md ./CLAUDE.md - Claude Code automatically reads
CLAUDE.mdon startup.
2. Referencing AGENTS.md
When initiating a coding request in Claude, reference the workflow:
Follow AGENTS.md. Optimize prompt, create TASKS.md, establish DESIGN.md if UI is required, and run sequential role execution.3. Concurrency Behavior
Claude functions primarily as a single-turn conversational agent or sequential tool runner. The orchestrator will automatically fall back to sequential execution:
- Execute
prompt-optimizer->planner-> (UI:design-taste). - Execute each chunk in
TASKS.mdsequentially. - Enforce
diff-guardon all edits. - Run
reviewerself-audit. - Record
teach-modeentry inLEARNING.md.
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
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.

