Community生產力與協作github.com

how-to

Turns a vague "I want to build X" idea from a NON-TECHNICAL person into a clear, plain-language plan — what pieces are needed and why, free vs. paid alternatives with real costs, and which legal/compliance things to check (privacy policy, GDPR/CCPA, payments, app store rules). Trigger this skill whenever the user types /how-to followed by their idea (e.g. "/how-to make a website for my pizzeria", "/how-to I want an app to book yoga lessons and get paid"), and ALSO whenever someone who is clearly not a developer describes wanting to build or launch something online (a site, app, shop, booking system, community, marketplace) and seems unsure what's actually involved, worried about cost, or asking "where do I even start" — even without using the /how-to command or technical vocabulary. Favor triggering this over answering directly when the request mixes a business idea with uncertainty about the technical/legal/cost side. Not for: users who are already developers asking a narrow...

how-to 是什麼?

how-to is a Claude Code agent skill that turns a vague "I want to build X" idea from a NON-TECHNICAL person into a clear, plain-language plan — what pieces are needed and why, free vs. paid alternatives with real costs, and which legal/compliance things to check (privacy policy, GDPR/CCPA, payments, app store rules). Trigger this skill whenever the user types /how-to followed by their idea (e.g. "/how-to make a website for my pizzeria", "/how-to I want an app to book yoga lessons and get paid"), and ALSO whenever someone who is clearly not a developer describes wanting to build or launch something online (a site, app, shop, booking system, community, marketplace) and seems unsure what's actually involved, worried about cost, or asking "where do I even start" — even without using the /how-to command or technical vocabulary. Favor triggering this over answering directly when the request mixes a business idea with uncertainty about the technical/legal/cost side. Not for: users who are already developers asking a narrow...

相容平台~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/dumitrescuvlad/how-to-skill/tree/HEAD/plugins/how-to/skills/how-to

Installed? Explore more 生產力與協作 skills: steipete/gemini, steipete/gh-issues, steipete/skill-creator · View all 6 →

在你喜歡的 AI 中提問

開啟一個已預先載入此 Agent Skill 的新對話。

說明文件


name: how-to description: Turns a vague "I want to build X" idea from a NON-TECHNICAL person into a clear, plain-language plan — what pieces are needed and why, free vs. paid alternatives with real costs, and which legal/compliance things to check (privacy policy, GDPR/CCPA, payments, app store rules). Trigger this skill whenever the user types /how-to followed by their idea (e.g. "/how-to make a website for my pizzeria", "/how-to I want an app to book yoga lessons and get paid"), and ALSO whenever someone who is clearly not a developer describes wanting to build or launch something online (a site, app, shop, booking system, community, marketplace) and seems unsure what's actually involved, worried about cost, or asking "where do I even start" — even without using the /how-to command or technical vocabulary. Favor triggering this over answering directly when the request mixes a business idea with uncertainty about the technical/legal/cost side. Not for: users who are already developers asking a narrow technical question (e.g. "how do I configure CORS on Express"), or requests to actually write code/configure infrastructure directly — this skill only produces the planning step, not the implementation.

How-To: from idea to plan

Why this skill exists

Non-technical people often abandon their idea not because it's hard, but because assistance jumps straight to the "how" (framework, hosting, deployment) taking for granted concepts like backend, GDPR, or recurring costs. This skill does the opposite: before writing a single line of code or recommending a specific tool, make the user understand WHAT is needed, WHY it's needed, HOW MUCH it costs (including free alternatives), and WHICH legal obligations apply — in the user's own words, not in technical jargon.

Don't treat the user as if they understand nothing: they simply don't have the vocabulary yet, not the intelligence. Explain, don't oversimplify.

Always respond in the same language the user wrote their request in.

Step 1 — Understand the idea

The input arrives as text after /how-to (e.g. "make a website for my pizzeria"). If it's vague or missing an important detail, ask at most 2-3 questions, ideally one at a time, always without unexplained jargon:

  1. What should people using this be able to do? (e.g. view a menu, order, book, pay, contact you, sign up...)
  2. How many people do you think will use it at first? (tens, hundreds, thousands per month) — needed to figure out whether free solutions are enough or something more robust is required.
  3. Will you be collecting people's data (email, phone, payments, accounts, addresses)?
  4. Do you already have a domain name, hosting, or a budget in mind, or are you starting from scratch?
  5. Where are you (and where are your users/customers mainly based)? This only matters to figure out which laws apply (e.g. EU → GDPR, California → CCPA). Never assume a jurisdiction without asking or without a clear signal in the request (see Common Pitfalls).
  6. Do you want just the plan today to follow at your own pace, or do you want hands-on help building it step by step afterward?

Skip any question already answered in the initial request. If the idea is already clear and complete, skip the interview and go straight to the plan, clearly flagging any assumptions you made.

Step 2 — Build the Plan

Always follow the structure in assets/plan-template.md. The fixed sections are:

  1. What you're building — a 1-2 sentence summary, in the user's own words, to confirm you understood correctly.
  2. The pieces you need — explain only the pieces relevant to THIS idea (not the whole glossary), using references/tech-glossary.md as a base. Explain each piece with "why you need it", not just its technical name.
  3. Your options, with real costs — for each non-trivial piece, present at least one free/near-free option (with its real limits) and one paid option (with the concrete benefit it unlocks), never just a list of product names without explaining the practical difference.
  4. Legal things to check — consult references/legal-triggers.md and mention ONLY the points that apply based on the user's answers (e.g. no GDPR note if they collect no data, no payment note if they sell nothing). Always visibly state that this is general orientation, not legal advice, and that for concrete situations (especially payments, sensitive data, minors) a professional opinion is worth getting.
  5. Concrete next steps — a numbered list of actions, where the first step must be small and doable today (e.g. "register this domain name" or "write out the menu items"), not a generic technical step like "configure the backend".

Step 3 — Offer to continue

Explicitly ask whether the user wants you to help with the hands-on build (choosing and setting up hosting, writing the first code, registering a domain, etc.) or whether they'd rather take the plan away and move at their own pace. If they want to continue, go one step at a time: propose the next decision to make, explain the options, wait for their answer, then move to the next step. Never bombard the user with several technical choices at once.

Tone and style

  • Never unexplained jargon: the first time you use a technical term, add a 5-10 word explanation in parentheses.
  • No endless lists of tools/products without context: 2-3 well-explained options beat 10 listed at random.
  • Be honest about the limits of free solutions (e.g. "X's free plan shows ads" or "past N users/month this won't be enough anymore") — inform, don't sell.
  • The plan must stay readable for someone who has never heard of hosting or backend: if you must choose between technical precision and clarity on a minor point, choose clarity and leave the deeper detail for when the user wants to move into actual implementation.

Common Pitfalls

  • Never assume a jurisdiction from the language the user types in. Someone writing in Italian or Spanish could be based anywhere; someone writing in English could be in the EU, the US, or elsewhere. Ask where the user (and their users) are based before citing specific laws like GDPR or CCPA, unless they already stated it. If they haven't answered and you must proceed with an assumption, label it explicitly as an assumption and say which laws you're applying because of it.
  • Don't flag legal obligations that don't apply. If the user collects no personal data at all (e.g. a pure informational page with no contact form), don't invent a GDPR or Privacy Policy requirement — say so.
  • Payment card data: never suggest the user (or you) handle raw card numbers directly, even "just to try it" — always route through a PCI-DSS compliant provider (Stripe, PayPal, etc.).
  • Sizing matters: don't recommend enterprise-grade infrastructure for a user expecting tens or low hundreds of users/month, and don't undersell a free tier's real limits (hidden ads, usage caps, missing custom domain) just to sound encouraging.
  • Already-technical users: if the request is clearly from someone who already knows the stack and just wants a scoping/legal checklist (not a beginner explanation), skip the glossary-style explanations and the beginner tone — give them the same structure, denser.

Last verified: 2026-11-15 (legal-triggers.md references current GDPR/CCPA/COPPA practice as of this date — re-verify periodically, rules and thresholds change).

Resources

  • references/tech-glossary.md — plain-language explanations of the most common technical concepts (frontend, backend, hosting, domain, database, API, CDN...). Consult it to learn how to explain a concept, don't copy it wholesale into the output.
  • references/legal-triggers.md — a table of "if your idea does X, then you probably need/should consider Y", organized by scenario (personal data, payments, cookies/analytics, minors, app store policies). Use it to decide WHAT to mention in the plan's legal section, not to give a definitive legal opinion.
  • assets/plan-template.md — the exact skeleton (headings and section order) to fill in for the final output.

相關技能