Explains the intent behind source code by finding original session transcripts. Use explain with a function, file, or line of code to understand why it exists.

Control consequential homelab changes with explicit scope, observed-state evidence, approval, rollback, and non-secret records. Use before changing guests, services, storage, networking, access, backups, monitoring, or secrets.

Guard consequential personal music-library work with explicit ownership, preview, recovery, and approval checks. Use before scanning, tagging, moving, deduplicating, importing, deleting, or synchronizing music files, metadata, playlists, samples, stems, or mixlists.

Clean up local git branches and remotes accumulated from PR reviews. Use when the user asks to clean branches, remove stale remotes, or tidy up the local git state.

Guides and best practices for working with Neon Serverless Postgres. Covers setup, connection methods, branching, autoscaling, scale-to-zero, read replicas, connection pooling, Neon Auth, and the Neon CLI, MCP server, REST API, TypeScript SDK, and Python SDK. Use when users ask about "Neon setup", "connect to Neon", "Neon project", "DATABASE_URL", "serverless Postgres", "Neon CLI", "neon", "Neon MCP", "Neon Auth", "@neondatabase/serverless", "@neondatabase/neon-js", "scale to zero", "Neon autoscaling", "Neon read replica", or "Neon connection pooling".

Stage + commit + push delegation a Haiku worker (token-cheap pattern, origen 2026-05-09). Orchestrator (Opus) prepara plan; Haiku ejecuta git workflow con guardrails verbatim. Activa: '/commit-push', 'commitea y sube', 'commit haiku', 'commit y push', 'commit + push'.

Use cuando reportes/investigues bug del copilot module: loops infinitos, cards faltantes, conversaciones vacías al refresh, extracción que falla, trazas que mienten, tools que no ejecutan, costos disparados, routing equivocado, prompt cache roto, mutaciones que no persisten, channel format ignorado, voseo en outputs. Activa también para extender (agregar provider, tool, workflow, channel, KB chunk) sin romper invariantes. Triggers: 'bug copilot', 'loop copilot', 'card no aparece', 'conversación vacía', 'documento no extrae', 'agente no responde', 'tool no ejecuta', 'trazas mienten', 'tokens burned', 'extract_document_to_fields falla', 'propose_field_updates no persiste', 'format_for_channel ignored', 'voseo en respuesta', 'cache hit rate', 'cuántos tokens', 'agregar provider', 'agregar workflow', 'agregar tool transversal', 'agregar canal'.

Interactive cross-feature navigation architect for Nicolify. Audits all routes and sidebar entries, maps user journeys across studios, detects orphaned features and dead-end flows, proposes navigation improvements with ASCII diagrams, generates clickable multi-page HTML prototypes on localhost:8888, and outputs FLOW-SPEC.md plus per-screen UI-SPEC updates for implementation agents. Use when the user asks about navigation coherence, user flows, journey mapping, orphaned features, dead-end screens, sidebar reorganization, cross-studio navigation, or feature discoverability. Triggers: 'flujo de usuario', 'navegación', 'journey', 'user flow', 'sidebar', 'rutas huérfanas', 'orphaned routes', 'dead end', 'flow audit', 'navigation audit', 'ux-flow', 'flow architect', 'cómo llega el usuario', 'discoverability', 'no encuentro', 'dónde está', 'reorganizar navegación', 'cross-feature flow', 'audita la navegación', 'mapa de rutas', 'flujos de la app'.

Use when creating social media content ideas, hunting for viral references, adapting content formulas from other niches/countries, or planning content calendars. Generates hook variations, writes caption drafts, curates cross-niche reference swipe files, scores references with STEPPS framework, produces complete content briefs, and builds weekly posting schedules — all grounded in brand and offer data. Integrates with Brand Studio (positioning, narrative, voice) and Offer Studio (promise, audience psychology). Triggers: 'contenido', 'content', 'ideas de contenido', 'reel', 'carrusel', 'post', 'viral', 'qué publico', 'dame ideas', 'inspiración', 'referencia', 'steal like an artist', 'calendario de contenido', 'qué posteo', 'ideas para Instagram', 'ideas para TikTok', 'content hunting'.

Respond to an automated reviewer's findings on the current feature PR — a narrow, headless responder. Triages each reviewer finding into Clear / Ambiguous / Complex / Out-of-PRD-Scope, then acts — fixes the cause and pushes (diff-only) for Clear, posts one in-thread reply for the rest. Skips findings it already handled. Invoked headless by the dispatcher's feedback gate; the dispatcher owns the round counter and the STUCK escalation. Triggers - address-feedback, address review comments, respond to PR review, handle reviewer findings, PR feedback loop (project)

Use when 需要计算/解释投资组合的年化收益率、月度现金流与长期（如30年）资产路径，且包含固定支出与不确定收入（自由职业波动、随机收入、回款集中）并需要给出耗尽概率与分位数（P10/P50/P90）

Use when reviewing a branch diff for security concerns — auth, tokens and sessions, injection, secrets, cookies, CSP and third-party content — and reporting findings with S-C/H/M/L IDs in the four-field format.

Retrieve ClinGen gene-disease validity assertions for a public gene or disease, and review source-linked public evidence and literature for one supported GRCh38 germline nuclear SNV or simple indel through Folklore Clinical Variant Interpretation MCP. Use when a scientific agent must branch deterministically on resolved, ambiguous, not-found, invalid, unsupported, or unavailable variant outcomes; chain a resolved public variant into related literature or publication details; or preserve evidence provenance without accepting patient, phenotype, family, segregation, or private case data.

Build applications and agents with Exa's API: search, contents extraction, answer, Agent API, monitors, websets, OpenAI-compatible endpoints, and exa-py/exa-js SDKs. Use when choosing Exa endpoints, writing Exa API calls, integrating semantic web search or research into products, or debugging Exa request shapes.

Use this skill when the user wants to analyze log files — find errors and their frequency, detect anomalies, build incident timelines, or summarize what happened during an outage.

Create text-driven visuals in Markdown: charts, diagrams, cards, architecture and page layouts. Charts and analytical views (bar, line, pie, heatmap, correlation, regression); reliability and operations (latency, incident, throughput, cycle time, OKR, standup, on-call); product and finance (funnel, retention, revenue, budget); process and workflow (approval, BPMN); software design and behaviour (class, state machine, sequence, C4); dependencies and impact (dependency graph, ER, causality); system architecture as HTML (layer stack, wings, zones, topology, service catalogue, request paths); infrastructure (cloud, Kubernetes, ETL, network, security, IAM, compliance); governance and people (ArchiMate, org chart, hiring); knowledge and planning (mind map, roadmap, Gantt, migration); documents (comparison, SWOT, memo, policy, catalogue, case study). Use when a document needs a diagram, chart or card. Figures render live. Not for slide decks or math notation. Not recommended: mermaid / canvas / drawio / dot.

How to add or modify Next.js experimental feature flags end-to-end. Use when editing config-shared.ts, config-schema.ts, define-env-plugin.ts, next-server.ts, export/worker.ts, or module.compiled.js. Covers type declaration, zod schema, build-time injection, runtime env plumbing, and the decision between runtime env-var branching vs separate bundle variants.

Use when fitting equations to data with PySR or SymbolicRegression.jl, when a user wants an interpretable formula, symbolic model, scaling law, or empirical relation discovered from numeric data, or when debugging a PySR search that is slow, stuck, or giving poor equations.

Extract a Markdown heading tree with line numbers before editing or integrating notes. Use when you need to inspect a long Markdown file quickly and choose the best insertion point instead of editing blind.

Organize menus and visit notes with grounded tasting analysis and comparisons to earlier experiences. Use when the user shares a restaurant menu, wants a tasting write-up, or asks to merge a visit into Notes/Gourmet.md without overwriting earlier visits.