review-learnings
Synthesizes accumulated QA learnings from .qa-learnings/ledger.md into prioritized, actionable plugin improvements. Use when the user says "review learnings", "what have we learned", "improve the plugin", "learnings report", or "synthesize QA feedback".
resilience-audit
Audits web apps for resilience against unexpected user behavior — accidental, edge-case, and chaotic. Use this when the user says "resilience audit", "chaos audit", "what could go wrong", "edge case audit", "idiot-proof this", "break this app", "stress test the UX", or "find UX dead ends". Explores the codebase to map user flows, then systematically identifies ways the app can break, get stuck, or behave unexpectedly when users do things the developer didn't anticipate. Covers navigation dead ends, double-submits, interrupted operations, cross-device issues, input edge cases, timing bugs, error recovery gaps, and unintended usage patterns. Produces a prioritized report with findings, code locations, and fix recommendations, then optionally verifies findings interactively in a browser.
use-profiles
Load saved Playwright storageState authentication profiles before browser automation. Activates when `.playwright/profiles.json` exists and browser work begins on authenticated pages. Trigger phrases include "use profile", "load profile", "browser as [role]", "authenticated browser", "logged in browser session".
desktop-workflow-generator
Generates desktop browser workflow documentation by exploring the app's codebase, then walking through the live app with the user step-by-step via Playwright to co-author verifications. Use when the user says "generate desktop workflows", "create desktop workflows", "update desktop workflows", or "generate browser workflows".
playwright-runner
Executes workflow markdown files interactively via Playwright CLI, stepping through each workflow action in a real browser. Use when the user says "run workflows", "run playwright", "test workflows", "execute workflows", or wants to interactively test their app against workflow documentation. Supports desktop, mobile, and multi-user workflows with authentication.
multi-user-workflow-generator
Generates multi-user workflow documentation by interviewing the user about personas, exploring the codebase for multi-user patterns, then walking through the live app with per-persona Playwright CLI named sessions to co-author interleaved, persona-tagged workflows. Use when the user says "generate multi-user workflows", "create multi-user workflows", or "generate concurrent user workflows". Produces persona-tagged workflow markdown that feeds into the multi-user converter and Playwright runner.
mobile-workflow-to-playwright
Converts mobile workflow markdown into a self-contained Playwright test project with mobile viewports (Chromium + WebKit), authentication scaffolding, UX anti-pattern assertions, and CI workflow. Use when the user says "convert mobile workflows to playwright", "translate mobile workflows to CI", or "generate mobile playwright tests".
desktop-workflow-to-playwright
Converts desktop workflow markdown into a self-contained Playwright test project with authentication scaffolding and CI workflow. Use when the user says "convert desktop workflows to playwright", "translate desktop workflows to CI", "generate desktop playwright tests", or wants to promote desktop workflows to automated CI tests.
multi-user-workflow-to-playwright
Converts multi-user workflow markdown into a self-contained Playwright test project with per-persona authentication, multi-context test patterns, and CI workflow. Use when the user says "convert multi-user workflows to playwright", "translate multi-user workflows to CI", or "generate multi-user playwright tests".
keyword-wedge
Analyzes an app's codebase and cross-references Google Search Console, PostHog, and Google Keyword Planner to identify low-competition keyword footholds and track expansion into adjacent terms. This skill should be used when the user says "keyword wedge", "find keyword opportunities", "seo analysis", "keyword strategy", "find search wedges", "keyword research for my app", "grow organic traffic", "what keywords should I target", "SEO for my app", "organic search strategy", or "how to rank higher". Generates markdown and HTML reports and maintains state across runs for expansion tracking.
mobile-workflow-generator
Generates mobile browser workflow documentation by exploring the app's codebase, then walking through the live app with the user step-by-step via Playwright in a mobile viewport (393x852) to co-author verifications. Use when the user says "generate mobile workflows", "create mobile workflows", "update mobile workflows", or "generate mobile browser workflows". Produces numbered workflow markdown files that feed into the mobile converter and Playwright runner. Includes iOS HIG awareness and mobile UX anti-pattern detection.
adversarial-audit
Audits SaaS and usage-based web apps for adversarial usage patterns — accidental, opportunistic, and deliberate. Use this when the user says "adversarial audit", "abuse case audit", "idiot-proof this app", "find usage exploits", "business logic audit", or "how could users break this". Explores the codebase to map the economic surface area (pricing tiers, usage limits, free trials, costly resources), then generates abuse cases where user behavior — intentional or not — could break assumptions, bypass limits, amplify costs, or corrupt state. Produces a prioritized markdown report with findings, code locations, and fix recommendations, then optionally verifies findings interactively in a browser.
sveltekit-svelte5-tailwind-skill
Comprehensive integration skill for building sites with SvelteKit 2, Svelte 5, and Tailwind CSS v4
codeagent
Execute codeagent-wrapper for multi-backend AI code tasks. Supports Codex, Claude, and Gemini backends with file references (@syntax) and structured output.
living-documentation
Sync spec files with code changes. Triggers when modifying code that affects .kiro/specs/*/requirements.md or .kiro/specs/*/design.md. Use after implementing features, fixing bugs, or refactoring that changes behavior documented in specs.
codex
Execute Codex CLI for code analysis, refactoring, and automated code changes. Use when you need to delegate complex code tasks to Codex AI with file references (@syntax) and structured output.
gemini
Execute Gemini CLI for AI-powered code analysis and generation. Use when you need to leverage Google's Gemini models for complex reasoning tasks.
kiro-specs
Create a Kiro spec for a feature in .kiro/specs create/update feature spec/PRD/RFC—requirements, design doc, and implementation tasks checklist.Trigger on spec/specification/PRD/RFC/tech spec, requirements/user story/acceptance criteria/EARS, design doc/architecture, task breakdown/implementation plan/checklist; 需求/验收/设计/任务.
multi-agent-orchestration
Orchestrate multi-agent workflows from a Kiro spec using codex (code) + Gemini (UI), including dispatch/review/state sync via AGENT_STATE.json + PROJECT_PULSE.md; triggers on user says "Start orchestration from spec at <path>", "Run orchestration for <feature>", or mentions multi-agent execution.
sequential-orchestration
Execute spec tasks one at a time with tmux visibility. Python-based orchestrator with transparent serial execution. Triggers on: rate limit, overnight run, throttled execution, avoid quota exhaustion, sequential mode, slow execution, or user says 'Run sequential orchestration for <spec>'.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
design-doc
Create technical design documents for new features, systems, refactoring plans, API designs, and database schemas. Use when asked to write a design doc, TRD (technical requirements document), RFC, or system design document. Triggers on requests like "write a design doc for X", "design the Y feature", "create a technical spec", or "plan the architecture for Z".
newsletter
Write a ready-to-send newsletter issue (and, when starting from zero, the recurring format and cadence to commit to): subject line options, preview text, body in one of six proven formats, and a single engagement CTA. Use when the user says 'write my newsletter', 'this week's issue', 'I want to start a newsletter', 'what should I send my list', 'help me email my subscribers regularly', or shares content to turn into an issue. Produces a complete issue draft with subject/preview variants — or a Newsletter Blueprint (format, cadence, section template) plus the first issue when setting one up.
product-photography
Produces professional AI product photography — clean e-commerce shots, lifestyle scenes, hero images, macro detail shots, and flat lays — as generation-ready prompt specs, and generates the files via FAL.ai fal-ai/nano-banana-pro when the automation is configured. Use when the user says 'product photos', 'shots of my product', 'images for my store / listing / landing page', 'hero image for my product', 'lifestyle photos', or shares a product needing marketing imagery. Produces one prompt-spec block per shot (shot type, lighting, background, composition, aspect ratio, negative constraints) with a shot list, variant plan, and file-naming conventions; runs docs/creative_cli.py product when FAL_API_KEY is set.
original-design
Facilitates an interactive session that turns a product or subject into an original, internally consistent visual design language for any artifact — infographics, video storyboards, websites, or mobile app UI/UX. Use when the user wants an original design language, identity, or art direction, or when a design feels generic, derivative, 'AI-default,' or inconsistent and needs one unifying idea. Triggers on 'design language', 'art direction', 'make it original', 'visual identity', 'looks generic', 'design a world'. Produces a completed Design Language Brief (core metaphor, visual vocabulary, design DNA, signature constraint, Originality Test verdicts) saved to the project and handed off to the production skill for the chosen medium.
image-generation
Turns any request for an AI-generated image into precise, generation-ready prompt specs and — when the FAL.ai automation is configured — the generated files themselves, using the single model fal-ai/nano-banana-pro. Use whenever the user asks to 'generate an image', 'make a picture of X', 'create a thumbnail / hero image / illustration / infographic', 'write me a prompt for this image', or any visual that isn't specifically product photography, a social-platform graphic, or a brand mark (hand those to the sibling skills). Produces one prompt-spec block per asset (subject, style, composition, lighting, mood, aspect ratio, negative constraints) plus file-naming and variant conventions, and runs docs/creative_cli.py to generate when a FAL_API_KEY is available.
lead-magnet
Design a lead magnet — the free offer that trades real value for an email address — by picking the right problem slice, hook, and format, validating it, and drafting the asset. Use when the user says 'grow my email list', 'I need a lead magnet / freebie / opt-in', 'create a free download', 'how do I capture leads', 'nobody signs up', or when a funnel needs an entry offer before the paid ask. Produces a Lead Magnet Spec (title, hook, format, contents outline, delivery, follow-up path) plus a draft of the asset itself when the format allows.
keyword-research
Build a prioritized keyword cluster map using the 6 Circles Method — keywords at the intersection of positioning alignment, customer language, competitor blind spots, workable search volume, real expertise, and business intent. Use when the user asks 'what keywords should I target', 'what should I write about', 'find SEO opportunities', 'plan my content strategy', 'what does my audience search for', or before any SEO content is written. Produces a Keyword Map: scored keywords grouped into topic clusters, each cluster mapped to the article that should target it, ready to hand to content production.
seo-content
Write a publish-ready, search-optimized article for a target keyword: SERP-validated brief, full draft matched to search intent, on-page metadata (title tag, meta description, URL slug), and schema markup. Use when the user says 'write a blog post about X', 'write an article that ranks', 'create SEO content', 'I need content for this keyword', or hands over a keyword/content brief from an SEO plan — even if they never say 'SEO'. Also use to rewrite or upgrade an existing article that isn't ranking. Produces the complete article plus a metadata block and an on-page checklist result.
positioning-angles
Find and state a market positioning that differentiates the user's offer: match the message to the market's maturity stage, name the unique mechanism, choose one psychological angle, and pressure-test the result. Use when the user asks 'how do I position this', 'how do I stand out', 'why should anyone pick us', 'write my value prop / tagline / headline claim', 'our marketing sounds like everyone else's', or when any copy or content work stalls because there's no clear core claim — even if they never say the word positioning. Also works in audit mode on an existing positioning. Produces a Positioning Statement: market stage, named mechanism, chosen angle with the claim written out, and a pass/fail test record.
error-handling-recovery
Audit and implement an app's error UX end-to-end: rewrite error messages, place them correctly, add recovery actions, and build error states for validation, network, permission, system, and 404 failures. Use when the user says 'improve my error handling', 'my error messages suck', 'users get stuck when something fails', 'add form validation errors', 'handle offline/network errors', 'design a 404 page', or when a review finds bare 'Something went wrong' strings, silent failures, or errors with no way forward. Produces an error-state matrix (every failure mode × message × recovery action) plus the implemented error components and copy.
sol-orchestrator
Orchestrates non-trivial software implementation with GPT-5.6 Sol as the decision-making root and bounded Sol Light/Medium, Terra, Luna, GPT-5.5, and Claude Sonnet 5 executors. Use when the user asks to build, implement, integrate, migrate, refactor, or fix work spanning multiple files or systems; requests parallel agents or an implementation plan; or needs evidence-backed execution with specialist routing, review gates, and end-to-end validation. Produces a grounded specification, dependency-aware task graph, implemented changes when authorized, and a verified completion report. Skip trivial one-file changes and explanation-only requests.
foundation-sprint
Evaluate, pressure-test, or sharpen any product, feature, app, startup, or business idea using the Foundation Sprint method from Jake Knapp and John Zeratsky's book Click (How to Make What People Want). Use this whenever the user wants to decide what to build, judge whether an idea is worth pursuing, find product-market fit, nail differentiation, choose between approaches or directions, write or critique a value proposition, or make an existing product better. Trigger on phrases like 'is this a good idea', 'should I build this', 'validate this idea', 'what should I build', 'how do I stand out', 'how do I differentiate', 'will people want this', 'evaluate my idea', 'critique my product', 'how do I improve my product', 'founding hypothesis', 'positioning', or any time someone is starting a project or stuck choosing a direction, even if they never mention the book. Produces a testable Founding Hypothesis, a differentiation 2x2, a Magic Lenses comparison, and a prove-it scorecard.
fable-like-implementation
Use when the session model is Opus 4.8 (claude-opus-4-8) and the user asks to build, add, implement, refactor, migrate, or integrate something non-trivial — 3+ files, a new dependency or subsystem, an API contract or database schema change, or meaningful ambiguity or risk — or says "plan this out", "spec this", "how should we build", "create an implementation plan". Also use when the user says "just implement it" but the work is non-trivial. Do NOT use on Claude Fable 5 or any other model, nor for one-line fixes, typo corrections, single-function changes, or questions that require no code change.
creative-strategist
Establishes a brand's visual direction and compresses it into a Creative Direction Brief with a paste-ready 'style block' that every downstream image prompt reuses, so all generated assets look like they came from one brand. Use when the user says 'define my brand style', 'I want a consistent look', 'what should my visuals look like', 'help me pick an aesthetic / mood / color palette', 'my generated images all look different', or before any multi-asset creative work where no style guide exists yet. Produces the Creative Direction Brief: aesthetic profile, palette with hex codes, style block for prompts, and prohibitions.
product-design-review
Run an evidence-based product design and UI/UX review of a digital product (web, mobile, desktop) — heuristic evaluation, task walkthroughs, visual and interaction critique, and WCAG 2.2 AA accessibility checks. Use when the user says 'review my app/page/site', 'critique this UI', 'something feels off', 'why are users dropping off', 'audit our onboarding/checkout/dashboard', 'is this usable/accessible', or shares a URL, screenshot, Figma link, or codebase and asks what to improve — even if they never say 'design review'. Produces a Design Review Report: executive summary, prioritized findings table with evidence and severity, flow walkthroughs, accessibility blockers, and next steps routed to the skill that fixes each category.
tweet-writer
Write high-engagement tweets and X/Twitter threads, grounded in live research of what's currently working in the user's niche: researches viral examples via web search, then drafts hook variants, a single-tweet version, and a thread version with alternates to test. Use when the user says 'write a tweet about X', 'turn this into a thread', 'help me go viral', 'grow my X/Twitter account', 'my tweets get no engagement', or shares an idea/article to tweet — any X/Twitter content request. Produces a Tweet Package: 3 hook options, final single tweet, full thread, and posting notes.
loading-states
Audit an app's async surfaces and implement the right loading, progress, and empty states — skeleton screens, spinners, progress bars, first-use/no-results/error-empty views — chosen by expected latency and layout knowledge. Use when the user says 'add loading states', 'the page just goes blank while fetching', 'add a skeleton screen', 'users think it's frozen', 'spinner or skeleton?', 'design the empty state', 'zero state', or when reviewing an app whose fetches show nothing. Produces a loading/empty-state audit of every async surface plus the implemented components.
layout-system
Fix or build responsive layout: page shells, grids, card layouts, sidebars, breakpoint strategy, container queries. Use when the user says 'this breaks on mobile', 'the layout is messy', 'things don't line up', 'our spacing is inconsistent between sections', 'make this responsive', 'center this properly', or asks for a dashboard/page/grid layout. Inspects existing CSS for layout smells (fixed widths, absolute positioning, media-query sprawl), then produces working layout code — refactored CSS/JSX with Grid/Flexbox decision rules applied, breakpoints derived from content, and a responsive verification checklist. Hands off pure spacing-token questions to design-foundation and text-readability questions to typography-system.
seo-strategy
Build a complete, prioritized SEO strategy for a site: topical authority map, winnable-keyword shortlist, content production pipeline, link-building plan, and technical baseline. Use when the user wants to grow organic traffic, asks 'how do I rank on Google', 'why isn't my site getting traffic', 'build me an SEO plan/strategy', 'what keywords should I target', 'how do I get backlinks', or wants to audit or scale their SEO — even if they never say the word 'strategy'. Produces an SEO Strategy Document with a scored keyword shortlist, a phased action plan sequenced by dependency, and a measurement plan.
sprint-runner
Use when the user wants to RUN a sprint as a facilitated workshop with a virtual team — not just get sprint-style analysis. Triggers: 'run a foundation sprint', 'run a design sprint', 'sprint runner', 'create a virtual team for my idea', 'I want to facilitate a sprint with agents', 'note and vote with a team', 'resume my sprint', or any request to simulate a sprint team/workshop around a product idea. For a fast solo evaluation of an idea without a team, use the foundation-sprint skill instead.
talking-head
Plan presenter-led and UGC-style videos: choose the presenter archetype, define styling, setting, lighting, and framing, write the hook/body/CTA script skeleton, and produce keyframe prompts for the repo's FAL.ai pipeline. Use whenever the user wants a talking-head video, presenter video, UGC ad, testimonial, founder video, explainer with a person on camera, spokesperson content, or 'someone talking about my product' — even if they just say 'I need a video of a person explaining this'. Produces a Talking Head Video Spec: presenter definition, look/setting/lighting/framing decisions, timed script skeleton, and generation-ready keyframe prompts for fal-ai/nano-banana-pro.
interaction-physics
Design and implement the motion layer of a UI — microinteractions, transitions, hover/press feedback, and animation timing/easing — as working CSS/JS plus a written animation spec. Use when the user says 'the app feels janky', 'animations feel off', 'make it feel smoother/snappier', 'add a transition', 'the modal just pops in', 'buttons feel dead', 'add some polish/delight', or when interactions give no feedback. Also use to audit existing animations for timing, easing, performance (GPU properties), and reduced-motion support. Produces an animation spec (duration/easing per interaction class) and the implemented transitions.
social-graphics
Produce platform-correct social media graphics: pick the right dimensions and layout per platform, write the headline/body/CTA copy, build the generation prompt, and generate the image via the repo's FAL.ai pipeline. Use whenever the user wants a social post visual, Instagram post/story/carousel, LinkedIn graphic, Twitter/X image, TikTok thumbnail, Pinterest pin, launch announcement graphic, or 'something to post about X' — even if they never name a platform. Also use to adapt one design across several platforms. Produces a Social Graphic Spec per asset (platform, dimensions, layout, copy, full generation prompt) plus generated images when FAL_API_KEY is available.
remotion-script-writer
Write a complete, render-ready Remotion video script as structured JSON: analyze the user's codebase or product, break the video into timed scenes, specify every visual element, animation, transition, and voiceover line, and list required assets and Remotion packages. Use whenever the user wants a Remotion video, a programmatic/code-rendered video, a product demo video of their app, an animated coding tutorial, a data-visualization video, or short-form animated social content — trigger on 'make a video of my app', 'Remotion', 'animated demo', 'code walkthrough video', 'render a video from code'. Produces a Remotion Script JSON (videoMetadata, scenes[], requiredAssets, technicalRequirements) that Remotion agent tooling can implement directly.
product-video
Plan an animated product video end-to-end: pick the video type, define the animation style and pacing, write a beat-by-beat shot list, and produce ready-to-run keyframe prompts. Use whenever the user wants a product video, product animation, launch video, promo or ad video, animated product reveal, 360 spin, feature showcase, or 'a short video for my product' — even if they only say 'I need a video for the launch' or 'make my product look good in motion'. Also use to storyboard a video another tool will render. Produces a Product Video Production Spec: concept, beat sheet with timings and transitions, keyframe prompt list for fal-ai/nano-banana-pro, and audio/CTA direction.
frontend-orchestrator
Diagnose a codebase's frontend design maturity and route the work through the right sequence of frontend-design skills. Use when the user makes a broad or vague design request — 'make this look better', 'polish the UI', 'this feels like an MVP', 'our frontend is a mess', 'where do I start with design', 'make it feel professional', 'plan a design system' — or when a request spans multiple design concerns and it's unclear which single skill applies. Assesses maturity by inspecting the actual code (Tailwind config, CSS variables, component structure, hex-code drift), picks one of five implementation paths, and produces a design roadmap: an evidence-backed maturity diagnosis plus an ordered skill sequence with the artifact each step passes to the next. If the request clearly maps to one concern (only spacing, only color, only type), skip this and invoke that skill directly.
email-sequences
Write a complete automated email sequence, every email fully drafted: welcome sequence for new subscribers, ongoing nurture rotation, conversion sequence for an offer, or launch sequence for something new. Use when the user says 'write my welcome emails', 'set up a drip campaign', 'I'm launching X and need emails', 'nurture my list', 'write a sales email sequence', or connects a lead magnet to follow-up — even if they don't know which sequence type they need. Produces a sequence map (per-email purpose and send-day) plus full drafts: subject line, preview text, body, and one CTA per email.
orchestrator
Dispatcher for the creative suite: diagnoses a multi-asset creative request with a few questions, then routes it through the right sequence of creative skills, naming the artifact each step passes to the next, and wires in the FAL.ai automation (single model fal-ai/nano-banana-pro via docs/creative_cli.py) when available. Use when the user asks for several creative deliverables at once or an outcome that implies them — 'assets for my product launch', 'set up my brand visuals', 'I need a logo, product shots, and social posts', 'a week of content', 'rebrand everything' — or when it's unclear which creative skill applies. Produces a Creative Production Plan: chosen route, ordered skill sequence with hand-off artifacts, generation checklist, and asset output map. For a single obvious asset, skip this and use the specific skill directly.
accessibility-excellence
Audit a frontend against WCAG and fix what fails: semantic HTML, keyboard navigation, focus management, screen-reader support (ARIA), color contrast, forms, and media alternatives. Use when the user asks 'is this accessible', 'make this WCAG/AA compliant', 'add keyboard navigation', 'fix screen reader support', 'a11y audit', 'we got an accessibility complaint/legal notice', or whenever building/reviewing UI components with interactive behavior — even if accessibility isn't mentioned. Produces a prioritized accessibility audit (issue × WCAG criterion × severity × fix) plus the implemented fixes in code.
Page 816 of 1670 · 83497 results
