Brief description of what this skill does and provides. Use when [clear trigger condition that indicates this skill should activate]. Keep under 200 words.
**Capability**: Provides comprehensive skill documentation with patterns, examples, and best practices for specific technical scenarios. **When to use**: Activate when encountering specific trigger scenarios like integration challenges, edge cases, or when implementing complex patterns that require proven approaches and common pitfall avoidance.
/plugin marketplace add NickCrew/claude-ctx-plugin/plugin install nickcrew-claude-ctx@NickCrew/claude-ctx-pluginThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Brief overview paragraph explaining what this skill provides, its purpose, and its scope. Include key concepts and what makes this skill valuable.
Provide 5-10 specific scenarios when this skill should be activated:
Brief introduction to foundational concepts needed to understand this skill.
Explanation of first essential concept with simple example:
// Simple, clear example demonstrating concept
// Include comments explaining key points
Key points:
Second essential concept with progression from basic to intermediate:
// Example showing concept application
// Demonstrate best practices
When to use:
Problem: Describe the problem this pattern solves
Solution: Explain the pattern approach
Example:
// Complete, working example
// Well-commented to explain approach
// Include edge cases if relevant
function examplePattern() {
// Implementation details
// Show best practices
}
Pros:
Cons:
When to use: Specific criteria for applying this pattern
Problem: Second problem domain
Solution: Alternative or complementary approach
Example:
// Different approach showing variety
// Demonstrate trade-offs
Comparison: How this pattern differs from Pattern 1
This section provides deeper patterns for complex scenarios. Load only when needed.
Context for when advanced usage is necessary:
// More sophisticated example
// Show integration with multiple concepts
// Demonstrate production-ready code
class AdvancedExample {
// Complete implementation
// Include error handling
// Show performance considerations
}
Considerations:
Handling edge cases and uncommon scenarios:
// Edge case handling
// Defensive programming
// Graceful degradation
// Show how this skill integrates with other systems
// Practical, real-world example
// Different integration scenario
// Demonstrate flexibility
Quick reference for implementing this skill effectively:
Problem: Description of what goes wrong
Why it happens: Explanation of root cause
Solution: How to avoid or fix
// Incorrect approach (anti-pattern)
// badExample();
// Correct approach
// goodExample();
Problem: Second common issue
Solution: Prevention strategy
// Example test cases
// Show test structure
// Demonstrate assertions
describe('Feature', () => {
it('should handle expected case', () => {
// Test implementation
});
it('should handle edge case', () => {
// Edge case testing
});
});
// Integration test example
// Show testing across boundaries
Context: Real-world situation description
Implementation:
// Complete, production-ready example
// Include error handling
// Show configuration
// Demonstrate best practices
class RealWorldExample {
// Full implementation
// Comments explaining decisions
// Edge case handling
}
Results: Outcome and benefits achieved
Context: Alternative use case
Implementation:
// Different approach for different context
Lessons learned: Insights from this implementation
Symptoms: What the user observes
Causes: Typical root causes
Solutions:
Prevention: How to avoid this issue
Symptoms: Observable behavior
Diagnostic steps:
Resolution: How to fix
This skill works well with:
Author commitment: Expected update frequency and maintenance approach
Contribution welcome: Areas where community contributions would be valuable
Known limitations: Current gaps or planned improvements
Deprecation policy: How breaking changes will be handled
This skill is licensed under the MIT License. See LICENSE file for details.
For issues or questions about this skill, please:
community-skill:your-skill-name labelThis skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.