your-skill-name

Brief description of what this skill does and provides. Use when [clear trigger condition that indicates this skill should activate]. Keep under 200 words.

13 stars

Best use case

your-skill-name is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Brief description of what this skill does and provides. Use when [clear trigger condition that indicates this skill should activate]. Keep under 200 words.

Teams using your-skill-name should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/.template/SKILL.md --create-dirs "https://raw.githubusercontent.com/NickCrew/Claude-Cortex/main/skills/community/.template/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/.template/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How your-skill-name Compares

Feature / Agentyour-skill-nameStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Brief description of what this skill does and provides. Use when [clear trigger condition that indicates this skill should activate]. Keep under 200 words.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Skill Title

Brief overview paragraph explaining what this skill provides, its purpose, and its scope. Include key concepts and what makes this skill valuable.

## When to Use This Skill

Provide 5-10 specific scenarios when this skill should be activated:

- Scenario 1: Specific use case with clear trigger
- Scenario 2: Another distinct situation
- Scenario 3: Related but different context
- Scenario 4: Edge case or advanced usage
- Scenario 5: Integration with other tools/frameworks

## Core Concepts

Brief introduction to foundational concepts needed to understand this skill.

### Concept 1: Foundation

Explanation of first essential concept with simple example:

```language
// Simple, clear example demonstrating concept
// Include comments explaining key points
```

**Key points:**
- Important aspect 1
- Important aspect 2
- Important aspect 3

### Concept 2: Building Blocks

Second essential concept with progression from basic to intermediate:

```language
// Example showing concept application
// Demonstrate best practices
```

**When to use:**
- Use case 1
- Use case 2
- Use case 3

## Common Patterns

### Pattern 1: [Pattern Name]

**Problem**: Describe the problem this pattern solves

**Solution**: Explain the pattern approach

**Example**:
```language
// Complete, working example
// Well-commented to explain approach
// Include edge cases if relevant

function examplePattern() {
  // Implementation details
  // Show best practices
}
```

**Pros:**
- Advantage 1
- Advantage 2
- Advantage 3

**Cons:**
- Limitation 1
- Limitation 2

**When to use**: Specific criteria for applying this pattern

### Pattern 2: [Pattern Name]

**Problem**: Second problem domain

**Solution**: Alternative or complementary approach

**Example**:
```language
// Different approach showing variety
// Demonstrate trade-offs
```

**Comparison**: How this pattern differs from Pattern 1

## Advanced Usage

This section provides deeper patterns for complex scenarios. Load only when needed.

### Advanced Pattern 1: [Complex Scenario]

Context for when advanced usage is necessary:

```language
// More sophisticated example
// Show integration with multiple concepts
// Demonstrate production-ready code

class AdvancedExample {
  // Complete implementation
  // Include error handling
  // Show performance considerations
}
```

**Considerations:**
- Performance impact
- Scalability concerns
- Security implications
- Maintenance burden

### Advanced Pattern 2: [Edge Cases]

Handling edge cases and uncommon scenarios:

```language
// Edge case handling
// Defensive programming
// Graceful degradation
```

## Integration Examples

### Integrating with [Related Technology 1]

```language
// Show how this skill integrates with other systems
// Practical, real-world example
```

### Integrating with [Related Technology 2]

```language
// Different integration scenario
// Demonstrate flexibility
```

## Best Practices Summary

Quick reference for implementing this skill effectively:

### Do's
- Do this for best results
- Always consider this aspect
- Prefer this approach when possible
- Validate this condition before proceeding
- Document this information for maintainability

### Don'ts
- Avoid this anti-pattern
- Don't forget this critical step
- Never do this in production
- Don't overlook this edge case
- Avoid this common mistake

### Performance Tips
- Optimization technique 1
- Optimization technique 2
- Caching strategy
- Resource management

### Security Considerations
- Security practice 1
- Security practice 2
- Input validation requirements
- Authentication/authorization concerns

## Common Pitfalls

### Pitfall 1: [Common Mistake]

**Problem**: Description of what goes wrong

**Why it happens**: Explanation of root cause

**Solution**: How to avoid or fix

```language
// Incorrect approach (anti-pattern)
// badExample();

// Correct approach
// goodExample();
```

### Pitfall 2: [Another Mistake]

**Problem**: Second common issue

**Solution**: Prevention strategy

## Testing Strategies

### Unit Testing

```language
// 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 Testing

```language
// Integration test example
// Show testing across boundaries
```

## Real-World Examples

### Example 1: [Practical Scenario]

**Context**: Real-world situation description

**Implementation**:
```language
// 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

### Example 2: [Different Scenario]

**Context**: Alternative use case

**Implementation**:
```language
// Different approach for different context
```

**Lessons learned**: Insights from this implementation

## Troubleshooting

### Issue 1: [Common Problem]

**Symptoms**: What the user observes

**Causes**: Typical root causes

**Solutions**:
1. First attempt solution
2. Alternative approach
3. Last resort option

**Prevention**: How to avoid this issue

### Issue 2: [Another Problem]

**Symptoms**: Observable behavior

**Diagnostic steps**:
1. Check this first
2. Verify this condition
3. Investigate this aspect

**Resolution**: How to fix

## Tools and Resources

### Recommended Tools
- **Tool 1**: What it does and when to use
- **Tool 2**: Alternative tool and trade-offs
- **Tool 3**: Complementary tool

### Libraries and Frameworks
- **Library 1**: Purpose and integration approach
- **Library 2**: Alternative library comparison

### Documentation Links
- [Official Documentation](https://example.com/docs)
- [API Reference](https://example.com/api)
- [Community Resources](https://example.com/community)

### Further Reading
- Article/book: Brief description
- Tutorial: What it covers
- Video course: Key takeaways

## Version History

- **1.0.0** (2024-10-17): Initial release
  - Core patterns implemented
  - Examples validated
  - Best practices documented

## Related Skills

This skill works well with:
- **related-skill-1**: How they complement each other
- **related-skill-2**: When to use together
- **related-skill-3**: Integration points

## Maintenance Notes

**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

## License

This skill is licensed under the MIT License. See LICENSE file for details.

## Author Contact

- **Name**: Your Name
- **Email**: your.email@example.com
- **GitHub**: [@yourusername](https://github.com/yourusername)
- **Website**: https://yourwebsite.com (optional)

For issues or questions about this skill, please:
1. Check documentation above
2. Search existing GitHub issues
3. Open new issue with `community-skill:your-skill-name` label
4. Contact author directly for urgent matters

Related Skills

writing-skills

13
from NickCrew/Claude-Cortex

Use when creating new skills, editing existing skills, or verifying skills work before deployment - applies TDD to process documentation by testing with subagents before writing, iterating until bulletproof against rationalization

workflow-security-audit

13
from NickCrew/Claude-Cortex

Comprehensive security assessment and remediation. Use for security reviews, compliance checks, vulnerability assessments.

workflow-performance

13
from NickCrew/Claude-Cortex

Systematic performance analysis and optimization. Use when things are slow, need optimization, or preparing for scale.

workflow-feature

13
from NickCrew/Claude-Cortex

Complete feature development workflow from design to deployment. Use when implementing new features or functionality.

workflow-feature-development

13
from NickCrew/Claude-Cortex

Complete workflow for developing new features from design to deployment. Use when starting a new feature, adding functionality, or building something new.

workflow-bug-fix

13
from NickCrew/Claude-Cortex

Systematic approach to identifying, fixing, and validating bug fixes. Use when fixing bugs, resolving issues, or addressing errors.

wiring-audit

13
from NickCrew/Claude-Cortex

User-triggered audit that finds wiring drift between a project's UI surfaces and backend capabilities — orphan surfaces (UI calls endpoints/hooks/procedures that no longer exist), unwired capabilities (backend routes/exports that nothing surfaces), shape drift (both exist but contracts mismatch), method drift (URL matches, HTTP verb does not), validation drift (frontend vs backend rules diverged), permission drift (UI exposes what backend forbids or vice versa), stale labels (UI text references renamed backend concepts), and unsurfaced configuration (env vars or flags that gate behavior with no UI or CLI to control them). This skill should be used when the user asks to "audit our wiring," "find UI/backend drift," "find unwired capabilities," "find stale surfaces," "check for contract violations," "find unused endpoints," "find unused hooks," "what mismatches between UI and backend," or any similar request whose deliverable is a prioritized findings report rather than a descriptive snapshot. Generic across UI frameworks but optimized for React applications (hooks, fetch, react-query, SWR, tRPC, server actions, react-router, Next.js). Not for descriptive architectural snapshots (use architectural-analysis), security audits (use security-auditor), or performance audits (use workflow-performance).

webapp-testing

13
from NickCrew/Claude-Cortex

Toolkit for interacting with and testing local web applications using Playwright. Use when verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

web-researcher

13
from NickCrew/Claude-Cortex

Use this skill when you need to research a topic online, gather information from multiple sources, or evaluate source credibility. Trigger phrases: 'research', 'find information about', 'look up', 'investigate'. Not for academic systematic reviews (use literature-reviewer) or fact-checking specific claims (use fact-checker).

visual-modes

13
from NickCrew/Claude-Cortex

Use when activating visual showcase modes (supersaiyan, kamehameha, over9000) for UI or interaction design - provides mode-specific enhancement checklists.

vibe-security

13
from NickCrew/Claude-Cortex

Comprehensive secure coding guide covering OWASP web vulnerabilities with prevention patterns and checklists. Use when writing or reviewing web application code to prevent XSS, CSRF, SSRF, SQL injection, access control flaws, and other common security vulnerabilities.

verification-before-completion

13
from NickCrew/Claude-Cortex

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always