A collection of Claude Code skills for product and design workflows.
| Skill | Purpose | Trigger examples |
|---|---|---|
| pm-craft | PM workflow — SDD-first, spec-before-code, plus meeting minutes from raw transcripts | 寫規格、寫 spec、寫需求、user story、handoff、整理會議記錄、meeting minutes |
| design-craft | HTML-native UI design — prototypes, slides, infographics | 做原型、做 mockup、幫我設計、做簡報 |
| pptx-craft | Style-driven PowerPoint — 7 distinct presets, anti-AI checklist | distinctive deck, editorial slides, swiss-style, bento grid, don't make it look AI |
npx github:MaxCHL/craft-skillsInstalls both skills into ~/.claude/skills/. Requires Claude Code.
A skill for the full PM document lifecycle, built on Spec-Driven Development (SDD) principles.
Supported documents
| Document | When to use |
|---|---|
| Opportunity Brief | New problem / idea validation |
| Epic | Feature set planning, roadmap unit |
| Product Spec | GWT acceptance criteria, engineering contract |
| User Story | Story breakdown, sprint-level tasks |
| Acceptance Checklist | PM AC + Engineering DoD |
| Handoff Doc | Design → Engineering handoff |
| Meeting Minutes | Turn raw meeting transcripts (STT output) into multi-dimensional minutes: TL;DR, Executive Summary, Detailed Notes, Decisions & Action Items |
Meeting Minutes — four built-in templates with routing keywords:
| Template | Use for |
|---|---|
template-product.md |
Product / business decision meetings (roadmap, OKR, pricing) |
template-one-on-one.md |
1-on-1s and manager check-ins (privacy-aware) |
template-customer-interview.md |
User research and customer interviews (JTBD framework) |
template-technical.md |
Architecture / technical decision meetings (ADR-style) |
Includes a 3-layer annotation system for STT corrections ([需確認] / [推測:X] / [unclear]),
a 6-phase workflow (Intake → Preprocess → Segment → Extract → Assemble → Verify & Save),
and saves output to ./meeting-notes/YYYY-MM-DD-{slug}.md by default.
Core principles
- Spec before code — no implementation discussion until spec is agreed
- GWT as the contract — Given/When/Then bridges PM, Design, and Engineering
- Ambiguity is a blocker — surface open questions before writing specs
- Non-Goals are first-class — what you won't do is as important as what you will
- Meeting minutes are evidence — preserve dissent, mark uncertainty, never invent metadata
A skill for high-fidelity HTML prototypes, interactive mockups, presentation slides, data infographics, and design critique — all in native HTML/CSS/JS.
Supported output types
| Output | When to use |
|---|---|
| Prototype / Mockup | Feature UI, interactive flows |
| Presentation slides | Decks, pitches, reports |
| Infographic | Data visualization, dashboards |
| Design critique | Review existing UI for issues |
| Style exploration | T1–T11 Timeless + R1–R9 Trending styles |
20 design styles
| Set | Count | Codes |
|---|---|---|
| Timeless | 11 | T1–T11 |
| Trending | 9 | R1–R9 |
A skill for distinctive PowerPoint decks that don't look AI-generated. Sits on top of the
standard pptx skill (which handles file ops) and adds a style-driven design layer.
7 style presets
| Style | Register |
|---|---|
| Swiss / International | rigorous, systematic, neutral |
| Editorial / Magazine | narrative, premium, long-form |
| Bento Grid | modular, product-launch, dense-but-clean |
| Brutalist | experimental, provocative, anti-corporate |
| Big Type / Manifesto | keynote, single-idea-per-slide |
| Data-dense / Analytical | Tufte-grade, numbers-heavy |
| Monograph / White-paper | academic, document-as-deck |
Core principles
- Style first, layout second, content third — pick the visual register before opening an editor
- Rhythm beats symmetry — never reuse the same layout primitive on adjacent slides
- Anti-AI checklist is the acceptance gate — 15 AI tells must be absent before a deck is "done"
Includes: 4 executable python-pptx recipes (Swiss tech talk, Editorial pitch, Bento launch,
Brutalist workshop), 16 layout primitives with helper functions, and a 15-point anti-AI QA checklist.
# Try a recipe locally
cd ~/.claude/skills/pptx-craft
uv venv && uv pip install python-pptx
.venv/bin/python -m recipes.tech_talk_swisspptx-craft is brand-neutral but supports brand color overlays via a sibling-skill convention.
Any installed Claude Code skill named <brand>-pptx-craft is auto-detected by pptx-craft's
Step 0 and offered (default: No) as an optional color overlay.
~/.claude/skills/
├── pptx-craft/ # base (this repo)
├── acme-pptx-craft/ # any brand extension you build
└── ...
Each extension provides only:
references/brand-tokens.md— hex / RGB / contrast / usage ratiosreferences/style-overlays.md— how the brand's colors map onto each of pptx-craft's 7 styles
Layout, typography, primitives, grid, and the anti-AI checklist still come from pptx-craft. This keeps brand-specific colors out of the public repo while letting any team layer their CI on top of the same proven structure.
pm-craft and design-craft are designed to work together:
pm-craft (Product Spec) ──────→ design-craft (prototype)
←────── (prototype feeds back into GWT coverage)
When a spec needs UI validation, pm-craft emits a design-craft handoff block.
When a prototype is ready, design-craft hands back to pm-craft to formalize behavior in GWT.
MIT