Create complete user-context instruction files using a structured discovery workflow and repository format rules.
Scanned 9/2/2026
Install to Claude Code
npx -y skills add majiayu000/claude-skill-registry --skill create-usercontext-instructions --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Create Usercontext Instructions?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/majiayu000-create-usercontext-instructions-claude-skill-registry)More formats (shields.io, HTML) on the badges page.
---
name: "create-usercontext-instructions"
description: "Create complete user-context instruction files using a structured discovery workflow and repository format rules."
metadata:
source_prompt: "prompts/create-usercontext-instructions.prompt.md"
workflow_type: "generation"
---
# 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.md` file.
- 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
1. Run phased discovery using `references/discovery-phases.md`.
2. Normalize findings into required schema using `references/output-schema.md`.
3. Apply format contract from `references/output-format.md`.
4. Validate against `references/quality-checklist.md` before final output.
5. If structured metadata is requested, apply `references/json-metadata-schema.md`.
## Output Expectations
- One complete `*.instructions.md` file 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.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!