| name | backy-frontend-desing-utility |
| description | Backy frontend design utility super-skill. Use for specialized validation and repair workflow for generated deck fidelity. Routes across 1 Open Design utility capabilities without installing them as 1 separate top-level skills. |
Backy Frontend Desing: Utility
Use this when the user asks for specialized validation and repair workflow for generated deck fidelity.
This is a compact router over 1 Open Design utility capabilities. Keep the top-level context small: start with the catalog, then load only the exact source reference files needed for the request.
Workflow
- Read
references/catalog.md to pick one primary capability and, if useful, one support capability.
- Read only the matching file(s) from
references/source/. Do not bulk-load every source file.
- Apply the source skill's constraints, but keep the repo's existing architecture and design system unless the user explicitly asks for a new direction.
- For UI work, verify real rendered output when a local app or HTML artifact exists. Use screenshots or browser checks for responsive and visual claims.
- If the requested work crosses modes, combine this with the relevant sibling skill, for example
backy-frontend-desing-design-system plus backy-frontend-desing-prototype.
Capability Map
pptx-html-fidelity-audit -> references/source/pptx-html-fidelity-audit.md
Backy Defaults
- Prefer distinctive, production-grade UI over generic AI template structure.
- Use real content and data from the user or project. Do not invent metrics, logos, testimonials, or product claims.
- Keep typography, spacing, interaction states, and responsive behavior as first-class acceptance criteria.
- When source skills conflict, choose the stricter visual QA rule and the simpler implementation.
- For existing products, improve the current surface instead of replacing product structure wholesale.
