co-founder
CLAUDE.md0 starsChanged 3 months agoMITView on GitHub
Distributable Claude Code plugin: 13 skills that give a solopreneur a co-founder, not a yes-man. This repo ships publicly (unlisted). Everything committed here is founder-visible.
The file
We split this CLAUDE.md into the rules it gives an agent
6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Privacy scrub: No private founder revenue, pricing, deal names, voice DNA, lane specifics, infrastructure facts, or private source paths …
- Distinctive: line 13
Voice laws: Every skill text passes /humanize-thinking.
- Very specific: line 16
Mechanics doctrine: Every skill follows the not-yet gate, receipts contract, facts-mine/decisions-yours interviews, effort sizing, and …
- Very specific: line 20
Every skills/*/SKILL.md frontmatter block parses as strict YAML.
- Very specific: line 23
Every release bumps .claude-plugin/plugin.json and adds a CHANGELOG entry with Impact, Compatibility, Update, Migration, and Delivery …
- Distinctive: line 28
Use one commit per logical fix and conventional messages naming the audit findings.
≈ “Common” is an estimate: at least 1 in 5 of the 27,641 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
cofounder-plugin: the /co-founder skill collection
Distributable Claude Code plugin: 13 skills that give a solopreneur a co-founder, not a yes-man. This repo ships publicly (unlisted). Everything committed here is founder-visible.
What this repo is
.claude-plugin/plugin.json+marketplace.json. CLI install:claude plugin marketplace add exm7777/co-founder→claude plugin install co-founder@atlas-kit --scope user→ verify withclaude plugin details co-founder@atlas-kit→ start a freshclaudesession.skills/: co-founder-setup, vision, plan, gauntlet, research, sprint, review, bank, steward, recall, offer, content-engine, plus the tiny help alias.CONVENTIONS.mdis the public shared contract. EachSKILL.mdplus its localreferences/is the public source of truth for that skill. The repository must stand on its own for external maintainers.
Build laws (non-negotiable)
- Privacy scrub. No private founder revenue, pricing, deal names, voice DNA, lane specifics, infrastructure facts, or private source paths ship. Templates contain empty shapes. References contain only distilled, de-identified heuristics.
- Voice laws. Every skill text passes /humanize-thinking; looks engineered (ASCII diagrams, precise technical vocabulary); uses the collection's direct, standard-punctuation voice.
- Craft rules. Predictable process (not output); state the positive; delete no-op sentences; progressive disclosure via references; plain markdown artifacts. Plugin installation, namespacing, cache paths, and restart behavior are Claude Code-specific.
- Per-skill gate. A skill ships only after adversarial QA (scenario simulation plus contract check by an independent worker) with findings fixed and maintainer approval recorded.
- Mechanics doctrine. Every skill follows the not-yet gate, receipts contract, facts-mine/decisions-yours interviews, effort sizing, and no-guessing-unattended law in
CONVENTIONS.md.
Release gates
claude plugin validate --strict .passes with zero warnings.- Every
skills/*/SKILL.mdfrontmatter block parses as strict YAML. - Native eval cases run, including trigger conflicts, fresh folder, re-sync, and the full loop.
- A simulated installed release resolves its shared contract from the versioned plugin cache.
- Every release bumps
.claude-plugin/plugin.jsonand adds a CHANGELOG entry with Impact, Compatibility, Update, Migration, and Delivery blocks. A push without a version bump does not update pinned installs, and third-party marketplace auto-update is off by default.
Git
Use one commit per logical fix and conventional messages naming the audit findings. Merge to main after maintainer approval. Never commit anything failing the privacy scrub.
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.

