audit-code
Run a two-pass, multidisciplinary code audit led by a tie-breaker lead, combining security, performance, UX, DX, and edge-case analysis into one prioritized report with concrete fixes. Use when the user asks to audit code, perform a deep review, stress-test a codebase, or produce a risk-ranked remediation plan across backend, frontend, APIs, infra scripts, and product flows.
What this skill does
# Audit Code ## Overview Run an expert-panel audit with strict sequencing and one unified output document. Produce findings first, sorted by severity, with file references, exploit/perf/flow impact, and actionable fixes. Load `references/audit-framework.md` before starting the analysis. ## Required Inputs Collect or infer the following: - Audit scope: paths, modules, PR diff, or whole repository. - Product context: PRD/spec/user stories, trust boundaries, and critical business flows. - Runtime context: deployment model, queue/cron/background jobs, traffic profile, data sensitivity, and abuse assumptions. - Constraints: timeline, acceptable risk, and preferred remediation style. If product context is missing, state assumptions explicitly and continue. ## Team Roles Use exactly these roles: - Security expert - Performance expert - UX expert - DX expert - Edge case master - Tie-breaker team lead The tie-breaker lead resolves conflicts, prioritizes issues, and produces the final single report. ## Workflow Follow this sequence every time: 1. Build Context Read code + product flows. Identify assets, entry points, high-risk operations, privileged actions, external dependencies, and "failure hurts" journeys. 2. Build Invariant Coverage Matrix Before specialist pass 1, map critical invariants to every mutating path (HTTP routes, webhooks, async jobs, scripts): - Data-link invariants: multi-table relationships that must remain consistent. - Auth lifecycle invariants: disable/revoke semantics for sessions/tokens/API keys. - Input/transport invariants: validation, content-type policy, body-size/parse behavior. - Shape invariants: trees/graphs must reject cycles where applicable. Treat missing parity across equivalent paths as a finding candidate. 3. Pass 1 Specialist Reviews Run role-specific analysis in this order: - Security - Performance - UX - DX - Edge case master Capture findings using the schema in `references/audit-framework.md`. 4. Tie-Breaker Reconciliation Resolve disagreements: - Decide whether contested items are true issues. - Set severity and confidence. - Remove duplicates and merge overlapping findings. 5. Cross-Review Pass 2 After edge-case findings, rerun specialists: - Security/Performance/UX/DX reassess prior findings and new edge-triggered scenarios. - Edge case master performs a final pass on residual risk after proposed mitigations. 6. Final Report Publish one document from the tie-breaker lead with: - Findings first (ordered by severity, then blast radius, then exploitability). - Open questions/assumptions. - Remediation plan with priority, owner type, and verification tests. - Short executive summary at the end. ## Quality Bar Enforce these requirements: - Use concrete evidence with file references and line numbers where available. - Include reproduction steps for security/performance/edge findings when feasible. - Prefer actionable fixes over abstract advice. - Separate confirmed defects from speculative risks. - Mark confidence for each finding. - Run a cross-route consistency sweep: equivalent endpoints/jobs must enforce equivalent invariants. - For each High/Critical finding, include at least one focused regression test/check. ## Safety and Policy Guardrails Apply these guardrails while auditing: - Do not provide operational abuse instructions or exploit weaponization details. - Evaluate manipulative UX patterns as legal/trust/reputation risk, not as recommended growth tactics. - Prioritize user safety, system integrity, and maintainable engineering outcomes. ## Output Format Follow this response structure: 1. Findings List only validated issues. Use the finding schema in `references/audit-framework.md`. 2. Open Questions / Assumptions State missing context that could change priority or validity. 3. Change Summary Summarize high-impact remediation themes in a few lines. 4. Suggested Verification List focused tests/checks to confirm each major fix. ## Runtime Heuristics When the target stack is Bun + SQLite, apply the runtime-specific checklist in `references/audit-framework.md` (`Runtime-Specific Heuristics (Bun + SQLite)`) before finalizing findings.
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.