connotation-cop

Audit terminology against a CONTEXT.md glossary and enforce ADR documentation.

Updated Jul 23, 2026
One-click install
npx skills add https://github.com/Theycallmeholla/skills --skill connotation-cop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: connotation-cop
Source: https://github.com/Theycallmeholla/skills/tree/main/skills/connotation-cop
Command: npx skills add https://github.com/Theycallmeholla/skills --skill connotation-cop

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill resolves ambiguity in project terminology and ensures that critical architectural decisions are documented consistently, preventing the common issue of teams using the same words to describe different concepts.

Core Features & Use Cases

  • Glossary Enforcement: Actively monitors conversations to ensure terms align with the project's CONTEXT.md glossary.
  • ADR Management: Identifies when a decision meets the threshold for an Architectural Decision Record and guides the user through the creation process.
  • Scenario Testing: Pushes abstract concepts through edge-case scenarios to expose hidden disagreements in domain modeling.

Quick Start

Use the connotation-cop skill to review our current terminology and identify any architectural decisions that need to be recorded as ADRs.

Frequently Asked Questions about connotation-cop

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

FAQPage Schema
How do I standardize project vocabulary to eliminate domain ambiguity?

To standardize project vocabulary, you audit terminology against a central CONTEXT.md glossary to ensure terms align and eliminate domain ambiguity across the team.

What is the best way to manage architectural decision records for high-impact design choices?

Managing architectural decision records involves identifying high-impact design choices and enforcing strict criteria to document them consistently in a defined Markdown format.

How does context mapping work for domain-driven design terminology?

Context mapping for domain-driven design works by pushing abstract concepts through edge-case scenarios to expose hidden disagreements and maintain a consistent project knowledge base.

When do I need to create an architectural decision record?

You need to create an architectural decision record when a design choice meets the specific threshold for high impact, requiring strict criteria and consistent Markdown documentation.

Can I use a central glossary to enforce consistent project terminology?

Yes, you can use a central glossary within CONTEXT.md to actively monitor conversations and enforce consistent project terminology, preventing teams from using the same words for different concepts.

What format should I use for architectural decision logging?

Architectural decision logging requires adherence to a defined Markdown format to maintain a consistent project knowledge base and properly document high-impact design choices.