Core programming concepts from variables through recursion. Covers data types (integers, floats, strings, booleans, arrays, objects), variables and scope (lexical, dynamic, block, function, global), control flow (conditionals, loops, pattern matching), functions (parameters, return values, closures, higher-order functions), recursion (base cases, call stack, tail recursion, mutual recursion), type systems (static vs dynamic, strong vs weak, type inference, generics), and error handling (exceptions, Result types, defensive programming). Use when teaching, reviewing, or diagnosing issues with fundamental programming constructs.
Software design principles, patterns, and architecture from SOLID through distributed systems. Covers the five SOLID principles with violations and fixes, DRY/KISS/YAGNI heuristics, separation of concerns, 12 GoF design patterns organized by intent (creational, structural, behavioral), architectural patterns (MVC, MVP, MVVM, layered, hexagonal, microservices, event-driven), coupling and cohesion metrics, dependency injection, and the design decision framework for choosing between competing approaches. Use when making design decisions, reviewing architecture, refactoring code, or teaching software engineering principles.
Embedded firmware development for microcontrollers including memory-mapped I/O, GPIO, interrupts, timers, UART/SPI/I2C serial protocols, PWM generation, ADC sampling, interrupt-driven versus polled architectures, RTOS fundamentals, and the bring-up sequence from power-on reset through first printf. Covers AVR/Arduino, ARM Cortex-M, and ESP32 patterns. Use when writing, porting, debugging, or reviewing firmware that directly manipulates hardware peripherals.
Engineering design cycle covering requirements elicitation, specifications writing, constraint identification, iterative prototyping, and design communication. Spans the full loop from problem definition through ideation, analysis, prototyping, testing, and redesign. Includes morphological charts, TRIZ, Pugh matrices, design reviews, and the distinction between functional and non-functional requirements. Use when framing engineering problems, generating design alternatives, writing specifications, or running design reviews.
Engineering ethics covering safety, professional codes of conduct, public welfare responsibility, whistleblowing, case studies (Challenger, Columbia, Hyatt Regency, Bhopal, Therac-25), and the ethical dimensions of design decisions. Includes the NSPE Code of Ethics, the iron ring tradition, risk communication, informed consent in engineering, and the duty to dissent. Use when analyzing ethical dimensions of engineering decisions, teaching professional responsibility, or reviewing designs for safety and public welfare.
Vocabulary learning strategies and retention science for any language -- frequency-based word selection, spaced repetition systems (Ebbinghaus forgetting curve, Leitner system, SM-2 algorithm), cognate exploitation, word family networks, context-based learning, collocations, depth of word knowledge (form, meaning, use), reading progression from controlled to authentic texts, and productive vs. receptive vocabulary thresholds. Use when building vocabulary plans, optimizing review schedules, selecting learning materials, or diagnosing vocabulary gaps.
How nutrition science becomes dietary guidance, and how industry, agriculture, and politics shape that process. Covers the US Dietary Guidelines cycle, food labeling, WIC and SNAP, commodity subsidies, and the documented history of industry influence on research and recommendations. Use when a question asks why a guideline says what it says, how a recommendation got written, or whether an industry-funded study should be trusted.
Provides Site Reliability Engineering best practices for SLOs, SLIs, SLAs, error budgets, toil reduction, reliability reviews, and capacity planning. Use when defining service objectives, measuring reliability, reducing toil, planning capacity, or when user mentions 'SRE', 'SLO', 'SLI', 'SLA', 'error budget', 'toil', 'reliability', 'on-call', 'capacity planning'.
Provides web accessibility best practices for semantic HTML, ARIA, keyboard navigation, color contrast, and screen reader patterns. Use when building UI components, reviewing accessibility, or when user mentions 'a11y', 'accessibility', 'ARIA', 'screen reader', 'keyboard navigation', 'WCAG'.
Polya's four-phase method applied to mathematical problems, extended with Schoenfeld's control/monitoring layer. Covers understand, devise plan, carry out, look back. Includes heuristics specific to math (specialize, generalize, vary the problem, introduce auxiliary elements) and the metacognitive discipline that separates routine computation from genuine problem solving.
Quality assurance and continuous improvement for software projects. Covers Deming's 14 Points for Management, PDCA cycle (Plan-Do-Check-Act), Six Sigma DMAIC, total quality management (TQM), quality metrics (defect density, code coverage, MTBF), testing strategies (unit, integration, system, acceptance), verification and validation (V&V), peer review and inspection, continuous improvement (kaizen), root cause analysis (5 Whys, fishbone), quality gates, definition of done, technical debt management, and Hamilton's priority display concept from Apollo as error prevention through system design.
Research methodology in psychology. Covers experimental design (independent/dependent variables, random assignment, control conditions, between/within-subjects designs), research ethics (informed consent, deception, debriefing, IRB review, APA ethical principles), statistical methods in psychology (null hypothesis significance testing, p-values, effect sizes, confidence intervals, power analysis), and the replication crisis (publication bias, p-hacking, questionable research practices, preregistration, open science). Use when designing psychological research, evaluating study quality, interpreting statistical findings, or discussing methodological rigor in psychology.
Experimental design principles for scientific inquiry. Covers variable identification and control, control groups (positive and negative), randomization, blinding, sample size and power, replication strategies, factorial designs, quasi-experimental approaches, and common design pitfalls. Use when designing, reviewing, or teaching about controlled experiments in any scientific discipline.
Principles and practices of communicating science to diverse audiences. Covers the CER (claims-evidence-reasoning) framework, lab report structure, peer review, scientific argumentation, audience adaptation, the baloney detection kit for evaluating sources, and the art of making complex ideas accessible without sacrificing accuracy. Use when writing, presenting, evaluating, or teaching science communication at any level.
Design heuristics for immersive environments — VR worlds, AR scenes, CAVE installations, responsive rooms. Covers scale and presence, lighting and atmosphere, sight-line composition, acoustic design, comfort-first layout, player/visitor flow, environmental storytelling, and the boundary between stage and audience. Includes Krueger's VIDEOPLACE heritage, Furness's Super Cockpit discipline, and contemporary guidelines for VR level design. Use when authoring or reviewing any environment whose purpose is to be experienced from within.
Issue triage and PR review — scans issues, triages, fixes, submits PRs, then adversarially reviews all open PRs. Parallel agent dispatch with worktree isolation.
Research writing conventions for academic and professional contexts. Covers the research process (question formation, literature review, methodology, evidence evaluation), academic genres (research paper, literature review, annotated bibliography, thesis/dissertation, conference paper), citation and attribution (MLA, APA, Chicago, IEEE, in-text vs. footnote, bibliography construction), source evaluation (CRAAP test, peer review, primary vs. secondary, bias detection), research argument construction (hypothesis-driven, question-driven, thesis as evolving claim), and ethical research practices (plagiarism, paraphrase integrity, IRB considerations, data transparency). Use when writing research papers, evaluating sources, constructing academic arguments, or teaching research methodology.
GSD tutorial, command reference, and workflow explainer. Explains what a GSD workflow command does before you run it. Activates when user is new to GSD, asks about commands, wants to understand workflows, or mentions preview.
Unit Circle Laboratory + sc-dev-team autonomous mission control. Provides human-in-the-loop automation layer, pipeline management, context lifecycle, stuck-state prevention. UC re-execution series and dev branch milestones. Adapted from uc-lab pattern for code plan/execute/verify/complete. Auto-activates during UC milestone work; trigger: user says 'bring up the dev team'.
Load, validate, and use DACP bundles as structured execution context. Detects .bundle/ companion directories, validates integrity (manifest schema, fidelity, provenance), loads typed data, and builds ExecutionContext for receiving agents. Scripts are NEVER auto-executed. Use when processing incoming DACP bundles, interpreting .bundle/ directories alongside .msg files, validating bundle integrity, or building execution context from bundle payloads.
Full review lifecycle — request reviews, handle feedback with technical rigor, and complete branch integration. Use when completing tasks, receiving feedback, or finishing feature branches.
Master Design Skill. Orchestrates AI-powered UI generation using Google Stitch MCP, guided by cm-ux-master intelligence and professional prompt enhancement pipelines. Implements the 'Stitch Build Loop', 'Prompt Optimization Structure', and strict design system adherence to generate production-ready UI previews before coding.
Craft CMS 5 PHP coding standards and conventions. ALWAYS load this skill when writing, editing, reviewing, or discussing any PHP file in a Craft CMS plugin or module — even for small edits. Also load when running ECS, PHPStan, or scaffolding with ddev craft make. Covers: PHPDoc blocks (@author, @since, @throws chains, documenting exceptions), section headers (=========), class organization, naming conventions (services, queue jobs, records, events, enums), defineRules() and validation, beforePrepare() and addSelect(), MemoizableArray, DateTimeHelper vs Carbon, strict_types and declare(strict_types=1) usage, short nullable notation (?string), typed properties, void return types, control flow patterns (early returns, match over switch), CP Twig template conventions, form macros, translations (Craft::t), ECS/PHPStan configuration, scaffolding commands, and the verification checklist. Triggers on: writing service classes, models, controllers, elements, element queries, records, queue jobs, migrations, or any PHP class in a Craft CMS context. Also triggers on PHP code review, refactoring, or style questions for Craft plugins and modules. NOT for front-end Twig templates (use craft-twig-guidelines), template architecture (use craft-site), or CP JavaScript/Garnish (use craft-garnish). If you are touching PHP code in a Craft CMS context, you need this skill.
Twig coding standards and conventions for Craft CMS 5 templates. ALWAYS load this skill when writing, editing, or reviewing any .twig file in a Craft CMS project — even for small edits. Covers: variable naming (camelCase, no abbreviations), null handling (?? operator, ??? with empty-coalesce plugin), whitespace control ({%- trimming, NOT {%- minify -%}), include isolation (always use 'only'), Craft Twig helpers ({% tag %}, tag(), attr(), |attr filter, |parseAttr, |append, svg()), collect() for props and class collections, .implode(), comment headers with ========= separators on component files, and common pitfalls (snake_case, macros as components, hardcoded colors). Triggers on: Twig template creation, editing, or review; .twig files; {% include %} with 'only'; {% tag %} and polymorphic elements; collect() and props.get(); class string building; attr() and |attr filter; svg() with styling and aria; ?? and ??? null coalescing; whitespace control and blank lines in output; minify alternatives; Twig file headers and comment blocks; variable naming conventions in Twig; currentSite, siteUrl, craft.entries, .eagerly(), .collect in template context. NOT for Twig architecture patterns, atomic design structure, or template routing (use craft-site). NOT for PHP code (use craft-php-guidelines). NOT for content modeling or field configuration (use craft-content-modeling).
Run API integration tests against the running backend, verify endpoints return expected responses and status codes. Use after deploying a preview or starting the dev server.
You are the **Chair** — John Carmack's philosophy made operational. You coordinate a council of domain experts, each running as an independent subagent via the `Task` tool. Your job is to map the code
You are a **specification engineer**. Your job is to produce the shortest structured document that makes "done" unambiguous — a spec an AI agent can execute against without drift, and a human can revi
React and Next.js performance optimization guidelines from Vercel Engineering. Use when writing, reviewing, or refactoring React/Next.js code — components, data fetching, bundle size, or performance.
**Source:** [vercel-labs/agent-skills](https://github.com/vercel-labs/agent-skills) — `skills/web-design-guidelines/SKILL.md` (MIT). Guidelines content is fetched from the URL below; install/update vi
Use when completing tasks, implementing major features, or before merging to verify work meets requirements - reviews implementation against plan or requirements with severity分级（Critical/Important/Minor）. NO MERGE WITHOUT CODE REVIEW FIRST.
Use when executing implementation plans with independent tasks - dispatches fresh subagent for each task with code review between tasks, enabling fast iteration with quality gates. Supports orchestrator, peer-to-peer, and pipeline coordination modes.