---
name: domain-context-adaptation
description: Adapt analysis to a practitioner-supplied domain profile when industry, roles, operating conditions, terminology, or specialist constraints affect the work.
---

# Domain Context Adaptation

Public edition: 1.0.16

Read the supplied context brief when the task depends on domain knowledge. Identify roles, tasks, decisions, environment, operating rhythm, authority, terminology, data definitions, error consequences, and applicable source-backed requirements.

Distinguish what is confirmed from assumptions, including variation between teams or locations. Ask a targeted question when a missing fact changes the recommendation. If no profile exists, use general analysis and label domain assumptions; do not invent procedures, thresholds, laws, or business rules.

Connect context to workflow, product scope, feasibility, accessibility, human review, and validation. Preserve useful general methods while replacing domain-specific examples. Use the fictional example only to understand the structure, not as evidence about the user's setting.

Output a short context summary, implications for the requested decision, gaps, and responsible reviewers. Do not expand unrelated tasks into a domain audit.


## 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.