---
description: Short and objective description of what the skill does and when to use it (appears in menus). This description is used by the agent to decide when to apply the skill.
name: Readable Skill Name (optional - if omitted, uses folder name)
---

# Skill Title

Detailed instructions for the agent on how to use this skill.

## When to Use

- Use this skill when...
- This skill is useful for...
- Apply in situations where...

## Step-by-Step Instructions

1. First do this...
2. Then do that...
3. Finish with...

## Conventions and Best Practices

- Always do X
- Never do Y
- Prefer Z when...

## Examples (optional)

### Example 1: Example Title

Input:

Expected output:

## Important Notes

- Important note 1
- Important note 2

[Specific action] + [in which context] + [following which criteria/patterns]

Is task single-purpose and instant?
├─ YES → Is it a custom command?
│         ├─ YES → Use slash command
│         └─ NO → Use skill
│
└─ NO → Does it require multiple steps and isolated context?
          ├─ YES → Use subagent
          └─ NO → Use skill

---
description: [Specific action] for [context] following [pattern/criteria]
---

# [Skill Name]

You are an expert in [specific domain].

## When to Use

Use this skill when:

- [Trigger 1]
- [Trigger 2]
- [Trigger 3]

## Process

1. [Step 1]
2. [Step 2]
3. [Step 3]

## Criteria and Conventions

- [Rule 1]
- [Rule 2]
- [Rule 3]

## Output Format (if applicable)

[Describe the expected output format]

---
description: Organizes and formats JavaScript/TypeScript imports in alphabetical order, groups by type (external, internal, types) and removes duplicates.
---

# Import Formatter

## When to Use

- When finishing a file with disorganized imports
- When asked to "organize imports"
- Before commits to maintain consistency

## Process

1. Identify all import statements
2. Classify into groups:
   - External (node_modules)
   - Internal (relative paths and aliases)
   - Types (import type)
3. Sort alphabetically within each group
4. Remove duplicates
5. Add blank line between groups

## Expected Format

```typescript
// External
import { useState } from "react";
import axios from "axios";

// Internal
import { Button } from "@/components/Button";
import { utils } from "../utils";

// Types
import type { User } from "@/types";
```

### Example 2: Changelog Generator

```markdown
---
description: Generates formatted changelog based on Git commits since last tag, categorizing by type (feat, fix, docs, etc.) following Conventional Commits.
---

# Changelog Generator

## When to Use

- When preparing a release
- When asked to "generate changelog"
- To document changes between versions

## Process

1. Fetch commits since last git tag
2. Parse messages following Conventional Commits
3. Categorize by type:
   - ✨ Features (feat:)
   - 🐛 Fixes (fix:)
   - 📚 Docs (docs:)
   - 🔧 Chore (chore:)
   - ♻️ Refactor (refactor:)
4. Format in markdown with bullet points
5. Include breaking changes in separate section

## Output Format

```markdown
## [Version] - [Date]

### ✨ Features
- feat(auth): add OAuth login
- feat(api): endpoint for file upload

### 🐛 Fixes
- fix(ui): fix responsive menu
- fix(db): resolve race condition in transactions

### 📚 Documentation
- docs: update README with new endpoints

### ⚠️ BREAKING CHANGES
- feat(api)!: remove endpoint /v1/legacy

## Creation Outputs

When creating a skill, you should:

1. **Create the directory**: `.cursor/skills/[skill-name]/`
2. **Create the file**: `SKILL.md` inside the directory
3. **Confirm location**: Inform where the skill was created
4. **Explain usage**: How to test/use the skill
5. **Suggest improvements**: If relevant, suggest refinements

## Quality Checklist

Before finalizing a skill, verify:

- [ ] Description is specific and clear about when to use
- [ ] Folder name uses kebab-case
- [ ] Instructions are actionable and unambiguous
- [ ] Scope is focused (one responsibility)
- [ ] Concrete examples are included (if applicable)
- [ ] Sections are well organized
- [ ] It's not a complex task (that should be a subagent)
- [ ] Output format is clear (if applicable)

## Output Messages

When creating a skill, inform the user:

---

## Remember

Skills are for **reusable knowledge and one-off actions**. For complex tasks with multiple steps, delegation, and isolated context, use **subagents** instead of skills.