Agent Skills: design-describe

[Design & Content] Describe a design based on screenshot/video

UncategorizedID: duc01226/easyplatform/design-describe

Install this agent skill to your local

pnpm dlx add-skill https://github.com/duc01226/EasyPlatform/tree/HEAD/.claude/skills/design-describe

Skill Files

Browse the full folder contents for design-describe.

Download Skill

Loading file tree…

.claude/skills/design-describe/SKILL.md

Skill Metadata

Name
design-describe
Description
"[Design & Content] Describe a design based on screenshot/video"

Think hard to describe the design based on this screenshot/video: <screenshot>$ARGUMENTS</screenshot>

Required Skills (Priority Order)

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

Ensure token efficiency while maintaining high quality.

Workflow:

  1. Use ai-multimodal skills to describe super details of the screenshot/video so the developer can implement it easily.
    • Be specific about design style, every element, elements' positions, every interaction, every animation, every transition, every color, every border, every icon, every font style, font size, font weight, every spacing, every padding, every margin, every size, every shape, every texture, every material, every light, every shadow, every reflection, every refraction, every blur, every glow, every image, background transparency, etc.
    • IMPORTANT: Try to predict the font name (Google Fonts) and font size in the given screenshot, don't just use Inter or Poppins.
  2. Use ui-ux-designer subagent to create a design implementation plan following the progressive disclosure structure so the result matches the screenshot/video:
    • 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).
  3. Report back to user with a summary of the plan.

IMPORTANT Task Planning Notes

  • Always plan and break many small todo tasks
  • Always add a final review todo task to review the works done at the end to find any fix or enhancement needed