CommunityCoding & Developmentgithub.com

jlvsebastian-stack/product-craft

Co-create a substantive digital product in the creator's chosen format from their own expertise, approved niche, offer, outline, language, and design. Use after the discovery interview; do not borrow another author's personalization or treat production materials as completed media.

What is product-craft?

product-craft is a Claude Code agent skill that co-create a substantive digital product in the creator's chosen format from their own expertise, approved niche, offer, outline, language, and design. Use after the discovery interview; do not borrow another author's personalization or treat production materials as completed media.

Works with~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/jlvsebastian-stack/product-studio-pilot/tree/main/skills/product-craft

Installed? Explore more Coding & Development skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →

Ask in your favorite AI

Open a new chat with this agent skill pre-loaded.

Documentation

Create the chosen product through conversation

Use the creator's confirmed interview material, wisdom, decisions, stories, exceptions, voice, audience, outcome, market observations, and approved outline. Shared teaching and design methods are reusable; personal details and voice come only from this creator. Do not fill a knowledge gap with invented authority.

Match the deliverable to its format:

  • Guide: complete explanations, decisions, actionable steps, useful worked examples, limits, and an application path.
  • Workbook: instruction, worked examples, meaningful exercises, useful result checks, and space to work. Apply workbook-craft when it is available.
  • Template kit: actual reusable templates, instructions, a filled example, and an explanation of how to adapt them. A list of template ideas is insufficient.
  • Checklist: specific observable checks, when and how to use them, and decision or recovery guidance where a check fails.
  • Spreadsheet, calculator, or tracker: define the actual task, inputs, units, assumptions, calculation logic, outputs and usage instructions. This local text exporter does not create working spreadsheets or connect Google accounts. A specification or screenshot is not the finished spreadsheet. Explain the missing capability and keep the specification available for a separate creator-chosen tool; never label it complete or force it into a document export.
  • Course or workshop materials: substantive teaching, worked demonstrations, learner activities and answer checks, plus facilitator or production notes where needed. Distinguish these files from a recorded or delivered course.

Work one meaningful section at a time. Agree on and obtain approval of a representative sample before expanding. Ask for missing experience, case, reasoning or exception, draft the section, get feedback, refine it, and obtain approval before the next section. approvedDraft must remain an exact prefix unless revisionIntent is true; do not normalize its punctuation or whitespace. With explicit revision intent change only the requested section; the UI retains an undo checkpoint. Do not generate an entire product from a vague topic or a series of unreviewed sections.

Write directly to the final reader in the selected language and voice. Keep specific judgments and natural wording rather than smoothing them into generic AI prose. Label illustrative examples. Never invent customer outcomes, credentials, demand, research, sales, or testimonials.

Keep a complete accumulated manuscript in brief.productDraft using readable Markdown. At outline stage use brief.outline instead; do not mislabel an outline as a manuscript. During creation, keep previously written and approved material and add or revise only the section under discussion. The chat reply explains the current decision and asks one useful next question; the manuscript contains the reader-facing product, not backstage chat or AI instructions.

At design stage, agree on language, tone, visual feeling, creator author information, print/screen use, accessibility needs and a representative sample. Use the supplied approved preferences as style context, not invented project facts. The local exporter creates PDF, Word, Markdown and Canva-compatible PowerPoint. Do not promise native Canva/Google files, generated images, live synchronization or media that has not been produced.

Keep brief.design as the overall visual direction. When useful, brief.designPlan is a JSON string {"sections":[{"heading":"Exact manuscript heading","layout":"teaching|example|exercise|checklist|summary|steps","purpose":"Short reader purpose"}]}. Choose varied layouts for actual reader tasks, use exact section headings and retain all manuscript content. Metadata is a design aid, not a substitute for prose, templates, examples or exercises.

At completion, always offer one or two useful optional companion products grounded in the confirmed buyer's task and current method, using a different format from the primary product. Explain why each fits and wait for the creator's choice; recommendations are not included or already-created extras. Always provide brief.listingCopy describing actual primary-product contents, audience, application and honest limits. If essential buyer/task/method/format/manuscript evidence is missing, ask for it instead of making up a recommendation or listing fact. Prices, proof, results and testimonials must not be invented. Keep listing copy and private profile instructions outside the reader manuscript.

At review, challenge generic filler, repeated advice, unsupported claims, incomplete exercises or templates, missing reader instructions, weak examples, and inconsistent design. A complete asset can be offered for the creator's sale review; it does not establish that the product will sell.

Related Skills