
Framework Context
- 42 installs
- 36 repo stars
- Updated July 14, 2026
- oimiragieo/agent-studio
Helps with ai & agent building tasks.
About
framework-context is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted development.
- framework-context
- AI & Agent Building
- AI-coding skill
Framework Context by the numbers
- 42 all-time installs (skills.sh)
- Ranked #8,023 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/oimiragieo/agent-studio --skill framework-contextAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 42 |
|---|---|
| repo stars | ★ 36 |
| Last updated | July 14, 2026 |
| Repository | oimiragieo/agent-studio ↗ |
What it does
Helps with ai & agent building tasks.
Files
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
1. 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. 2. 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. 3. 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. 4. NEVER write or modify framework files from within this skill — framework-context is read-only; mutations require the appropriate creator/updater skill. 5. 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 |
<identity> Framework grounding skill for memory architecture, routing, workflows, hooks, and directory layout. </identity>
<capabilities>
- Produce scoped context summaries (
memory,agents,workflows,hooks,all) - Anchor every section to concrete repository paths
- Standardize framework context output for reflection/planning consumers
</capabilities>
<instructions> <execution_process>
Step 0: Resolve Scope
- Accept
scopeargument: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:
1. Memory System 2. Agents and Routing 3. Workflows 4. Hooks 5. 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.
</execution_process> </instructions>
<examples> <usage_example> Example Invocations:
// 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' });</usage_example> </examples>
Memory Protocol (MANDATORY)
Before starting:
Get-Content .claude/context/memory/learnings.md -TotalCount 120After 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.
Invoke the framework-context skill and follow it exactly as presented to you
#!/usr/bin/env node
/**
* Framework Context - Post-Execute Hook
* Runs after the skill executes for cleanup, logging, or follow-up actions.
*
* This hook receives the skill execution result as JSON in process.argv[2]
*/
const fs = require('fs');
const path = require('path');
const { safeParseJSON } = require('../../../lib/utils/safe-json.cjs');
// Parse hook input
const result = safeParseJSON(process.argv[2] || '{}');
console.log('📝 [FRAMEWORK-CONTEXT] Post-execute processing...');
/**
* Process execution result
*/
function processResult(_result) {
// TODO: Add your post-processing logic here
// Examples:
// - Log execution to audit file
// - Send notifications
// - Update memory files
// - Trigger follow-up actions
return { success: true };
}
// Run post-processing
const outcome = processResult(result);
if (outcome.success) {
console.log('✅ [FRAMEWORK-CONTEXT] Post-processing complete');
process.exit(0);
} else {
console.error('⚠️ [FRAMEWORK-CONTEXT] Post-processing had issues');
process.exit(0); // Don't fail the skill for post-processing issues
}
#!/usr/bin/env node
/**
* Framework Context - Pre-Execute Hook
* Runs before the skill executes to validate input or prepare context.
*
* This hook receives the skill invocation context as JSON in process.argv[2]
*/
const fs = require('fs');
const path = require('path');
const { safeParseJSON } = require('../../../lib/utils/safe-json.cjs');
// Parse hook input
const input = safeParseJSON(process.argv[2] || '{}');
console.log('🔍 [FRAMEWORK-CONTEXT] Pre-execute validation...');
/**
* Validate input before execution
*/
function validateInput(_input) {
const errors = [];
// TODO: Add your validation logic here
// Example:
// if (!input.requiredField) {
// errors.push('Missing required field: requiredField');
// }
return errors;
}
// Run validation
const errors = validateInput(input);
if (errors.length > 0) {
console.error('❌ Validation failed:');
errors.forEach(e => console.error(' - ' + e));
process.exit(1);
}
console.log('✅ [FRAMEWORK-CONTEXT] Validation passed');
process.exit(0);
framework-context Research Requirements
Generated: 2026-02-28
Skill Description
Load and synthesize framework architecture context for reflection and planning tasks.
Research Areas
- Current best practices for framework-context
- Industry standards and tooling
- Integration patterns
Source References
- To be populated by skill-updater research phase
framework-context Rules
Purpose
Load and synthesize framework architecture context for reflection and planning tasks.
Best Practices
- Follow established patterns
- Validate inputs at boundaries
Integration Points
See SKILL.md for complete documentation.
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"title": "framework-context Input Schema",
"description": "Input validation schema for framework-context skill",
"type": "object",
"required": [],
"properties": {},
"additionalProperties": true
}
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"title": "framework-context Output Schema",
"description": "Output validation schema for framework-context skill",
"type": "object",
"required": ["success"],
"properties": {
"success": {
"type": "boolean",
"description": "Whether the skill executed successfully"
},
"result": {
"type": "object",
"description": "The skill execution result",
"additionalProperties": true
},
"error": {
"type": "string",
"description": "Error message if execution failed"
}
},
"additionalProperties": true
}
#!/usr/bin/env node
/**
* Framework Context - Main Script
* Provide structured framework context for system-level reflection and planning decisions.
*
* Usage:
* node main.cjs [options]
*
* Options:
* --help Show this help message
*/
const fs = require('fs');
const path = require('path');
// Find project root
function findProjectRoot() {
let dir = __dirname;
while (dir !== path.parse(dir).root) {
if (fs.existsSync(path.join(dir, '.claude'))) {
return dir;
}
if (path.basename(dir) === '.claude') {
return path.dirname(dir);
}
dir = path.dirname(dir);
}
return process.cwd();
}
const PROJECT_ROOT = findProjectRoot();
const _CLAUDE_DIR = path.join(PROJECT_ROOT, '.claude');
// Parse command line arguments
const args = process.argv.slice(2);
const options = {};
for (let i = 0; i < args.length; i++) {
if (args[i].startsWith('--')) {
const key = args[i].slice(2);
const value = args[i + 1] && !args[i + 1].startsWith('--') ? args[++i] : true;
options[key] = value;
}
}
/**
* Main execution
*/
function main() {
if (options.help) {
console.log(`
Framework Context - Main Script
Usage:
node main.cjs [options]
Options:
--help Show this help message
`);
process.exit(0);
}
console.log('🔧 Framework Context executing...');
console.warn('WARNING: This skill is currently a scaffold and has no implementation.');
process.exit(1);
}
main();
framework-context Implementation Template
Goal
- Define target outcome and acceptance criteria.
TDD
1. Red 2. Green 3. Refactor
Verification
- lint
- format
- targeted tests