Communitygithub.com

design-foundations

Establish or refine semantic colors, themes, mobile/desktop typography and icon sizing before component construction. Use when visual foundations are missing or explicitly being changed. For ordinary pack requests, enter through design-workflow unless its stage is already active or this specialist is explicitly requested in isolation.

¿Qué es design-foundations?

design-foundations is a Claude Code agent skill that establish or refine semantic colors, themes, mobile/desktop typography and icon sizing before component construction. Use when visual foundations are missing or explicitly being changed. For ordinary pack requests, enter through design-workflow unless its stage is already active or this specialist is explicitly requested in isolation.

Compatible con✓Claude Code~Codex CLI~Cursor
npx skills add https://github.com/pankajvaghela/design-system-workflow/tree/HEAD/skills/design-foundations

Preguntar en tu IA favorita

Abre un nuevo chat con esta habilidad de agente ya precargada.

Documentación

Establish visual foundations

For ordinary pack requests, start with design-workflow. If it already assigned this active stage, execute it without routing back: return a checked artifact and respect its current review/continuation mode and authorized boundary. Do not bypass a pending gate or expand that scope. An explicitly requested isolated specialist task is the routing exception and stays within its own scope.

Start with approved foundations

Inspect product/design guidance, existing palette, tokens, theme modes, typography and representative screens. Establish the authoritative source. Reuse approved foundations; a new screen or component does not authorize rebranding. If they already satisfy the task, record that reuse and return without inventing a new palette or review cycle. Changing an approved foundation requires explicit scope; report conflicts rather than silently replacing it.

When foundations are undecided, propose a small coherent direction grounded in the audience, brand and required UI. Offer alternatives only for a real unresolved decision. Decide which themes are required by the brief: do not automatically add light, dark or high-contrast modes. Theme switching behavior (system preference, manual choice, persistence) is a separate product decision; identify it only if relevant, and do not imply a mockup implements it.

Define only the roles the UI needs

  • Keep brand/base colors separate from semantic roles such as background, surface, text, border, action, focus and feedback. Reuse existing names and scales; avoid tokenizing every literal or generating unused shades.
  • Map the same semantic roles to values in each required theme. Preserve existing aliases and identities. Selected, bookmarked, disabled and error states must remain distinguishable in every required theme, with cues beyond color where needed.
  • Use editor-native variables, modes or styles when supported. Bind components to semantic roles; do not duplicate an entire component library per theme. If mode switching or bindings are unsupported, provide clearly labeled previews and a small mapping table, and state that they are not functioning theme bindings.
  • Preserve approved typography, icon style and imagery. Confirm how the palette works with them; redesigning them is not implied by color work.

Establish typography and icon sizing when needed

Use the typography specification for the role contract, editable specimen, mobile/desktop example scale and acceptance checks.

Treat typography as a reusable foundation alongside colors. If a scale is missing or explicitly requested, define semantic roles in native text styles before propagating them through components and screens. Reuse existing approved styles on subsequent screens; do not restart foundations for each screen.

  • Define only needed roles, such as page title, section title, item title, body, label, metadata and caption. Record font family, weight, size and line height; add tracking only where intentional.
  • Start with the user’s chosen primary viewport/platform and review its scale at actual width and 100% scale. Add only the other requested platforms, deriving values for their density and reading width rather than applying one multiplier. Mobile-first is one explicit choice, never the default.
  • Put a compact, editable specimen beside the color foundations. Include realistic titles, multiline body text, field labels and metadata so hierarchy and wrapping can be judged in context. Product-specific numbers belong in that product's system, not universal defaults in this skill.
  • When applying an approved scale to existing screens, update canonical sources and inspect linked instances and intentional overrides. Preserve unrelated layout choices; adjust spacing only where the new type metrics require it.
  • Define compact icon sizes and stroke weight separately from their larger interaction targets. Match semantic meaning: share, external link, expand and bookmark are different actions. Use approved brand assets for provider buttons and check applicable provider guidance; do not redraw or recolor logos as ordinary UI icons.

Produce a reviewable foundation

For color work, show palette roles and representative UI samples in every required theme, including text, surfaces, action/focus and relevant selected states. Temporary samples are exploration artifacts, not duplicate canonical components. Check actual foreground/background pairs, including transparency and image overlays; consult current official accessibility guidance for applicable contrast thresholds. Record measured results and unchecked combinations instead of claiming accessibility from appearance. Static previews cannot establish runtime theme or assistive-technology behavior.

Return only the foundations in scope: palette/theme mappings, typography specification with approval status, icon sizing, representative previews, relevant check evidence and unresolved decisions. Typography-only work reuses approved colors without a new palette exercise. In default workflow mode, wait for explicit approval before dependent component work; explicit continuation still requires verification and cannot resolve a genuinely missing user decision. Revisions that materially change an approved foundation return to the orchestrator's review gate.

Pass approved roles and bindings to design-components, and implementation mappings to design-handoff only when needed. Do not publish or modify application code as part of this stage.

Skills relacionados