agentleFS
raymondwareraymondware/scribe/CLAUDE.md

scribe

CLAUDE.md0 starsChanged 3 months agoMITView on GitHub

Scribe is a Claude Code plugin that orchestrates specialist agents to produce high-quality longform writing. It catches AI-default writing patterns before they ship. ${CLAUDE_PLUGIN_ROOT}/skills/humanize/SKILL.md provides /scribe:humanize for direct edits of existing prose. It runs in the current conversation without the conductor, pattern draw, audit log, or Sameness Score. Keep this separate from the existing pipeline commands. Use the writer's voice and preserve claims instead of enforcing blanket pattern substitutions. Community-sourced patterns go in anti-patterns/sourced-from-research/ via the research-scout agent. Base patterns…

  • In this repository2 other files it gives its agents.

The file

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

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

  • 5

    Very specific

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

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

    All internal paths use ${CLAUDE_PLUGIN_ROOT}/ prefix

    line 22
  2. Very specific:

    Create agents/your-agent.md with YAML frontmatter (name, model, description).

    line 36
  3. Very specific:

    If the agent participates in the pipeline, update skills/scribe/references/orchestration/pipeline.md

    line 39
  4. Very specific:

    Create a file in skills/scribe/references/personas/ following the existing format.

    line 49
  5. Very specific:

    No em-dashes in any content (this rule applies recursively - scribe must not exemplify what it flags)

    line 53
  6. Distinctive:

    Keep agent prompts under 100 lines unless the role genuinely requires more

    line 56

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

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md

Scribe Plugin - Contributor Guide

What This Is

Scribe is a Claude Code plugin that orchestrates specialist agents to produce high-quality longform writing. It catches AI-default writing patterns before they ship.

Structure

scribe/
├── .claude-plugin/     # Plugin manifest (plugin.json, marketplace.json)
├── agents/             # Flat directory, auto-discovered by Claude Code
├── commands/           # /scribe:* slash commands
├── skills/             # Scribe pipeline and focused humanize skill
├── anti-patterns/      # Base + research-sourced AI-ism library
├── state/              # Append-only audit log (state/draws.jsonl)
└── tools/              # Draw simulator and validators

Conventions

  • All internal paths use ${CLAUDE_PLUGIN_ROOT}/ prefix
  • Agents are flat in agents/ (no subdirectories - breaks auto-discovery)
  • Anti-patterns at repo root (not nested in skills/) because many agents read them
  • Specialists use Haiku (fast, cheap, constrained output)
  • Implementation agents use Sonnet (code generation)
  • Conductor, voice-critic, and critique-synthesizer use Opus (complex judgment, synthesis)
  • Conductor never writes or critiques - only coordinates

Focused Humanize Skill

${CLAUDE_PLUGIN_ROOT}/skills/humanize/SKILL.md provides /scribe:humanize for direct edits of existing prose. It runs in the current conversation without the conductor, pattern draw, audit log, or Sameness Score. Keep this separate from the existing pipeline commands. Use the writer's voice and preserve claims instead of enforcing blanket pattern substitutions.

Adding a New Agent

  1. Create agents/your-agent.md with YAML frontmatter (name, model, description). Set model to a tier alias (haiku, sonnet, opus), never a pinned model ID
  2. Reference files using ${CLAUDE_PLUGIN_ROOT}/path/to/file
  3. Define clear inputs, outputs, and constraints
  4. If the agent participates in the pipeline, update skills/scribe/references/orchestration/pipeline.md

Adding a New Anti-Pattern

Community-sourced patterns go in anti-patterns/sourced-from-research/ via the research-scout agent. Base patterns in anti-patterns/language.md, structure.md, or rhetoric.md are manually curated.

Each new pattern needs a manifest.json entry with id, categories, severity_default, source_file, anchor, personas, site_signals.

Adding a New Persona

Create a file in skills/scribe/references/personas/ following the existing format. Update skills/scribe/references/personas/README.md and skills/scribe/SKILL.md.

Code Style

  • No em-dashes in any content (this rule applies recursively - scribe must not exemplify what it flags)
  • Writer-to-writer voice: specific, direct, no marketing register
  • Conventional commits (feat:, fix:, docs:)
  • Keep agent prompts under 100 lines unless the role genuinely requires more

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.