Frontend/UI Classification
This is the single source of truth for "is this frontend/UI work?". refine (design-aware refinement), implement (Design Check gate and isUiTicket flag), and any other caller apply exactly this rule — never restate the keyword list inline in a calling skill; reference this skill instead.
A ticket or task is classified as frontend/UI when its title, description, acceptance criteria, or digest summary mention any of:
- UI components, pages, views, layouts, forms, or modals
- Visual design, styling, CSS, animations, or themes
- Frontend frameworks (React, Angular, Vue, Svelte, etc.)
If none of these signals are present, treat the work as backend/infrastructure/data and skip design-specific behavior.
Visual-check signals (subset)
A stronger subset of signals indicates the change is visually verifiable and warrants the ui:visual-check label / interactive browser verification: CSS, layout, responsive behavior, themes, design tokens, styling, visual polish, animations, or appearance changes.
1---2name: frontend-classification3description: Classify whether a ticket is frontend or UI work. Use when deciding whether design-aware planning, visual verification, UI tests, or screenshot capture applies.4---56## Frontend/UI Classification78This is the single source of truth for "is this frontend/UI work?". `refine` (design-aware refinement), `implement` (Design Check gate and `isUiTicket` flag), and any other caller apply exactly this rule — never restate the keyword list inline in a calling skill; reference this skill instead.910A ticket or task is classified as **frontend/UI** when its title, description, acceptance criteria, or digest summary mention any of:1112- UI components, pages, views, layouts, forms, or modals13- Visual design, styling, CSS, animations, or themes14- Frontend frameworks (React, Angular, Vue, Svelte, etc.)1516If none of these signals are present, treat the work as backend/infrastructure/data and skip design-specific behavior.1718## Visual-check signals (subset)1920A stronger subset of signals indicates the change is *visually verifiable* and warrants the `ui:visual-check` label / interactive browser verification: CSS, layout, responsive behavior, themes, design tokens, styling, visual polish, animations, or appearance changes.
matteobortolazzo