Claude Code Skills · page 158

Expert guidance for creating Claude Code slash commands. Use when working with slash commands, creating custom commands, understanding command structure, or learning YAML configuration.

Expert guidance for creating, building, and using Claude Code subagents and the Task tool. Use when working with subagents, setting up agent configurations, understanding how agents work, or using the Task tool to launch specialized agents.

Systematic debugging techniques including error classification, root cause analysis (5 Whys), reproduction strategies, and error documentation. Use when debugging errors, investigating failures, analyzing stack traces, fixing bugs, or documenting errors in error-log.md. (project)

Detect and resolve package dependency conflicts before installation across npm/yarn/pnpm, pip/poetry, cargo, and composer. Auto-trigger when installing/upgrading packages. Validates peer dependencies, version compatibility, security vulnerabilities. Auto-resolves safe conflicts (patches, dev deps), suggests manual review for breaking changes. Prevents conflicting versions, security vulnerabilities, broken builds.

Preview command effects without making changes. Simulates file writes, git operations, agent spawns, and state changes. All reads execute normally for accurate preview. Use --dry-run flag on any command.

Classify workflow failures and attempt automatic recovery. Use when sprint/feature fails during implementation to determine if auto-fix is possible or manual intervention required.

Completes feature/epic workflows after deployment with comprehensive walkthrough generation for epics (v5.0+), roadmap updates, artifact archival, documentation, and branch cleanup. Use after /ship-prod, /deploy-prod, or /build-local completes, or when user asks to finalize. (project)

Enforce git commits after every phase and task to enable rollback and prevent lost work. Auto-trigger when completing phases, tasks, or when detecting uncommitted changes. Auto-commit with Conventional Commits format. Verify branch safety, check for merge conflicts, enforce clean working tree. Block completion if changes not committed.

Detect and prevent hallucinated technical decisions during feature work. Auto-trigger when suggesting technologies, frameworks, APIs, database schemas, or external services. Validates all tech decisions against docs/project/tech-stack.md (single source of truth). Blocks suggestions that violate documented architecture. Requires evidence/citation for all technical choices. Prevents wrong tech stack, duplicate entities, fake APIs, incompatible versions.

Executes implementation tasks using Test-Driven Development, prevents code duplication through anti-duplication checks, and maintains quality through continuous testing. Use when implementing features from tasks.md, during the /implement phase, or when the user requests TDD-based implementation. (project)

Extract reusable components from approved HTML mockups during implementation. Identifies patterns, maps CSS to Tailwind, and populates prototype-patterns.md for visual fidelity. Use at start of /implement for UI-first features.

Validates production readiness through performance benchmarking, accessibility audits, security reviews, and code quality checks. Use after implementation phase completes, before deployment, or when conducting quality gates for features. (project)

Identify and execute independent operations in parallel for 3-5x speedup. Auto-analyzes task dependencies, groups into batches, launches parallel Task() calls. Applies to /optimize (5 checks), /ship pre-flight (5 checks), /implement (task batching), /prototype (N screens). Auto-triggers when detecting multiple independent operations in a phase.

Generates implementation plans with code reuse analysis, architecture design, and complexity estimation during the /plan phase. Use when planning feature implementation, analyzing code reuse opportunities, or designing system architecture after specification phase completes. Integrates with 8 project documentation files for constraint extraction. (project)

Executes production deployment workflow by promoting validated staging builds to production with semantic versioning, health checks, and release tagging. Use when running /ship-prod command, deploying to production after staging validation, or promoting staging builds to production environment.

Orchestrates /init-project command execution through interactive questionnaire (15 questions), brownfield codebase scanning (tech stack detection, ERD from migrations), and 8-document generation (overview, architecture, tech-stack, data, API, capacity, deployment, workflow). Use when user runs /init-project, requests project documentation generation, or asks about architecture setup for greenfield/brownfield projects. (project)

Generate regression tests when bugs are discovered during /debug or continuous checks. Auto-detects test framework, creates Arrange-Act-Assert tests, and links to error-log.md entries. (project)

Manages product roadmap via GitHub Issues (brainstorm, prioritize, track). Auto-validates features against project vision (from overview.md) before adding to roadmap. Use when running /roadmap command or mentions 'roadmap', 'add feature', 'brainstorm ideas', or 'prioritize features'.

Integration guide for shadcn/ui components with OKLCH design tokens. Use when setting up shadcn, customizing themes, or adding components to Next.js projects. Auto-trigger on /init --tokens --shadcn flag.

>

>

>

>

>

>

>

>

>

模拟高三语文辅导老师，辅导现代文阅读、古诗文鉴赏、文言文翻译、作文写作等语文问题。重语感培养、文本解读、写作思维。当学生提出语文问题、请求分析课文、讲解古诗词、修改作文时使用。

模拟高三英语辅导老师，辅导英语阅读理解、完形填空、语法填空、写作等问题。重语言能力培养、做题技巧、词汇积累。当学生提出英语问题、请求讲解语法、分析阅读题、修改作文时使用。

模拟高三通用技术辅导老师，辅导技术设计、结构分析、流程图、算法、简单编程等通用技术问题。重实践操作、设计思维、问题解决能力培养。当学生提出技术设计、结构优化、流程设计、算法问题时使用。

模拟高三文科辅导老师，用启发式教学方法辅导政治、历史、地理等文科综合问题。侧重理解、记忆、分析能力培养。当学生提出文科问题、请求讲解历史事件、地理现象、政治原理时使用。

模拟中国高三理科辅导老师，用渐进式教学方法辅导数学、物理、化学、生物等理科问题。当学生提出理科问题、请求讲解、说"不懂"、"教我"时使用。适用于高考备考、解题辅导、概念理解。

Use when the user wants to turn a static scene, character images, aerial map, drawn path, or route-control image into an immersive first-person FPV AI video prompt, especially Seedance/Kling/Runway/Veo style one-shot videos with numbered stop markers, red-line path control, world-map flythroughs, camera route planning, variable character counts, non-human POVs such as drones, pets, robot vacuums, character references, timed interactions, dialogue, spatial audio, and negative constraints.

|

|

|

|

|

|

>

>

>

>

Deploy one validated mergetrain train through an attributable human confirmation dialog.

Operate a local mergetrain queue for coding-agent branches. Use when inspecting queue health, enqueueing committed work, validating a train, following progress, or recovering from blocked and crashed runs.

Installs and connects Firekeep, a self-hosted persistent memory and working-context layer for AI agents, then verifies it with the product's own health check. Use this skill when the user asks to install, set up, or connect Firekeep; when Firekeep's tools are missing, failing, or not connected to a server; or when they want their agent to remember decisions, context, and past work across sessions, machines, and different agents — even if they do not mention Firekeep by name.

Session 0 — write the rules file (ark.config.json) to match the real folders. Optional extra rules inside a layer. CLI validates.

Shortcut to /ark-adopt for a new tree. Deprecated as a first-class door.

Fix illegal imports and one leftover-design refactor. CLI is a sensor; you edit files.

Shortcut — edit the rules file or extra rules. Use /ark-adopt or /ark-autopilot.

How much of the tree the rules file covers. CLI is a sensor; read the source.

Explain the rules file in plain language and generate the HTML report.

Map import rules and leftover design. No apply. CLI is a sensor; you read the tree.

Shortcut to /ark-autopilot for a small illegal-import cluster.

Shortcut to /ark-autopilot for illegal-import fixes. CLI validates — you edit code.

Where does new code go? Names the folder from the rules file and writes the file there.

Wire the optional ArkRun extra (arkgate/runtime). One candidate. Extra on via /ark-adopt.

2–3 options for one import-rule or ArkRules decision. Not a full map (use /ark-explore).

Upgrade ArkGate. Preview first, keep customized files, then apply.

Professional frontend standards for building, scaffolding, extending, or reviewing any UI or frontend project — new or existing — even when standards aren't explicitly asked for. Keeps generated code consistent, reusable, secure, and production-quality. Framework-agnostic: React, Vue, Angular, Svelte, plain JS.

>

>

>

>

>

>

>

>

>

>

>

>

>

>

>

>

>

>

>

>

>

>

Verify and rights-safely project LiquiLens Evidence Carrier or Fleet Brief JSON in local files. Use for provenance, clock, integrity, redistribution, FDC3, OpenLineage, or four-product brief-validation tasks; not for collecting market data, trading, recommendations, ratings, or bypassing source rights.