establishing-project-context

Create and maintain a CONTEXT.md defining shared project vocabulary.

968|43|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/GanyuanRan/Aegis --skill establishing-project-context
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: establishing-project-context
Source: https://github.com/GanyuanRan/Aegis/tree/main/skills/establishing-project-context
Command: npx skills add https://github.com/GanyuanRan/Aegis --skill establishing-project-context

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams avoid miscommunication by establishing a shared vocabulary through a CONTEXT.md at the project root.

Core Features & Use Cases

  • Create and maintain a CONTEXT.md at the project root to define domain terms, relationships, and resolved ambiguities.
  • Use CONTEXT-MAP.md for monorepos to map context names to their locations, while keeping system-wide terms in root CONTEXT.md.
  • Write term resolutions immediately as they are clarified to prevent re-litigation.
  • Integrate CONTEXT.md with agent workflows for brainstorming, planning, and debugging.

Quick Start

Create or update the root CONTEXT.md with 3-5 core domain terms and immediate term resolutions.

Frequently Asked Questions about establishing-project-context

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I establish a shared project vocabulary to align teams?▼

To establish a shared project vocabulary, create a CONTEXT.md file at the project root defining 3-5 core domain terms with precise one-sentence definitions to align stakeholders and resolve ambiguities.

What is the best way to maintain domain terms in a monorepo?▼

For monorepos, maintain domain terms by keeping system-wide definitions in the root CONTEXT.md and mapping context names to specific locations using a CONTEXT-MAP.md file.

When do I need to update the CONTEXT.md file?▼

You need to update CONTEXT.md immediately when ambiguous terms are clarified during onboarding, brainstorming, planning, or debugging to prevent re-litigation and ensure continuous team alignment.

Can I integrate context documentation with agent workflows for debugging?▼

Yes, you can integrate CONTEXT.md with agent workflows for debugging, planning, and brainstorming to provide precise domain term definitions and resolve ambiguous terminology automatically.

What should a domain term definition in CONTEXT.md avoid?▼

A domain term definition in CONTEXT.md should avoid implementation details, providing only a precise one-sentence definition to clarify meaning without tying it to specific code structures.