context-explicitness

Makes repository assumptions, constraints, and agent context explicit and machine-enforceable.

1|Updated Aug 14, 2026
One-click install
npx skills add https://github.com/zhiyuan-zhang0206/Ava --skill context-explicitness-zhiyuan-zhang0206
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: context-explicitness
Source: https://github.com/zhiyuan-zhang0206/Ava/tree/main/ava_builtins/skills/ava-serious-engineering/ai-era/context-explicitness
Command: npx skills add https://github.com/zhiyuan-zhang0206/Ava --skill context-explicitness-zhiyuan-zhang0206

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI coding agents have no memory between sessions, so repositories that rely on tribal knowledge cause agents to repeat the same mistakes. This Skill turns the repository into the agent's memory by making every assumption, constraint, and invariant explicit, machine-readable, and backed by enforcement that fails visibly when violated. ## Core Features & Use Cases - Enforced Context Rules: Pair every "must" or "never" rule in AGENTS.md or CLAUDE.md with a linter, CI check, architecture test, or compilation error so rules cannot silently rot. - Module Boundary Enforcement: Use tools like dependency-cruiser or import-linter to make module boundaries structural constraints rather than documentation conventions. - Feedback Loop for Learning: Convert every bug fix or correction into an AGENTS.md update in the same PR, so the rulebase compounds as the team's immune system. - Use Case: When setting up a repository for AI-agent development, audit it with the included checklist: can a fresh agent, reading only the repo, avoid repeating past mistakes? ## Quick Start Ask the agent to audit this repository's AGENTS.md and module boundaries against the context-explicitness checklist and propose enforced rules for any prose-only constraints.

Frequently Asked Questions about context-explicitness

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

FAQPage Schema
How do I make AGENTS.md rules enforceable instead of prose-only?▼

Pair every "must" or "never" statement with an automated check: a linter rule, CI step, architecture test, or compilation error. The gold standard is a rule whose violation fails CI; the minimum viable is a written review checklist item.

How do I enforce module boundaries for AI coding agents?▼

Use tooling rather than conventions: dependency-cruiser for JavaScript/TypeScript or import-linter for Python, with architecture tests that fail on boundary violations. Boundaries enforced in CI are real; boundaries in documentation alone are not.

Do 1M-token context windows eliminate the need for context management?▼

No. Larger windows introduce context rot, where irrelevant information degrades reasoning quality and token costs scale up. Practice minimum-sufficient-context, use sub-agents with condensed summaries, and treat context budget as a first-class resource.

When should AGENTS.md be updated after a bug fix?▼

In the same PR as the fix, not as a follow-up. Every correction that reveals a missing or incorrect constraint must update the context rule before merging, so the next agent cannot repeat the mistake.

How much does context infrastructure cost to maintain?▼

The Codified Context study measured roughly a 24% knowledge-to-code ratio for agent-compatible repositories. Budget context maintenance in sprint planning as part of "done," and run periodic context audits with a fresh agent to measure error rates.

What are the limits of prose-only repository documentation for agents?▼

Prose-only rules rot silently because nothing fails when they become false, and stale rules actively mislead agents. Treat stale AGENTS.md content as a bug of equal severity to a failing test and prune obsolete rules aggressively.