dev-workflow

**目的**：检测并行路径、不完整替代、死保底。从 `reviewing-architecture` skill 吸收。

**前置条件**：dispatch prompt 包含 `Crystal file:` 路径且非 "none"。如果无 crystal 文件引用，跳过本策略。

Use this agent to analyze design prototypes from Stitch, Figma, or other design tools. Performs dual-channel analysis (image + code simultaneously), extracts design tokens, translates to target platform, and validates against UX assertions when in pipeline mode. Examples: <example> Context: User created a Stitch prototype and wants AI analysis. user: "Analyze this Stitch design" assistant: "I'll use the design-analyzer agent for dual-channel analysis." </example> <example> Context: Pipeline mode, validating prototype against design doc. user: "Check if this prototype matches our design" assistant: "I'll use the design-analyzer agent to validate against the design doc." </example>

Use this agent to audit codebase alignment against structured design documents. Extracts assertions from documents mechanically based on known template structures and verifies each assertion against the actual code. Examples: <example> Context: Project has been through several dev-guide phases and docs may be stale. user: "Check if the code still matches the design docs" assistant: "I'll use the design-drift-auditor agent to audit alignment." </example> <example> Context: User suspects feature scope has drifted from project-brief. user: "Run a design drift check focusing on scope" assistant: "I'll use the design-drift-auditor agent to check scope assertions." </example>

**目的**：验证计划完整且忠实地覆盖设计文档的所有要求，在执行前捕获 Gap A-E。

Use when Claude exhibited unexpected behavior, for periodic rule health checks, or after adding new rules. Audits CLAUDE.md rules from the AI execution perspective for conflicts, loopholes, gaps, and redundancies.

Use before any creative work — creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Use after resolving a bug, completing a task with notable pitfalls, or discovering an important architecture constraint. Extracts a structured entry from the session and saves it to the knowledge base.

Use when the user says 'commit' or wants to save progress after completing a task. Analyzes uncommitted changes, groups them logically, and commits with conventional format messages.

Use before /write-plan or when the session has settled significant design decisions. Extracts the decision history from the current conversation into a persistent crystal file that /write-plan and plan-verifier consume.

3 hooks across 3 events