@ngxtm/devkit 3.7.0 → 3.9.0

package/merged-commands/context-driven-development.md

@@ -0,0 +1,400 @@
+---
+name: context-driven-development
+description: Use this skill when working with Conductor's context-driven
+  development methodology, managing project context artifacts, or understanding
+  the relationship between product.md, tech-stack.md, and workflow.md files.
+metadata:
+  version: 1.0.0
+---
+
+# Context-Driven Development
+
+Guide for implementing and maintaining context as a managed artifact alongside code, enabling consistent AI interactions and team alignment through structured project documentation.
+
+## Do not use this skill when
+
+- The task is unrelated to context-driven development
+- You need a different domain or tool outside this scope
+
+## Instructions
+
+- Clarify goals, constraints, and required inputs.
+- Apply relevant best practices and validate outcomes.
+- Provide actionable steps and verification.
+- If detailed examples are required, open `resources/implementation-playbook.md`.
+
+## Use this skill when
+
+- Setting up new projects with Conductor
+- Understanding the relationship between context artifacts
+- Maintaining consistency across AI-assisted development sessions
+- Onboarding team members to an existing Conductor project
+- Deciding when to update context documents
+- Managing greenfield vs brownfield project contexts
+
+## Core Philosophy
+
+Context-Driven Development treats project context as a first-class artifact managed alongside code. Instead of relying on ad-hoc prompts or scattered documentation, establish a persistent, structured foundation that informs all AI interactions.
+
+Key principles:
+
+1. **Context precedes code**: Define what you're building and how before implementation
+2. **Living documentation**: Context artifacts evolve with the project
+3. **Single source of truth**: One canonical location for each type of information
+4. **AI alignment**: Consistent context produces consistent AI behavior
+
+## The Workflow
+
+Follow the **Context → Spec & Plan → Implement** workflow:
+
+1. **Context Phase**: Establish or verify project context artifacts exist and are current
+2. **Specification Phase**: Define requirements and acceptance criteria for work units
+3. **Planning Phase**: Break specifications into phased, actionable tasks
+4. **Implementation Phase**: Execute tasks following established workflow patterns
+
+## Artifact Relationships
+
+### product.md - Defines WHAT and WHY
+
+Purpose: Captures product vision, goals, target users, and business context.
+
+Contents:
+
+- Product name and one-line description
+- Problem statement and solution approach
+- Target user personas
+- Core features and capabilities
+- Success metrics and KPIs
+- Product roadmap (high-level)
+
+Update when:
+
+- Product vision or goals change
+- New major features are planned
+- Target audience shifts
+- Business priorities evolve
+
+### product-guidelines.md - Defines HOW to Communicate
+
+Purpose: Establishes brand voice, messaging standards, and communication patterns.
+
+Contents:
+
+- Brand voice and tone guidelines
+- Terminology and glossary
+- Error message conventions
+- User-facing copy standards
+- Documentation style
+
+Update when:
+
+- Brand guidelines change
+- New terminology is introduced
+- Communication patterns need refinement
+
+### tech-stack.md - Defines WITH WHAT
+
+Purpose: Documents technology choices, dependencies, and architectural decisions.
+
+Contents:
+
+- Primary languages and frameworks
+- Key dependencies with versions
+- Infrastructure and deployment targets
+- Development tools and environment
+- Testing frameworks
+- Code quality tools
+
+Update when:
+
+- Adding new dependencies
+- Upgrading major versions
+- Changing infrastructure
+- Adopting new tools or patterns
+
+### workflow.md - Defines HOW to Work
+
+Purpose: Establishes development practices, quality gates, and team workflows.
+
+Contents:
+
+- Development methodology (TDD, etc.)
+- Git workflow and commit conventions
+- Code review requirements
+- Testing requirements and coverage targets
+- Quality assurance gates
+- Deployment procedures
+
+Update when:
+
+- Team practices evolve
+- Quality standards change
+- New workflow patterns are adopted
+
+### tracks.md - Tracks WHAT'S HAPPENING
+
+Purpose: Registry of all work units with status and metadata.
+
+Contents:
+
+- Active tracks with current status
+- Completed tracks with completion dates
+- Track metadata (type, priority, assignee)
+- Links to individual track directories
+
+Update when:
+
+- New tracks are created
+- Track status changes
+- Tracks are completed or archived
+
+## Context Maintenance Principles
+
+### Keep Artifacts Synchronized
+
+Ensure changes in one artifact reflect in related documents:
+
+- New feature in product.md → Update tech-stack.md if new dependencies needed
+- Completed track → Update product.md to reflect new capabilities
+- Workflow change → Update all affected track plans
+
+### Update tech-stack.md When Adding Dependencies
+
+Before adding any new dependency:
+
+1. Check if existing dependencies solve the need
+2. Document the rationale for new dependencies
+3. Add version constraints
+4. Note any configuration requirements
+
+### Update product.md When Features Complete
+
+After completing a feature track:
+
+1. Move feature from "planned" to "implemented" in product.md
+2. Update any affected success metrics
+3. Document any scope changes from original plan
+
+### Verify Context Before Implementation
+
+Before starting any track:
+
+1. Read all context artifacts
+2. Flag any outdated information
+3. Propose updates before proceeding
+4. Confirm context accuracy with stakeholders
+
+## Greenfield vs Brownfield Handling
+
+### Greenfield Projects (New)
+
+For new projects:
+
+1. Run `/conductor:setup` to create all artifacts interactively
+2. Answer questions about product vision, tech preferences, and workflow
+3. Generate initial style guides for chosen languages
+4. Create empty tracks registry
+
+Characteristics:
+
+- Full control over context structure
+- Define standards before code exists
+- Establish patterns early
+
+### Brownfield Projects (Existing)
+
+For existing codebases:
+
+1. Run `/conductor:setup` with existing codebase detection
+2. System analyzes existing code, configs, and documentation
+3. Pre-populate artifacts based on discovered patterns
+4. Review and refine generated context
+
+Characteristics:
+
+- Extract implicit context from existing code
+- Reconcile existing patterns with desired patterns
+- Document technical debt and modernization plans
+- Preserve working patterns while establishing standards
+
+## Benefits
+
+### Team Alignment
+
+- New team members onboard faster with explicit context
+- Consistent terminology and conventions across the team
+- Shared understanding of product goals and technical decisions
+
+### AI Consistency
+
+- AI assistants produce aligned outputs across sessions
+- Reduced need to re-explain context in each interaction
+- Predictable behavior based on documented standards
+
+### Institutional Memory
+
+- Decisions and rationale are preserved
+- Context survives team changes
+- Historical context informs future decisions
+
+### Quality Assurance
+
+- Standards are explicit and verifiable
+- Deviations from context are detectable
+- Quality gates are documented and enforceable
+
+## Directory Structure
+
+```
+conductor/
+├── index.md              # Navigation hub linking all artifacts
+├── product.md            # Product vision and goals
+├── product-guidelines.md # Communication standards
+├── tech-stack.md         # Technology preferences
+├── workflow.md           # Development practices
+├── tracks.md             # Work unit registry
+├── setup_state.json      # Resumable setup state
+├── code_styleguides/     # Language-specific conventions
+│   ├── python.md
+│   ├── typescript.md
+│   └── ...
+└── tracks/
+    └── <track-id>/
+        ├── spec.md
+        ├── plan.md
+        ├── metadata.json
+        └── index.md
+```
+
+## Context Lifecycle
+
+1. **Creation**: Initial setup via `/conductor:setup`
+2. **Validation**: Verify before each track
+3. **Evolution**: Update as project grows
+4. **Synchronization**: Keep artifacts aligned
+5. **Archival**: Document historical decisions
+
+## Context Validation Checklist
+
+Before starting implementation on any track, validate context:
+
+### Product Context
+
+- [ ] product.md reflects current product vision
+- [ ] Target users are accurately described
+- [ ] Feature list is up to date
+- [ ] Success metrics are defined
+
+### Technical Context
+
+- [ ] tech-stack.md lists all current dependencies
+- [ ] Version numbers are accurate
+- [ ] Infrastructure targets are correct
+- [ ] Development tools are documented
+
+### Workflow Context
+
+- [ ] workflow.md describes current practices
+- [ ] Quality gates are defined
+- [ ] Coverage targets are specified
+- [ ] Commit conventions are documented
+
+### Track Context
+
+- [ ] tracks.md shows all active work
+- [ ] No stale or abandoned tracks
+- [ ] Dependencies between tracks are noted
+
+## Common Anti-Patterns
+
+Avoid these context management mistakes:
+
+### Stale Context
+
+Problem: Context documents become outdated and misleading.
+Solution: Update context as part of each track's completion process.
+
+### Context Sprawl
+
+Problem: Information scattered across multiple locations.
+Solution: Use the defined artifact structure; resist creating new document types.
+
+### Implicit Context
+
+Problem: Relying on knowledge not captured in artifacts.
+Solution: If you reference something repeatedly, add it to the appropriate artifact.
+
+### Context Hoarding
+
+Problem: One person maintains context without team input.
+Solution: Review context artifacts in pull requests; make updates collaborative.
+
+### Over-Specification
+
+Problem: Context becomes so detailed it's impossible to maintain.
+Solution: Keep artifacts focused on decisions that affect AI behavior and team alignment.
+
+## Integration with Development Tools
+
+### IDE Integration
+
+Configure your IDE to display context files prominently:
+
+- Pin conductor/product.md for quick reference
+- Add tech-stack.md to project notes
+- Create snippets for common patterns from style guides
+
+### Git Hooks
+
+Consider pre-commit hooks that:
+
+- Warn when dependencies change without tech-stack.md update
+- Remind to update product.md when feature branches merge
+- Validate context artifact syntax
+
+### CI/CD Integration
+
+Include context validation in pipelines:
+
+- Check tech-stack.md matches actual dependencies
+- Verify links in context documents resolve
+- Ensure tracks.md status matches git branch state
+
+## Session Continuity
+
+Conductor supports multi-session development through context persistence:
+
+### Starting a New Session
+
+1. Read index.md to orient yourself
+2. Check tracks.md for active work
+3. Review relevant track's plan.md for current task
+4. Verify context artifacts are current
+
+### Ending a Session
+
+1. Update plan.md with current progress
+2. Note any blockers or decisions made
+3. Commit in-progress work with clear status
+4. Update tracks.md if status changed
+
+### Handling Interruptions
+
+If interrupted mid-task:
+
+1. Mark task as `[~]` with note about stopping point
+2. Commit work-in-progress to feature branch
+3. Document any uncommitted decisions in plan.md
+
+## Best Practices
+
+1. **Read context first**: Always read relevant artifacts before starting work
+2. **Small updates**: Make incremental context changes, not massive rewrites
+3. **Link decisions**: Reference context when making implementation choices
+4. **Version context**: Commit context changes alongside code changes
+5. **Review context**: Include context artifact reviews in code reviews
+6. **Validate regularly**: Run context validation checklist before major work
+7. **Communicate changes**: Notify team when context artifacts change significantly
+8. **Preserve history**: Use git to track context evolution over time
+9. **Question staleness**: If context feels wrong, investigate and update
+10. **Keep it actionable**: Every context item should inform a decision or behavior

package/merged-commands/context-engineering.md

@@ -0,0 +1,107 @@
+---
+name: context-engineering
+description: >-
+  Check context usage limits, monitor time remaining, optimize token consumption, debug context failures.
+  Use when asking about context percentage, rate limits, usage warnings, context optimization, agent architectures, memory systems.
+version: 1.0.0
+---
+
+# Context Engineering
+
+Context engineering curates the smallest high-signal token set for LLM tasks. The goal: maximize reasoning quality while minimizing token usage.
+
+## When to Activate
+
+- Designing/debugging agent systems
+- Context limits constrain performance
+- Optimizing cost/latency
+- Building multi-agent coordination
+- Implementing memory systems
+- Evaluating agent performance
+- Developing LLM-powered pipelines
+
+## Core Principles
+
+1. **Context quality > quantity** - High-signal tokens beat exhaustive content
+2. **Attention is finite** - U-shaped curve favors beginning/end positions
+3. **Progressive disclosure** - Load information just-in-time
+4. **Isolation prevents degradation** - Partition work across sub-agents
+5. **Measure before optimizing** - Know your baseline
+
+**IMPORTANT:**
+- Sacrifice grammar for the sake of concision.
+- Ensure token efficiency while maintaining high quality.
+- Pass these rules to subagents.
+
+## Quick Reference
+
+| Topic | When to Use | Reference |
+|-------|-------------|-----------|
+| **Fundamentals** | Understanding context anatomy, attention mechanics | [context-fundamentals.md](./references/context-fundamentals.md) |
+| **Degradation** | Debugging failures, lost-in-middle, poisoning | [context-degradation.md](./references/context-degradation.md) |
+| **Optimization** | Compaction, masking, caching, partitioning | [context-optimization.md](./references/context-optimization.md) |
+| **Compression** | Long sessions, summarization strategies | [context-compression.md](./references/context-compression.md) |
+| **Memory** | Cross-session persistence, knowledge graphs | [memory-systems.md](./references/memory-systems.md) |
+| **Multi-Agent** | Coordination patterns, context isolation | [multi-agent-patterns.md](./references/multi-agent-patterns.md) |
+| **Evaluation** | Testing agents, LLM-as-Judge, metrics | [evaluation.md](./references/evaluation.md) |
+| **Tool Design** | Tool consolidation, description engineering | [tool-design.md](./references/tool-design.md) |
+| **Pipelines** | Project development, batch processing | [project-development.md](./references/project-development.md) |
+| **Runtime Awareness** | Usage limits, context window monitoring | [runtime-awareness.md](./references/runtime-awareness.md) |
+
+## Key Metrics
+
+- **Token utilization**: Warning at 70%, trigger optimization at 80%
+- **Token variance**: Explains 80% of agent performance variance
+- **Multi-agent cost**: ~15x single agent baseline
+- **Compaction target**: 50-70% reduction, <5% quality loss
+- **Cache hit target**: 70%+ for stable workloads
+
+## Four-Bucket Strategy
+
+1. **Write**: Save context externally (scratchpads, files)
+2. **Select**: Pull only relevant context (retrieval, filtering)
+3. **Compress**: Reduce tokens while preserving info (summarization)
+4. **Isolate**: Split across sub-agents (partitioning)
+
+## Anti-Patterns
+
+- Exhaustive context over curated context
+- Critical info in middle positions
+- No compaction triggers before limits
+- Single agent for parallelizable tasks
+- Tools without clear descriptions
+
+## Guidelines
+
+1. Place critical info at beginning/end of context
+2. Implement compaction at 70-80% utilization
+3. Use sub-agents for context isolation, not role-play
+4. Design tools with 4-question framework (what, when, inputs, returns)
+5. Optimize for tokens-per-task, not tokens-per-request
+6. Validate with probe-based evaluation
+7. Monitor KV-cache hit rates in production
+8. Start minimal, add complexity only when proven necessary
+
+## Runtime Awareness
+
+The system automatically injects usage awareness via PostToolUse hook:
+
+```xml
+<usage-awareness>
+Claude Usage Limits: 5h=45%, 7d=32%
+Context Window Usage: 67%
+</usage-awareness>
+```
+
+**Thresholds:**
+- 70%: WARNING - consider optimization/compaction
+- 90%: CRITICAL - immediate action needed
+
+**Data Sources:**
+- Usage limits: Anthropic OAuth API (`https://api.anthropic.com/api/oauth/usage`)
+- Context window: Statusline temp file (`/tmp/ck-context-{session_id}.json`)
+
+## Scripts
+
+- [context_analyzer.py](./scripts/context_analyzer.py) - Context health analysis, degradation detection
+- [compression_evaluator.py](./scripts/compression_evaluator.py) - Compression quality evaluation

package/merged-commands/context-fundamentals.md

@@ -0,0 +1,192 @@
+---
+name: context-fundamentals
+description: "Understand what context is, why it matters, and the anatomy of context in agent systems"
+source: "https://github.com/muratcankoylan/Agent-Skills-for-Context-Engineering/tree/main/skills/context-fundamentals"
+risk: safe
+---
+
+## When to Use This Skill
+
+Understand what context is, why it matters, and the anatomy of context in agent systems
+
+Use this skill when working with understand what context is, why it matters, and the anatomy of context in agent systems.
+# Context Engineering Fundamentals
+
+Context is the complete state available to a language model at inference time. It includes everything the model can attend to when generating responses: system instructions, tool definitions, retrieved documents, message history, and tool outputs. Understanding context fundamentals is prerequisite to effective context engineering.
+
+## When to Activate
+
+Activate this skill when:
+- Designing new agent systems or modifying existing architectures
+- Debugging unexpected agent behavior that may relate to context
+- Optimizing context usage to reduce token costs or improve performance
+- Onboarding new team members to context engineering concepts
+- Reviewing context-related design decisions
+
+## Core Concepts
+
+Context comprises several distinct components, each with different characteristics and constraints. The attention mechanism creates a finite budget that constrains effective context usage. Progressive disclosure manages this constraint by loading information only as needed. The engineering discipline is curating the smallest high-signal token set that achieves desired outcomes.
+
+## Detailed Topics
+
+### The Anatomy of Context
+
+**System Prompts**
+System prompts establish the agent's core identity, constraints, and behavioral guidelines. They are loaded once at session start and typically persist throughout the conversation. System prompts should be extremely clear and use simple, direct language at the right altitude for the agent.
+
+The right altitude balances two failure modes. At one extreme, engineers hardcode complex brittle logic that creates fragility and maintenance burden. At the other extreme, engineers provide vague high-level guidance that fails to give concrete signals for desired outputs or falsely assumes shared context. The optimal altitude strikes a balance: specific enough to guide behavior effectively, yet flexible enough to provide strong heuristics.
+
+Organize prompts into distinct sections using XML tagging or Markdown headers to delineate background information, instructions, tool guidance, and output description. The exact formatting matters less as models become more capable, but structural clarity remains valuable.
+
+**Tool Definitions**
+Tool definitions specify the actions an agent can take. Each tool includes a name, description, parameters, and return format. Tool definitions live near the front of context after serialization, typically before or after the system prompt.
+
+Tool descriptions collectively steer agent behavior. Poor descriptions force agents to guess; optimized descriptions include usage context, examples, and defaults. The consolidation principle states that if a human engineer cannot definitively say which tool should be used in a given situation, an agent cannot be expected to do better.
+
+**Retrieved Documents**
+Retrieved documents provide domain-specific knowledge, reference materials, or task-relevant information. Agents use retrieval augmented generation to pull relevant documents into context at runtime rather than pre-loading all possible information.
+
+The just-in-time approach maintains lightweight identifiers (file paths, stored queries, web links) and uses these references to load data into context dynamically. This mirrors human cognition: we generally do not memorize entire corpuses of information but rather use external organization and indexing systems to retrieve relevant information on demand.
+
+**Message History**
+Message history contains the conversation between the user and agent, including previous queries, responses, and reasoning. For long-running tasks, message history can grow to dominate context usage.
+
+Message history serves as scratchpad memory where agents track progress, maintain task state, and preserve reasoning across turns. Effective management of message history is critical for long-horizon task completion.
+
+**Tool Outputs**
+Tool outputs are the results of agent actions: file contents, search results, command execution output, API responses, and similar data. Tool outputs comprise the majority of tokens in typical agent trajectories, with research showing observations (tool outputs) can reach 83.9% of total context usage.
+
+Tool outputs consume context whether they are relevant to current decisions or not. This creates pressure for strategies like observation masking, compaction, and selective tool result retention.
+
+### Context Windows and Attention Mechanics
+
+**The Attention Budget Constraint**
+Language models process tokens through attention mechanisms that create pairwise relationships between all tokens in context. For n tokens, this creates n² relationships that must be computed and stored. As context length increases, the model's ability to capture these relationships gets stretched thin.
+
+Models develop attention patterns from training data distributions where shorter sequences predominate. This means models have less experience with and fewer specialized parameters for context-wide dependencies. The result is an "attention budget" that depletes as context grows.
+
+**Position Encoding and Context Extension**
+Position encoding interpolation allows models to handle longer sequences by adapting them to originally trained smaller contexts. However, this adaptation introduces degradation in token position understanding. Models remain highly capable at longer contexts but show reduced precision for information retrieval and long-range reasoning compared to performance on shorter contexts.
+
+**The Progressive Disclosure Principle**
+Progressive disclosure manages context efficiently by loading information only as needed. At startup, agents load only skill names and descriptions—sufficient to know when a skill might be relevant. Full content loads only when a skill is activated for specific tasks.
+
+This approach keeps agents fast while giving them access to more context on demand. The principle applies at multiple levels: skill selection, document loading, and even tool result retrieval.
+
+### Context Quality Versus Context Quantity
+
+The assumption that larger context windows solve memory problems has been empirically debunked. Context engineering means finding the smallest possible set of high-signal tokens that maximize the likelihood of desired outcomes.
+
+Several factors create pressure for context efficiency. Processing cost grows disproportionately with context length—not just double the cost for double the tokens, but exponentially more in time and computing resources. Model performance degrades beyond certain context lengths even when the window technically supports more tokens. Long inputs remain expensive even with prefix caching.
+
+The guiding principle is informativity over exhaustiveness. Include what matters for the decision at hand, exclude what does not, and design systems that can access additional information on demand.
+
+### Context as Finite Resource
+
+Context must be treated as a finite resource with diminishing marginal returns. Like humans with limited working memory, language models have an attention budget drawn on when parsing large volumes of context.
+
+Every new token introduced depletes this budget by some amount. This creates the need for careful curation of available tokens. The engineering problem is optimizing utility against inherent constraints.
+
+Context engineering is iterative and the curation phase happens each time you decide what to pass to the model. It is not a one-time prompt writing exercise but an ongoing discipline of context management.
+
+## Practical Guidance
+
+### File-System-Based Access
+
+Agents with filesystem access can use progressive disclosure naturally. Store reference materials, documentation, and data externally. Load files only when needed using standard filesystem operations. This pattern avoids stuffing context with information that may not be relevant.
+
+The file system itself provides structure that agents can navigate. File sizes suggest complexity; naming conventions hint at purpose; timestamps serve as proxies for relevance. Metadata of file references provides a mechanism to efficiently refine behavior.
+
+### Hybrid Strategies
+
+The most effective agents employ hybrid strategies. Pre-load some context for speed (like CLAUDE.md files or project rules), but enable autonomous exploration for additional context as needed. The decision boundary depends on task characteristics and context dynamics.
+
+For contexts with less dynamic content, pre-loading more upfront makes sense. For rapidly changing or highly specific information, just-in-time loading avoids stale context.
+
+### Context Budgeting
+
+Design with explicit context budgets in mind. Know the effective context limit for your model and task. Monitor context usage during development. Implement compaction triggers at appropriate thresholds. Design systems assuming context will degrade rather than hoping it will not.
+
+Effective context budgeting requires understanding not just raw token counts but also attention distribution patterns. The middle of context receives less attention than the beginning and end. Place critical information at attention-favored positions.
+
+## Examples
+
+**Example 1: Organizing System Prompts**
+```markdown
+<BACKGROUND_INFORMATION>
+You are a Python expert helping a development team.
+Current project: Data processing pipeline in Python 3.9+
+</BACKGROUND_INFORMATION>
+
+<INSTRUCTIONS>
+- Write clean, idiomatic Python code
+- Include type hints for function signatures
+- Add docstrings for public functions
+- Follow PEP 8 style guidelines
+</INSTRUCTIONS>
+
+<TOOL_GUIDANCE>
+Use bash for shell operations, python for code tasks.
+File operations should use pathlib for cross-platform compatibility.
+</TOOL_GUIDANCE>
+
+<OUTPUT_DESCRIPTION>
+Provide code blocks with syntax highlighting.
+Explain non-obvious decisions in comments.
+</OUTPUT_DESCRIPTION>
+```
+
+**Example 2: Progressive Document Loading**
+```markdown
+# Instead of loading all documentation at once:
+
+# Step 1: Load summary
+docs/api_summary.md          # Lightweight overview
+
+# Step 2: Load specific section as needed
+docs/api/endpoints.md        # Only when API calls needed
+docs/api/authentication.md   # Only when auth context needed
+```
+
+## Guidelines
+
+1. Treat context as a finite resource with diminishing returns
+2. Place critical information at attention-favored positions (beginning and end)
+3. Use progressive disclosure to defer loading until needed
+4. Organize system prompts with clear section boundaries
+5. Monitor context usage during development
+6. Implement compaction triggers at 70-80% utilization
+7. Design for context degradation rather than hoping to avoid it
+8. Prefer smaller high-signal context over larger low-signal context
+
+## Integration
+
+This skill provides foundational context that all other skills build upon. It should be studied first before exploring:
+
+- context-degradation - Understanding how context fails
+- context-optimization - Techniques for extending context capacity
+- multi-agent-patterns - How context isolation enables multi-agent systems
+- tool-design - How tool definitions interact with context
+
+## References
+
+Internal reference:
+- [Context Components Reference](./references/context-components.md) - Detailed technical reference
+
+Related skills in this collection:
+- context-degradation - Understanding context failure patterns
+- context-optimization - Techniques for efficient context use
+
+External resources:
+- Research on transformer attention mechanisms
+- Production engineering guides from leading AI labs
+- Framework documentation on context window management
+
+---
+
+## Skill Metadata
+
+**Created**: 2025-12-20
+**Last Updated**: 2025-12-20
+**Author**: Agent Skills for Context Engineering Contributors
+**Version**: 1.0.0