context-engineering
Skill2 starsChanged 24 days agoMITView on GitHub
Ensure the internal context an agent needs is current, complete, and placeholder-free before each session. Define minimum AI-accessible documentation per repo. Use at session startup to verify internal context is available to AI tools. Implements DORA AI Capability 3.
131 other projects use a version of this.
Adopted by
Most recently taken up by
- thistleknot/skillstheir own version, first seen Nov 8, 2026
- gerivdb/SKILLStheir own version, first seen Nov 8, 2026
- ishandutta2007/Awesome-Agent-Skillstheir own version, first seen Nov 8, 2026
- MMACABRE/SKILLStheir own version, first seen Nov 8, 2026
- gopalparashar421/agent-skillstheir own version, first seen Nov 8, 2026
- komluk/scaffoldingtheir own version, first seen Nov 7, 2026
Used with
Projects with it also use using-agent-skills, idea-refine and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
LLl0k0laDSkillusing-agent-skills
Use when starting a session or when you need to discover which skill applies to the current task. This is the meta-skill that governs how all other skills are discovered and invoked.
Also in 36 projects that use this
LLl0k0laDSkillidea-refine
Refine ideas through structured divergent and convergent thinking. Use "idea-refine" or "ideate" to trigger.
Also in 44 projects that use this
HK-hubSkilldeprecation-and-migration
Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when deciding whether to maintain or sunset existing code.
Also in 40 projects that use this
MrCipherSmithSkillconstraint-driven-development
Use when a project needs a persistent, measurable quality bar — starting a project without documented standards, 'set up constraints', or when coverage/perf/a11y thresholds get re-debated per-PR. Produces CONSTRAINTS.md with enforceable numbers, ratchets, and a guard against silent weakening. NOT for throwaway prototypes or a one-off CI setup.
Also in 14 projects that use this
HK-hubSkillsource-driven-development
Grounds every implementation decision in official documentation. Use when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters.
Also in 44 projects that use this
- +6 more from LLl0k0laD
- +1 more from HK-hub
Other versions131 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 131
- addyosmani/agent-skills★ 114ksame name
- bojieli/ai-agent-book-projects★ 53ksame name
- bojieli/ai-agent-book★ 53ksame name
- rohitg00/pro-workflow★ 2.9ksame name
- mrgoonie/claudekit-skills★ 2.2ksame name
- kdlbs/kandev★ 1.1ksame name
- liza-mas/liza★ 418same name
- typv/nest-turbo-starter★ 224same name
- VAMFI/claude-user-memory★ 206same name
- shashankswe2020-ux/whoop-mcp★ 174same name
121 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- opencode/AGENTS.mdAGENTS.md
- scripts/AGENTS.mdAGENTS.md
- ai-stanceSkill
- continuous-evalsSkill
- dev-experienceSkill
- discoverySkill
- documentationSkill
- langSkill
- ufawkes-knowledgeSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 117 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 31
Every uFawkes\* repo must maintain these files for AI-accessible context.
- Distinctive: line 62
Run at the start of every opencode session involving more than one file change.
“Common” is measured: kept by at least 6 in 10 of the 117 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Skill: Context Engineering
Load trigger:
"load context-engineering skill"> DORA: AI Capability 3: AI-accessible internal data Token cost: Low
Purpose
Move AI tools from generic assistants to specialized experts by connecting them to internal documentation and codebase structure. "Context engineering" is the practice of deliberately managing what internal knowledge is available to AI tools at session start — not just what prompt you give them.
DORA AI Capabilities Model v2025.1: "Connecting AI to your internal documentation and codebases moves it from a generic assistant to a specialized expert."
This skill eliminates the "re-discover context every session" tax — particularly costly at 2hrs/day across an 8-repo portfolio.
Minimum Corpus per Repo
Every uFawkes* repo must maintain these files for AI-accessible context. Missing files are flagged as corpus gaps, not silently ignored.
| File | Required | Purpose |
README.md | ✅ Mandatory | What this is, quick start, current status |
AGENTS.md | ✅ Mandatory | Agent suite, skill list, handoff protocol |
ARCHITECTURE.md or docs/ARCHITECTURE.md | ✅ Mandatory | System design, component relationships |
CONTRIBUTING.md | ✅ Mandatory | How to contribute — must not be a placeholder |
AI_STANCE.md | ✅ Mandatory | AI policy (see ai-stance skill) |
tests/README.md or equivalent | ✅ Mandatory | How to run tests, what they cover |
CHANGELOG.md | ✅ Mandatory | Release history |
DORA-event-format.md | ⚠ Required when uFawkesObs wired | Deployment event schema for DORA metrics |
Per-Repo Corpus Extensions
Beyond the minimum, each repo has domain-specific files that should be in the corpus:
| Repo | Additional corpus files |
fawkes | .agents/ directory tree, ROADMAP.md, .opencode/plans/roadmap.md, .gitops-templates/ |
uFawkesObs | docs/ARCHITECTURE.md, tests/acceptance/ structure, docs/production-hardening.md |
uFawkesAI | Full .agents/skills/ directory tree, all agent .md files |
uFawkesPipe | Pipeline definition files (.woodpecker.yml), docker-compose.yml |
uFawkesDevX | devcontainer.json, golden path templates |
uFawkesDORA | Dashboard JSON, metric query definitions |
uFawkesSec | Policy definitions (OPA Rego or Kyverno), threat model |
uFawkes.dev | _config.yml, _data/, navigation structure, SKILL.md files under .agents/ |
Session Startup Checklist
Run at the start of every opencode session involving more than one file change. Takes under 2 minutes. Prevents context-blind agent decisions.
# 1. Verify minimum corpus files exist
for f in README.md AGENTS.md CONTRIBUTING.md AI_STANCE.md CHANGELOG.md; do
[ -f "$f" ] || echo "CORPUS GAP: $f missing"
done
# Check for ARCHITECTURE.md in either location
[ -f "ARCHITECTURE.md" ] || [ -f "docs/ARCHITECTURE.md" ] || \
echo "CORPUS GAP: ARCHITECTURE.md missing (check docs/ too)"
# Check for test README
[ -f "tests/README.md" ] || [ -f "tests/TESTING.md" ] || \
echo "CORPUS GAP: test suite documentation missing"
# 2. Check AGENTS.md references current skill list
# (Agent should read AGENTS.md and verify all listed skills exist in .agents/skills/)Corpus Quality Signals
These indicate the corpus will give poor context — flag them, don't silently continue:
| Signal | Problem | Remediation |
CONTRIBUTING.md contains [Add contribution guidelines here] | Placeholder — agents read wrong content | Fill CONTRIBUTING.md before session |
README.md "Status" section missing | Agent doesn't know current state | Add Status section |
AGENTS.md references skills that don't exist | Stale skill list | Update AGENTS.md or create missing skill |
| ARCHITECTURE.md last modified > 90 days ago + recent structural changes | Stale architecture | Update ARCHITECTURE.md |
AI_STANCE.md last reviewed > 90 days ago | Stale policy | Run ai-stance audit sub-skill |
Span Events
Emit these telemetry spans (integrates with agent-observability skill):
| Span | When | Attributes |
context.corpus.verified | Startup check complete | repo, corpus_current, gap_count |
context.corpus.gap | A required file is missing | repo, missing_file |
context.corpus.stale | Corpus > 24hrs old | repo, hours_stale |
context.corpus.rebuilt | Corpus rebuild triggered | repo, files_indexed |
Output Format
{
"skill": "context-engineering",
"repo": "paruff/REPO_NAME",
"corpus_current": true,
"last_built": "2026-06-16T08:00:00Z",
"hours_stale": 2,
"missing_files": [],
"corpus_quality_warnings": [],
"pending_skills": ["j-curve-navigation"],
"ready_for_session": true
}Sub-Skills
| Sub-skill | Purpose |
context-engineering/startup | Run the session startup checklist |
context-engineering/audit | Full corpus audit across all 8 uFawkes* repos |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

