---
name: [descriptive-kebab-case-name]
description: |
  [Precise description, including: (1) What problem is solved (2) Triggering conditions (error message/symptom/scenario)
  (3) Technologies/frameworks involved. Start with "Use when:" to list usage scenarios.
  The quality of description directly determines whether semantic matching can hit this Skill. ]
author: Claude Code
version: 1.0.0
date: YYYY-MM-DD
---

# [Skill name — human readable title]

## Problem

[Problem description: What are the pain points? Why not obvious? 1-2 paragraphs]

## Context / Trigger Conditions

[When should this Skill be activated? List specific conditions:]

- [Exact error message 1]
- [Exact error message 2]
- [observable symptoms or behaviors]
- [Environmental conditions (framework/tools/platform)]

## Solution

[Step-by-step solution, usually 3-5 steps]

### Step 1: [Step 1]

[Detailed description, with code examples (if applicable)]

```language
// sample code
```

### Step 2: [Step 2]

[Continue with clear, actionable steps]

### Step 3: [Step 3]

[Include alternatives or variations if any]

## Verification

[How to confirm that the plan is valid:]

1. [Verification Step 1]
2. [Verification Step 2]
3. [Expected results]

## Example

**Scenario**: [Specific real case]

**Before**：
```
[error message or problem code]
```

**After**：
```
[Fixed code or successful output]
```

## Notes

[Notes, edge cases:]

- [Note 1]
- [When this Skill should not be used]
- [See also: Related Skill names]

## References

- [Source link 1 (if web research available)]
- [Source link 2]
