apply-yc
CLAUDE.md16 starsChanged 7 months agoMITView on GitHub
Skill for helping founders write YC applications that get interviews. skills/yc-application/SKILL.md — router + core principles. 7 workflow modes: 1. Draft from scratch 2. Critique existing draft 3. Stuck on one question 4. Video prep 5. Interview prep 6. Reapplying 7. Strategic context (RFS, deal terms, partners) Reference files in skills/yc-application/references/ — load the relevant one per mode. Don't load all 7. When bumping the plugin version, update ALL THREE in the same commit — they must always match: Never…
In this repository4 other files it gives its agents.
- form-fillSkill
- founder-profileSkill
- apply-yc-onboardingSkill
- yc-applicationSkill
The file
We split this CLAUDE.md into the rules it gives an agent
6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
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
- Distinctive: line 20
Default to drafting actual answers, not advice.
- Distinctive: line 21
No marketing-speak. Flag it.
- Very specific: line 22
No fabricated metrics. Use placeholders like [USERS].
- Distinctive: line 23
No em dash. Hyphens or rephrase.
- Distinctive: line 29
When bumping the plugin version, update ALL THREE in the same commit — they must always match:
- Distinctive: line 35
Never let these diverge. If you find them out of sync, fix all three before proceeding.
≈ “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
apply-yc Plugin
Skill for helping founders write YC applications that get interviews.
Skill
skills/yc-application/SKILL.md — router + core principles. 7 workflow modes:
- Draft from scratch
- Critique existing draft
- Stuck on one question
- Video prep
- Interview prep
- Reapplying
- Strategic context (RFS, deal terms, partners)
Reference files in skills/yc-application/references/ — load the relevant one per mode. Don't load all 7.
Principles
- Default to drafting actual answers, not advice. Founder is on deadline.
- No marketing-speak. Flag it. Rewrite it.
- No fabricated metrics. Use placeholders like
[USERS]. - No em dash. Hyphens or rephrase.
- Honesty over polish. Partner-level directness.
- Real examples only: Dropbox S07, Basedash S20.
Versioning Rule
When bumping the plugin version, update ALL THREE in the same commit — they must always match:
.claude-plugin/plugin.json→"version": "X.Y.Z"README.md→ badgehttps://img.shields.io/badge/version-X.Y.Z-greenCHANGELOG.md→ new## [X.Y.Z] - YYYY-MM-DDsection
Never let these diverge. If you find them out of sync, fix all three before proceeding.
Maintenance
See docs/sources.md for citation URLs and refresh schedule.
See CHANGELOG.md for version history.
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.