Skip to main content
ClaudeWave

Claude Code Skills · page 47

Individual Claude Code skills mined from every repository in the directory: each SKILL.md, installable with one command, with its full definition and the repository's trust signals.

13,377 skills1-command install
  1. STATE.md reading, writing, and field-level updates. Provides cross-session state persistence via .planning/STATE.md with structured fields for current task, completed phases, blockers, decisions, and quick tasks.

  2. Template loading, variable filling, and scaffolding for all GSD artifacts. Manages 22+ templates covering every document type in the GSD system, from PROJECT.md to milestone archives.

  3. Plan structure validation, phase completeness checks, reference integrity verification, and artifact existence confirmation. Provides the structured verification layer ensuring GSD artifacts are well-formed and complete.

  4. Urgent issue classification, root cause analysis, and fast-path routing for production hotfixes

  5. Capture, validate, query, and sync architectural patterns and design decisions in the knowledge graph

  6. Review designs, products, and features with Steve Jobs'' standards: ruthless simplicity, focus, and end-to-end excellence. Use when the user mentions "Steve Jobs review", "design review", "product review", "what would Steve do", "insanely great", "simplify this product", "too many features", "product taste", or "saying no". Also trigger when critiquing a UI, feature, or roadmap for focus and simplicity, when cutting scope to the essential, or when pressure-testing the complete experience from first run to daily use. Covers the simplicity audit, the no list, design-is-how-it-works, end-to-end experience ownership, demo culture, and a Jobs-style review protocol with binary verdicts. For visual design fundamentals, see refactoring-ui. For usability audits, see ux-heuristics. For detail polish, see microinteractions.

  7. Start and scale networked products using Andrew Chen''s "The Cold Start Problem" framework for network effects. Use when the user mentions "network effects", "chicken and egg", "cold start", "two-sided marketplace", "atomic network", "hard side", "liquidity", "critical mass", "invite-only launch", or "come for the tool stay for the network". Also trigger when launching a marketplace, social, or collaboration product that is worthless without other users, deciding launch sequencing and seeding tactics, or diagnosing stalled network growth or degradation at scale. Covers the five stages: the cold start, the tipping point, escape velocity, hitting the ceiling, and the moat. For word-of-mouth virality, see contagious. For habit-driven retention, see hooked-ux.

  8. Formulate and audit real strategy using Richard Rumelt''s "Good Strategy Bad Strategy": an honest diagnosis, a guiding policy, and coherent action instead of goals, vision, and wishful thinking. Use when the user mentions "good strategy bad strategy", "strategy kernel", "diagnosis guiding policy coherent action", "our strategy is just goals", "strategic planning", "mission vs strategy", "review my strategy", or "annual plan". Also trigger when auditing strategy docs or pitch decks for fluff, turning goal lists into real strategy, formulating strategy for a product or company, or identifying leverage and proximate objectives. Covers the kernel of strategy, bad-strategy detection, and sources of power. For product positioning, see obviously-awesome. For creating uncontested markets, see blue-ocean-strategy.

  9. Manage for output using Andrew S. Grove''s "High Output Management": a manager''s output is their organization''s output, raised by choosing high-leverage activities. Use when the user mentions "high output management", "managerial leverage", "one-on-ones", "1:1 agenda", "OKRs", "performance review", "task-relevant maturity", "delegation", "meeting overload", or "new manager". Also trigger when structuring a manager''s calendar and meeting cadence, designing team metrics and indicators, running planning processes, coaching managers on delegation and training, or preparing and auditing performance reviews. Covers output-focused management, production principles, leverage, meetings as the medium of management, decisions, OKRs, and task-relevant maturity. For intrinsic motivation design, see drive-motivation. For a company-wide operating system, see traction-eos.

  10. Choose and audit startup metrics using Alistair Croll and Benjamin Yoskovitz''s "Lean Analytics: Use Data to Build a Better Startup Faster". Use when the user mentions "what metrics should we track", "KPIs", "north star metric", "One Metric That Matters", "OMTM", "vanity metrics", "analytics dashboard", "DAU/MAU", "churn benchmark", or "measure product-market fit". Also trigger when choosing metrics for a startup or feature, auditing dashboards for vanity metrics, setting metric targets and baselines, or instrumenting a product by business model and stage. Covers good-vs-vanity metrics, the One Metric That Matters, metrics by business model, the five startup stages, and benchmarks with lines in the sand. For the build-measure-learn loop itself, see lean-startup. For fixing activation and retention, see improve-retention.

  11. Design products and pricing around validated willingness to pay using Madhavan Ramanujam & Georg Tacke''s "Monetizing Innovation". Use when the user mentions "pricing", "how much should we charge", "willingness to pay", "pricing page", "pricing tiers", "packaging", "freemium vs free trial", "monetization model", "price increase", or "good-better-best". Also trigger when designing or auditing pricing and packaging for a product, validating willingness to pay before building, segmenting customers by value, or choosing between subscription, usage-based, and freemium models. Covers price-before-product, willingness-to-pay conversations, the four monetization failure types (feature shock, minivation, hidden gem, undead), leader/filler/killer packaging, and behavioral pricing. For offer and guarantee design, see hundred-million-offers. For discovering what customers value, see jobs-to-be-done.

  12. Organize business and technology teams for fast flow using Matthew Skelton and Manuel Pais''s "Team Topologies". Use when the user mentions "team topologies", "Conway''s law", "platform team", "stream-aligned team", "team boundaries", "cognitive load", "how should we split teams", "org design", "who owns this service", or "team dependencies". Also trigger when reorganizing engineering teams, aligning team and service boundaries, splitting a monolith and deciding team ownership, reducing cross-team dependencies and handoffs, or designing an internal platform. Covers the four team types, three interaction modes, the inverse Conway maneuver, and fracture planes. For bounded contexts and domain boundaries, see domain-driven-design. For dependency direction inside a codebase, see clean-architecture.

  13. Safely change and test untested codebases using Michael C. Feathers'' "Working Effectively with Legacy Code". Use when the user mentions "legacy code", "no tests", "untested codebase", "how do I test this", "seams", "characterization tests", "sprout method", "afraid to change this code", "monster method", or "dependency breaking". Also trigger when modifying code without tests safely, getting a class under test when constructors, statics, or singletons block it, adding features to tangled modules, or planning incremental test coverage for an old codebase. Covers the legacy code change algorithm, seams, characterization tests, sprout/wrap, and dependency-breaking techniques. For refactoring code that already has tests, see refactoring-patterns. For day-to-day code quality, see clean-code.

  14. >-

  15. Fast non-interactive briefing before any meeting — auto-detects your next calendar event, pulls relationship history, surfaces open commitments, and produces a one-page brief in under 30 seconds. Use this whenever the user says "brief me", "give me a quick brief", "what's coming up", "background on my next call", "who am I meeting next", "brief me on Sarah", "I have a call in 10 min", "quick rundown", or right before walking into a meeting. Different from /minutes-prep — brief is the fast hook-fireable version that doesn't ask questions and doesn't set goals. Use brief when speed matters; use prep when the user wants to think hard about goals first.

  16. Manage old recordings — find large files, archive old meetings, delete processed originals. Use when the user says "clean up recordings", "how much space are meetings using", "delete old recordings", "archive meetings", "manage meeting storage", or asks about disk space from minutes.

  17. Post-meeting debrief — analyzes what happened, compares outcomes to your prep intentions, tracks decision evolution. Use when the user says "debrief", "what just happened in that meeting", "what did we decide", "debrief that call", "post-meeting", "what changed", or right after stopping a recording.

  18. Cross-meeting entity graph — query who/what/when across all your meetings as structured data, with co-occurrence and cross-entity queries that text search can't answer. Use whenever the user says "show me everyone who mentioned X", "all mentions of Y across meetings", "who knows about Z", "graph", "across all meetings", "entity search", "first time we talked about", "trend for X over time", "who's been mentioned alongside", or wants to query meetings as an index rather than full-text search. Builds a JSON entity index on first run (one-time slow), then answers queries instantly. Surface this skill for relationship intelligence, due diligence, or any "across all my history" question that text search alone can't answer.

  19. Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.

  20. Extract facts from meetings and update your knowledge base — person profiles, chronological log, and index. Use when the user asks "ingest my meetings", "update my knowledge base", "extract facts from meetings", "sync meetings to wiki", "backfill knowledge", or wants their PARA/Obsidian/wiki profiles updated from conversation data.

  21. Health-check your meeting knowledge for contradictions, stale commitments, and decision conflicts. Use when the user asks "any conflicts in my meetings", "check for stale action items", "lint my meetings", "consistency check", "are there contradictions", or wants to audit their decision history.

  22. List recent meetings and voice memos. Use when the user asks "what meetings did I have", "show my recent recordings", "any meetings today", "list my voice memos", or wants an overview of their meeting history. Also use when they need to find a specific meeting by browsing rather than searching.

  23. Self-coaching analysis of your own behavior across meetings — talk-time ratio, filler words, hedging language, monologue length, energy patterns, and (when meetings are tagged via /minutes-tag) what your behavior in winning meetings looks like vs losing ones. Use this whenever the user says "how did I do", "review my last meeting", "mirror", "self-review", "show my patterns", "coach me", "where am I weak", "talk time", "am I improving", "what do I do in meetings I win", "feedback on me", or asks for any kind of personal feedback on their own meeting behavior. This is the rare skill that gives the user a mirror to their own habits — surface it whenever they show curiosity about their own performance, even if they don't use the word "mirror".

  24. Add a note to the current recording or annotate a past meeting. Use whenever the user says "note that", "remember this", "mark this as important", "add a note about", "annotate the meeting", or wants to capture a thought during or after a recording. Plain text input — no markdown needed.

  25. Interactive meeting preparation — builds a relationship brief and talking points before a call. Use when the user says "prep me for my call with", "I'm meeting with X", "prepare me for", "what should I bring up with", "meeting prep", "get ready for my call", or wants to review history with someone before a meeting.

  26. Generate a daily digest of today's meetings and voice memos — key decisions, action items, and themes across all recordings. Use when the user asks "recap my day", "what happened in my meetings today", "daily summary", "what did I discuss today", "any action items from today", or wants a consolidated view of the day's conversations.

  27. Start or stop recording a meeting, call, or voice memo. Use this whenever the user says "record", "start recording", "capture this meeting", "stop recording", "I'm in a meeting", "take notes on this call", or wants to transcribe live audio. Also use when they ask about recording status or want to know if something is being recorded.

  28. Search past meeting transcripts and voice memos for specific topics, people, decisions, or ideas. Use this whenever the user asks "what did we discuss about X", "find that meeting where we talked about Y", "what did Alex say", "did we decide on", "what was that idea about", or any question that could be answered by searching their meeting history. Also use for "do I have any notes about" or "check my meetings for".

  29. Guided first-time setup for Minutes — download whisper model, create directories, configure audio input. Use when the user says "set up minutes", "install minutes", "first time setup", "configure minutes", "get started with minutes", "how do I start using minutes", or when verify shows missing components.

  30. Lightweight outcome tagging for meetings — won, lost, stalled, great, or noise. Use whenever the user says "tag this meeting", "mark that as a win", "that one was a loss", "tag yesterday's call as stalled", "mark this great", "that meeting was noise", "label that meeting", or any time they describe a meeting outcome in passing. Tagging takes 5 seconds and unlocks /minutes-mirror correlation analysis — the more meetings get tagged, the smarter mirror gets at telling the user what behavior patterns lead to wins. Surface this skill any time the user mentions a meeting result, win, loss, or wasted time.

  31. Verify that Minutes is properly set up and working — model downloaded, mic accessible, directories exist, no stale state. Use when the user says "is minutes working", "check my setup", "verify minutes", "test recording setup", "why isn't minutes working", "minutes health check", or after running setup for the first time.

  32. Analyze a product walkthrough, bug report video, Loom, or ScreenPal using Minutes transcription plus visual review. Use when the user wants a recorded demo or bug clip turned into a durable brief with transcript, key frames, issues, and next steps.

  33. Weekly meeting synthesis — themes, decision arcs, stale commitments, and what deserves your attention next week. Use when the user says "weekly review", "what happened this week", "weekly summary", "recap my week", "any outstanding items", "week in review", or at the end of a work week.

  34. Launch an autonomous THINK→EXECUTE→REFLECT experiment loop on a GPU project

  35. Search papers from top AI/ML conferences

  36. Daily arXiv paper recommendations with automatic deduplication

  37. Check status of running autonomous experiment loops

  38. Check GPU status, running experiments, and available resources

  39. Refresh Obsidian dashboard and daily notes from current experiment state

  40. Deep analysis of a single paper with figure extraction from arXiv source

  41. Generate structured research progress reports

  42. lore1.2k

    SpecStory Lore - mine your SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more) into a persistent corpus, surface your reproducible workflows with corroborated evidence, and interactively forge the chosen ones into skills installed across all your agent harnesses. Use when the user wants to turn past AI coding sessions into reusable skills, asks "what could I make into a skill", "mine my lore", "forge skills from my history", or points at a .specstory/history directory.

  43. Conversational AI-first interface with minimal controls, clear outcomes, and delegated task flows for agentic workflows.

  44. ant1.2k

    Structured, enterprise-focused design system emphasizing clarity, consistency, and efficiency for data-dense web applications.

  45. App dashboard with purple-themed aesthetic, top-bar navigation, card-based layouts, and developer-first workflows.

  46. High-contrast, expressive style with creative typography and bold color choices for visually striking interfaces.

  47. bento1.2k

    Modular grid layout with card-like blocks, clear hierarchy, soft spacing, and subtle visual contrast for organized, scannable interfaces.

  48. bold1.2k

    Strong visual presence with heavyweight typography, high-contrast colors, and commanding layouts.

  49. Raw, anti-design aesthetic inspired by concrete architecture with unadorned elements, jarring layouts, and functional minimalism.

  50. cafe1.2k

    Cozy cafe-inspired interface with warm tones, soft typography, and clean layouts for a relaxed browsing experience.

  51. claude1.2k

    A research-journal aesthetic printed on warm stone — authoritative, editorial, almost achromatic. Pages live on warm ivory parchment (never pure white), with near-black slate as the dominant ink.

  52. Soft, rounded 3D-like shapes mimicking malleable clay with playful, puffy elements and colorful surfaces.

  53. clean1.2k

    Simplicity-focused design with ample whitespace, legible typography, and a limited color palette to reduce visual clutter.

  54. codex1.2k

    A radically minimal, blank-canvas interface built as a pure edge-to-edge surface, with almost no color and typography carrying the visual weight. Black serves as the only filled color, the only divider, and the sole surface tone cards.

  55. Vibrant, high-contrast palettes and gradients for engaging, memorable, and modern user experiences.

  56. Current-era minimalist design with bento grids, dark mode support, and high-performance accessible layouts.

  57. Professional, brand-aligned design with structured grids, minimalist layouts, and consistent enterprise patterns.

  58. cosmic1.2k

    Futuristic sci-fi aesthetic with dark themes, vibrant neon accents, and immersive spatial elements.

  59. Playful, character-driven design with expressive typography and bold graphics for landing pages and creative projects.

  60. Dark-themed cloud-platform aesthetic with modular grids, glass-like panels, and strong data hierarchy for productivity dashboards.

  61. Dot-pattern rendering technique that simulates shades with a limited palette for nostalgic, retro, high-contrast visuals.

  62. doodle1.2k

    Hand-drawn, sketch-like style with doodles, handwritten fonts, and imperfect lines for a playful, informal feel.

  63. High-contrast, theatrical design with bold layouts, immersive visuals, and unconventional compositions that command attention.

  64. Magazine-inspired editorial layout with refined serif typography, structured grids, and elegant reading experiences.

  65. Graceful, refined aesthetic with delicate typography, minimal palettes, and polished layouts that exude sophistication.

  66. Dynamic, vibrant style with thick borders, geometric shapes, high-contrast colors, and expressive typography conveying motion and vitality.

  67. Clean, high-contrast enterprise design for data-driven workflows with intuitive drag-and-drop patterns and structured layouts.

  68. Vibrant, personality-driven design with bold colors, playful graphics, and dynamic layouts that balance creativity with structure.

  69. Game-inspired fantasy aesthetic with bold, premium visuals, rich color palettes, and immersive thematic elements.

  70. A playful, energetic, cartoonesque interface inspired by friendly children's-book illustrations — warm cream backgrounds, big bold custom display typography, saturated brand color blocks, thick black outlines, generously rounded shapes

  71. flat1.2k

    Two-dimensional minimalist style with vibrant colors, clean typography, and no 3D effects for fast, user-friendly interfaces.

  72. Approachable, intuitive design with rounded elements, ample whitespace, and soft pastel color palettes.

  73. Forward-looking design with tech-inspired typography, modern layouts, and a sleek, innovation-driven aesthetic.

  74. Frosted glass effect with translucent layers, subtle blur, and luminous borders for depth and modern elegance.

  75. Smooth color transitions and gradient-rich surfaces for modern, playful interfaces with visual depth.

  76. An immersive, interactive, exhibit-style interface that blends storytelling, animation, and gamified elements to create a playful, experience-driven journey. The entire app sits on a single continuous brand-colored canvas (deep green)

  77. A modern, graphic, editorial-poster aesthetic — warm and confident — built on alternating cream and burnt orange sections, an amber brand color.

  78. levels1.2k

    Conversion-focused design that removes friction and guides users toward action through clarity, trust, and speed.

  79. lingo1.2k

    Playful, minimal design with bright colors, rounded shapes, tactile 3D borders, and friendly illustrations for approachable interfaces.

  80. luxury1.2k

    High-end dark aesthetic with bold headings, monochromatic palette, and premium feel for luxury brand experiences.

  81. Google's Material Design with layered surfaces, dynamic theming, built-in motion, and responsive cross-platform patterns.

  82. matrix1.2k

    A cyber-slick, dark-only Matrix-inspired interface defined by minimalist fashion, high-tech digital elements

  83. Stripped-back design emphasizing whitespace, clean typography, and restrained color for maximum clarity and focus.

  84. modern1.2k

    Contemporary editorial style with serif typography, minimal palettes, and clean layouts for polished digital products.

  85. mono1.2k

    Monospace-driven, matrix-inspired design with high-contrast elements, compact density, and a hacker-chic aesthetic.

  86. Modern take on brutalism with bold borders, vivid accent colors, and raw, high-contrast layouts on warm surfaces.

  87. neon1.2k

    Electric neon glow effects with high-contrast color pairings for bold, attention-grabbing interfaces.

  88. Soft, extruded UI elements with inner and outer shadows on monochromatic surfaces for a tactile, embedded look.

  89. pacman1.2k

    Retro arcade-inspired design with pixel fonts, dotted borders, playful high-contrast colors, and 8-bit game aesthetics.

  90. paper1.2k

    Paper-textured, print-inspired design with minimal colors, clean serif/sans typography, and tactile surface qualities.

  91. Spatial depth design with isometric views, vanishing points, and layered elements that guide attention through 3D-like realism.

  92. Apple-inspired premium aesthetic with precise spacing, modern typography, and a refined, polished visual language.

  93. Polished, business-ready design with modern typography, structured layouts, and a trustworthy visual identity.

  94. Print-inspired visual language for books, magazines, and reports with editorial grids and expressive typography.

  95. Carefully curated, modern minimal style with elegant serif typography and understated, sophisticated palettes.

  96. retro1.2k

    Throwback design with vintage-inspired typography, high-contrast retro palettes, and nostalgic visual elements.

  97. riso1.2k

    A playful, joyful, two-color risograph print aesthetic built on a single warm off-white paper surface running through every section

  98. sega1.2k

    A playful, arcade-inspired interface for games — built on the VT323 pixel typeface, hard-edged 0px corners, chunky pill buttons that physically press into solid offset blocks

  99. shadcn1.2k

    Shadcn/ui-inspired design with minimal, clean components, monochrome palette, and utility-first patterns.

  100. simple1.2k

    Straightforward, no-frills design with clean typography, neutral colors, and intuitive layouts that stay out of the way.