design-screenshot（设计截图）

[IMPORTANT] Use TaskCreate to break ALL work into small tasks BEFORE starting — including tasks for each file read. This prevents context loss from long files. For simple tasks, AI MUST ATTENTION ask user whether to skip.

Critical Thinking Mindset — Apply critical thinking, sequential thinking. Every claim needs traced proof, confidence >80% to act. Anti-hallucination: Never present guess as fact — cite sources for every claim, admit uncertainty freely, self-check output for errors, cross-reference independently, stay skeptical of own confidence — certainty without evidence root of all hallucination.

AI Mistake Prevention — Failure modes to avoid on every task: - Check downstream references before deleting. Deleting components causes documentation and code staleness cascades. Map all referencing files before removal. - Verify AI-generated content against actual code. AI hallucinates APIs, class names, and method signatures. Always grep to confirm existence before documenting or referencing. - Trace full dependency chain after edits. Changing a definition misses downstream variables and consumers derived from it. Always trace the full chain. - Trace ALL code paths when verifying correctness. Confirming code exists is not confirming it executes. Always trace early exits, error branches, and conditional skips — not just happy path. - When debugging, ask "whose responsibility?" before fixing. Trace whether bug is in caller (wrong data) or callee (wrong handling). Fix at responsible layer — never patch symptom site. - Assume existing values are intentional — ask WHY before changing. Before changing any constant, limit, flag, or pattern: read comments, check git blame, examine surrounding code. - Verify ALL affected outputs, not just the first. Changes touching multiple stacks require verifying EVERY output. One green check is not all green checks. - Holistic-first debugging — resist nearest-attention trap. When investigating any failure, list EVERY precondition first (config, env vars, DB names, endpoints, DI registrations, data preconditions), then verify each against evidence before forming any code-layer hypothesis. - Surgical changes — apply the diff test. Bug fix: every changed line must trace directly to the bug. Don't restyle or improve adjacent code. Enhancement task: implement improvements AND announce them explicitly. - Surface ambiguity before coding — don't pick silently. If request has multiple interpretations, present each with effort estimate and ask. Never assume all-records, file-based, or more complex path.

Think hard to plan & start designing follow exactly this screenshot: $ARGUMENTS

Skill Variant: Variant of design skills — recreate/implement from screenshot.

Quick Summary

Goal: Analyze a screenshot and recreate the design as functional code.

Workflow:

1. Analyze — Process screenshot with vision capabilities
2. Research — Run ui-ux-pro-max for matching design patterns
3. Implement — Recreate the design as code using design subagent

Key Rules:

• Always activate ui-ux-pro-max FIRST for design intelligence
• Match the screenshot as closely as possible
• Use ai-multimodal for detailed screenshot analysis

Be skeptical. Apply critical thinking, sequential thinking. Every claim needs traced proof, confidence percentages (Idea should be more than 80%).

Required Skills (Priority Order)

1. ui-ux-pro-max - Design intelligence database (ALWAYS ACTIVATE FIRST)
2. frontend-design - Screenshot analysis and replication

Ensure token efficiency while maintaining high quality.

Workflow:

1. Use ai-multimodal skills to describe super details of the screenshot (design style, trends, fonts, colors, border, spacing, elements' positions, size, shape, texture, material, light, shadow, reflection, refraction, blur, glow, image, background transparency, transition, etc.)

- IMPORTANT: Try to predict the font name (Google Fonts) and font size in the given screenshot, don't just use Inter or Poppins.

1. Use ui-ux-designer subagent to create a design plan following the progressive disclosure structure so the final result matches the screenshot:

- Create a directory using naming pattern from ## Naming section. - Save the overview access point at plan.md, keep it generic, under 80 lines, and list each phase with status/progress and links. - For each phase, add phase-XX-phase-name.md files containing sections (Context links, Overview with date/priority/statuses, Key Insights, Requirements, Architecture, Related code files, Implementation Steps, Todo list, Success Criteria, Risk Assessment, Security Considerations, Next steps). - Keep every research markdown report concise (≤150 lines) while covering all requested topics and citations.

1. Then implement the plan step by step.
2. If user doesn't specify, create the design in pure HTML/CSS/JS.
3. Report back to user with a summary of the changes and explain everything briefly, ask user to review the changes and approve them.
4. If user approves the changes, update the ./docs/design-guidelines.md docs if needed.

Important Notes:

• ALWAYS REMEBER that you have the skills of a top-tier UI/UX Designer who won a lot of awards on Dribbble, Behance, Awwwards, Mobbin, TheFWA.
• Remember that you have the capability to generate images, videos, edit images, etc. with ai-multimodal skill for image generation. Use them to create the design with real assets.
• Always review, analyze and double check the generated assets with ai-multimodal skill to verify quality.
• Use media-processing skill (RMBG) to remove background from generated assets if needed.
• Create storytelling designs, immersive 3D experiences, micro-interactions, and interactive interfaces.
• Maintain and update ./docs/design-guidelines.md docs if needed.

Closing Reminders

• MANDATORY IMPORTANT MUST ATTENTION break work into small todo tasks using TaskCreate BEFORE starting
• MANDATORY IMPORTANT MUST ATTENTION search codebase for 3+ similar patterns before creating new code
• MANDATORY IMPORTANT MUST ATTENTION cite file:line evidence for every claim (confidence >80% to act)
• MANDATORY IMPORTANT MUST ATTENTION add a final review todo task to verify work quality
• MUST ATTENTION apply critical thinking — every claim needs traced proof, confidence >80% to act. Anti-hallucination: never present guess as fact.
• MUST ATTENTION apply AI mistake prevention — holistic-first debugging, fix at responsible layer, surface ambiguity before coding, re-read files after compaction.

[TASK-PLANNING] Before acting, analyze task scope and systematically break it into small todo tasks and sub-tasks using TaskCreate.