跳到正文
cccskills
免费在 GitHub 公开

make-playbook

Indie maker playbook for bootstrapped apps inspired by Pieter Levels' MAKE: The Indie Maker Blueprint. Use when a user is starting or sizing an app idea, choosing what to build next, building a minimal product, preparing a launch, diagnosing stalled growth, deciding pricing or monetization, automating operations, maintaining a per-app MAKE.md tracker, or evaluating whether to sell a product.

中文简介正在准备中。当前显示原文说明。

查看安装方法

包含的文件(12)

  • SKILL.md3.6 KB
  • agents/openai.yaml227 B
  • README.md852 B
  • references/automate.md4.5 KB
  • references/build.md5.2 KB
  • references/ethos.md3.7 KB
  • references/exit.md6.3 KB
  • references/grow.md4.6 KB
  • references/idea.md6.6 KB
  • references/launch.md5.3 KB
  • references/monetize.md6.2 KB
  • templates/make-tracker.md2.8 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

MAKE Playbook

Use this skill as a stage-specific operating system for solo and bootstrapped software products. It is an original checklist and diagnostic system inspired by Pieter Levels' MAKE: The Indie Maker Blueprint; it is not a substitute for the book. Keep attribution intact when reusing the references.

Stage Model

Idea -> Build -> Launch -> Grow -> Monetize -> Automate -> Exit

Always treat references/ethos.md as the standing frame for bootstrapping, persistence, and ethical constraints. Load it once per session when it has not already been read. Its constraints override stage tactics: no fake engagement, fake reviews, dishonest growth hacks, user-hostile monetization, or selling user data.

Workflow

  1. Identify the app and current stage. If the user has not named the app or the current situation, ask one concise question. If a MAKE.md file exists in the project root, read it first because it may already contain this state.
  2. Load the current stage reference. Load one adjacent stage when the question is on a boundary, such as build/launch for "is this ready to launch" or grow/monetize for "traffic but no revenue."
  3. Apply the reference to the user's specific app. Use the diagnostic questions at the end of each reference to get missing facts, then convert the checklist into a concrete action list for this product and this week.
  4. Push toward shipping. When the user is stuck in abstraction, give the smallest next action that creates market evidence.
  5. Offer to create or update a tracker. For a new app, copy templates/make-tracker.md to the project root as MAKE.md and fill in what is known. For an existing MAKE.md, update the relevant section as decisions are made.
  6. End with action, not advice. Close every response with a short, time-boxed next step unless the user explicitly requested only analysis.

Reference Routing

User situationLoad
"I do not know what to build", idea feels broad, niche is unclearreferences/idea.md
Stuck choosing stack, overbuilding, outsourcing before proofreferences/build.md
Built something but nobody knows, launch plan is vaguereferences/launch.md
Traffic plateaued, retention unclear, growth depends on paid adsreferences/grow.md
Users but no revenue, pricing/model is unclearreferences/monetize.md
Revenue exists but founder is the bottleneckreferences/automate.md
Acquisition offer, sale timing, valuation, or diligence questionsreferences/exit.md

Tracker Handling

  • Prefer MAKE.md in the project root for per-app state.
  • Preserve user-written sections and update only the stage details relevant to the conversation.
  • Keep the tracker factual: current stage, niche, decisions, launch dates, pricing, repeat tasks, and post-mortem notes.
  • When copying the template, replace obvious placeholders rather than leaving a blank scaffold if the conversation already contains the answers.

Response Shape

For most requests, return:

  1. Stage diagnosis in one or two sentences.
  2. The key constraints or evidence gaps.
  3. A numbered plan of concrete actions.
  4. Tracker updates made or recommended.
  5. The next action to take today or this week.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Transform saved links, papers, articles, posts, videos, and reference collections into approachable AI teaching artifacts for later study. Use when a user wants to queue learning material, create a readable explanation from a source, teach a paper or post step by step, or run an interactive tutor that validates understanding over multiple sessions.

中文简介正在准备中。当前显示原文说明。

tamdogood/builder-essential-skills2262026年8月17日 更新

Inspect an unfamiliar repository, turn a focused Markdown behavior scenario into a deterministic test in the repository's native test stack, run it, and preserve traceability between intent and code. Use when asked to add scenario tests, compile acceptance criteria or Given/When/Then Markdown into executable tests, reproduce a user-visible regression, or convert a narrow workflow specification into stable web, API, CLI, desktop, or mobile interaction coverage. Do not use for broad exploratory journeys or agent-judged smoke tests.

中文简介正在准备中。当前显示原文说明。

tamdogood/builder-essential-skills2262026年8月17日 更新

Apply a disciplined engineering workflow to any code change. Use whenever implementing a feature, fixing a bug, or refactoring — before writing code, not after. Walks orient → baseline → smallest change → test → verify → self-review, and enforces language-agnostic hard gates (don't mass-reformat, keep the linter and type-checker clean, keep the build and tests green, make interface changes additive, protect security invariants).

中文简介正在准备中。当前显示原文说明。

tamdogood/builder-essential-skills2262026年8月17日 更新

Create truthful, human-centered marketing campaigns for an app or product, including positioning, channel copy, original artwork, editable layouts, README banners, and selective website integration. Use when asked to make launch materials, promotional artwork, social assets, campaign kits, ads, or marketing content from an existing product; to adapt a visual reference without copying it; or to add approved campaign art to product surfaces. Do not invent claims, fake UI, publish, deploy, or replace product proof without explicit evidence and authorization.

中文简介正在准备中。当前显示原文说明。

tamdogood/builder-essential-skills2262026年8月17日 更新

Create or update a complete repository skill from a user's idea, including the workflow instructions, references, scripts or assets, agent metadata, skill-card artwork, cinematic banner artwork, README links, discovery metadata, and validation. Use when the user asks to create a new skill, add a skill to this collection, turn a workflow into a reusable skill, or make a skill's documentation and artwork consistent with the repository.

中文简介正在准备中。当前显示原文说明。

tamdogood/builder-essential-skills2262026年8月17日 更新

lead

免费

Use when the user asks to run or continue an autonomous build: turn a goal into an approved plan, dispatch implementation and review agents, and finish with one pull request. The Lead is a provider-neutral orchestrator that makes decisions but never writes code, edits files, runs commands, or reviews its own work.

中文简介正在准备中。当前显示原文说明。

tamdogood/builder-essential-skills2262026年8月17日 更新

查看 tamdogood 的全部技能

报告此技能的问题