contextualize

Hyper-Contextualize

This skill audits the installed HACF agent instruction files (CLAUDE.md, AGENTS.md, GEMINI.md) to verify they frame HACF as a development toolchain rather than the project subject. It also checks README.md for HACF context bleed.

Run this skill:

• After installing HACF into an existing project for the first time
• When you notice the AI treating HACF skills/schemas as the project's own features
• After /hyper-update if you merged agent files and the framing may have been lost

---

Step 1 — Pre-flight Check

Verify .agents/ exists in the current directory. If not, halt with: ERROR: No .agents/ directory found. This is not an HACF project.

---

Step 2 — Scan Agent Files

Read each of the following from the project root if they exist: CLAUDE.md, AGENTS.md, GEMINI.md, README.md

For each agent file (CLAUDE.md, AGENTS.md, GEMINI.md), check:

1. Framing banner present? Look for the string HACF as a Toolchain near the top of the file.
2. Internal migration notice present? Look for any of: deadline 2026-06-17, CI lint will enforce, docs/MIGRATION_RULES.md.
3. Framework Upgrade & Maintenance section present? Look for a heading with exactly that text — it describes /hyper-update internals and should not appear in user project docs.

---

Step 3 — Report Findings

Print a structured audit report:

HACF Contextualization Audit
─────────────────────────────────────────────
✅ CLAUDE.md   — Framing: PRESENT  |  Internal notices: NONE
⚠️  AGENTS.md   — Framing: MISSING  |  Internal notices: FOUND (migration notice)
❌ GEMINI.md   — File not found (Gemini not installed — skip)
📄 README.md   — Checked (see findings below)

If all installed agent files pass all checks: output [CONTEXTUALIZED: OK] and stop.

---

Step 4 — Ask How to Fix

If any issues were found, use AskUserQuestion with these options:

• Replace with install templates (Recommended) — copies .agents/install-templates/<file> over each affected file. Canonical framing, no stale notices. Project-specific customizations in the current files will be lost.
• Inject framing banner only — prepends the "HACF as a Toolchain" block to each affected file without touching the rest. Preserves existing content but does NOT remove stale migration notices.
• Show diff first, decide per file — display a summary of differences between install template and current file, then ask Replace / Inject / Skip for each file individually.