agentsclimarketplace

Create project instructions

Skill MSiccDev/ai-context-kit/skills/create-project-instructions

AI Context Kit provides a structured, instruction-based framework for context-aware AI collaboration across LLM providers. It includes authoritative specs, canonical templates, and skills workflows for creating and validating user context and project AGENTS.md files.

Install
npx -y skills add MSiccDev/ai-context-kit --skill create-project-instructions

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 11 stars11 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Create project-context AGENTS.md files using phased discovery, required operational sections, and session-state modeling.

SKILL.md

2.9 KB, as published. Nobody here has run it

Create Project Context AGENTS

Purpose

Generate project-context AGENTS.md files with required sections, role definitions, command namespace controls, and validation-ready structure.

When To Use

  • Use this skill when the task is to create or regenerate project-context AGENTS.md.
  • Use this skill when project context must include role/phase/style defaults.
  • Do not use this skill for user-context instruction generation.

How to Invoke

Load or attach this file's contents into your AI session to activate the workflow (paste, upload, or reference with #file:skills/create-project-instructions/SKILL.md in VS Code Copilot Chat). In Claude Projects, add it to project knowledge. See Invoking Skills in the README for full platform guidance.

Required Inputs

  • Project name, description, and current phase.
  • Tech stack, architecture, and repository structure.
  • Roles, default session state, and command namespace.
  • Objectives, testing strategy, and documentation standards.

Workflow

  1. Run phased discovery using references/discovery-phases.md.
  2. Apply required output schema from references/output-schema.md.
  3. Build command and role structures using:
    • references/command-template.md
    • references/role-template.md
  4. Apply artifact/summary contract from references/output-format.md.
  5. Stamp <!-- spec_version: 1.4.3 --> as an HTML comment at the top of the generated AGENTS.md.
  6. Validate completeness using references/quality-checklist.md before final output.

Output Expectations

  • One complete AGENTS.md file with all required project-context sections.
  • Session-state and command-reference elements are fully populated.
  • Core project-context required-section completeness is enforced through AGENTS structure.
  • Role definitions and examples are project-specific and actionable.
  • Output remains 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
  • Command template: references/command-template.md
  • Role templates: references/role-template.md
  • Output contract: references/output-format.md
  • Quality checklist: references/quality-checklist.md
  • Structure baseline: ../../templates/AGENTS_template.md
  • Example reference: ../../AGENTS.md

Constraints And Safety

  • Keep recommendations tied to project scope.
  • Avoid placeholders in final command examples unless explicitly unresolved.
  • Use relative paths for references.
  • Do not introduce provider-specific assumptions.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.