Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".

Interactive QA session where user reports bugs or issues conversationally, and the agent files GitHub issues. Explores the codebase in the background for context and domain language. Use when user wants to report bugs, do QA, file issues conversationally, or mentions "QA session".

Migrate bUnit test files from deprecated beta API (1.0.0-beta-10) to bUnit 2.x stable API. Use this when working on .razor test files in BlazorWebFormsComponents.Test that contain old patterns like TestComponentBase, Fixture, or SnapshotTest.

This skill automates the adaptation of pre-trained machine learning models using transfer learning techniques. It is triggered when the user requests assistance with fine-tuning a model, adapting a pre-trained model to a new dataset, or performing transfer learning. It analyzes the user's requirements, generates code for adapting the model, includes data validation and error handling, provides performance metrics, and saves artifacts with documentation. Use this skill when you need to leverage existing models for new tasks or datasets, optimizing for performance and efficiency.

Three.js shaders - GLSL, ShaderMaterial, uniforms, custom effects. Use when creating custom visual effects, modifying vertices, writing fragment shaders, or extending built-in materials.

Three.js scene setup, cameras, renderer, Object3D hierarchy, coordinate systems. Use when setting up 3D scenes, creating cameras, configuring renderers, managing object hierarchies, or working with transforms.

This skill automates the adaptation of pre-trained machine learning models using transfer learning techniques. It is triggered when the user requests assistance with fine-tuning a model, adapting a pre-trained model to a new dataset, or performing transfer learning. It analyzes the user's requirements, generates code for adapting the model, includes data validation and error handling, provides performance metrics, and saves artifacts with documentation. Use this skill when you need to leverage existing models for new tasks or datasets, optimizing for performance and efficiency.

This skill should be used when the user says "plan infra change", "arn-infra-change-plan", "infra change plan", "plan this infrastructure change", "create infra plan", "arn infra plan", "plan the infra spec", "infrastructure implementation plan", "infra plan from spec", "generate infra plan", "plan infrastructure", or wants to generate a phased implementation plan from an infrastructure change specification, structured by provisioning order, blast radius, rollback checkpoints, and environment promotion gates.

This skill should be used when the user says "pre-mortem", "premortem", "risk analysis", "stress premortem", "failure analysis", "what could go wrong", "pre mortem", "investigate failure", "failure modes", or wants to stress-test a product concept by applying Gary Klein's pre-mortem methodology to identify hypothetical failure root causes, early warning signals, and mitigation strategies. Produces a pre-mortem report with 3 root causes across distinct failure dimensions and recommended concept updates.

This skill should be used when the user says "execute plan with teams", "run plan teams", "execute with agent teams", "team execution", "execute plan with agent teams instead of subagents", "teams mode", "agent teams mode", "execute with teams", or wants to execute a structured project plan using Claude Code's experimental Agent Teams feature. Creates a team of executor, reviewer, and architect teammates that collaborate on task implementation with built-in quality gates. Requires the experimental Agent Teams feature to be enabled. For standard subagent-based execution, use arn-code-execute-plan instead.

This skill should be used when the user says "report issue", "arness code report", "code report", "something went wrong", "report a bug", "file arness code issue", "arness code broke", "report arness code problem", "diagnose issue", "arness doctor", "run doctor", "diagnose arness code", "arn-code-report", or wants to report a problem with an Arness Code workflow skill. Invokes the arn-code-doctor agent to diagnose the issue, then files a GitHub issue on the Arness plugin repository. Do NOT use this for filing issues on the user's own project — use /arn-code-create-issue for that. For Spark issues use /arn-spark-report. For Infra issues use /arn-infra-report.

This skill should be used when the user says "prfaq", "pr faq", "pr/faq", "press release stress test", "stress prfaq", "amazon pr faq method", "test the pitch with a pr/faq", "validate concept through pr/faq", "critique press release", "pr faq stress test", "will this marketing story hold up", or wants to stress-test a product concept by drafting a compelling press release and FAQ, then adversarially critiquing it to find where the concept cracks under scrutiny. Produces a PR/FAQ report with the full draft, adversarial questions, crack point analysis, and recommended concept updates.

This skill should be used when the user says "stress interview", "synthetic interview", "user interview stress test", "interview my personas", "test with synthetic users", "persona interview", "simulate user interviews", "run user interviews", or wants to stress-test a product concept by conducting structured interviews with synthetic personas through three adversarial lenses (Pragmatist, Skeptic, Power User). Produces an interview report with per-persona findings, synthesized themes, and recommended concept updates.

This skill should be used when the user says "spark report", "report spark issue", "spark broke", "arn-spark-report", "greenfield issue", "report greenfield problem", "report spark problem", "diagnose spark", "spark doctor", "spark bug", "spark not working", or wants to report a problem with an Arness Spark workflow skill. Invokes the arn-spark-doctor agent to diagnose the issue, then files a GitHub issue on the Arness plugin repository. Do NOT use this for filing issues on the user's own project — use /arn-code-create-issue for that.

This skill should be used when the user says "competitive analysis", "gap analysis", "competitive gap", "stress competitive", "compare competitors", "feature comparison", "competitive stress test", "market comparison", "competitor analysis", or wants to stress-test a product concept by conducting deep competitive gap analysis with feature comparison, gap identification, and positioning assessment. Produces a competitive report with a feature matrix, per-competitor analysis, and recommended concept updates.

This skill should be used when the user says "infra report", "report infra issue", "infra broke", "arn-infra-report", "infrastructure issue", "report deployment problem", "report infrastructure problem", "diagnose infra", "infra doctor", or wants to report a problem with an Arness Infra workflow skill. Invokes the arn-infra-doctor agent to diagnose the issue, then files a GitHub issue on the Arness plugin repository. Do NOT use this for filing issues on the user's own project — use /arn-code-create-issue for that.

This skill should be used when the user says "review plan", "validate plan", "check plan", "sanity check the plan", "verify plan", "review my plan", "audit plan", "is my plan ready", or wants to validate a structured project plan for completeness, correctness, and pattern compliance before execution. Checks structural completeness, document quality, dependency graph consistency, codebase reference validity, and pattern compliance. Offers to fix found issues interactively and can proceed directly to arn-code-taskify when the plan passes.

Refactor high-complexity React components in Dify frontend. Use when `pnpm analyze-component --json` shows complexity > 50 or lineCount > 300, when the user asks for code splitting, hook extraction, or complexity reduction, or when `pnpm analyze-component` warns to refactor before testing; avoid for simple/well-structured components, third-party wrappers, or when the user explicitly wants testing without refactoring.

**UTILITY SKILL** — Artifact template structures, H2 compliance rules, and documentation styling for agent outputs (Steps 1-7). WHEN: "generate artifact", "check H2 structure", "artifact template", "step 7 as-built". USE FOR: generating any agent artifact, checking H2 structure compliance. DO NOT USE FOR: Azure resource configuration (use azure-defaults), Bicep/Terraform patterns (use azure-bicep-patterns or terraform-patterns).