Wire ETL, ingestion, cron, edge-function, and queue jobs correctly. Use for "build a pipeline", "sync X into Y", "nightly aggregation", "cron double-counts", "dedupe", "backfill", "the numbers are wrong after a retry". Bakes in idempotency, atomic writes, data contracts, dead-letter, and observability.
Build interactive, accessible charts, graphs, and data dashboards using Recharts, D3, or Victory. Use when the user says "chart", "graph", "data visualization", "analytics dashboard", "metrics display", "D3", "Recharts", "time-series", or "data display".
Diagnose one error/bug with hypotheses and runtime evidence before fixing. Use when "debug this error", "investigate this bug", or behavior is unexpected. FEβBE contract mismatch β debug-fe-be-integration. Sentry backlog/monitoring β debug-sentry-monitor. Bug-to-PR lifecycle β workflow-fix-and-ship.
Diagnose and fix frontendβbackend contract failures by tracing client requests, server logs, validation, auth, and responses on both sides. Use for API 4xx/5xx, mismatched payloads, validation failures, or "frontend and backend disagree". Single-layer errors β debug-error.
Operate Sentry: triage/fix unresolved issues, reduce noise, audit instrumentation, and monitor after deploy. Use when "check Sentry", "fix Sentry issues", "review production errors", or "improve error tracking". One named bug through PR β workflow-fix-and-ship. Plan-only observability β plan-error-handling.
Release an npm package: version, CHANGELOG, publish, verify. Use when "publish this package", "release to npm", or "ship a new npm version". Running-app production deploy β workflow-ship-and-observe.
Post-deploy smoke test across browser, Sentry, Supabase, Langfuse, and the public web. Use when "verify deploy", "smoke test production", "post-release check", or "ship or rollback". Deploy + observation loop β workflow-ship-and-observe. npm package release β deploy-npm.
Design RESTful and GraphQL APIs following current best practices for naming, versioning, error shapes, and auth patterns. Use when the user says "design an API", "create endpoints", "structure my API responses", "plan API architecture", "REST vs GraphQL", or "API contract".
Create museum-quality visual art in .png and .pdf formats using design philosophy. Use when user asks for poster, visual design, infographic, certificate, badge, banner, social media graphic, print design, or mentions "create artwork", "design graphic", "visual identity", or "print material".
Create a new production-grade UI from scratch β not a polish pass. Use when "build this UI", "design this page", or "new dashboard layout". Polish existing β enhance-web-ui. Landing β enhance-web-landing. Redesign existing β enhance-web-redesign.
Create original algorithmic visuals with p5.js, Canvas, or SVG using seeded randomness and interactive controls. Use when "generative art", "procedural visuals", "flow fields", "particle system", or "art from code". Data charts β data-visualization. UI illustration β design-frontend.
Design mobile-first UIs: touch targets, safe areas, gestures, then enhance up. Use when building for small screens, touch, swipe, PWA, or tablet. Linearized desktop / responsive audit β audit-responsive.
Design and implement new isolated motion β micro-interactions, page transitions, scroll, hover β with Framer Motion, CSS, or GSAP. Use when adding one animation to a new surface. Existing-app coherent pass β enhance-motion. Do not fire for "motion pass across the app".
Generate Product Requirements Documents through structured conversation for any project. Use when starting a new feature, documenting requirements, creating specs before implementation, or needing clarity on scope and success criteria.
Build a new design system (tokens, variants, theming). Use when "create a design system" or "component library from scratch". Drifted existing system β housekeep-design. Plan-only unification β plan-uiux-unification.
Create and maintain lightweight Architecture Decision Records as agent-readable decision memory β what was decided, why, and which alternatives were rejected. Use when "record this decision", "set up ADRs", "the agent keeps suggesting Y again". Docs vs code drift β plan-docs-sync. Session state β handoff.
Co-author structured documents (specs, PRDs, RFCs) through a 3-stage workflow: context gathering, drafting, and reader testing. Use when writing proposals, technical specs, or similar structured content. Repo decision-memory system (INDEX.md, rejected alternatives, agent rules) β docs-adr.
Build and sharpen a project's domain model β a CONTEXT.md glossary and ubiquitous language. Use when pinning down terminology, or the agent "uses the wrong words". Repo decision-memory system (INDEX.md, rejected alternatives) β docs-adr.
Cross-surface UIUX separation skill for hybrid web apps that ship as PWA + iOS + Android via Capacitor (or Tauri / Expo Web / Ionic / RN-Web). Use when a previous UI/UX sweep "improved one surface and broke the other" β desktop polished but mobile cramped, or mobile native but desktop wastes space.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page β the rest are on their repository pages: