implement

# Implement Standard implementation flow: load style rules, make the change, run post-implementation QA. ## Task Tracking At the start, use `TaskCreate` to create a task for each step: 1. Run `/code-style` skill 2. Load task-specific skills 3. Make the change 4. Run verification 5. Run `/preview` skill for UI/UX changes 6. Run `/finalize` skill ## Step 1: Run `/code-style` Skill Run the `/code-style` skill to load mirror, reuse, and symmetry rules before editing. ## Step 2: Load Task-Specific Skills Scan the work for types that match available skills, matching against the richest context available: a plan's **Implementation Steps** if a plan is in conversation context, otherwise the user request, a prior skill's task description, or an improvement entry. For each unambiguous match, run the skill via the Skill tool. For example, if the work includes "add a Drizzle migration" and a skill exists whose triggers reference Drizzle migrations, load it. If a work type has no matching skill trigger, do not load a generic skill. If unsure, do not load. ## Step 3: Make the Change Apply the change described by the current context — the user request, a prior skill's task description, or an improvement entry. Keep the edit scoped to what the context describes. If the scope balloons beyond what the context specified, stop and confirm scope before continuing. ## Step 4: Run Verification If a Verification section is in conversation context (e.g., from a plan file), execute the co...