agentleFS
Sign inStart free
MSiccDevMSiccDev/ai-context-kit/skills/create-usercontext-instructions/SKILL.md

create-usercontext-instructions

Skill12 starsChanged 4 months agoMITView on GitHub

Create complete user-context instruction files using a structured discovery workflow and repository format rules.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this skill when the task is to create or regenerate a *_usercontext.instructions.md file.

    line 17
  2. Distinctive:

    Use this skill when user context must be gathered through structured phases.

    line 18
  3. Distinctive:

    Do not use this skill for project AGENTS.md (project context) files.

    line 19
  4. Very specific:

    Run phased discovery using references/discovery-phases.md.

    line 28
  5. Very specific:

    If structured metadata is requested, apply references/json-metadata-schema.md.

    line 33
  6. Distinctive:

    Use relative paths for references.

    line 54
  7. Distinctive:

    Avoid unrelated recommendations outside user-context scope.

    line 55

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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. Stamp spec_version: "1.5.0" in the YAML frontmatter of the generated artifact.
  5. Validate against references/quality-checklist.md before final output.
  6. 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free