Frontend Design Quality
Inspect before you style. The existing design system, brand, tokens, components, typography, spacing, and interaction patterns are the source of truth; one-off styling is drift.
Direction
- Choose an intentional visual direction appropriate to the product. Avoid generic template aesthetics, decorative noise, and gradients-for-their-own-sake.
- Use reusable tokens and components instead of one-off values. Extend the system deliberately when it genuinely lacks something.
- Design mobile and desktop deliberately rather than compressing a desktop layout. Protect visual hierarchy, readability, contrast, alignment, and layout stability.
Boundaries
- The server is authoritative for permissions and protected data; client checks improve UX, they are not authorization.
- Keep server state, URL state, form state, and transient UI state distinct. Reuse the project's data-fetching and error patterns; do not add a state library for local state without demonstrated cross-component need.
- Avoid unsafe HTML injection; encode for the rendering context and review any sanitizer configuration (
vuln-audit for anything user-authored).
States
Implement loading, empty, success, stale, error, disabled, read-only, permission-denied, overflow, and long-content states where applicable, before polishing the happy path. Prevent race-driven stale updates with cancellation, request identity, or the framework's data layer.
Motion
Use motion to communicate hierarchy or state, never as decoration alone, and respect prefers-reduced-motion.
Accessibility
Non-negotiable and always composed with this capability: semantic HTML, keyboard order, focus restoration, labels, contrast, zoom, and reflow (accessibility-quality).
Verification
Verify rendered behavior, not source alone: mobile and desktop breakpoints, focus states, each implemented state, and the important flows. Measure bundle or render cost only when the task affects them (performance-scalability).
1---2name: frontend-design-quality3description: >-4 Implement visual frontend work with an intentional design direction: inspect5 the existing design system and tokens, design mobile and desktop6 deliberately, implement every state (loading, empty, error, disabled,7 overflow, permission-denied), protect hierarchy and layout stability, and8 verify rendered behavior. Always composes with accessibility-quality. Use9 for UI implementation, styling, layout, and component work.10license: MIT11metadata:12 source: https://skillmd.com/skills/al-janef/frontend-design-quality13---1415# Frontend Design Quality1617Inspect before you style. The existing design system, brand, tokens, components, typography, spacing, and interaction patterns are the source of truth; one-off styling is drift.1819## Direction2021- Choose an intentional visual direction appropriate to the product. Avoid generic template aesthetics, decorative noise, and gradients-for-their-own-sake.22- Use reusable tokens and components instead of one-off values. Extend the system deliberately when it genuinely lacks something.23- Design mobile and desktop deliberately rather than compressing a desktop layout. Protect visual hierarchy, readability, contrast, alignment, and layout stability.2425## Boundaries2627- The server is authoritative for permissions and protected data; client checks improve UX, they are not authorization.28- Keep server state, URL state, form state, and transient UI state distinct. Reuse the project's data-fetching and error patterns; do not add a state library for local state without demonstrated cross-component need.29- Avoid unsafe HTML injection; encode for the rendering context and review any sanitizer configuration (`vuln-audit` for anything user-authored).3031## States3233Implement loading, empty, success, stale, error, disabled, read-only, permission-denied, overflow, and long-content states where applicable, before polishing the happy path. Prevent race-driven stale updates with cancellation, request identity, or the framework's data layer.3435## Motion3637Use motion to communicate hierarchy or state, never as decoration alone, and respect `prefers-reduced-motion`.3839## Accessibility4041Non-negotiable and always composed with this capability: semantic HTML, keyboard order, focus restoration, labels, contrast, zoom, and reflow (`accessibility-quality`).4243## Verification4445Verify rendered behavior, not source alone: mobile and desktop breakpoints, focus states, each implemented state, and the important flows. Measure bundle or render cost only when the task affects them (`performance-scalability`).