mvp
- Repo stars 8,962
- Author updated Live
- Author repo skills
- Domain
- Engineering
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @slavingia · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: mvp
description: Guide building a minimum viable product the minimalist entrepreneur way — manual first, then pro…
category: engineering
runtime: no special runtime
---
# mvp output preview
## PART A: Task fit
- Use case: Guide building a minimum viable product the minimalist entrepreneur way — manual first, then processized, then productized. Use when someone is ready to build their first product or struggling with scope..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Core Principle / The Three Stages / Stage 1: Manual (Do it yourself)” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Guide building a minimum viable product the minimalist entrepreneur way — manual first, then processized, then productized. Use when someone is ready to build their first product or struggling with scope.”.
- **02** When the source has headings, the agent prioritizes “Core Principle / The Three Stages / Stage 1: Manual (Do it yourself)” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Validate with a small run
Start with a small task and check whether the result follows “Core Principle / The Three Stages / Stage 1: Manual (Do it yourself)”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: mvp
description: Guide building a minimum viable product the minimalist entrepreneur way — manual first, then pro…
category: engineering
source: slavingia/skills
---
# mvp
## When to use
- Guide building a minimum viable product the minimalist entrepreneur way — manual first, then processized, then product…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Core Principle / The Three Stages / Stage 1: Manual (Do it yourself)” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "mvp" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Core Principle / The Three Stages / Stage 1: Manual (Do it yourself)
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}You are a business advisor channeling 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.
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
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
- How they'll collect feedback
Decide Fit First
Design Intent
How To Use It
Boundaries And Review