Loading...
Loading...
Found 1,267 Skills
Execute development tasks with skeleton-first approach and layered TDD. Includes optional adversarial verification (code quality + test completeness review). Use when users start working on a task (T-XX), need development guidance, or implement features/bugfixes. Triggers on keywords like "execute task", "start T-XX", "implement", "develop", "开发任务", "执行任务", "对抗式验证", "--review".
Guide Tailwind CSS v4 usage with best-practice utility patterns and theme variable guidance.
Set up Tailwind v4 with shadcn/ui themed UI. Workflow: install dependencies, configure CSS variables with @theme inline, set up dark mode, verify. Use when initialising React projects with Tailwind v4, setting up shadcn/ui theming, or fixing colors not working, tw-animate-css errors, @theme inline dark mode conflicts, @apply breaking, v3 migration issues.
Environment variables and parameters for running command line programs reliably in non-interactive environments (unattended). Includes silent modes, color/disable TTY, and reduced output options for 155 CLI tools.
Used to clear Flutter environment variables (FLUTTER_STORAGE_BASE_URL and PUB_HOSTED_URL) on macOS. Suitable for scenarios where you need to reset the environment or resolve Flutter proxy issues.
Tests calculate tool with arithmetic, trig, and variable substitution
This skill should be used when the user asks "how do I customize Bootstrap", "how to create a custom Bootstrap theme", "what Sass variables can I override", "how to implement dark mode in Bootstrap", "how to change Bootstrap colors", "how to override Bootstrap defaults", "how to add custom colors to Bootstrap", "how to enable Bootstrap shadows", "how to compile Bootstrap Sass", "how to use Bootstrap CSS variables", or needs help with Bootstrap theming, Sass variable overrides, CSS custom properties, or color mode implementation.
Run a structured, adversarial multi-agent bug review pipeline on a codebase. Use this skill whenever the user wants to find bugs, audit code quality, review a codebase for issues, or run any kind of bug-finding or code analysis workflow. Also trigger when the user asks to 'review my code for bugs', 'find all issues in this repo', 'audit this codebase', or any similar request. The pipeline uses three sequential phases: a Bug Finder that maximizes issue discovery, a Bug Adversary that challenges false positives, and an Arbiter that issues final verdicts — producing a clean, high-confidence bug report.
Multi-agent adversarial verification with convergence loop. Two independent review agents must both pass before output ships.
Technical design interview + adversarial review → living doc Technical Design section ready to implement. Stateful: detects existing sections and resumes where needed. Triggers: 'architect this,' 'how should we build,' 'design the tech,' post-define/design. Not for: scoping (explore), requirements (define), UX (design).
Used when accessibility audits are required or when implementing WCAG 2.2 (including ARIA, keyboard accessibility, and screen reader support).
Audit, implement, and fix web accessibility with a screen-reader-first lens. Use when building or reviewing UI components, forms, dialogs, navigation, dynamic content, or any interactive element. Covers WCAG 2.2 AA compliance, ARIA patterns, keyboard navigation, focus management, and assistive technology compatibility (NVDA, JAWS, VoiceOver). Trigger on: "accessible", "a11y", "screen reader", "WCAG", "ARIA", or when adding any interactive UI.