agentleFS
paruffparuff/uFawkesAI/.agents/skills/context-engineering/SKILL.md

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

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.
  • LLl0k0laDSkill

    using-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

  • LLl0k0laDSkill

    idea-refine

    Refine ideas through structured divergent and convergent thinking. Use "idea-refine" or "ideate" to trigger.

    Also in 44 projects that use this

  • HK-hubSkill

    deprecation-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

  • MrCipherSmithSkill

    constraint-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-hubSkill

    source-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

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
  1. Distinctive:

    Every uFawkes\* repo must maintain these files for AI-accessible context.

    line 31
  2. Distinctive:

    Run at the start of every opencode session involving more than one file change.

    line 62

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

FileRequiredPurpose
README.md✅ MandatoryWhat this is, quick start, current status
AGENTS.md✅ MandatoryAgent suite, skill list, handoff protocol
ARCHITECTURE.md or docs/ARCHITECTURE.md✅ MandatorySystem design, component relationships
CONTRIBUTING.md✅ MandatoryHow to contribute — must not be a placeholder
AI_STANCE.md✅ MandatoryAI policy (see ai-stance skill)
tests/README.md or equivalent✅ MandatoryHow to run tests, what they cover
CHANGELOG.md✅ MandatoryRelease history
DORA-event-format.md⚠ Required when uFawkesObs wiredDeployment event schema for DORA metrics

Per-Repo Corpus Extensions

Beyond the minimum, each repo has domain-specific files that should be in the corpus:

RepoAdditional corpus files
fawkes.agents/ directory tree, ROADMAP.md, .opencode/plans/roadmap.md, .gitops-templates/
uFawkesObsdocs/ARCHITECTURE.md, tests/acceptance/ structure, docs/production-hardening.md
uFawkesAIFull .agents/skills/ directory tree, all agent .md files
uFawkesPipePipeline definition files (.woodpecker.yml), docker-compose.yml
uFawkesDevXdevcontainer.json, golden path templates
uFawkesDORADashboard JSON, metric query definitions
uFawkesSecPolicy 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:

SignalProblemRemediation
CONTRIBUTING.md contains [Add contribution guidelines here]Placeholder — agents read wrong contentFill CONTRIBUTING.md before session
README.md "Status" section missingAgent doesn't know current stateAdd Status section
AGENTS.md references skills that don't existStale skill listUpdate AGENTS.md or create missing skill
ARCHITECTURE.md last modified > 90 days ago + recent structural changesStale architectureUpdate ARCHITECTURE.md
AI_STANCE.md last reviewed > 90 days agoStale policyRun ai-stance audit sub-skill

Span Events

Emit these telemetry spans (integrates with agent-observability skill):

SpanWhenAttributes
context.corpus.verifiedStartup check completerepo, corpus_current, gap_count
context.corpus.gapA required file is missingrepo, missing_file
context.corpus.staleCorpus > 24hrs oldrepo, hours_stale
context.corpus.rebuiltCorpus rebuild triggeredrepo, 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-skillPurpose
context-engineering/startupRun the session startup checklist
context-engineering/auditFull corpus audit across all 8 uFawkes* repos

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.