Expo and React Native app-development workflow for this repo. Use when building or updating packages/mobile, Expo Router screens, React Native components, mobile iOS or Android behavior, safe area, navigation, gestures, deep links, offline sync, camera, QR, app config, or EAS profile work.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI).…
Create a new npm package that implements a kanban-lite storage plugin. Use this whenever the user asks to build a new kanban-lite provider, external storage plugin, card.storage plugin, attachment.storage plugin, or a package that can be selected in .kanban.json. If the backend or package details are incomplete, ask a…
Modern field-worker mobile UI/UX patterns for Kanban Lite. Use when designing, reviewing, or refining React Native or Expo mobile screens for field workers, iOS, Android, safe area, navigation, gestures, deep links, offline sync, camera, QR, task detail, forms, comments, attachments, or checklist flows.
Create or update kanban-lite plugin optionsSchema() / uiSchema metadata for shared Plugin Options forms. Use this whenever a task mentions plugin option schemas, optionsSchema, uiSchema, policyOptionsSchemas, JSON Forms provider options, secret field metadata, or schema-driven plugin settings editors.
React Native mobile testing, performance, and release hardening for this repo. Use when validating Expo or React Native changes across mobile, iOS, Android, safe area, navigation, gestures, deep links, offline sync, camera, QR, testing, release, preview builds, startup performance, or no-stale-flash regressions.
Build scalable design systems with Tailwind CSS v4, design tokens, component libraries, and responsive patterns. Use when creating component libraries, implementing design systems, or standardizing UI patterns.
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".
Refactoring specialist — removes dead code, reduces complexity, consolidates duplicates, improves readability. Use when the user asks to simplify, refactor, clean up, reduce complexity, or remove dead code. Never adds features — only restructures existing code. Triggers: 'simplify', 'refactor', 'clean up', 'reduce…
Challenges assumptions, finds edge cases, identifies over-engineering, spots logic gaps in plans and code. Use when the user asks to critique, challenge assumptions, find edge cases, review quality, or check for over-engineering. Never implements. Triggers: 'critique', 'challenge', 'edge cases', 'over-engineering'…
Root-cause analysis, stack trace diagnosis, regression bisection, error reproduction. Use when the user asks to debug, diagnose, find root cause, trace errors, or investigate failures. Never implements fixes. Triggers: 'debug', 'diagnose', 'root cause', 'why is this failing', 'trace error', 'bisect', 'regression'.
UI/UX design specialist — creates layouts, themes, color schemes, design systems, and validates visual hierarchy, responsive design, and accessibility. Use when the user asks for design help, UI review, visual feedback, create a theme, responsive check, or design system. Triggers: 'design', 'UI', 'layout', 'theme'…
Container management, CI/CD pipelines, infrastructure deployment, environment configuration. Use when the user asks to deploy, configure infrastructure, set up CI/CD, manage containers, or handle DevOps tasks. Triggers: 'deploy', 'CI/CD', 'Docker', 'container', 'pipeline', 'infrastructure', 'environment', 'staging'…
Generates technical documentation, README files, API docs, diagrams, and walkthroughs. Use when the user asks to document, write docs, create README, generate API documentation, or produce technical writing. Triggers: 'document', 'write docs', 'README', 'API docs', 'walkthrough', 'technical writing', 'diagrams'.
Writes code using TDD (Red-Green), implements features, fixes bugs, refactors. Use when the user asks to implement, build, create, code, write, fix, or refactor. Never reviews its own work. Triggers: 'implement', 'build', 'create', 'code', 'write', 'fix', 'refactor', 'add feature'.
Multi-agent orchestration for project execution, feature implementation, and automated verification. Primary entry point for all tasks. Detects phase, routes to agents, synthesizes results. Never executes directly. Triggers: any user request, multi-step tasks, complex implementations, project coordination.
Creates DAG-based execution plans with task decomposition, wave scheduling, and pre-mortem risk analysis. Use when the user asks to plan, design an approach, break down work, estimate effort, or create an implementation strategy. Triggers: 'plan', 'design', 'break down', 'decompose', 'strategy', 'approach', 'how to…
Explores codebase, identifies patterns, maps dependencies, discovers architecture. Use when the user asks to research, explore, analyze code, find patterns, understand architecture, investigate dependencies, or gather context before implementation. Triggers: 'research', 'explore', 'find patterns', 'analyze'…
Use when creating or updating Slidev demo presentations, product demo decks, conference demo decks, live walkthrough slides, launch presentations, or sales/demo storytelling decks. Good for beautiful Slidev slides, audience-friendly story flow, truthful product positioning, strong presenter notes, feature proof…