petrogurcak
127 verified skills148 total stars
plan-challenger
Adversarial review of implementation plans — finds failure modes, hidden dependencies, scope risks, missing edge cases, and architecture concerns BEFORE coding begins. Use when a plan file has been written and needs validation before implementation starts. Mandatory in planning skill Phase 3 Step 2. Works in both Claude Code and Gemini CLI.
tools2
planning
Explores requirements, brainstorms approaches, writes a detailed TDD implementation plan, and reviews it with adversarial agents before handing off to execution. Use when user says "plan", "naplanuj", "plan na X", or wants to plan a new feature or change before coding. NOT for bug fixes (use debugging), trivial changes under 3 steps, or when a plan file already exists.
development2
video-scripting
Use when writing long-form video scripts that need retention engineering and narrative structure. Trigger phrases - "writing YouTube video script", "VSL (video sales letter)", "long-form video script", "course module video", "explainer video", "retention curve optimization", "video script for course", "scénář YouTube videa", "VSL skript", "long-form video", "scénář kurzového videa", "video script". Do NOT use for short-form TikTok/Reels under 60s — use copywriting:ig-content.
data-ai2
email-sequences
Use when writing multi-day email sequences — 4-day indoctrination sequence, welcome email series, Soap Opera Sequence (SOS), drip campaign, tripwire upsell flow, post-purchase email sequence, evergreen email funnel, indoktrinační sekvence, uvítací email série, drip kampaň, automatická sekvence po nákupu, tripwire upsell, email onboarding flow, launch sequence. Do NOT use for single one-off emails — use copywriting:newsletter instead.
documentation2
mobile-store-release
Use when releasing an Expo/React Native mobile app to App Store and Google Play - covers eas submit, ASC "Submit for Review", Play promote Internal→Production, OTA update, and decoding common silent failures (Apple agreement expiry, missing English locale, Background Location declaration, web bundle failure on react-native-maps).
development2
info-product-launch
Specialized 8-week launch cadence for info-products — online courses, cohort programs, memberships, communities, ebooks, masterminds. Combines Jeff Walker's Product Launch Formula (Seed/Internal/JV variants, PLC sequence, open-cart day-by-day) with Stu McLaren's membership mechanics (closed cart, Success Path) and Hormozi Grand Slam Offer stacking. Use when planning "launch online kurzu", "info-product launch", "PLF launch", "course launch", "membership launch", "cohort launch", "ebook launch", "open cart close cart", "8-week launch of online course", "beta cohort to launch sequence", "spuštění kurzu", "launch členské sekce", "open cart strategie". Differentiates from marketing:launch-strategy (generic SaaS/app launches) — info-product-specific. NOT for SaaS launches, physical products, or services.
testing2
marketing-orchestrator
Orchestrates marketing and growth work by detecting business stage, goal type, and routing to specialized skills (offer-creation, growth-hacking, product-led-growth, saas-bootstrap, uvp-optimization, launch-orchestrator, testimonial-harvesting, sell-like-crazy). Use when planning marketing strategy, go-to-market, growth strategy for SaaS, launch planning, beta tester program, social proof collection, or asking "how do I get first customers" or "help me grow my product". Trigger phrases - "launch", "spuštění produktu", "beta tester program", "testimonial harvest", "sběr referencí", "social proof before launch". NOT for when you already know the exact specialist skill needed, just copywriting (use copywriting-orchestrator), just UX (use ux-orchestrator), or just positioning (use uvp-optimization).
development2
testimonial-harvesting
Builds a pre-launch social proof strategy through structured beta programs using D'Souza Brain Audit interviews. Use when launching new products/services and need compelling testimonials, planning a beta cohort, designing interview questions to harvest objection-busting social proof, improving video testimonials for landing pages, or designing case studies with metrics. Trigger phrases include "beta tester program for testimonials", "pre-launch social proof", "Brain Audit testimonial framework", "case study harvest", "reverse testimonial", "video testimonial mechanics", "social proof landing page", "sběr referencí", "beta tester program", "testimonial pro landing page", "social proof před launchem", "rozhovor s klientem", "case study sběr", "reference před spuštěním". NOT for ongoing case study production (use growth-hacking case-study approach), offer design (use offer-creation), or conversion optimization (use ux-optimization).
development2
email-orchestrator
Use when working on email copy and the format is unclear or could be either single email or multi-day sequence. Routes between copywriting:newsletter (one-off campaigns, holiday emails, weekly newsletter, single broadcast) and copywriting:email-sequences (indoctrination sequences, welcome series, drip campaigns, tripwire flows, SOS). Trigger phrases - "email copy", "psaní emailů", "email campaign", "emailový obsah", "email content help", "potřebuju email", "I need email copy", "email marketing", "email automatizace". Do NOT trigger when format is already clear (use specific skill directly).
development2
launch-orchestrator
Use when planning a product launch and the product type is unclear or could be either generic (SaaS/app/physical) or info-product. Routes between marketing:launch-strategy (generic launches) and marketing:info-product-launch (courses, memberships, ebooks, cohorts, communities). Trigger phrases - "launch", "spuštění", "go-to-market", "product launch", "release strategy", "uvedení na trh", "launch plan", "spuštění produktu", "launch sequence", "launch strategy". Do NOT trigger when product type is already clear (use specific skill directly).
development2
copywriting-orchestrator
Detects content type and routes to the right specialized copywriting skill (ig-orchestrator, email-orchestrator, video-scripting, web-copy, product-copy, storytelling). Use when the user asks for copy but it is unclear which specialist to use, or for multi-channel campaigns spanning several formats. Trigger phrases - "write copy for", "help me with copywriting", "product launch campaign", "I need marketing text", "make it more compelling", "tell a story", "video script", "VSL", "email sequence", "drip campaign". Do NOT use when you already know the exact medium — call the specialist skill directly instead.
development2
batna-strategy
Use when user prepares strategic structure of negotiation — BATNA, ZOPA, anchoring, multi-issue trades, leverage analysis. Fisher/Ury Getting to Yes + Malhotra/Bazerman Negotiation Genius. Trigger phrases — "BATNA", "alternativy", "leverage", "ZOPA", "anchor", "pricing power", "walk-away", "interests vs positions", "Fisher Ury", "Getting to Yes", "co dělat když má víc síly". Do NOT use for verbal delivery (tactical-empathy), body reading (reading-people), or email (written-negotiation).
development2
consistency
Use when auditing project for internal consistency — duplicates, dead code, cross-layer drift (DB↔ORM↔TS↔Zod), naming drift across layers, time drift (TODO >6mo), i18n key drift, and structural inconsistency in homogeneous file groups (e.g. SKILL.md format across plugins). Interactive walkthrough — categorizes problems CRITICAL/MEDIUM/COSMETIC and walks through one by one with Fix/Defer/Skip choice. Trigger phrases — "consistency audit", "audit projektu", "zkontroluj konzistenci", "najdi nesrovnalosti", "/consistency". NOT for code review of recent changes (use deep-review), single-domain checks (security/api/database — use specialists), or when you want automated fixes without confirmation.
tools2
handoff
Captures planning rationale (why-this-approach, rejected alternatives, user preferences voiced, adversarial findings, constraints) into plan file as Handoff Context section before /clear, updates .claude/ACTIVE_CONTEXT.md, and offers commit. Use when finishing planning before execute, when user says "handoff", "predej do execute", "zabal pred clear", "priprav na clear", "clear pred execute". Invokable explicitly via /development:handoff [plan-path]. NOT for general session save (use session-context) or for execute itself (use executing-plans).
development2
projectsetup
Creates CLAUDE.md and .claude/ directory with development principles (TDD, Git safety, verification, checkpoints), session context files, and MCP server configuration. Supports Generic, Nette, Flutter, and Frontend variants. Use when user says "setup this project", "initialize project", or when starting a new project without CLAUDE.md. NOT for adding workflow optimizations to an existing setup (use workflow-optimization) or for framework-specific implementation (use framework workflow skills).
tools2
workflow-optimization
Adds modular workflow optimizations to existing projects including mistakes tracking, verification checklists, context pruning, code quality hooks, pattern learning, checkpoints, build error resolver, project summaries, and enforcement hooks. Use when user says "optimize workflow", "add mistakes tracking", "setup verification", or after running projectsetup to enhance the development workflow. NOT for initial project setup (use projectsetup first) or for creating CLAUDE.md from scratch.
development2
written-negotiation
Use for written/async negotiation — drafting response to angry email, written contract neg, async deal closing, Slack/DM de-escalation. Voss adapted to written + Goulston principles for async + de-escalation patterns. Trigger phrases — "email", "zpráva", "Slack DM", "dopis", "písemně", "draftit odpověď", "písemná de-escalation", "answer the angry email", "smluvní email", "follow-up email", "respond to objection". Do NOT use for live verbal (use tactical-empathy or emotional-conflict), body reading (reading-people).
development2
tactical-empathy
Use when user needs to know WHAT TO SAY in live verbal negotiation — mirroring, labeling, calibrated questions, late-night-FM-DJ voice, no-oriented questions, Black Swans, Ackerman bargaining. Chris Voss methodology + BCSM (Behavioral Change Stairway Model). Trigger phrases — "co říct", "mirroring", "labeling", "calibrated questions", "Voss", "tactical empathy", "live verbal", "co odpovědět". Do NOT use for body language (use reading-people), email (use written-negotiation), or strategic prep (use batna-strategy).
development2
emotional-conflict
Use for live high-emotion conflict — cofounder split, firing, family business, partnership breakup, unhappy klient face-to-face. Goulston Just Listen + Kohlrieser Hostage at the Table + Stone/Patton/Heen Difficult Conversations. Trigger phrases — "spor", "konflikt", "cofounder split", "vyhazov", "firing", "family business", "rodinny byznys", "unhappy klient live", "partnership breakup", "high stakes emotional", "Goulston", "de-escalation live". Do NOT use for regular business pricing neg (use orchestrator full flow), email/written (use written-negotiation), or actual abuse/crisis (refer to professional helpline).
development2
negotiation
Detects negotiation sub-intent and routes to the right specialist (reading-people, tactical-empathy, batna-strategy, emotional-conflict, written-negotiation). Use when user mentions vyjednávání, jednání, deal, smlouva, salary, conflict, but it's unclear which aspect they need. Trigger phrases — "vyjednavani", "vyjednat", "jednani", "negotiation", "deal", "smlouva", "konflikt", "spor", "vest jednani", "obchodni jednani". Do NOT use when intent is clear — call specialist directly (reading-people for "číst lidi", tactical-empathy for "co říct", written-negotiation for "draftit email", emotional-conflict for "cofounder spor").
development2
reading-people
Use when user wants to read body language, nonverbal cues, comfort/discomfort signals during in-person/video meeting, pitch, interview, or negotiation. Joe Navarro methodology — limbic system, baseline, feet→face honesty hierarchy. Trigger phrases — "číst lidi", "řeč těla", "body language", "nonverbalni komunikace", "pozorovat", "Navarro", "co znamená když...". Do NOT use for verbal tactics (use tactical-empathy), strategic prep (use batna-strategy), or written communication (use written-negotiation).
development2
deep-review
Orchestrates comprehensive code review by auto-detecting stack and routing to specialized review skills (security, database, API, UX, business). Use after completing significant code changes, before deploy to production, or when you want a thorough multi-perspective audit. Trigger phrases include "deep review", "review my changes", "code audit", "hloubkova analyza". Not for quick spot checks — use individual specialist skills (security-review, database-review, api-design-review) directly for focused single-domain reviews.
development1
link-building
Builds website authority through strategic link acquisition. Covers the 5 currencies framework, linkable asset creation, prospecting with search operators, broken link building with email templates, link opportunity qualifiers, outreach email principles, and measurement. Use when building backlink profile, creating linkable assets, doing outreach campaigns, or analyzing competitor backlinks. Trigger phrases: 'link building', 'backlinks', 'outreach', 'domain authority', 'linkable assets', 'broken link building'. NOT for internal linking strategy (use on-page-seo) or on-page optimization (use on-page-seo).
development1
sitemap-management
Creates, optimizes, and monitors XML sitemaps for efficient crawling and indexing. Covers sitemap index files, image/video/news sitemaps, IndexNow protocol, large site strategy (100K+ pages), JavaScript-rendered content, dynamic generation (Next.js/WordPress), and Google Search Console monitoring. Use when creating sitemaps, fixing indexing issues, implementing IndexNow, or managing crawl budget for large sites. Trigger phrases: 'sitemap', 'XML sitemap', 'IndexNow', 'crawl budget', 'indexing issues'. NOT for robots.txt configuration (use technical-seo) or page-level canonical tags (use technical-seo).
development1
verify
Runs full project verification suite (tests, build, lint/typecheck, plan task checklist, optional browser smoke test) and presents results with actual command output as evidence. Use after all plan tasks are complete, when user says "verify", "zverifikuj", or before merging to confirm everything works. NOT for running a single test file or for debugging failures (use systematic-debugging).
development1
ux-expert-dialogue
Runs interactive expert review sessions where a senior UX composite persona (Nielsen, Krug, Kahneman, Cialdini, Ilincev) challenges decisions, provides direct critique with data-backed reasoning, and brainstorms alternatives section-by-section. Use when creating a new website/landing page and need expert challenge, want section-by-section review with quantified impact estimates, need an opponent who questions assumptions, brainstorming design alternatives, or preparing for major redesign or launch. Trigger phrases include "expert review", "critique my design", "challenge my assumptions", "section-by-section review". NOT for quick fixes with known solutions (use ux-optimization), implementing proven patterns directly, or when you want agreement rather than challenge.
development1
ux-optimization
Diagnoses UX issues and provides concrete, code-ready solutions based on 213 real case studies, covering forms, e-commerce, design, mobile, A/B testing, performance, accessibility, admin dashboards, data tables, CRUD operations, navigation, persuasion patterns, and micro-interactions. Use when form conversion is below 50%, cart abandonment exceeds 70%, users miss CTAs, mobile UX is frustrating, or you need to set up A/B tests. Trigger phrases include "improve conversion", "optimize forms", "fix checkout", "A/B test", "UX audit". NOT for value proposition clarity issues (use uvp-optimization), expert design critique sessions (use ux-expert-dialogue), or writing copy (use web-copy).
development1
cowork-setup
Creates `~/Claude-shared/` (user-level shared context — about-me, voice, working-rules, projects-index) and per-project scaffolding in `~/Projects/<name>/` for Claude Cowork non-development projects (marketing, copywriting, strategy, concepts, research). Lightweight alternative to development:projectsetup. Use when user says "setup cowork project", "nový cowork projekt", "nastav coworku", "cowork init", or starting non-dev work in Cowork desktop app. NOT for development projects (use development:projectsetup) or for adding workflow optimizations to existing setup (use workflow-optimization).
development1
ig-content
Use when writing Instagram copy — posts, captions, carousels, Reels captions. Produces 3-5 ready-to-paste variants in code blocks using Otto Bohuš methodology (concrete numbers over adjectives, banned words removed, sentences under 20 words, triáda). Strict output discipline - NEVER outputs HOOK/SUBSTANCE/PAYOFF labels in final copy. Trigger phrases - "napiš IG post", "create caption", "IG carousel", "Reel caption", "Instagram copy", "post pro Instagram". Do NOT use for IG planning/strategy (use ig-strategy), production setup or filming (use ig-strategy), or non-IG copy (use copywriting-orchestrator to route).
development1
ig-orchestrator
Use when user mentions Instagram, IG, Reels, Stories, posts, captions, carousels — but it is unclear whether they want to WRITE copy, PLAN content, set up PRODUCTION, or analyze ANALYTICS. Routes to the right IG specialist (ig-content for writing, ig-strategy for planning/production, future ig-reels/ig-stories/ig-ads/ig-analytics). Trigger phrases - "instagram", "ig", "reel", "story", "post", "carousel", "social media obsah". Do NOT use when intent is clear - call specialist directly (ig-content for "napiš caption", ig-strategy for "jaký formát").
development1
ig-strategy
Use when planning Instagram content — what to make, when to publish, how to film, engagement tactics, monetization. Covers 4 idea criteria (relativita, otázky, reakce, nereálnost), 9 video formats, 7-10 video consistency rule, technical settings (4K/30fps iPhone+Android), engagement tactics (kontroverze, úmyslná chyba, CTA), Reel vs Story vs Post comparison, monetizace (brand deals, affiliate, vlastní produkty). Trigger phrases - "co točit", "jaký formát", "IG strategie", "engagement plán", "technické nastavení", "shot list", "monetizace IG", "IG plán". Do NOT use for writing IG copy (use ig-content), generic narrative frameworks (use storytelling), or non-IG strategy (use copywriting-orchestrator).
development1
sell-like-crazy
Use when building sales funnels, sales pages, VSL scripts, email sequences, or any conversion-driven copy. Applies Sabri Suby's 8-phase direct response sales system — Larger Market Formula, Halo Strategy customer research, HVCO lead magnets, Godfather Offer construction, Magic Lantern Technique, Soap Opera email sequences. Also use when applying conversion principles (urgency, scarcity, risk reversal, social proof) to existing copy from ig-content, newsletter, or web-copy skills.
development1
database-review
SQL/ORM patterns review - N+1 queries, indexy, transactions, connection management
data-ai1
designing-abstractions
Use this skill BEFORE planning a module/API, BEFORE writing a helper/wrapper/dispatcher, OR when refactoring duplicated code — even if the user doesn't explicitly say "abstraction". Enforces responsibilities-before-abstraction analysis (enumerate concerns, find invariants, choose named domain models over flat signatures) and produces a required "Abstraction Strategy" artifact. Prevents god-functions, stringly-typed dispatchers like send(type="X"), parameter sprawl, duplicated parallel implementations across files, and premature DRY. Trigger whenever the user asks to — extract a helper, consolidate/unify/sjednotit duplicated code, add a dispatcher or shared module, refactor or DRY something up, design an API or notification/email/logging system, write validation, or whenever a plan touches two or more call sites sharing logic. Also invoke when the user says "duplikace", "extrahuj", "sjednoť", "refactor", "helper", "dispatcher", "shared", "parse", "validate input".
tools1
openspec-workflow
Use when implementing complex features requiring clear specifications before coding - creates spec-driven workflow with proposals, task breakdown, and delta documentation; works standalone or with OpenSpec CLI for enhanced features
tools1
children-stories
Use when writing children's literature — picture books, verse books, early readers, bedtime stories for ages 3-8. Three modes — blueprint (creates story blueprint with age calibration, characters, voice, narrative pattern), write (writes one story per invocation), test (read-aloud checklist + iterative rewrite from children's feedback). Trigger phrases — "children's story", "dětský příběh", "picture book", "obrazková kniha", "pohádka", "bedtime story", "příběh na dobrou noc", "write for kids", "psát pro děti". Do NOT use for non-fiction (use knowledge-book), marketing copy (use copywriting-orchestrator), or adult fiction.
testing1
plugins/copywriting/skills/instagram-content
--- name: instagram-content description: Creates viral Instagram Reels, Stories, and posts using the Hook-Substance-Payoff framework, with technical recording settings, engagement tactics, caption copywriting, and hashtag strategy. Use when scripting short-form video, writing IG captions, or developing Instagram content strategy. Trigger phrases: "Instagram reel", "IG post", "social media content", "stories script", "caption for Instagram". Do NOT use for long-form blog posts (use web-copy), pro
tools1
create-persona
Scaffolds a new autonomous AI persona with directory structure, manifest, sources config, knowledge registry section, and OpenClaw cron job. Use when creating a new agent persona like "product-advisor", "seo-monitor", etc.
data-ai1
plugins/copywriting/skills/writing-clearly-and-concisely
--- name: writing-clearly-and-concisely description: Applies Strunk's Elements of Style rules to make any prose clearer, stronger, and more concise — active voice, omit needless words, specific language, positive form. Use when writing or editing documentation, README files, commit messages, error messages, UI copy, reports, or any text humans will read. Trigger phrases: "make this clearer", "edit for conciseness", "improve my writing", "proofread this". Do NOT use for marketing copywriting (use
tools1
analytics-report
Generates analytics reports for projects using GA4, Search Console, and backend data. Use when user says "analytics report", "jak je na tom [project]", "weekly report", "tydni report", or "analyzuj [project]". NOT for setting up tracking (use analytics-setup), NOT for SEO audit (use seo-optimization).
development1
agent-team-development
Executes implementation plans by spawning parallel teammates in tmux split panes, each owning a module, with a persistent review teammate for quality gates. Use when you have a plan with 3+ independent modules touching different files and want parallel execution. Trigger phrases - "execute plan in parallel", "spawn teammates", "team development", "parallel implementation", "tmux teammates". NOT for sequential single-module tasks or when modules share the same files (use development-workflow instead).
development1
flutter-workflow
Docs-first development workflow for Flutter/Dart projects covering widgets, state management, navigation, and platform integration (iOS/Android/Web). Fetches current documentation via MCP before any implementation. Use when building or modifying Flutter apps. Trigger phrases - "flutter", "dart", "flutter widget", "flutter app", "flutter navigation", "flutter state management". NOT for React Native/Expo (use expo-workflow) or web-only frontends (use frontend-app/frontend-lp).
tools1
fullstack-orchestrator
Orchestrates fullstack application development by coordinating backend and frontend workflow skills, managing API contracts, and ensuring consistency between layers. Auto-detects tech stack or asks. Use when a feature requires both backend API and frontend UI, or when starting a new fullstack project. Trigger phrases - "fullstack", "full stack", "backend and frontend", "API plus UI", "new project with both layers". NOT for backend-only (use fastapi-workflow) or frontend-only work (use frontend-app/frontend-lp).
development1
sentry-fix
Use when asked to fix Sentry issues, check Sentry errors, or auto-fix bugs from error monitoring. Fetches unresolved issues, investigates root cause, creates fix branch, tests, and merges.
testing1
referral-program
Designs and optimizes referral and affiliate programs for SaaS products using referral loop framework, incentive design, and viral mechanics. Use when building a referral program, improving referral conversion, designing affiliate programs, or adding viral loops. Triggers include "referral program", "affiliate program", "viral growth", "word of mouth", "referral loop". NOT for general growth experiments (use growth-hacking), product onboarding (use product-led-growth), paid acquisition (use marketing-orchestrator), or launch distribution (use launch-strategy).
development1
saas-bootstrap
Guides bootstrapped SaaS founders using Stair Step Method and 3 High / 3 Low Metrics from Rob Walling's The SaaS Playbook. Use when evaluating a SaaS idea, deciding what to focus on as a solo founder, tracking SaaS health metrics, or growing without funding. Triggers include "should I build this SaaS", "solo founder focus", "bootstrap vs VC", "is my SaaS healthy". Do NOT use for creating offers (use offer-creation), growth experiments (use growth-hacking), product onboarding (use product-led-growth), or positioning (use uvp-optimization).
development1
labor-law
Czech labor law specialist — validates feature designs and questions against Zákoník práce (262/2006 Sb.) with exact paragraph citations. Use when asked about employment contracts (HPP, DPP, DPC), working hours, overtime, vacation, termination, severance, minimum wage, or any Czech labor code question.
development1
competitive-analysis
Analyzes competitors systematically covering landscape mapping, messaging comparison, feature matrices, content gap analysis, positioning strategy, and battlecard creation. Use when entering a new market, comparing positioning against competitors, building feature comparison matrices, creating sales battlecards, identifying content gaps, or preparing competitive pitch slides. Trigger phrases include "who are my competitors", "competitive landscape", "feature comparison", "battlecard". NOT for defining your own value proposition (use uvp-optimization), creating offers (use offer-creation), setting pricing (use pricing), or writing copy (use web-copy).
development1
pricing
Designs pricing pages, price tables, and price increase communication using Dima Melnik methodology with 18 price offer design tactics and 10 price increase tactics. Use when creating or optimizing pricing pages, structuring SaaS/subscription tiers, planning price increases for existing customers, writing price increase emails, or auditing pricing presentation. Trigger phrases include "pricing page", "raise prices", "price table", "tier structure", "price increase email". NOT for product positioning (use uvp-optimization), general copywriting (use copywriting-orchestrator), or financial/accounting decisions.
testing1
uvp-optimization
Defines and optimizes Unique Value Propositions through a 4-phase framework (Position, Formulate, Test, Implement) based on proven methodologies and case studies like Groove (+104% conversion). Use when creating a new website/landing page needing a core value proposition, homepage has low conversion despite traffic, users don't understand your offer within 5 seconds, need to differentiate from competitors, or A/B testing value propositions. Trigger phrases include "value proposition", "positioning", "users don't get what we do". NOT for writing final copy (use web-copy), optimizing UVP placement/design (use ux-optimization), or writing product descriptions (use product-copy).
development1
product-orchestrator
Routes product management questions to the right specialized skill (discovery, prioritization, strategy, PMF, metrics) based on problem type. Use for any general product decision or strategy question when you are unsure which specific product skill to invoke. Triggers include "help with product", "what should we build", "product advice", "how do I approach this product problem". Do NOT use when you already know the specific sub-skill needed — call it directly instead.
development1
abstraction-review
Use this skill to review code for bad abstractions, duplicated parallel implementations, stringly-typed dispatchers, god-functions, parameter sprawl, primitive obsession, and mixed concerns — both in isolation ("review tyhle abstrakce", "je tenhle dispatcher OK?") and as a specialist lens inside deep-review. Invoke whenever a PR or diff adds/modifies a helper, wrapper, dispatcher, shared module, OR consolidates duplicated code, OR when the user asks "zreview mi tyhle abstrakce", "je ta refactor OK", "není to over-DRY", "nemáme tady god-function", "napsal jsem helper — je to dobré?". Complements security-review, database-review, api-design-review as the design-quality lens.
tools1
database-review
Reviews database code for N+1 queries, missing indexes, transaction handling, connection pooling, and query patterns across SQL and ORM layers. Use when optimizing slow queries, reviewing database changes, debugging performance issues, preparing for scaling, or as part of deep-review. Trigger phrases include "review database code", "check queries", "DB performance", "find N+1". Not for database schema design or migrations — focused on code-level query patterns and performance.
development1
aso-optimization
Optimizes App Store and Google Play listings for maximum visibility and conversion, covering keyword optimization, screenshot design, icon testing, description writing, and A/B testing (PPO, Store Listing Experiments). Based on Advanced ASO Book by Phiture and AppTweak. Use when an app is not appearing in search results, has low impression-to-download conversion, planning app store listing optimization, creating/updating screenshots and icons, or launching a new app. Trigger phrases include "app store optimization", "ASO", "app keywords", "app screenshots". NOT for web SEO (use on-page-seo), in-app conversion optimization, or app review/ratings management.
development1
hreflang-i18n
Implements and audits hreflang tags and international SEO strategy. Covers implementation methods (HTML/HTTP/sitemap), common errors with detection and fixes, cross-domain setups, content localization vs translation, country targeting decision tree (ccTLD/subdirectory/subdomain), and systematic audit workflow. Use when setting up multi-language sites, fixing hreflang errors, choosing international URL structure, or auditing existing i18n implementation. Trigger phrases: 'hreflang', 'international SEO', 'multilingual', 'localization', 'multi-language', 'i18n', 'translation SEO'. NOT for general technical audits (use technical-seo) or on-page content in one language (use on-page-seo).
development1
image-seo
Optimizes images for search engines, Core Web Vitals, and visual search. Covers format selection (AVIF/WebP/JPEG), LCP optimization with fetchpriority, lazy loading rules, alt text best practices, responsive images (srcset/sizes), compression thresholds, Google Lens optimization, and Open Graph images. Use when optimizing image performance, fixing LCP issues caused by images, writing alt text, setting up responsive images, or optimizing for visual search. Trigger phrases: 'image optimization', 'lazy loading', 'WebP', 'AVIF', 'alt text', 'image compression', 'OG image', 'Google Lens'. NOT for general page speed (use technical-seo) or on-page keyword optimization (use on-page-seo).
development1
keyword-research
Discovers, analyzes, and prioritizes keywords for SEO and content strategy using free tools (Google Keyword Planner, Ubersuggest, AlsoAsked, Google Trends). Covers seed keyword discovery, long-tail expansion, metrics analysis, and content clustering. Use when starting a new website/project needing keyword strategy, planning content calendar based on search demand, finding low-competition quick wins, analyzing competitor keyword gaps, or building topic clusters. Trigger phrases include "keyword research", "find keywords", "content strategy keywords", "what to write about". NOT for on-page optimization with existing keywords (use on-page-seo), writing content (use web-copy), or setting up analytics (use analytics-setup).
tools1
schema-markup
Implements and validates structured data (JSON-LD) for rich results and AI visibility. Covers active schema types, deprecated types timeline, video schema (VideoObject, Clip, SeekToAction, BroadcastEvent), @id entity graphs, validation workflow, and common errors. Use when adding structured data, fixing schema errors, implementing video markup, or optimizing for AI search entity understanding. Trigger phrases: 'schema', 'structured data', 'JSON-LD', 'rich results', 'video schema', 'markup validation'. NOT for on-page content optimization (use on-page-seo) or general AI search strategy (use ai-ready).
tools1
technical-seo
Audits and sets up technical SEO foundations covering Core Web Vitals (LCP, INP, CLS), crawlability (robots.txt, sitemaps, canonicals), security headers, and mobile-first optimization, with automated audits via claude-in-chrome. Use when auditing for technical SEO issues, setting up technical foundation, fixing Core Web Vitals, or debugging crawlability issues. Trigger phrases: 'technical SEO audit', 'Core Web Vitals', 'robots.txt', 'page speed', 'crawlability', 'security headers'. NOT for structured data (use schema-markup), international/hreflang (use hreflang-i18n), on-page content (use on-page-seo), or keyword research (use keyword-research).
development1
team-briefing
Activates virtual AI team personas (marketing, growth, copywriting, SEO, UX, security, product, analytics, pricing, brand, legal) to review a plan from cross-functional perspectives and provide actionable suggestions. Use after brainstorming or planning is complete, before implementation begins, when you want diverse domain perspectives on a plan. Trigger phrases include "team briefing", "review this plan with the team", "get team feedback", "cross-functional review". Not for code review (use deep-review) or single-domain feedback — this is multi-persona strategic review.
development1
ui
Use when designing or improving any UI — combines UX analysis with copywriting for interface text. Covers screens, components, pages, forms, modals, onboarding flows.
content-media1
wrapup
Performs end-of-session reflection by saving context to ACTIVE_CONTEXT.md, checking for mistakes to log, extracting lessons learned, and identifying documentation updates needed. Use after merging to development, when user says "wrapup", "zabal to", or at the end of a development session. NOT for saving context mid-session (use session-context) or for standalone mistake logging.
development1
quality-reviewer
Reviews code quality independently of plan — TDD compliance, error handling, code smells, security basics, performance red flags. Use after implementation is complete. Focuses on code itself, not whether it matches plan (use compliance-reviewer for that). Works in both Claude Code and Gemini CLI.
tools1
api-design-review
REST API conventions, error handling, versioning, pagination, rate limiting
development1
api-design-review
Reviews REST API design for conventions, error handling, versioning, pagination, and rate limiting. Use when reviewing API endpoints, designing new APIs, auditing existing REST services, or as part of deep-review. Trigger phrases include "review my API", "check API design", "API audit", "review endpoints". Not for GraphQL or gRPC reviews — focused on REST only.
development1
analytics-setup
Sets up Google Tag Manager and Google Analytics 4 for websites with automated browser setup via claude-in-chrome. Use when launching a new site needing tracking, migrating to GTM/GA4, adding event tracking (clicks, forms, conversions), setting up e-commerce tracking, or debugging tracking issues. Trigger phrases include "set up GTM", "configure GA4", "tracking plan", "add event tracking", "debug analytics". NOT for analyzing existing data/reports (use google-analytics MCP), keyword research (use keyword-research), or SEO optimization (use seo-optimization).
tools1
ecommerce
Ceska e-commerce legislativa — posuzuje pravni compliance e-shopu, obchodni podminky, odstoupeni od smlouvy, reklamace, cookies, GDPR v kontextu e-shopu, ceny/DPH/Omnibus, pristupnost, ADR, GPSR. Tri mody — audit otazky (konkretni pravni dotaz), compliance check (systematicky audit vsech oblasti), planning (checklist pro novy e-shop). Trigger phrases — "e-shop legislativa", "obchodni podminky", "reklamace", "odstoupeni od smlouvy", "cookie lista", "compliance e-shopu", "co musim mit na e-shopu", "zakladam e-shop".
testing1
agent-design
Knowledge base for designing AI agents — persona crafting, system prompt patterns, multi-agent orchestration, memory design, evaluation. Use when creating or improving an autonomous AI agent persona, writing agent templates, or debugging agent behavior. NOT a workflow — this is reference material to inform decisions.
development1
banana-illustrator
Vizualni produkce detske knihy "Mlsne tlapky" ve stylu Andrea Tachezy. Character bible, style locking, spread kompozice. Pro generovani obrazku pouziva creative:image-generation skill.
data-ai1
ai-ready
Makes websites discoverable and citable by AI search engines and agents (ChatGPT, Perplexity, Claude, Gemini) through llms.txt setup, robots.txt for AI crawlers, markdown serving via content negotiation, and structured data for AI citations. Use when launching a new site wanting AI discoverability, existing site not appearing in AI search results, optimizing for AI citations and referral traffic, or setting up SaaS marketing site for AI. Trigger phrases include "AI search", "llms.txt", "AI crawlers", "Perplexity citations". NOT for traditional Google SEO (use on-page-seo), technical performance audits (use technical-seo), or keyword research (use keyword-research).
development1
brand-strategy
Use when building a new brand, repositioning an existing brand, or defining brand identity before naming or visual design. Trigger phrases — "brand strategy", "brand identity", "brand positioning", "buduj znacku", "brand archetyp", "positioning", "brand prism", "znackova strategie".
development1
brand-naming
Complete brand naming workflow — from brief through linguistic analysis to domain-checked finalists. Use when naming a company, product, SaaS, app, or service. Trigger phrases include "name my brand", "brand name", "company name", "product name", "how to name", "naming". Not for logo design (use logo-design) or brand voice definition (use brand-voice).
development1
churn-prevention
Reduces voluntary churn (cancel flow design, exit surveys, dynamic save offers) and involuntary churn (dunning, smart retries, payment recovery) for SaaS products. Use when churn rate is too high, designing cancel flows, building retention systems, or recovering failed payments. Triggers include "reduce churn", "cancel flow", "dunning", "failed payments", "retention". NOT for user onboarding (use product-led-growth), growth experiments (use growth-hacking), pricing strategy (use pricing), or UX optimization (use ux-optimization).
development1
competitor-pages
Creates high-converting X vs Y competitor comparison pages and alternative pages for SEO. Covers URL/title patterns, content structure, schema markup (Product + ItemList + FAQPage), fairness guidelines, table design for featured snippets, hub-and-spoke internal linking, programmatic generation at scale, and conversion optimization. Use when creating comparison landing pages, building 'alternatives to X' pages, or scaling competitor content programmatically. Trigger phrases: 'X vs Y', 'competitor comparison', 'comparison page', 'alternatives page', 'versus page'. NOT for general content optimization (use on-page-seo) or full programmatic SEO infrastructure (use programmatic-seo).
development1
compliance-reviewer
Reviews implementation against plan — checks all tasks implemented, DoD met, no missing pieces, no scope creep. Use after implementation is complete and before merge. Plan is source of truth. Works in both Claude Code and Gemini CLI.
tools1
plugins/copywriting/skills/brand-voice
--- name: brand-voice description: Guides you through creating a complete Brand Voice document — personality, voice attributes, tone adaptation, style rules, terminology, brand codes (recurring language signals), e-shop touchpoint mapping, and strategic word exclusion. Use when defining a new brand voice, auditing existing voice for consistency, auditing e-shop language across all touchpoints, or documenting voice guidelines for AI/copywriters/team. Trigger phrases: "define brand voice", "brand
tools1
build-error-resolver
Fixes build/type errors with minimal diffs. No refactoring, no architecture changes. Use when build fails (TypeScript compilation, Python type checks, Rust cargo build, etc.). Works in both Claude Code and Gemini CLI.
tools1
demo
Creates executable demo documents that prove a feature works with reproducible steps, using showboat and rodney for browser automation. Use after verification passes and the feature has visible UI, API, or CLI output worth demonstrating. Trigger phrases - "create demo", "prove it works", "udelej demo", "dokaž že to funguje", "showboat", "demo document". NOT for pure refactoring, config-only changes, or internal code reorganization with no visible output.
tools1
development-workflow
Orchestrates complete feature development from design through execution strategy selection, framework-specific implementation, and code review. Use when building, creating, or adding something new to a codebase. Trigger phrases - "build", "create", "add", "implement", "make", "set up", "I need", "I want", "přidej", "vytvoř", "udělej", "postav". NOT for fixing bugs (use debugging), finishing/merging (use finish), or purely frontend tasks with known stack (use frontend-app/frontend-lp).
development1
domain-checker
# Domain Availability Checker Skill ## Popis Tento skill umožňuje hromadnou kontrolu dostupnosti domén pomocí DNS a WHOIS lookupů. Funguje bez API klíče, zcela zdarma. ## Kdy použít - Uživatel chce zkontrolovat dostupnost domén - Brainstorming názvů pro projekty/mikroslužby - Hromadná kontrola více TLD kombinací - Hledání volných kreativních domén (.work, .io, .menu, .today, atd.) ## Jak použít ### Krok 1: Nainstalovat závislosti ```bash pip install python-whois dnspython --break-system-pack
development1
fastapi-workflow
Docs-first development workflow for Python + FastAPI + Pydantic v2 projects with async APIs, dependency injection, and SQLAlchemy. Fetches current documentation via MCP before any implementation. Use when building or modifying FastAPI backends, API endpoints, Pydantic models, or database operations. Trigger phrases - "fastapi", "python api", "backend api", "pydantic", "sqlalchemy", "async api", "dependency injection". NOT for frontend work (use frontend-app/frontend-lp) or non-Python backends.
tools1
finance-ops
Tracks unit economics, hidden costs, and margins across projects. Use when calculating CAC, LTV, margin analysis, cost breakdowns, or comparing profitability between projects. Trigger phrases — "unit economics", "kolik nas stoji zakaznik", "marze", "hidden costs", "kolik vydelavame", "cost per project", "financni prehled", "burn rate", "runway".
business1
research
Deep research on any topic using Claude (WebSearch), Gemini (web grounding), or both. Use when starting brainstorming on new topics, unfamiliar domains, or skill creation. Use when planning needs external knowledge (new libraries, APIs, best practices). Use when user says 'research', 'prozkoumej', 'zjisti', 'najdi informace'. Standalone or called from other skills.
development1
frontend-lp
Docs-first development workflow for landing pages, marketing websites, and product showcases using React/Vite/Tailwind/shadcn/Magic UI with animated components and premium UI. Use when building static marketing pages, product showcases, or conversion-focused landing pages. Trigger phrases - "landing page", "marketing site", "product showcase", "LP", "homepage", "sales page", "launch page". NOT for web applications with auth/state/CRUD (use frontend-app instead) or mobile apps (use expo-workflow/flutter-workflow).
development1
frontend-workflow
Docs-first development workflow for Vite/TypeScript/Tailwind/Alpine.js projects optimized for e-commerce UI. Fetches current documentation via MCP before any implementation. Use when building or modifying e-commerce frontends with Alpine.js and Tailwind. Trigger phrases - "e-commerce frontend", "shop UI", "product page", "cart", "tailwind alpine", "vite typescript". NOT for React-based landing pages (use frontend-lp) or React web apps (use frontend-app).
tools1
gdpr
GDPR and Czech data protection specialist — validates data processing, employee monitoring, consent, and DPIA requirements against GDPR (2016/679) and Czech ZZOÚ (110/2019). Use when asked about personal data processing, employee data, monitoring, cookies, data subject rights, or privacy compliance.
testing1
growth-hacking
Provides systematic, data-driven growth experimentation using Growth Process, ICE Scoring, and Must-Have Survey from Sean Ellis's Hacking Growth. Use when prioritizing growth experiments, setting up a growth process, or measuring if your product is must-have. Triggers include "how do I grow faster", "which channel first", "growth experiments", "do I have product-market fit". Do NOT use for creating offers (use offer-creation), positioning (use uvp-optimization), product onboarding (use product-led-growth), or SaaS metrics (use saas-bootstrap).
data-ai1
image-generation
Generate images via Ideogram 3.0 (typography, character/style consistency, brand colors) or Nanobanana / Google Imagen 3 (artistic textures, fast iterations). Cowork-friendly — uses bash + REST API, no MCP required, keys fetched from 1Password. Use whenever the user wants to create, generate, or produce any image — product photos, brand visuals, illustrations, social posts, mockups, posters, icons, or visual content. Triggers also on "Ideogram", "nanobanana", "Imagen", "vygeneruj obrázek", "udělej vizuál".
tools1
mac-cleanup
Safely free up Mac storage by finding and cleaning storage hogs — Docker (images, containers, build cache, volumes), Xcode (simulators, DerivedData, DeviceSupport), app caches, Homebrew cache, unused app data, and logs. Interactive — always asks before deleting. Use when user says "cleanup", "free space", "disk full", "storage", "uvolni misto", "maz disk", "malo mista", "kolik mam mista", or when disk space is running low.
development1
legal-orchestrator
Routes legal compliance questions to specialist skills (labor-law, gdpr). Use when asking about legal compliance, employment law, data protection, contract validity, or whether a feature design meets Czech regulations. Trigger phrases include "je to legalni", "zakonik prace", "GDPR", "pracovni smlouva", "je tohle v souladu se zakonem", "legal check". NOT for writing marketing copy or business strategy.
testing1
logo-design
Reference guide for logo design covering principles, color/shape/typography psychology, Paul Rand's 7-step test, professional 8-step process, and AI-assisted workflows. Use when creating a new logo, briefing a designer, evaluating existing logos, rebranding, or building brand identity from scratch. Trigger phrases include "design a logo", "evaluate my logo", "logo brief", "brand identity". Not for full brand strategy or brand guidelines — focused specifically on logo creation and evaluation.
development1
offer-creation
Creates compelling, high-value offers using Grand Slam Offer, Value Equation, and M-A-G-I-C Headline frameworks from Alex Hormozi's $100M Offers. Use when creating a new product/service offer, designing pricing and value stacking, making an offer stand out from competition, naming offers and headlines, or when conversion rate is low. Trigger phrases include "irresistible offer", "value stacking", "offer naming", "my offer doesn't convert". NOT for positioning strategy (use uvp-optimization), growth experiments (use growth-hacking), or onboarding optimization (use product-led-growth).
development1
on-page-seo
Optimizes individual web pages for search rankings through content and entity strategy. Covers the 8 On-Page Tablets (URL, titles, headers, keywords, LSI, images, outbound links, internal linking), Entity SEO (Knowledge Graph, entity homes, topical authority, siloing), and E-E-A-T framework. Use when optimizing page content for specific keywords, building entity authority, or auditing on-page SEO elements. Trigger phrases: 'on-page SEO', 'title tag', 'meta description', 'H1', 'keyword density', 'content optimization', 'E-E-A-T', 'entity SEO'. NOT for technical issues (use technical-seo), link building (use link-building), AI search (use ai-ready), or structured data implementation (use schema-markup).
development1
merge
Commits current work, merges feature branch into development, re-runs tests on merged result, and cleans up the feature branch and worktree. Use after verification passes, when user says "merge", "mergni", or when the verify skill confirms all checks pass. NOT for merging to main/production or for creating pull requests.
development1
plugins/copywriting/skills/newsletter
--- name: newsletter description: Writes high-converting emails — newsletters, promo campaigns, onboarding sequences, cold outreach — using a 9-step email anatomy framework with subject line techniques, personalization, PROTTO methodology, and psychological triggers. Use when creating any email that needs to drive opens, clicks, or replies. Trigger phrases: "write a newsletter", "email campaign", "subject line", "email sequence", "cold email". Do NOT use for website copy (use web-copy), product
tools1
security-review
OWASP Top 10 security checklist pro code review - injection, auth, XSS, CSRF, sensitive data
development1
product-led-growth
Helps build products that sell themselves using Bowling Alley Framework and MOAT Framework from Wes Bush's Product-Led Growth. Use when optimizing onboarding, choosing between freemium and free trial, reducing time-to-value, or deciding product-led vs sales-led approach. Triggers include "freemium or free trial", "users sign up but don't convert", "onboarding is confusing", "self-serve SaaS". Do NOT use for creating offers (use offer-creation), positioning (use uvp-optimization), growth experiments (use growth-hacking), or SaaS metrics (use saas-bootstrap).
development1
product-metrics
Helps define what to measure and how using North Star Metric, AARRR Pirate Metrics, and HEART frameworks. Use when choosing KPIs, defining success criteria, building analytics strategy, or evaluating product health. Triggers include "what metrics should we track", "what's our North Star", "are we measuring the right things", "how do I set up KPIs". Do NOT use for understanding customers (use product-discovery), prioritizing features (use product-prioritization), or defining long-term direction (use product-strategy).
development1
product-prioritization
Provides structured frameworks (RICE, ICE, MoSCoW, Kano) to rank features and decide what to build first. Use when prioritizing a backlog, resolving stakeholder disagreements, or handling feature request overload. Triggers include "what should we build next", "how do I prioritize", "CEO wants X but data says Y", "20 ideas and 3 developers". Do NOT use for understanding customer needs (use product-discovery), defining long-term direction (use product-strategy), or measuring impact (use product-metrics).
development1
programmatic-seo
Builds and scales programmatic SEO — auto-generated landing pages from templates + structured data targeting thousands of long-tail keywords. Use when planning database-driven page generation (integration pages, comparison pages, city/location pages, template galleries, directory/aggregator pages), scaling organic traffic with repeatable patterns, or building product-led SEO experiences. Trigger phrases include "programmatic SEO", "pSEO", "auto-generate pages", "template pages at scale", "database-driven pages", "long-tail at scale". NOT for hand-written editorial content (use on-page-seo), keyword research phase (use keyword-research), fixing crawl/speed/indexing issues (use technical-seo), or optimizing for AI search engines (use ai-ready).
development1
ralph-loop-setup
Creates the 4-file structure (prd.json, prompt.md, progress.txt, ralph.sh) for autonomous AI coding loops that implement tasks unattended. Use when user has multiple small implementation stories with clear acceptance criteria and wants code to ship overnight or in the background. NOT for exploratory work, complex features requiring design decisions, tasks needing human judgment, or when no automated validation is available.
development1
security-review
Performs OWASP Top 10 security audit on code — checks for SQL injection, XSS, CSRF, broken authentication, sensitive data exposure, and access control issues. Use when reviewing code before deploy, after adding auth or payment features, during security audits, or as part of deep-review. Trigger phrases include "security check", "review for vulnerabilities", "security audit", "check for injection". Not for infrastructure/DevOps security, network configuration, or cloud IAM reviews — focused on application-level code security.
development1
storytelling
Use when writing story-driven landing pages, pitch decks, brand messaging, case studies, founder stories, About pages, sales emails, presentations, or any content that needs narrative structure. Use when user asks to make copy more compelling, engaging, or persuasive through storytelling. Trigger phrases - "tell a story", "make it more compelling", "narrative structure", "story-driven", "brand story", "founder story", "customer story", "pitch narrative". Do NOT use for fiction writing, creative writing workshops, or screenplays. For general copywriting routing use copywriting-orchestrator instead.
data-ai1
ux-orchestrator
Orchestrates UX work by detecting problem type and routing to specialized skills (ux-optimization, ux-expert-dialogue, uvp-optimization) based on keywords, context, and business goals. Use for any UX improvement request where the right specialist is unclear, vague requests like "make it better" or "improve conversion", new website/landing page projects, UX audit requests, or multi-aspect UX work. Trigger phrases include "improve UX", "UX audit", "make it convert better". NOT for when you already know the exact specialist skill needed, just A/B testing (use ux-optimization), just expert critique (use ux-expert-dialogue), or just positioning (use uvp-optimization).
development1
plugins/copywriting/skills/web-copy
--- name: web-copy description: Writes and optimizes all website copy — homepage (9 key elements), About Us, landing pages, sales pages, and blog strategy. Covers Blueprint 5-question framework, Triada persuasion, PROTTO steps 4-6, hero images, formatting, and psychological triggers. Use when creating or auditing any website page. Trigger phrases: "homepage copy", "landing page", "about us page", "sales page", "website text", "web redesign". Do NOT use for product descriptions (use product-copy)
tools1
workflow-optimization
Adds Anthropic-inspired workflow optimization to existing projects - mistakes tracking, verification checklists, context pruning, code quality hooks, pattern learning, and build error resolution
development1
ios-ui-guidelines
Provides Apple Human Interface Guidelines adapted for React Native + Expo + React Native Paper, covering typography, spacing, colors, dark mode, shapes, animations, Liquid Glass, gestures, forms, navigation, and accessibility. Use when designing, building, or reviewing iOS screens in React Native apps, or when user asks about HIG compliance, iOS design patterns, or "how should this look on iOS". NOT for Android-specific design or web-only UI.
development1
seo-orchestrator
Routes SEO requests to the correct specialist skill based on intent. Use when user asks for general SEO help, a full audit, or when the specific SEO discipline is unclear. Trigger phrases: 'SEO', 'optimize for search', 'SEO audit', 'search engine optimization'. Routes to 12 specialist skills covering on-page, technical, schema, images, sitemaps, i18n, keywords, links, competitors, programmatic, AI search, and app store optimization.
testing1
deep-review
Use after completing significant code changes - orchestrates specialized review skills (security, database, API, UX) based on auto-detected stack and scope
development1
fullstack-orchestrator
Use when developing fullstack applications - orchestrates backend and frontend workflow skills, coordinates API contracts, and ensures consistency between layers. Detects tech stack automatically or asks.
development1
openspec-workflow
Use when implementing complex features requiring clear specifications before coding - creates spec-driven workflow with proposals, task breakdown, and delta documentation; works standalone or with OpenSpec CLI for enhanced features
tools1
dtp-typography
Specialized DTP and Typography skill for beginning readers and individuals with dyslexia. Based on the "Supermáňa" methodology and Christian Boer's Dyslexie font principles. Focuses on syllable-based decoding, extreme spacing, and weighted-base fonts to prevent letter mirroring and visual crowding. Use when designing children's books, educational materials, or accessible interfaces for early learners. Trigger phrases - "dtp for kids", "typography for dyslexia", "beginning reader layout", "syllable spacing", "Supermáňa style".
testing1
knowledge-book
Use when writing a non-fiction knowledge book — compact books that package expertise into memorable formats (like Steal Like an Artist, Rework, Zluta kniha). Two modes — setup (creates book blueprint with positioning, archetype, voice, outline) and chapter (writes one chapter per invocation). Trigger phrases — "write a book", "napsat knihu", "knowledge book", "book chapter", "kapitola", "book blueprint", "osnova knihy", "kniha o". Do NOT use for fiction, academic papers, blog posts (use web-copy), or marketing copy (use copywriting-orchestrator).
development1
plugins/copywriting/skills/product-copy
--- name: product-copy description: Creates high-converting e-commerce product descriptions using a 7-step framework — product classification (Type A technical vs Type B experiential), competitive research, page structure with 11 sections, SEO elements, and quality controls. Use when writing or optimizing product pages for e-shops, marketplaces, or online stores. Trigger phrases: "product description", "e-shop copy", "product page", "e-commerce text". Do NOT use for general website copy (use web
tools1
debugging
Systematic debugging wrapper that investigates, hypothesizes, verifies, and fixes bugs using TDD. Use when something is broken, crashing, or producing errors. Trigger phrases - "fix", "broken", "error", "crash", "doesn't work", "debug", "oprav", "nefunguje", "spadá", "chyba", "proč to nefunguje", "nejde", "selhává". NOT for building new features or refactoring working code (use development-workflow instead).
development1
expo-workflow
Docs-first development workflow for React Native + Expo projects (SDK 54+, RN 0.79+) with Tamagui and Liquid Glass for premium iOS UI. Fetches current documentation via MCP before any implementation. Use when building or modifying Expo/React Native mobile apps. Trigger phrases - "expo", "react native", "mobile app", "tamagui", "liquid glass", "iOS app", "Android app". NOT for web-only frontends (use frontend-app/frontend-lp) or Flutter apps (use flutter-workflow).
tools1
finish
Orchestrates all post-execution phases in sequence - verify (tests, build, lint), demo (optional executable proof), merge (commit, merge to development branch, cleanup), and wrapup (context, lessons, docs). Use after all tasks from an implementation plan are complete. Trigger phrases - "finish", "done coding", "dokonči", "hotovo", "zabal to", "wrap up", "merge it". NOT for mid-implementation work or when tasks are still incomplete.
development1
frontend-app
Docs-first development workflow for web applications using Vite/TypeScript/Tailwind/Alpine.js - dashboards, admin panels, CRUD apps, e-commerce backends. Use when building interactive web apps with auth, state management, and server-side rendering. Trigger phrases - "web app", "dashboard", "admin panel", "CRUD app", "e-commerce backend", "vite app", "alpine.js app". NOT for landing pages or marketing sites (use frontend-lp instead) or mobile apps (use expo-workflow/flutter-workflow).
development1
inbox
Fetches and processes items queued from mobile via email (articles, GitHub repos, links, newsletters). Use when user says "inbox", "zkontroluj inbox", "check inbox", "co je noveho", or at session start to review new items. NOT for general email management or reading unrelated emails.
testing1
openspec-workflow
Implements spec-driven development with a 5-stage workflow (proposal, alignment, implementation, archive, spec update) that separates specifications from code. Use when building complex features requiring multiple steps, stakeholder alignment, or explicit scope boundaries, or when user says "openspec", "specs first", or "write specification". NOT for trivial bug fixes, single-line changes, config updates, or throwaway prototypes.
development1
second-opinion
Gemini second opinion on any document — specs, plans, designs. Provides a DIFFERENT perspective, not validation. Use after writing a design spec or plan — provides Gemini's perspective before user review. Use when user says 'second opinion', 'druhy nazor', 'co na to Gemini', 'over to Gemini'. Always uses Gemini (different AI = different blind spots).
documentation1
session-context
Manages persistent context between Claude Code sessions by loading ACTIVE_CONTEXT.md and DECISIONS.md at session start and saving progress at session end. Use when user says "load context", "nacti kontext", "save context", "uloz kontext", "log decision", or automatically at session start/end. NOT for project setup (use projectsetup) or for tracking mistakes (use workflow-optimization).
development1
gastro-education
Use when creating educational content about gastronomy and restaurant business — courses, books, video series, training programs. Also use when reviewing or improving existing gastro educational materials. Trigger phrases include "gastro kurz", "kniha o restauraci", "vzdelavaci obsah", "gastro education", "restaurant course", "training program".
testing1
launch-strategy
Plans and executes product launches for SaaS, apps, and digital products. Covers launch type selection (soft/hard, MVP/full, PLG/sales-led), pre-launch audience building, multi-platform launch execution (Product Hunt, HN, Twitter/X, Reddit), and post-launch 30-60-90 day plan. Use when planning a product launch, preparing for Product Hunt or Hacker News, building a pre-launch waitlist, or deciding launch timing and channels. Triggers include "launch plan", "Product Hunt strategy", "how to launch", "pre-launch checklist", "go-to-market". NOT for ongoing growth experiments (use growth-hacking), product onboarding flows (use product-led-growth), pricing strategy (use pricing), or positioning work (use uvp-optimization).
development1
product-discovery
Guides customer research and idea validation using JTBD, Opportunity Solution Trees, and The Mom Test. Use when you need to understand customer needs, validate ideas, run user interviews, or decide what to build. Triggers include "do customers want this", "how do I validate", "user research", "what should we build". Do NOT use for prioritizing known opportunities (use product-prioritization), defining long-term direction (use product-strategy), or measuring product health (use product-metrics).
development1
product-market-fit
Evaluates whether your product has achieved product-market fit using PMF Survey (40% test), PMF Engine, and Crossing the Chasm frameworks. Use when asking "do we have PMF", measuring retention, evaluating churn, or deciding whether to scale or invest in growth. Triggers include "are we building the right thing", "users sign up but don't stay", "should we scale". Do NOT use for understanding customer needs (use product-discovery), choosing what to build (use product-prioritization), or defining direction (use product-strategy).
development1
product-strategy
Connects company vision to execution using Product Operating Model, OKRs, and outcome-driven roadmapping. Use when defining product vision, setting goals, building roadmaps, or aligning teams on long-term direction. Triggers include "what's our product vision", "how do I set OKRs", "we need a roadmap", "where are we going". Do NOT use for deciding what to build specifically (use product-discovery), deciding build order (use product-prioritization), validating PMF (use product-market-fit), or choosing metrics (use product-metrics).
development1