Create User Context Instructions
Purpose
Generate a complete user-context instruction file with required sections, privacy-aware content handling, and consistent output formatting.
When To Use
- •Use this skill when the task is to create or regenerate a
*_usercontext.instructions.mdfile. - •Use this skill when user context must be gathered through structured phases.
- •Do not use this skill for project
AGENTS.md(project context) files.
Required Inputs
- •Target identity label and role/title.
- •Privacy expectations (full detail vs placeholders).
- •Technical profile, projects, goals, style, and constraints.
- •Desired output filename/path.
Workflow
- •Run phased discovery using
references/discovery-phases.md. - •Normalize findings into required schema using
references/output-schema.md. - •Apply format contract from
references/output-format.md. - •Validate against
references/quality-checklist.mdbefore final output. - •If structured metadata is requested, apply
references/json-metadata-schema.md.
Output Expectations
- •One complete
*.instructions.mdfile for user context. - •Required section coverage and logical ordering are preserved.
- •Privacy handling is explicit and consistent.
- •Output is provider-neutral.
- •Output contract and summary format follow
references/output-format.md.
Resources
- •Discovery workflow:
references/discovery-phases.md - •Output schema:
references/output-schema.md - •Optional metadata schema:
references/json-metadata-schema.md - •Output contract:
references/output-format.md - •Quality checklist:
references/quality-checklist.md - •Structure baseline:
../../templates/usercontext_template.instructions.md - •Example reference:
../../usercontexts/sample_usercontext.instructions.md
Constraints And Safety
- •Keep provider-neutral wording.
- •Preserve sensitive data boundaries; prefer placeholders when requested.
- •Use relative paths for references.
- •Avoid unrelated recommendations outside user-context scope.