react-flow-usage
Comprehensive React Flow (@xyflow/react) patterns and best practices for building node-based UIs, workflow editors, and interactive diagrams. Use when working with React Flow for (1) building flow editors or node-based interfaces, (2) creating custom nodes and edges, (3) implementing drag-and-drop workflows, (4) optimizing performance for large graphs, (5) managing flow state and interactions, (6) implementing auto-layout or positioning, or (7) TypeScript integration with React Flow.
idapython
IDA Pro Python scripting for reverse engineering. Use when writing IDAPython scripts, analyzing binaries, working with IDA's API for disassembly, decompilation (Hex-Rays), type systems, cross-references, functions, segments, or any IDA database manipulation. Covers ida_* modules (50+), idautils iterators, and common patterns.
API Contract Sync Manager
Validate OpenAPI, Swagger, and GraphQL schemas match backend implementation. Detect breaking changes, generate TypeScript clients, and ensure API documentation stays synchronized. Use when working with API spec files (.yaml, .json, .graphql), reviewing API changes, generating frontend types, or validating endpoint implementations.
data-safety-auditor
Comprehensive data safety auditor for Vue 3 + Pinia + IndexedDB + PouchDB applications. Detects data loss risks, sync issues, race conditions, and browser-specific vulnerabilities with actionable remediation guidance.
document-sync
A robust skill that analyzes your app's actual codebase, tech stack, configuration, and architecture to ensure ALL documentation is current and accurate. It never assumes—always verifies and compares the live system with every documentation file to detect code-doc drift and generate actionable updates.
master-plan-manager
Safe MASTER_PLAN.md management with backup, validation, and intelligent updates. Use when updating task tracking, adding features to roadmap, or modifying project documentation.
plugin-creator
Create, validate, and publish Claude Code plugins and marketplaces. Use this skill when building plugins with commands, agents, hooks, MCP servers, or skills.
Comprehensive Testing & Verification
MASTER Vue.js application testing with strict enforcement of verification protocols. Systematically test functionality with Playwright, validate bug fixes, verify features work, and enforce zero-tolerance policies for false success claims. MANDATORY testing with visual evidence before any deployment or functionality claims.
safe-project-organizer
Safely analyze and reorganize project structure with multi-stage validation, dry-run previews, and explicit user confirmation. Use when projects need cleanup, standardization, or better organization.
skill-creator-doctor
Create, repair, maintain, and consolidate skills. This skill should be used when users want to create new skills, fix broken skills that won't load, diagnose skill system issues, maintain skill health, or consolidate duplicate/obsolete skills. Automatically detects and repairs common skill loading problems including missing registry entries, metadata format issues, and structural problems. Provides comprehensive skill ecosystem management including duplicate detection, merge workflows, and archival processes.
skills-manager
Universal consolidation & audit skill for Claude Code skills. Analyzes project state, detects redundancies, and safely manages skills with backup, confirmations, and rollback capabilities. Never assumes without verifying actual code and usage patterns.
math-tools
Deterministic mathematical computation using SymPy. Use for ANY math operation requiring exact/verified results - basic arithmetic, algebra (simplify, expand, factor, solve equations), calculus (derivatives, integrals, limits, series), linear algebra (matrices, determinants, eigenvalues), trigonometry, number theory (primes, GCD/LCM, factorization), and statistics. Ensures mathematical accuracy by using symbolic computation rather than LLM estimation.
AI Truthfulness Enforcer
MANDATORY verification system that prevents Claude Code instances from making false claims or fabricating evidence. Enforces cryptographic verification, real testing evidence, and automatic claim validation before any success statements can be made.
chief-architect
PERSONAL APP ARCHITECT - Strategic development orchestrator for personal productivity applications. Analyzes project context, makes architectural decisions for single-developer projects, delegates to specialized skills, and ensures alignment between user experience goals and technical implementation. Optimized for personal apps targeting 10-100 users.
aoconnect
CLI for interacting with AO processes using @permaweb/aoconnect - spawn processes, send messages, read results, monitor messages, and dry run
arweave
Upload files and websites to permanent storage on Arweave (permaweb), and manage ArNS domain records. Use when the user wants to publish content to Arweave, deploy a static site to the permaweb, or attach a transaction to an ArNS name (ar.io).
monitor
Node.js CLI for interacting with the AO Task Monitor API - get system health, alerts, logs, and task metrics for AO processes
spa-builder
Build Single Page Applications using Scout Atoms + json-render + onhyper deployment stack. Creates Vite-based React apps with SSE streaming, component catalogs, and one-command deployment to onhyper.io. Triggers: (1) Creating new SPAs with AI-powered content generation, (2) Building component catalogs with atom schemas, (3) Deploying single-file HTML apps to onhyper.io, (4) Setting up Scout API integration with proxy layer, (5) Working with SSE streaming patterns.
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.
prd
Create self-verifying PRDs for autonomous execution. Interviews users to gather requirements, then generates structured prd.json with phased implementation and appropriate testing strategies. Supports 7 task categories with type-specific workflows. Use when user says "create a prd", "prd for", "plan a feature", "plan this", "write prd", or wants to plan any multi-step implementation work.
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.
ralph-preflight
Pre-flight check for Ralph TUI loops. Validates config, templates, prd.json, and environment before starting a loop. Run after /prd to verify everything is ready. Detects global CLAUDE.md conflicts, validates template variables, and provides launch commands.
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.
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-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.
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.
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.
epic-database
Guide on Prisma, SQLite, and LiteFS for Epic Stack
epic-testing
Guide on testing with Vitest and Playwright for Epic Stack
epic-forms
Guide on forms with Conform and validation with Zod for Epic Stack
epic-permissions
Guide on RBAC system and permissions for Epic Stack
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, 台灣訂閱金流).
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-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-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, 台灣訂閱金流).
Page 644 of 1647 · 82342 results