agentleFS
tdiminotdimino/claude-code-minoan/CLAUDE.md

claude-code-minoan

CLAUDE.md41 starsChanged 7 months agoMITView on GitHub

Curated ~/.claude/ configuration for Claude Code: 94 skills, 46 hooks, 20 commands, CLI tools, and a VS Code extension. See CONTRIBUTING.md for full guidelines.

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

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

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No API keys in the repo--use placeholders

    line 23

≈ “Common” is an estimate: at least 1 in 5 of the 25,680 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

Claude-Code-Minoan

Curated ~/.claude/ configuration for Claude Code: 94 skills, 46 hooks, 20 commands, CLI tools, and a VS Code extension.

Architecture

@ARCHITECTURE.md

Structure

skills/{category}/{name}/  →  installs flat to ~/.claude/skills/{name}/
hooks/                     →  ~/.claude/hooks/ (wire in settings.json)
plugins/{name}/            →  claude plugin marketplace add ./plugins/{name} (function-hook plugins)
commands/                  →  ~/.claude/commands/
bin/                       →  ~/.local/bin/
lib/                       →  ~/.claude/lib/

Contributing

  • Skills must be self-contained--no cross-skill imports
  • Hooks must wrap json.load in try/except--malformed input must not crash
  • No API keys in the repo--use placeholders
  • Flat skill names are authoritative--never reference category paths in code

See CONTRIBUTING.md for full guidelines.

Quick Reference

  • Setup: ./setup.sh or see README.md Quick Start
  • Sync from private: ./scripts/sync-to-repo.sh [--dry-run]
  • Sync config: .sync-config.json (category map, exclusions)
  • Skill counts: find skills -name SKILL.md -not -path '*/_archive/*' | wc -l

Guides

  • ARCHITECTURE.md -- Repo layout, skill anatomy, hook wiring, invariants
  • hooks/README.md -- All 46 hooks explained, including the SubagentStart/Stop loggers (subagent-spawn-log.py + subagent-stop-log.py) that catch silent subagent failures (tool errors, 32K output truncation, empty responses). Read when investigating subagent costs or unexplained agent behavior.
  • docs/ecosystem.md -- Companion projects (Claudicle, Dabarat, ClipLog, claude-peers)
  • docs/guides/usermodel-guide.md -- The userModel persona system
  • docs/guides/progressive-disclosure.md -- The agent_docs pattern
  • docs/guides/session-continuity.md -- Triple-handoff system
  • docs/global-setup/README.md -- Full ~/.claude/ structure reference
  • CLAUDE.template.md -- Teammate-ready global CLAUDE.md (no personal details)

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.

Reviews can't be read right now.

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.