Framework Context
Overview
Provide a consistent, source-anchored model of this framework so agents can reason about system-level behavior without guessing.
When to Use
- System-level reflection or metacognitive assessment
- Planning tasks that depend on routing/memory/workflow architecture
- Capability-gap analysis before recommending ecosystem evolution
Iron Laws
- ALWAYS load framework context before any system-level reflection, planning, or capability-gap analysis — reasoning about architecture without grounding produces hallucinated paths and phantom agents.
- NEVER fabricate file paths or agent names that are not confirmed by reading canonical sources — invented paths break downstream agents that try to use them.
- ALWAYS scope the context load to only what the consuming task needs (
memory, agents, workflows, hooks, or all) — loading all sources for a narrow task wastes tokens and buries relevant signals.
- NEVER write or modify framework files from within this skill — framework-context is read-only; mutations require the appropriate creator/updater skill.
- ALWAYS report missing sources explicitly as
missing source: <path> rather than silently omitting a section — silent omissions cause downstream agents to make decisions on incomplete context.
Anti-Patterns
| Anti-Pattern |
Why It Fails |
Correct Approach |
| Skipping context load before reflection |
Reflection uses stale or hallucinated routing/memory assumptions |
Always invoke framework-context first; never reflect from memory alone |
Loading full all scope for a narrow task |
Token budget consumed by irrelevant sections; key signal buried |
Pass --scope memory or --scope agents to limit output to what's needed |
| Inferring file paths from naming conventions |
Paths change; inferred paths break agent pipelines |
Always read canonical sources and report actual paths found |
| Writing to framework files inside this skill |
Bypasses creator workflow and post-creation integration steps |
Use appropriate creator/updater skill for any write operations |
| Silently omitting sections when source is missing |
Consumer assumes context is complete; makes decisions on gaps |
Report missing source: <path> explicitly for every unresolvable section |
Step 0: Resolve Scope
- Accept
scope argument: memory | agents | workflows | hooks | all
- Default to
all
Step 1: Load Canonical Sources
Read only what is required by scope:
- Memory:
.claude/docs/MEMORY_SYSTEM.md
- Agent registry/routing:
.claude/context/agent-registry.json, .claude/lib/routing/routing-table.cjs
- Reflection flow hooks:
.claude/hooks/reflection/reflection-queue-processor.cjs, .claude/hooks/reflection/reflection-step0-guard.cjs
- Workflow catalog:
.claude/docs/@ENTERPRISE_WORKFLOWS.md
- Global framework references:
.claude/CLAUDE.md
Step 2: Emit Structured Context
Output sections in this exact order:
- Memory System
- Agents and Routing
- Workflows
- Hooks
- Directory Layout
Each section must include:
- 2-6 concise bullets
- At least one concrete path reference
- Behavior notes (what triggers what)
Step 3: Scope Filter
- If
scope != all, return only relevant section(s)
- Never fabricate unknown paths or flows
- If a source is missing, state
missing source: <path>
Step 3: Output
Return markdown only; do not write framework files from this skill.
// Full framework model
Skill({ skill: 'framework-context' });
// Memory-only context for reflection prep
Skill({ skill: 'framework-context', args: '--scope memory' });
// Workflow/hook-only context for integration analysis
Skill({ skill: 'framework-context', args: '--scope workflows' });
Memory Protocol (MANDATORY)
Before starting:
Get-Content .claude/context/memory/learnings.md -TotalCount 120
After completing:
- New framework-context pattern ->
.claude/context/memory/learnings.md
- Broken/ambiguous framework mapping ->
.claude/context/memory/issues.md
- Architectural interpretation decision ->
.claude/context/memory/decisions.md
ASSUME INTERRUPTION: Your context may reset. If it's not in memory, it didn't happen.
1---2name: framework-context3description: Load and synthesize framework architecture context for reflection and planning tasks.4version: 1.1.05model: sonnet6invoked_by: both7user_invocable: true8tools: [Read, Skill]9error_handling: graceful10streaming: supported11verified: true12lastVerifiedAt: 2026-02-22T00:00:00.000Z13source: builtin14trust_score: 10015provenance_sha: 2d1d97ef8eef4f7e16metadata:17 source: https://skillmd.com/skills/oimiragieo/framework-context18---1920# Framework Context2122## Overview2324Provide a consistent, source-anchored model of this framework so agents can reason about system-level behavior without guessing.2526## When to Use2728- System-level reflection or metacognitive assessment29- Planning tasks that depend on routing/memory/workflow architecture30- Capability-gap analysis before recommending ecosystem evolution3132## Iron Laws33341. **ALWAYS** load framework context before any system-level reflection, planning, or capability-gap analysis — reasoning about architecture without grounding produces hallucinated paths and phantom agents.352. **NEVER** fabricate file paths or agent names that are not confirmed by reading canonical sources — invented paths break downstream agents that try to use them.363. **ALWAYS** scope the context load to only what the consuming task needs (`memory`, `agents`, `workflows`, `hooks`, or `all`) — loading all sources for a narrow task wastes tokens and buries relevant signals.374. **NEVER** write or modify framework files from within this skill — framework-context is read-only; mutations require the appropriate creator/updater skill.385. **ALWAYS** report missing sources explicitly as `missing source: <path>` rather than silently omitting a section — silent omissions cause downstream agents to make decisions on incomplete context.3940## Anti-Patterns4142| Anti-Pattern | Why It Fails | Correct Approach |43| ------------------------------------------------- | ---------------------------------------------------------------- | -------------------------------------------------------------------------- |44| Skipping context load before reflection | Reflection uses stale or hallucinated routing/memory assumptions | Always invoke framework-context first; never reflect from memory alone |45| Loading full `all` scope for a narrow task | Token budget consumed by irrelevant sections; key signal buried | Pass `--scope memory` or `--scope agents` to limit output to what's needed |46| Inferring file paths from naming conventions | Paths change; inferred paths break agent pipelines | Always read canonical sources and report actual paths found |47| Writing to framework files inside this skill | Bypasses creator workflow and post-creation integration steps | Use appropriate creator/updater skill for any write operations |48| Silently omitting sections when source is missing | Consumer assumes context is complete; makes decisions on gaps | Report `missing source: <path>` explicitly for every unresolvable section |4950<identity>51Framework grounding skill for memory architecture, routing, workflows, hooks, and directory layout.52</identity>5354<capabilities>55- Produce scoped context summaries (`memory`, `agents`, `workflows`, `hooks`, `all`)56- Anchor every section to concrete repository paths57- Standardize framework context output for reflection/planning consumers58</capabilities>5960<instructions>61<execution_process>6263### Step 0: Resolve Scope6465- Accept `scope` argument: `memory | agents | workflows | hooks | all`66- Default to `all`6768### Step 1: Load Canonical Sources6970Read only what is required by scope:7172- Memory: `.claude/docs/MEMORY_SYSTEM.md`73- Agent registry/routing: `.claude/context/agent-registry.json`, `.claude/lib/routing/routing-table.cjs`74- Reflection flow hooks: `.claude/hooks/reflection/reflection-queue-processor.cjs`, `.claude/hooks/reflection/reflection-step0-guard.cjs`75- Workflow catalog: `.claude/docs/@ENTERPRISE_WORKFLOWS.md`76- Global framework references: `.claude/CLAUDE.md`7778### Step 2: Emit Structured Context7980Output sections in this exact order:81821. **Memory System**832. **Agents and Routing**843. **Workflows**854. **Hooks**865. **Directory Layout**8788Each section must include:8990- 2-6 concise bullets91- At least one concrete path reference92- Behavior notes (what triggers what)9394### Step 3: Scope Filter9596- If `scope != all`, return only relevant section(s)97- Never fabricate unknown paths or flows98- If a source is missing, state `missing source: <path>`99100### Step 3: Output101102Return markdown only; do not write framework files from this skill.103104</execution_process>105</instructions>106107<examples>108<usage_example>109**Example Invocations**:110111```javascript112// Full framework model113Skill({ skill: 'framework-context' });114115// Memory-only context for reflection prep116Skill({ skill: 'framework-context', args: '--scope memory' });117118// Workflow/hook-only context for integration analysis119Skill({ skill: 'framework-context', args: '--scope workflows' });120```121122</usage_example>123</examples>124125## Memory Protocol (MANDATORY)126127**Before starting:**128129```powershell130Get-Content .claude/context/memory/learnings.md -TotalCount 120131```132133**After completing:**134135- New framework-context pattern -> `.claude/context/memory/learnings.md`136- Broken/ambiguous framework mapping -> `.claude/context/memory/issues.md`137- Architectural interpretation decision -> `.claude/context/memory/decisions.md`138139> ASSUME INTERRUPTION: Your context may reset. If it's not in memory, it didn't happen.