This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
This is a collection of 62 agent skills for Claude, Claude Code, Claude Cowork, Codex, Cursor, OpenClaw, Hermes Agent and other agentskills.io-compatible agents. Skills provide specialized domain knowledge and frameworks for specific use cases (UX design, marketing, product strategy, sales, operations, positioning, virality, code quality, systems architecture, etc.). Twelve of them are metaskills — guided journeys that orchestrate the other skills step by step toward a goal.
skills/
├── .claude-plugin/
│ └── marketplace.json # Claude plugin marketplace — SOURCE OF TRUTH for collections/versions
├── {skill-name}/
│ ├── SKILL.md # Main skill file with YAML frontmatter + markdown instructions
│ └── references/ # Supporting reference files (optional)
│ └── *.md
├── scripts/ # sync-ide-skills.sh, generate-codex-plugins.sh, sync-marketplace-versions.sh
├── .github/workflows/ # CI: syncs marketplace versions to the GitHub release
├── CLAUDE.md # This file
├── README.md # Skill catalog with descriptions and installation instructions
│
│ # ---- everything below is GENERATED (do not hand-edit) ----
├── .claude/ .cursor/ .windsurf/ .pi/ # per-IDE skills/ symlink mirrors (sync-ide-skills.sh)
├── .agents/
│ ├── skills/ # flat skill symlinks for Codex / .agents-convention agents
│ └── plugins/marketplace.json # Codex plugin marketplace (mirrors .claude-plugin/)
└── plugins/{collection}/ # Codex plugins: .codex-plugin/plugin.json + skills/ symlinks
The Codex plugin standard (plugins/ + .agents/plugins/marketplace.json) is generated from .claude-plugin/marketplace.json by scripts/generate-codex-plugins.sh — same 10 collections, same skill membership, versions tracked automatically. Never hand-edit the generated trees.
| Category | Skills |
|---|---|
| Metaskills | create-business, create-website, create-app, improve-business, improve-website, improve-app, grow-business, grow-website, grow-app, improve-code-quality, remove-technical-debt, design-code-architecture |
| UX/Design | refactoring-ui, ios-hig-design, ux-heuristics, hooked-ux, improve-retention, web-typography, top-design, design-everyday-things, lean-ux, microinteractions, steve-jobs-design-review |
| Marketing/CRO | cro-methodology, storybrand-messaging, scorecard-marketing, contagious, one-page-marketing |
| Sales/Influence | influence-psychology, predictable-revenue, made-to-stick, hundred-million-offers |
| Product/Innovation | jobs-to-be-done, lean-startup, design-sprint, inspired-product, continuous-discovery, 37signals-way |
| Product/Strategy | mom-test, negotiation, monetizing-innovation, lean-analytics |
| Strategy/Growth | crossing-the-chasm, blue-ocean-strategy, traction-eos, obviously-awesome, good-strategy-bad-strategy, cold-start-problem |
| Code Quality | clean-code, refactoring-patterns, software-design-philosophy, pragmatic-programmer, domain-driven-design, working-with-legacy-code |
| Systems/Architecture | ddia-systems, system-design, clean-architecture, release-it, high-perf-browser, team-topologies |
| Team/Management | drive-motivation, high-output-management |
Each skill has a SKILL.md with this structure:
---
name: skill-name
description: 'Framework description based on Author''s "Book Title". Use when you need to: (1) first use case, (2) second use case, (3) third use case.'
license: MIT
metadata:
author: wondelai
version: "1.0.0"
---
# Skill Title
Intro paragraph about the framework.
## Core Principle
**Bold opening statement.** Foundation paragraph.
## Scoring
**Goal: 10/10.** Score with a reproducible rule tied to the Quick Diagnostic that spans the full 0-10 — e.g. `score = round(rows passed / N × 10)` — then spell out the 9-10 / 7-8 / 5-6 / <=3 bands. (Don't write "1 point per row" when there are fewer than 10 rows: the top band becomes unreachable.)
## Framework Sections
### 1. First Section
**Core concept:** ...
**Why it works:** ... (only when it states a real mechanism — cut if it just restates the Core concept)
**Key insights:** (bullet list of non-obvious points only)
**Product applications:** (table: Context | Application | Example)
**Copy patterns:** (bullet list with quoted examples)
**Ethical boundary:** ... (only when a concrete, behavior-changing constraint — omit platitudes the model already follows)
See [references/file.md](references/file.md) when <situation> — <what it adds> (inline when-to-read pointer, at the point of need; no trailing roster)
## Common Mistakes
(Table: Mistake | Why It Fails | Fix)
## Quick Diagnostic
(Table: Question | If No | Action)
## Further Reading
(Amazon links with ?tag=wondelai00-20)
## About the Author
(Author bio)name: Unique identifier (lowercase, hyphens for spaces, max 64 chars)description: What the skill does and when to use it (max 1024 chars). Use numbered use cases:(1) ..., (2) ..., (3) ...
license: License name (we use MIT)metadata.author: Author/organization name (we usewondelai)metadata.version: Semantic version
The YAML frontmatter description field is critical for skill discovery - it should include keywords and trigger phrases that help match user requests to the skill. Single quotes in YAML values must be escaped by doubling them ('').
The 12 metaskills (create/improve/grow × business/website/app, improve-code-quality, remove-technical-debt, design-code-architecture) are orchestrators, not book skills — do not force-fit the book template above (no Scoring, Further Reading, or About the Author). Their SKILL.md sections, in order: intro → ## Core Principle (the journey's sequencing law) → ## Journey Map (Phase | Skill | Question it answers | Artifact) → ## Operating Rules (rules 1–7 word-identical across all 12; rule 8 is the journey-specific guardrail) → ## Intake → ## Phases (each phase has six fields: Purpose, Brief (fallback), Invoke, Decide with the user, Artifact, Done when) → ## Optional Phases → ## Common Mistakes → ## Completing the Journey. Descriptions follow a 5-sentence formula whose 4th sentence routes to sibling metaskills (negative triggers) — keep the routing mutually consistent when editing. Metaskills write UPPERCASE artifacts into the user's project docs/ folder; the canonical skeletons and section headings live in docs/ARTIFACT-REGISTRY.md — artifact headings quoted in phases must match it, and each metaskill's references/artifact-templates.md copies the skeletons it creates.
- Create a new folder:
{skill-name}/ - Create
SKILL.mdwith YAML frontmatter (name,description) and skill instructions - Add
references/folder with supporting.mdfiles (each 1500-3000 words) - Add the skill to
README.md:- Add to "Via skills.sh" installation list
- Add row to "Available Skills" table
- Add "Skill Details" section (description, About the author, Use when, Example prompts)
- Add to "Copyright & Disclaimer" section
- Add the skill's path to
.claude-plugin/marketplace.jsonunder the appropriate plugin collection (add the./skill-nameentry only — do not hand-pick a version; see Versioning Policy) - Run
scripts/sync-ide-skills.sh— regenerates the IDE mirrors (.claude/.cursor/.windsurf/.pi/.agents) and the Codex plugin marketplace (plugins/+.agents/plugins/). These are generated; never hand-edit them.
/plugin marketplace add wondelai/skills
/plugin install product-strategy@wondelai-skills # Jobs to Be Done, Negotiation, Mom Test, Monetizing Innovation, Lean Analytics
/plugin install ux-design@wondelai-skills # Refactoring UI, iOS HIG, UX Heuristics, Hooked, Improve Retention, Web Typography, Top Design, Design of Everyday Things, Lean UX, Microinteractions, Steve Jobs Design Review
/plugin install marketing-cro@wondelai-skills # CRO, StoryBrand, Scorecard Marketing, Contagious, 1-Page Marketing
/plugin install sales-influence@wondelai-skills # Influence Psychology, Predictable Revenue, Made to Stick, $100M Offers
/plugin install product-innovation@wondelai-skills # Lean Startup, Design Sprint, Design of Everyday Things, Inspired, Continuous Discovery
/plugin install strategy-growth@wondelai-skills # Crossing the Chasm, Blue Ocean Strategy, Traction/EOS, Obviously Awesome, Good Strategy Bad Strategy, Cold Start Problem
/plugin install team-motivation@wondelai-skills # Drive (Autonomy, Mastery, Purpose), High Output Management
/plugin install code-craftsmanship@wondelai-skills # Clean Code, Refactoring Patterns, Software Design Philosophy, Pragmatic Programmer, DDD, Working with Legacy Code
/plugin install systems-architecture@wondelai-skills # DDIA, System Design, Clean Architecture, Release It!, High Performance Browser Networking, Team Topologies
/plugin install metaskills@wondelai-skills # 12 guided journeys: create/improve/grow × business/website/app + improve-code-quality, remove-technical-debt, design-code-architecturenpx skills add wondelai/skills # All skills
npx skills add wondelai/skills/{skill-name} # Individual skillSkills use semantic versioning (MAJOR.MINOR.PATCH):
- MAJOR: Breaking changes or complete rewrites
- MINOR: New features, significant enhancements, new sections
- PATCH: Bug fixes, typo corrections, small clarifications
Auto-increment rule: When modifying a skill's SKILL.md or its references/ files, always bump the version in the frontmatter:
- Content addition/enhancement → bump MINOR (e.g.,
1.0.0→1.1.0) - Small fix/typo → bump PATCH (e.g.,
1.1.0→1.1.1)
Example:
metadata:
author: wondelai
version: "1.1.0"The versions in .claude-plugin/marketplace.json (top-level metadata.version and every plugins[].version) are not hand-edited. They are auto-synced to the latest GitHub release by .github/workflows/sync-marketplace-version.yml, which runs scripts/sync-marketplace-versions.sh on each published release and commits the result to main. To ship: bump the affected skills' SKILL.md versions, merge, then publish a vX.Y.Z GitHub release — the workflow sets all marketplace versions to X.Y.Z. To sync without a release, run scripts/sync-marketplace-versions.sh X.Y.Z locally.
Commit directly to main.