Contextual rule precedence

These examples and illustrative results are independently authored teaching materials, not measured model results.

Use case

Improve an existing brand site. Its brief explicitly preserves purple #6D28D9 and asks for clearer hierarchy and spacing. A design reference discourages purple effects as a default. This does not require replacing an established brand color.

Mechanism

Separate explicit requirements, conditional defaults and accessibility obligations. State the applicable override: the brand color is specified, so retain it; defaults govern unspecified choices. Apply the selected rules to components and states, then inspect for local implementations drifting back to another default palette.

Bad example

Improve hierarchy and spacing for the brand site above. The reference discourages purple, so replace #6D28D9 everywhere with green to modernize the site.

Good example

Improve the site while preserving the brief's #6D28D9 brand color. Treat the reference's no-purple preference as a default for unspecified branding, overridden here by the explicit brief. Improve hierarchy, spacing and neutral surfaces. Inspect distinguishability and contrast in purple links, buttons and focus states. Identify concrete accessibility conflicts and adjust the affected shade or use when needed.

Why the change matters

The bad instruction turns a conditional preference into a universal ban that overrides the brand brief. Declaring default and override together explains the retained purple and keeps later components from independently choosing another palette.

Observable expectation

An illustrative rule record attributes purple to the brief, neutral backgrounds to an unspecified choice and focus/text contrast to actual checks. Inspect the page and interaction states for consistent brand identity and evaluate each reference recommendation’s conditions.

Replacing the brand solely because of a default ban, or skipping contrast because the brand is fixed, fails this fixture.

Limits

This method resolves design guidance in context, not system-level instruction hierarchy. Aesthetic preferences and numeric style dials are not measured evidence; brand constraints do not waive accessibility. For genuinely incompatible requirements, record the conflict and candidate adjustments first.