Works On My Machine
A skill suite that
learns from you.
A repeatable workflow for building software with AI. Ships with skills. Captures what you learn as golden specs. Gets better every time you use it.
Built for Claude Code. Designed to be forked.
$ git clone https://github.com/YOU/womm-skills ~/.womm-skills
01 — The Problem
AI workflows are still
being written.
AI-assisted development is barely two years old. The tooling exists but the process of going from idea to shipped software is still ad-hoc. Most people open a chat, type "build me X," and hope for the best.
$ claude "add stripe payments"
✓ Generated checkout page
✓ Added Stripe gem
✗ Skipped webhook verification
✗ Hardcoded API keys
✗ Missed redirect race condition
✗ No idempotent writes
3 hours debugging later...
Same mistakes next project.
$ claude /design-doc
What payment events need handling?
How should failed payments retry?
$ claude /implement
Reading: RAILS_STRIPE_INTEGRATION.md
✓ Webhook verification included
✓ Idempotent writes for race condition
✓ Customer Portal for billing mgmt
Shipped in 45 minutes.
Next project starts here.
02 — The Workflow
A repeatable process,
not a collection of prompts.
Each skill encodes a multi-step process with specific structure. Not "write me a plan" — a guided interview that asks the hard questions first, then produces artifacts at every step.
1. Interview — Deep conversation to explore the idea
Built into /design-doc. Asks the hard questions first.
2. Design Doc — Architecture, constraints, open questions
Structured document. Not a chat transcript.
3. Epic Breakdown — Stories, dependencies, risk ordering
Ship the riskiest thing first.
4. Implementation Plan — Patterns, files, decisions
Technical approach for a single epic.
5. Implement — Execute stories one by one
Tests and commits between each story.
6. Capture — Write down what you learned
Golden spec: what worked, what didn't, the gotchas.
7. Loop — Next project starts with everything you know
New problems feed back into step 1.
Process
/design-doc Interview, explore, produce a structured design document /epic-breakdown Break the design into epics with dependencies and risk ordering /implementation-plan Technical approach for one epic — patterns, files, decisions /implement Execute stories with tests and commits between each /golden-spec-create Capture what you learned — what worked, what didn't, gotchas Fork Lifecycle
/about Overview of the suite — what's included and how it works /upstream-sync Pull updates from the upstream repo into your fork /fork-share Share your golden specs or skills back to the community Example: what /design-doc produces
# Stripe Integration — Design Doc
## Architecture
Plans page → Stripe Checkout (hosted) → Webhook
activates subscription → Customer Portal for mgmt
## Key Decisions
• Webhooks are source of truth (not redirect)
• 5 webhook events to handle
• Idempotent writes for redirect/webhook race
## Open Questions
• Metered billing or flat rate?
• Free tier or trial-only?
• Grace period on failed payments?
03 — Golden Specs
Knowledge that compounds.
Golden specs are documents written after solving a real problem. What worked, what didn't, and the gotchas you'd want to know next time. Flat markdown files — write one and every project sees it immediately. Replace the included examples with your own as you build.
Excerpt from a real golden spec:
## What Worked
• Stripe Checkout (hosted) → no custom payment UI
• Webhooks as source of truth, not success redirect
• Customer Portal for payment methods + cancellation
## Gotchas
• button_to uses Turbo fetch by default — needs
data: { turbo: false } for Stripe redirect
• current_period_start/end moved in API 2025-03-31
• Must handle race: redirect arrives before webhook
## Testing
• Generate valid webhook sigs with OpenSSL::HMAC
• Stub Stripe API calls, never hit real endpoints
• 4 secrets per env in AWS Secrets Manager
04 — Forking
Fork it. Make it yours.
It's cheaper to fork and customize than to submit a PR and wait for review. WOMM Skills assumes every fork diverges quickly. That's expected. That's the design.
~/.womm-skills/
skills/
design-doc.md — modified for your team's process
deploy-checklist.md — new skill you added
golden-specs/
NEXTJS_VERCEL_DEPLOY.md — your stack
PLANETSCALE_MIGRATIONS.md — your gotchas
STRIPE_CONNECT_MARKETPLACE.md — your patterns
CLAUDE.md — your stack, your preferences
Skills
Installed via Claude Code's plugin system. Cached. Available everywhere. Modify them to fit your workflow.
Golden Specs
Flat markdown files, read directly from disk. Write a new one and every project sees it immediately. No reinstall.
Fork Constellation → See what others have built with their forks.
05 — Get Started
Minutes to set up.
Gets better forever.
# 1. Fork on GitHub, then clone
$ git clone https://github.com/YOU/womm-skills ~/.womm-skills
# 2. Add upstream for updates via /upstream-sync
$ cd ~/.womm-skills
$ git remote add upstream https://github.com/works-on-your-machine/womm-skills
# 3. Register as a local marketplace
$ claude plugin marketplace add ~/.womm-skills
# 4. Install the plugin
$ claude plugin install womm-skills@womm-skills
# Re-run this after editing skills to refresh the cache
# 5. Add golden specs to your global config
# Paste this into ~/.claude/CLAUDE.md:
Reference golden specs at ~/.womm-skills/golden-specs/
for architectural patterns and implementation guidance.
# 6. Grant path access
# Add to ~/.claude/settings.json under allowedPaths:
"~/.womm-skills"
✓ Done.
Skills work everywhere. Golden specs grow over time.
Try /design-doc in your next project.
06 — For Teams
Want this for your team?
I work with engineering teams to set up agentic coding workflows and build custom skill suites tailored to their stack.
1:1 and small group training
Hands-on sessions teaching your team to build effectively with AI coding tools.
Custom skill suite setup
Fork and customize WOMM Skills for your stack, or build a skill suite from scratch.
Golden spec workshops
Turn your team's tribal knowledge into a growing knowledge base that accelerates every project.