---
name: design-system-context
description: Apply a practitioner-supplied design system and delivery conventions when defining prototype or UI implementation guidance.
---

# Design System Context

Public edition: 1.0.16

Read the user's approved design-system sources and implementation constraints. Identify framework, components, tokens, interaction conventions, states, responsive behavior, accessibility requirements, and review expectations.

Prefer existing components where they meet the need. Explain any proposed exception and its rationale. Do not invent token names or values, copy another organization's design assets, or assume a particular framework. If standards are missing, label proposed defaults and the decisions requiring confirmation.

Keep product intent in the blueprint and detailed component rules in the design-system reference. Connect error, empty, loading, permission, and recovery behavior to implementation and validation. Produce guidance sized to the requested artifact; do not prescribe a new design system unless requested.


## Supplied project context

Use the project profile explicitly supplied by the user or established project instructions; bundled blank templates are not project requirements. Do not assume that a filename, installation or source listing means its contents are available. Identify the sources actually read. Unfilled placeholders remain unknowns. A referenced URL is unverified until its contents are available. If sources conflict materially, explain the conflict and seek the governing source rather than silently choosing one.

Keep user profiles and requested presentation adaptations outside installed plugin files so updates preserve them. Do not write to caches or change project requirements merely because the plugin was updated. For design-system work, neutral renderer styling is a default, not automatic implementation of a supplied system. Consult [context setup](references/public-library/CONFIGURATION.md) when configuring a project, not for unrelated tasks.

## Foundations and attribution

Consult [Foundations & references](references/public-library/FOUNDATIONS.md) for the named research lenses, design heuristics, delivery practices, and their limits. Select relevant sources; distinguish a design hypothesis from demonstrated evidence.