One-click install
npx skills add https://github.com/alexandremendoncaalvaro/CorridorKey-Runtime --skill ad-domain
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ad-domain
Source: https://github.com/alexandremendoncaalvaro/CorridorKey-Runtime/tree/main/.agents/skills/ad-domain
Command: npx skills add https://github.com/alexandremendoncaalvaro/CorridorKey-Runtime --skill ad-domain

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Lazily create or update CONTEXT.md (Layer 2 — ubiquitous language per Evans 2003) at the repo root, or CONTEXT-MAP.md plus per-context CONTEXT.md for multi-context repos. Captures canonical project-specific nouns, the aliases to avoid, the Relationships between them, and resolved ambiguities. Triggers on "domain term", "ubiquitous language", "glossary", "what should we call", "naming drift", canonical noun, "Avoid", "/ad-domain", or whenever a grilling/spec/architecture session resolves a vocabulary question. Lazy by design — file only exists when there is something to write.

Core Features & Use Cases

  • Lazy lifecycle owner of CONTEXT.md. Process scaffold for capturing the project's ubiquitous language.
  • Captures canonical project-specific nouns with aliases-to-avoid, relationships, and flagged ambiguities.
  • Supports single-context or CONTEXT-MAP.md multi-context repos and lazy creation.

Quick Start

Create or update CONTEXT.md at the repo root (or CONTEXT-MAP.md plus per-context CONTEXT.md for multi-context repos) once terms are resolved.

Frequently Asked Questions about ad-domain

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

FAQPage Schema
How do I maintain a ubiquitous language glossary for domain-driven design without manual overhead?

You can lazily capture and maintain a project-specific ubiquitous language in CONTEXT.md, recording canonical nouns, aliases to avoid, and relationships only when domain terms are actually resolved during sessions.

What is the best way to document naming drift and resolved ambiguities in a multi-context repository?

Documenting naming drift in a multi-context repository involves generating a CONTEXT-MAP.md file alongside per-context CONTEXT.md files, ensuring resolved ambiguities and canonical nouns are cross-referenced appropriately.

When do I need a CONTEXT-MAP.md file instead of a single CONTEXT.md for my domain language?

A CONTEXT-MAP.md file is needed instead of a single CONTEXT.md when managing a multi-context repository, allowing you to organize and cross-reference ubiquitous language across distinct bounded contexts separately.

How does lazy creation of a domain glossary work during spec drafting?

Lazy creation of a domain glossary works by writing to CONTEXT.md only when a vocabulary question is resolved during spec drafting or grilling, meaning the file only exists when there is something canonical to record.

Can I capture canonical nouns and aliases to avoid without pre-configuring a glossary file?

Yes, you can capture canonical nouns and aliases to avoid without pre-configuring a glossary file, because the process scaffold creates or updates CONTEXT.md automatically once terms are explicitly resolved.