creador-habilidades

Files (2)

• SKILL.md
• SKILL-TEMPLATE.md · assets/

SKILL.md (first lines)

## Cuando usar

Usa esta skill cuando quieras crear una skill nueva y reutilizable.
- Cuando un patrón se repite y la IA necesita guía paso a paso.
- Cuando las convenciones del proyecto piden instrucciones propias.
- Cuando un flujo complejo se beneficia de un checklist o decision tree.
No la uses para tareas de una sola vez (one-off); resuélvelas directo sin crear skill.

## When to Create a Skill

Create a skill when:

- A pattern is used repeatedly and AI needs guidance
- Project-specific conventions differ from generic best practices
- Complex workflows need step-by-step instructions
- Decision trees help AI choose the right approach

**Don't create a skill when:**

- Documentation already exists (create a reference instead)
- Pattern is trivial or self-explanatory
- It's a one-off task

---

## Skill Structure

```
skills/{skill-name}/
├── SKILL.md              # Required - main skill file
├── assets/               # Optional - templates, schemas, examples
│   ├── template.py
│   └── schema.json
└── references/           # Optional - links to local docs
    └── docs.md           # Points to docs/developer-guide/*.mdx
```

---

## SKILL.md Template

```markdown
---
name: {skill-name}
description: >
  {One-line description of what this skill does}.
  Trigger: {When the AI should load this skill}.
license: Apache-2.0
metadata:
  version: "1.0"
---

## When to Use

{Bullet points of when to use this skill}

## Critical Patterns

{The most important rules - what AI MUST know}

## Code Examples

{Minimal, focused examples}

## Commands

```bash
{Common commands}
```

## Resources

- **Templates**: See [assets/](assets/) for {description}
- **Documentation**: See [references/](references/) for local docs

```

---

## Naming Conventions

| Type | Pattern | Examples |
|------|---------|----------|
| Generic skill | `{technology}` | `pytest`, `playwright`, `typescript` |
| Project-specific | `{project}-{component}` | `api-auth`, `ui-checkout`, `sdk-payments` |
| Testing skill | `test-{component}` | `test-sdk`, `test-api` |
| Workflow skill | `{action}-{target}` | `creador-habilidades`, `jira-task` |

---

## Decision: assets/ vs references/

```

Need code templates?        → assets/
Need JSON schemas?          → assets/
Need example configs?       → assets/
Link to existing docs?      → references/
Link to external guides?    → references/ (with local path)

```

**Key Rule**: `references/` should point to LOCAL files (`docs/developer-guide/*.mdx`), not web URLs.

---

## Decision: Project-Specific vs Generic

```

Patterns apply to ANY project?     → Generic skill (e.g., pytest, typescript)
Patterns are project-specific?     → {project}-{name} skill
Generic skill needs project info?  → Add references/ pointing to project docs

```

---

## Frontmatter Fields

From tontojil/PerfeckCode, Apache-2.0.

More from tontojil/PerfeckCode