# Do It Context

> Use when project terms, relationships, or invariants drift between user language, docs, and implementation.

- Skill: `tdwhere123/do-it-context` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tdwhere123/do-it-context`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tdwhere123/do-it-context/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: tdwhere123 (https://skillmd.com/u/tdwhere123)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tdwhere123/do-it-context

---


# Project Context

Resolve ambiguous names and conflicting facts against current code, project
instructions, and the user's intended meaning. Separate domain concepts from
implementation labels; make important relationships and invariants explicit.

Prefer the existing glossary or documentation owner. If a concise context file
would prevent repeated confusion, propose or maintain it within the authorized
scope; .do-it/CONTEXT.md is one possible home, not a required authority.

Keep stable project facts, temporary assumptions, and task progress distinguishable.
Include only terms that help decisions, with source links when useful. Update
consumers of renamed concepts without inventing a second source of truth.