| name | backy-frontend-desing-director |
| description | Backy frontend design director super-skill. Use for broad UI/UX, taste, visual strategy, design systems, prototypes, media assets, decks, templates, and choosing the right grouped Backy frontend design skill from the Open Design catalogue. |
Backy Frontend Desing Director
Use this as the first stop for broad design, UI/UX, frontend taste, product polish, visual direction, landing pages, app redesigns, design systems, decks, media assets, and presentation-quality artifacts.
It compresses the Open Design catalogue into grouped Backy skills so the picker does not need 132 separate top-level entries.
Route By Intent
backy-frontend-desing-design-system: 36 capabilities for UI/UX taste, visual systems, critique, platform rules, Figma handoff, copy, conversion, and product design direction.backy-frontend-desing-prototype: 32 capabilities for single-screen HTML prototypes, landing pages, dashboards, documents, motion UI, social cards, and interactive demos.backy-frontend-desing-image: 24 capabilities for static visual asset generation, screenshots, posters, image editing, mockups, restoration, and vision workflows.backy-frontend-desing-video: 17 capabilities for motion frames, HyperFrames, Remotion/video editing, logo outros, data-chart clips, download/clip workflows, and text/video generation.backy-frontend-desing-deck: 9 capabilities for slide decks, web presentations, keynote-style pages, PPTX generation, and executive presentation workflows.backy-frontend-desing-template: 9 capabilities for opinionated reusable visual templates for reports, quarterly reviews, editorial decks, research videos, and cinematic layouts.backy-frontend-desing-audio: 4 capabilities for speech, music, jingles, album concepts, voiceover, and brand-sound workflows.backy-frontend-desing-utility: 1 capabilities for specialized validation and repair workflow for generated deck fidelity.
Workflow
- Read
references/catalog.md for the full catalogue summary.
- Choose the smallest matching mode group. If the user asks for implementation UI, usually pair
backy-frontend-desing-design-system with backy-frontend-desing-prototype.
- Ask for clarification only when output format, platform, or brand constraints are impossible to infer safely.
- For a concrete build, use the grouped skill's source reference for exact constraints. For broad strategy, stay at catalog level.
- Before finalizing visual work, verify responsiveness and rendered appearance whenever a browser or preview is available.
Naming Note
The prefix intentionally uses desing because that is the requested Backy skill namespace: backy-frontend-desing-....
Hard Rules
- Do not install or trigger all 132 source skills at once.
- Do not copy a template blindly into an existing app. Adapt it to the product, route, component model, and design tokens.
- Do not invent business proof, metrics, screenshots, brand partnerships, or testimonials.
- Prefer fewer stronger surfaces over many shallow decorative variants.
