Frontend Visual Systems
Use this skill to turn research and product intent into an executable visual system.
Boundary
- Define tokens, density, typography, color, icon strategy, layout rhythm, and interaction tone.
- Act as the normal Frontend Design coordinator for production UI work. Classify the task before choosing delegates.
- Treat product-interface work as Frontend work even when the user says
"browser extension", "popup", "settings page", "desktop", "Tauri",
"Electron", "native-WebView", "mobile", "Android", or "Compose" rather than
"web page".
- Do not implement the app; route implementation to the official
build-web-apps capability or project code workflow.
- Do not rely on decorative blobs, generic purple gradients, or unexplained hero copy.
- Do not use academic or journal-inspired palettes from
palette/ as direct UI colors. Product surfaces need semantic tokens; scientific palettes may map only to chart roles.
Workflow
- P0 product/state contract: summarize the product job, primary states, user actions, and target surface.
- P1 design authority and direction: identify canonical Figma, another durable authority, or current production grammar for a narrow fix; choose the visual direction and delegate only where needed.
- P2 implementation handoff: translate the accepted direction into concrete tokens, components, states, assets, motion, and implementation notes.
- P3 actual-surface convergence: verify the rendered browser or native-WebView surface that the claim is about; record P1/P2/P3 findings against the exact candidate.
- P4 whole-product taste: ask observable taste questions and require independent confirmation for substantive redesign, release gates, major canonical-design convergence, major native user-flow milestones, or whole-product hierarchy/interaction-model changes.
For product-interface copy, insert a content-architecture handoff before final
wording:
SURFACE:
UI_ROLE:
PRODUCT_STATE:
USER_JOB:
USER_CONSEQUENCE_OR_NEXT_ACTION:
NEIGHBORING_VISIBLE_COPY:
LOCALE:
PROTECTED_MEANING:
DISCLOSURE_LEVEL:
LENGTH_OR_VIEWPORT_CONSTRAINT:
DESIGN_AUTHORITY: optional
TERMINOLOGY_OR_BRAND_TOKENS: optional
Send that handoff to Clear Writing product-ui-copy for wording under frozen
meaning. Frontend remains responsible for whether the text belongs there,
amount, hierarchy, progressive disclosure, neighboring-copy relationship, and
final rendered page/screen rhythm.
Scale the work before delegating:
- S1 targeted/local fix: use existing production grammar; do not force Figma, full redesign, or independent review unless the fix exposes a larger product/design gap.
- S2 bounded UI change: extend only the affected states, components, and authority source.
- S3 product/redesign: run the full P0-P4 loop.
Design authority and surface are modifiers, not size classes. Figma is conditional authority, not mandatory. Browser evidence proves browser behavior; native-WebView claims need native evidence or a clearly bounded user-only stop.
Delegate ownership:
product-ux-planning: product job, primary states, actionability, lifecycle, normal-vs-diagnostic boundary, visible metric/ranking semantics.
visual-direction: whole-screen direction, composition, differentiator, and observable taste questions.
design-system-tokens: component craft, icon source/registry/provenance, semantic typography, color, status, state, and token grammar.
figma-design-to-code: canonical Figma authority, completeness, round-trip, and final design/render convergence.
motion-interaction: motion intent and the boundary between design motion and runtime latency or jank.
responsive-accessibility-review: applicable P1 accessibility/responsive constraints and P3 closure.
webapp-testing: browser evidence companion for F-C; not a native or design authority.
research-product-frontend: research-specific UI constraints after this coordinator has classified the generic product/design route.
Do not activate this coordinator for backend/API/math tasks, provider/runtime
debugging, network/tunnel changes, Room/WorkManager/data-layer changes, or
README/docs-only writing when no user-facing product interface is in scope.
When a platform-specific product UI task routes through this coordinator, keep
local platform authority intact. For example, Android/Compose implementation
details still belong to the project's Android/Compose owner; Frontend Design
coordinates product-interface architecture and rendered acceptance.
Production Frontend Design Gates
Apply these gates before a frontend candidate is described as production-ready,
user-ready, release-ready, or ready for external acceptance.
F-A Design Authority And State Coverage
Do not force every project into Figma. When a canonical Figma file, design
handoff, product design brief, or other current design source exists, treat it
as production visual authority rather than inspiration. Read the current design
source before coding or reviewing. Material states, variants, responsive
breakpoints, interaction states, and important transitions that will ship need a
design target; if they are missing, close the design-source gap instead of
inventing the state directly in code.
F-B Design-System Coherence
Use shared component families and tokens for layout, typography, spacing,
radius, surfaces, icon style, and motion. Icons should belong to a coherent
family; motion should clarify state or hierarchy and must respect reduced
motion. Brand/product assets and generic UI chrome must remain visually
consistent. When the frozen product claim includes multiple locales or finite
reachable enums, all user-visible tokens for those locales must be covered;
internal identifiers are not an acceptable production fallback except for
narrowly approved proper names or acronyms.
F-C Actual-Surface Convergence
Verify the real target surface, not only component snippets or screenshots.
When a canonical design exists, compare complete native screens against the
design source at normal working sizes and record intentional deviations.
Screenshots alone do not prove click, native, provider, persistence, or live
behavior. Producer self-QA should catch obvious hierarchy, spacing, overflow,
translation-token, interaction, and motion defects before external acceptance.
F-D Producer Admission And Handoff Reachability
Producer self-QA is admission to independent review or user handoff, not an
independent quality proof. Bind P1=0/P2=0 to the exact candidate, surface,
state, and evidence. If the final report asks the user to click, select, expand,
save, or authorize a UI control and the producer can safely exercise it, verify
that the control is visible, enabled, triggered by real interaction, reaches the
expected next state or user-only boundary, and has no obvious P2 defect.
Classify defects before repair:
- Design defect: return to P0/P1 and the relevant authority/delegate.
- Implementation drift: repair the implementation without changing the design source.
- Product semantic defect: return to product UX/state semantics.
- Runtime-only repair: fix runtime behavior while preserving accepted design intent.
Interaction causality belongs to F-C. Ordinary browser locator/actionability
plus a postcondition is enough unless there is a competing route or control-path
claim; then prove the specific route.
Quality Bar
- Avoid generic "AI page" tells: undifferentiated purple gradients, oversized cards, weak contrast, random icon mixes, decorative motion, and unsupported hero copy.
- Prefer one strong visual idea over a pile of effects.
- Use screenshot comparison and browser QA to verify hierarchy, density, text fit, responsive behavior, and motion restraint.
- Whole-product taste is observable judgment: ask whether hierarchy, density,
motion, iconography, affordances, copy placement, and state transitions feel
coherent in the actual screen, not whether a checklist keyword appears.
1---2name: frontend-visual-systems3description: Convert frontend references and product intent into design tokens, visual direction, palette, typography, icon, layout, density, and motion rules for implementation by a frontend builder.4status: active5provenance: user-authored6trusted: false7requires_network: false8writes_files: true9executes_code: false10secrets_needed:11last_reviewed: 2026-07-1312profile_tags:13 - web-development14recommended_scope: project15icon_small: assets/app-facing.svg16icon_large: assets/app-facing.svg17metadata:18 source: https://skillmd.com/skills/yuukias/frontend-visual-systems19---2021# Frontend Visual Systems2223Use this skill to turn research and product intent into an executable visual system.2425## Boundary2627- Define tokens, density, typography, color, icon strategy, layout rhythm, and interaction tone.28- Act as the normal Frontend Design coordinator for production UI work. Classify the task before choosing delegates.29- Treat product-interface work as Frontend work even when the user says30 "browser extension", "popup", "settings page", "desktop", "Tauri",31 "Electron", "native-WebView", "mobile", "Android", or "Compose" rather than32 "web page".33- Do not implement the app; route implementation to the official `build-web-apps` capability or project code workflow.34- Do not rely on decorative blobs, generic purple gradients, or unexplained hero copy.35- Do not use academic or journal-inspired palettes from `palette/` as direct UI colors. Product surfaces need semantic tokens; scientific palettes may map only to chart roles.3637## Workflow38391. P0 product/state contract: summarize the product job, primary states, user actions, and target surface.402. P1 design authority and direction: identify canonical Figma, another durable authority, or current production grammar for a narrow fix; choose the visual direction and delegate only where needed.413. P2 implementation handoff: translate the accepted direction into concrete tokens, components, states, assets, motion, and implementation notes.424. P3 actual-surface convergence: verify the rendered browser or native-WebView surface that the claim is about; record P1/P2/P3 findings against the exact candidate.435. P4 whole-product taste: ask observable taste questions and require independent confirmation for substantive redesign, release gates, major canonical-design convergence, major native user-flow milestones, or whole-product hierarchy/interaction-model changes.4445For product-interface copy, insert a content-architecture handoff before final46wording:4748```text49SURFACE:50UI_ROLE:51PRODUCT_STATE:52USER_JOB:53USER_CONSEQUENCE_OR_NEXT_ACTION:54NEIGHBORING_VISIBLE_COPY:55LOCALE:56PROTECTED_MEANING:57DISCLOSURE_LEVEL:58LENGTH_OR_VIEWPORT_CONSTRAINT:59DESIGN_AUTHORITY: optional60TERMINOLOGY_OR_BRAND_TOKENS: optional61```6263Send that handoff to Clear Writing `product-ui-copy` for wording under frozen64meaning. Frontend remains responsible for whether the text belongs there,65amount, hierarchy, progressive disclosure, neighboring-copy relationship, and66final rendered page/screen rhythm.6768Scale the work before delegating:6970- S1 targeted/local fix: use existing production grammar; do not force Figma, full redesign, or independent review unless the fix exposes a larger product/design gap.71- S2 bounded UI change: extend only the affected states, components, and authority source.72- S3 product/redesign: run the full P0-P4 loop.7374Design authority and surface are modifiers, not size classes. Figma is conditional authority, not mandatory. Browser evidence proves browser behavior; native-WebView claims need native evidence or a clearly bounded user-only stop.7576Delegate ownership:7778- `product-ux-planning`: product job, primary states, actionability, lifecycle, normal-vs-diagnostic boundary, visible metric/ranking semantics.79- `visual-direction`: whole-screen direction, composition, differentiator, and observable taste questions.80- `design-system-tokens`: component craft, icon source/registry/provenance, semantic typography, color, status, state, and token grammar.81- `figma-design-to-code`: canonical Figma authority, completeness, round-trip, and final design/render convergence.82- `motion-interaction`: motion intent and the boundary between design motion and runtime latency or jank.83- `responsive-accessibility-review`: applicable P1 accessibility/responsive constraints and P3 closure.84- `webapp-testing`: browser evidence companion for F-C; not a native or design authority.85- `research-product-frontend`: research-specific UI constraints after this coordinator has classified the generic product/design route.8687Do not activate this coordinator for backend/API/math tasks, provider/runtime88debugging, network/tunnel changes, Room/WorkManager/data-layer changes, or89README/docs-only writing when no user-facing product interface is in scope.9091When a platform-specific product UI task routes through this coordinator, keep92local platform authority intact. For example, Android/Compose implementation93details still belong to the project's Android/Compose owner; Frontend Design94coordinates product-interface architecture and rendered acceptance.9596## Production Frontend Design Gates9798Apply these gates before a frontend candidate is described as production-ready,99user-ready, release-ready, or ready for external acceptance.100101### F-A Design Authority And State Coverage102103Do not force every project into Figma. When a canonical Figma file, design104handoff, product design brief, or other current design source exists, treat it105as production visual authority rather than inspiration. Read the current design106source before coding or reviewing. Material states, variants, responsive107breakpoints, interaction states, and important transitions that will ship need a108design target; if they are missing, close the design-source gap instead of109inventing the state directly in code.110111### F-B Design-System Coherence112113Use shared component families and tokens for layout, typography, spacing,114radius, surfaces, icon style, and motion. Icons should belong to a coherent115family; motion should clarify state or hierarchy and must respect reduced116motion. Brand/product assets and generic UI chrome must remain visually117consistent. When the frozen product claim includes multiple locales or finite118reachable enums, all user-visible tokens for those locales must be covered;119internal identifiers are not an acceptable production fallback except for120narrowly approved proper names or acronyms.121122### F-C Actual-Surface Convergence123124Verify the real target surface, not only component snippets or screenshots.125When a canonical design exists, compare complete native screens against the126design source at normal working sizes and record intentional deviations.127Screenshots alone do not prove click, native, provider, persistence, or live128behavior. Producer self-QA should catch obvious hierarchy, spacing, overflow,129translation-token, interaction, and motion defects before external acceptance.130131### F-D Producer Admission And Handoff Reachability132133Producer self-QA is admission to independent review or user handoff, not an134independent quality proof. Bind `P1=0/P2=0` to the exact candidate, surface,135state, and evidence. If the final report asks the user to click, select, expand,136save, or authorize a UI control and the producer can safely exercise it, verify137that the control is visible, enabled, triggered by real interaction, reaches the138expected next state or user-only boundary, and has no obvious P2 defect.139140Classify defects before repair:141142- Design defect: return to P0/P1 and the relevant authority/delegate.143- Implementation drift: repair the implementation without changing the design source.144- Product semantic defect: return to product UX/state semantics.145- Runtime-only repair: fix runtime behavior while preserving accepted design intent.146147Interaction causality belongs to F-C. Ordinary browser locator/actionability148plus a postcondition is enough unless there is a competing route or control-path149claim; then prove the specific route.150151## Quality Bar152153- Avoid generic "AI page" tells: undifferentiated purple gradients, oversized cards, weak contrast, random icon mixes, decorative motion, and unsupported hero copy.154- Prefer one strong visual idea over a pile of effects.155- Use screenshot comparison and browser QA to verify hierarchy, density, text fit, responsive behavior, and motion restraint.156- Whole-product taste is observable judgment: ask whether hierarchy, density,157 motion, iconography, affordances, copy placement, and state transitions feel158 coherent in the actual screen, not whether a checklist keyword appears.