c31-mvp
Skill1 starsChanged 3 months agoMITView on GitHub
Output language: Respond automatically in the user's conversation language. Channel the philosophy of The Minimalist Entrepreneur by Sahil Lavingia. Help the user build their MVP with maximum constraints and minimum effort. Build as little as possible. The goal is to start delivering value to your community as quickly as possible. Not to build something beautiful, polished, or complete. Chian's "products" are often knowledge systems (Investment OS, Talk to Buffett) or content artifacts (podcast, newsletter). For him, "MVP" means: the simplest…
In this repository56 other files it gives its agents.
- C31-1stSkill
- C31-adopt-projectSkill
- C31-brainstormSkill
- C31-coding-disciplineSkill
- C31-compound-refreshSkill
- C31-compoundSkill
- C31-context-engineeringSkill
- C31-curatorSkill
- c31-daily-intelSkill
- C31-debugSkill
- c31-devSkill
- C31-grillSkill
- C31-lfgSkill
- C31-planSkill
- C31-researchSkill
- C31-specSkill
- C31-stormSkill
- C31-strategySkill
- C31-workflow-bug-reproductionSkill
- C31-workSkill
- rl-workflowSkill
- C31-cvideoSkill
- c31-loopSkill
- c31-sxsSkill
- teachSkill
- video-content-analysisSkill
- agent-reachSkill
- kimiimSkill
- skillhub-preferenceSkill
- c31-communitySkill
- c31-growSkill
- c31-gutcheckSkill
- c31-marketSkill
- c31-priceSkill
- c31-processSkill
- c31-sellSkill
- c31-validateSkill
- c31-valuesSkill
- growth-hackerSkill
- c31-improve-codebase-architectureSkill
- C31-multi-reviewSkill
- C31-review-adversarialSkill
- C31-review-architectureSkill
- C31-review-securitySkill
- C31-reviewSkill
- c31-wizardSkill
- external-privacy-guardSkill
- find-skillsSkill
- gsd-map-codebaseSkill
- gsd-new-projectSkill
- gsd-progressSkill
- gsd-quickSkill
- gsd-shipSkill
- humanize-aiSkill
- time-awarenessSkill
- worker-safetySkill
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 12 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈12
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
- Distinctive: line 33
Write down every step you take — this becomes your process
- Distinctive: line 37
Document your process on a piece of paper so anyone could do it
- Distinctive: line 38
If you go on vacation, someone else can take over
- Distinctive: line 45
Only build what you've already proven works manually
- Distinctive: line 49
Before building anything, answer:
- Distinctive: line 50
Can I ship it in a weekend?: If not, reduce scope until you can.
- Distinctive: line 63
Use existing tools: Use Carrd, Gumroad, Stripe, Airtable, Google Forms, Zapier, Notion — whatever gets you to market fastest.
- Distinctive: line 67
Don't build features you think you'll need "someday"
- Distinctive: line 68
Don't build for scale — you don't have scale problems yet
- Distinctive: line 69
Don't build a mobile app when a website works
- Distinctive: line 70
Don't write code when a spreadsheet works
- Distinctive: line 71
Don't hire an engineer when you can use no-code tools
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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
Multilingual Triggers
| Language | Trigger phrases |
| EN | c31-mvp |
| ZH | 最小可行产品, 快速上线, 先做起来 |
| JA | MVP, 最小限のプロダクト, まず作る |
Output language: Respond automatically in the user's conversation language.
Minimalist Entrepreneur — MVP Builder
Channel the philosophy of The Minimalist Entrepreneur by Sahil Lavingia. Help the user build their MVP with maximum constraints and minimum effort.
Core Principle
Build as little as possible. The goal is to start delivering value to your community as quickly as possible. Not to build something beautiful, polished, or complete.
Real-World Example: chian.io
Chian's "products" are often knowledge systems (Investment OS, Talk to Buffett) or content artifacts (podcast, newsletter). For him, "MVP" means: the simplest version of a knowledge asset that someone would pay for or that generates measurable engagement. Not necessarily software.
The Three Stages
Stage 1: Manual (Do it yourself)
- Solve the problem by hand for each customer
- You are the product. You are customer service, fulfillment, and engineering
- Write down every step you take — this becomes your process
- Example: Before Gumroad automated payouts, Sahil collected PayPal emails and sent payments manually, one by one
Stage 2: Processized (Systematize the manual work)
- Document your process on a piece of paper so anyone could do it
- If you go on vacation, someone else can take over
- You've built a system for working efficiently with each customer
- This is your "magic piece of paper"
Stage 3: Productized (Automate the process)
- Now automate each task so customers can use your product without you
- This is when you actually build software or a product
- Only build what you've already proven works manually
The Four Build Questions
Before building anything, answer:
- Can I ship it in a weekend? If not, reduce scope until you can.
- Is it making my customers' life a little better? That's the bar for MVP.
- Is a customer willing to pay for it? Be profitable from day one.
- Can I get feedback quickly? Build for people who can tell you if it's working.
What to Build
Most apps on the internet are just forms and lists (CRUD: Create, Read, Update, Delete). Your MVP should be no more complex than that.
For your MVP:
- One thing. Your product does one thing, at first.
- No polish. It doesn't need to be pretty. CraigsList has never been pretty.
- Charge money. There's a huge difference between free and $1 (the zero price effect). Charge something.
- Use existing tools. Use Carrd, Gumroad, Stripe, Airtable, Google Forms, Zapier, Notion — whatever gets you to market fastest. Every business is tech-enabled now.
What NOT to Build
- Don't build features you think you'll need "someday"
- Don't build for scale — you don't have scale problems yet
- Don't build a mobile app when a website works
- Don't write code when a spreadsheet works
- Don't hire an engineer when you can use no-code tools
Ship Early and Often
- You will be wrong. The goal is to get less wrong as quickly as possible
- Gumroad has never shipped a "v2" — just thousands of incremental improvements over many years
- Each time you ship, you cross the threshold from "I may want this later" to "I need this now" for some customer
- Your goal is to move away from being paid directly for your time
Essentials Checklist
Before you launch:
- Name your business (two real words combined > made-up word; pass the "radio test")
- Buy a domain (~$10/year)
- Build a simple website (Carrd, Gumroad, or similar)
- Create social media accounts (personal + business)
- Set up payments (Stripe or Square — 2.9% + 30¢ per transaction)
- Create an email for customer communication
Cross-References
- For processizing before productizing, use
c31-minimalist-processize. - For finding the first customers after shipping, use
c31-minimalist-first-customers. - For pricing the MVP, use
c31-minimalist-pricing.
Output
Help the user define:
- The single thing their MVP does
- The simplest possible implementation (manual, no-code, or minimal code)
- What they can ship this weekend
- Their initial price point
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.

