setup-claude
Interactive Claude Code repository setup and optimization. Configures the complete ecosystem - skills, commands, subagents, hooks, rules, MCPs, and plugins. Invoke with /setup-claude init or /setup-claude audit.
sprint-protocol
Use when turning founder requirements, research packets, plans, specs, and system designs into one or more independently executable Claude/Cloud Code implementation sprints with story writing, review, execution, optional verification, and sprint-level commits.
agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
launchpad
Decide HOW to run a coding task — interactive, goal mode, or a workflow — then author the launch-ready prompt or goal package for Claude Code, Codex, or Antigravity. Use when the user says "launchpad", "start a goal", "set up a goal/sprint", "should this be a goal or interactive", "plan an autonomous run", "I want to brain-dump a task", "help me write a goal prompt", or is about to kick off a long autonomous run and wants it scoped, delegated, and verifiable first.
qa-video-producer
Use after QA has already passed to produce founder-facing proof videos with a Browser Use-verified workflow, a Playwright-recorded walkthrough, Remotion intro/outro, and Deepgram narration. Never use for partial, failed, or blocked QA runs.
dogfood
Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.
browser-proof-video
Capture browser proof artifacts and render final verification videos. Use when proof-driven verification needs Agent Browser screenshots/WebM/logs, artifact validation, Deepgram narration, or Remotion MP4 output.
code-review-swarm
Run a structured code-review swarm for a PR, branch, or diff. Use when proof-driven verification needs read-only review shards, especially when subagents are explicitly authorized or the diff exceeds 10 files or 1,200 diff lines.
computer-use-fallback
Use Computer Use as a fallback when proof-driven verification cannot be completed with structured browser automation. Applies to native desktop apps, browser extensions, existing logged-in browser profiles, iOS simulators, file pickers, desktop GUI-only flows, or bugs that only reproduce in a real GUI.
remotion-best-practices
Best practices for Remotion - Video creation in React
verification-setup
Prepare or diagnose the proof-driven verification environment. Use when asked to set up, install, upgrade, doctor, validate prerequisites, or troubleshoot Agent Browser, ffmpeg, Deepgram CLI, Remotion, Next.js DevTools MCP, or GTM Hub dev-server readiness for proof-driven verification.
verify-pr-proof
Single-invocation ProofOps orchestrator for verifying a PR, branch, or completed coding task end to end with definition-of-done gating, Code Review agents, Browser QA agents, Developer Fixer agents, optional framework diagnostics, Agent Browser evidence, iterative fixes, validated artifacts, optional Remotion plus Deepgram proof video, and final commit. Use when the user asks to verify, review, prove, QA, test, inspect a PR/branch/task, create evidence, produce proof of work, or run ProofOps.
qa-video-director
Use after QA has passed to plan and produce polished founder-facing proof videos as separate intro, deliberate walkthrough, and optional closeout segments with synchronized narration, visible cursor/clicks, validation, and ffmpeg stitching.
qa
Use when the user asks Codex to set up the QA plugin pipeline, verify completed work, review code, run tests, debug Next.js or Convex behavior, use Browser Use for real browser QA, fix issues, update documentation, create narrated proof videos, explain QA/plugin behavior, commit changes, or verify one or more completed sprint folders.
sprint-execute
Use when the user asks Codex to execute a sprint, implement all sprint stories, run a multi-agent development sprint, or carry stories through code changes and commits.
sprint-research
Use when the user asks Codex to research a feature, review an existing plan/spec, size work into one or more sprints, create sprint artifacts, or turn broad requirements into a sprint distribution.
sprint-review
Use when the user asks Codex to review sprint stories, audit story quality, incorporate feedback, check story sizing, or create the verification checklist before implementation.
sprint-stories
Use when the user asks Codex to write sprint stories, convert a sprint plan into implementation stories, generate STORY files, or prepare a reviewed sprint backlog.
sprint-verify
Use when the user asks Codex to verify a completed sprint, run browser QA, produce evidence, fix verification bugs, invoke Browser Use or verification plugins, create a verification report, or prepare a PR.
audit-run
The full audit→fix cycle for Millwork OS production runs — invoke with a run/chat URL (or thread id) plus the requester's brain-dump of observations. Use whenever the user says "audit this run", pastes a millos.ai chat URL with complaints, asks why a run was slow/wrong/expensive, or says "execute the audit findings". Covers evidence collection (checkpoints, Langfuse, DB, VFS artifacts, Vercel/Railway logs), cost+time accounting, two-persona judgment, problem documentation, the fix plan with execution lanes, and — after approval — the agent-team execution, verification loop, build gate, PR, and optional live verification + deployment.
autosprint
Plan and autonomously execute engineering sprints end to end — research a problem with small agent teams, write an epic/task sprint plan with self-contained per-task specs, launch the bundled dynamic-workflow executor (one agent per task, per-task commits, autonomous epic reviews, live progress dashboard), and hand off a PR with a completion report and human verification guide. Use when the user wants to plan or run a sprint, audit a problem before sprinting it, turn research or a PRD into autonomously executable work, launch overnight/unattended implementation, check on or resume a running sprint, or hand finished AI work to engineers for verification. Successor to sprint-protocol, built on Claude Code dynamic workflows, with optional Codex CLI task routing.
essayist
Turn rough dictated thoughts into a publishable technical essay in the author's own voice — researched, fact-checked, cited, illustrated with figures, and proofread by parallel review agents before delivery. Use whenever the user wants to write or draft a technical article, essay, blog post, X/Twitter long-form post, or Medium piece; says "write this up", "turn my notes/thoughts into a post", "help me write about what i learned/built"; or dictates a messy stream of thoughts about a technical topic they want published. A raw voice-transcription braindump is the expected input, not a problem to fix.
recur-portal
Implement Customer Portal for subscription self-service. Use when building account pages, letting customers manage subscriptions, update payment methods, view billing history, or when user mentions "customer portal", "帳戶管理", "訂閱管理", "更新付款方式", "self-service". Taiwan subscription billing via PAYUNi (recur.tw, 台灣訂閱金流).
recur-checkout
Implement Recur checkout flows including embedded, modal, and redirect modes. Use when adding payment buttons, checkout forms, subscription purchase flows, or when user mentions "checkout", "結帳", "付款按鈕", "embedded checkout". Taiwan subscription billing via PAYUNi (recur.tw, 台灣訂閱金流).
recur-quickstart
Quick setup guide for Recur payment integration, from account signup (via the Recur MCP OAuth flow) to the first checkout. Use when starting a new Recur integration, creating a Recur account, setting up API keys, creating a product, installing the SDK, or when user mentions "申請 Recur 帳號", "integrate Recur", "setup Recur", "Recur 串接", "金流設定". Taiwan subscription billing via PAYUNi (recur.tw, 台灣訂閱金流).
recur-entitlements
Implement access control and permission checking with Recur entitlements API. Use when building paywalls, checking subscription status, gating premium features, or when user mentions "paywall", "權限檢查", "entitlements", "access control", "premium features". Taiwan subscription billing via PAYUNi (recur.tw, 台灣訂閱金流).
recur-webhooks
Set up and handle Recur webhook events for payment notifications. Use when implementing webhook handlers, verifying signatures, handling subscription events, or when user mentions "webhook", "付款通知", "訂閱事件", "payment notification". Taiwan subscription billing via PAYUNi (recur.tw, 台灣訂閱金流).
recur-help
List all available Recur skills and how to use them. Use when user asks "what can Recur do", "Recur skills", "Recur 有什麼功能", "help with Recur", "如何使用 Recur skills". Taiwan subscription billing via PAYUNi (recur.tw, 台灣訂閱金流).
your-skill-name
清晰描述这个 Skill 的功能以及何时使用它。包含触发条件和使用场景。
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
vercel-deploy
Deploy applications and websites to Vercel. Use this skill when the user requests deployment actions such as "Deploy my app", "Deploy this to production", "Create a preview deployment", "Deploy and give me the link", or "Push this live". No authentication required - returns preview URL and claimable deployment link.
huggingface-hub
Expert knowledge for the Hugging Face Hub ecosystem including HTTP/curl API usage, Python/JavaScript SDKs, Spaces apps (Gradio, Docker), model formats (GGUF, PEFT/LoRA), datasets (pandas, Polars, DuckDB), automation (webhooks, Jobs), and security features. Use when working with Hub APIs, huggingface_hub Python code, Spaces apps, inference providers, model/dataset repositories, or Hub automation.
stripe-sync-minimal
Complete guide for stripe-sync-engine in one skill. Use when the user wants to "sync stripe to database," "stripe-sync-engine," "stripe postgres sync," or needs a quick all-in-one reference.
stripe-sync-query
When the user wants to query synced Stripe data. Also use when the user mentions "query stripe data," "stripe tables," "select from stripe," "stripe analytics," or "stripe SQL."
stripe-sync-setup
When the user wants to set up stripe-sync-engine in their project. Also use when the user mentions "set up stripe-sync-engine," "install stripe sync," "configure stripe sync," "add stripe database sync," or "stripe to postgres."
stripe-sync-troubleshooting
When the user is experiencing issues with stripe-sync-engine. Also use when the user mentions "not working," "webhook error," "signature failed," "connection error," "data not syncing," or "stripe sync broken."
stripe-sync-webhook
When the user wants to create webhook handlers for stripe-sync-engine. Also use when the user mentions "webhook endpoint," "processWebhook," "stripe webhook handler," "stripe events," or "real-time sync."
stripe-sync-migrations
When the user wants to run database migrations for stripe-sync-engine. Also use when the user mentions "run migrations," "stripe schema," "create stripe tables," "database setup," or "stripe_migrations."
stripe-sync-backfill
When the user wants to import historical Stripe data. Also use when the user mentions "backfill stripe data," "syncBackfill," "import stripe data," "sync existing data," or "historical sync."
notebooklm-ppt-designer
国际一流PPT设计架构师，将内容素材（讲稿/主题词/大纲）转化为可直接执行的PPT设计方案。适用于：(1) 根据演讲稿生成PPT设计提示词，(2) 将主题词扩展为完整PPT设计方案，(3) 为内容大纲选择最佳视觉形式，(4) 生成符合品牌视觉规范的设计参数，(5) 输出Gamma Pro等工具可用的生成指令。当用户提及"PPT设计"、"演示文稿"、"幻灯片"、"presentation"、"slides"、"设计方案"、"NotebookLM"、"Gamma"、"Keynote风格"等关键词时触发。
gitsite-content-manager
自动管理 GitSite 静态网站生成器项目的 blogs、books 和 pages 内容。当用户需要创建博客文章、书籍章节、书籍或静态页面时使用此 skill。该 skill 会自动创建正确的目录结构、生成带有完整 frontmatter 的 Markdown 模板文件，并提供内容管理的 Python 脚本。适用于使用 GitSite CLI 构建的静态网站项目。
feishu-bitasks-manager
飞书多维表格管理工具。智能识别字段，自动适应不同的表头结构。支持获取记录列表、创建记录、更新记录状态。适用于各类飞书多维表格项目。
zotero-search
Search the user's local Zotero library, find related papers via Semantic Scholar, and discover citations/references. **Claude only** - this skill requires a local Zotero instance and access to a port on localhost. Use when the user asks to search their Zotero library, find papers on a topic, explore citations of a paper, or find related literature. Supports cross-referencing Semantic Scholar results against the local library.
web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
spacetimedb-best-practices
SpacetimeDB development best practices for TypeScript server modules and client SDK. This skill should be used when writing, reviewing, or refactoring SpacetimeDB code to ensure optimal patterns for real-time, multiplayer applications. Triggers on tasks involving SpacetimeDB modules, tables, reducers, subscriptions, or React integration.
moltoverflow
Search and contribute to the moltoverflow knowledge base for programming packages. Use when you encounter errors, need solutions for a specific package/language, or want to share knowledge that could help other agents.
terraform-ibm-modules-solution-builder
Workflows for generating terraform solution that are the composition of one or several Terraform IBM Modules (TIM). Use when working with IBM Cloud infrastructure as code, Terraform modules, infrastructure automation, or cloud resource provisioning. Provides workflows for module discovery, composition patterns, code generation, and validation. Essential for tasks involving IBM Cloud VPC, compute, networking, security, databases, observability, or any IBM Cloud service deployment. Triggers on keywords like "terraform", "IBM Cloud", "infrastructure", "IaC", "modules", "deploy", "provision", or specific IBM Cloud services (VPC, VSI, OpenShift, etc.).
fill-the-gaps
Assumption-first planning and design gap analysis. Use when user is in PLANNING mode, explicitly asks to plan or discuss, asks for a gap analysis / design review / stress-test of a spec or design document, or when agent faces open decisions — including headless tasks where the deliverable is proposals and open questions as files. Instead of interrogating the user, the agent proposes concrete tagged answers in small verify-style rounds (or directly in the output documents when no user is in the loop), surfaces contradictions as questions, and asks only the questions that genuinely fork the design.
typescript-engineering
Use this skill whenever the user asks you to write, edit, review, refactor, debug, or design TypeScript or TSX code. It is especially relevant for application code, backend routes, React/UI work, schemas, runtime boundaries, persistence, async workflows, API contracts, tests, lint/typecheck fixes, and code review. Apply it even when the user does not explicitly mention "TypeScript" if the files or project are TypeScript-based.
Page 1494 of 1704 · 85183 results
