cc-plugin-extensions

# Plugin Extension Pattern

Extend marketplace plugins with project-specific context using `.local.md` files. These files bridge general plugin skills to a specific codebase.

## When to Use This Skill

Apply this skill when:
- Installing a marketplace plugin in a project
- A plugin skill is generic but project-specific guidance is needed
- Documenting project-specific file paths, conventions, or workflows that relate to a plugin
- Setting up a new project that uses existing plugins

### Key Distinction
`.local.md` files are **agent context** (for Claude), not human documentation (like READMEs or guides). Treat them like CLAUDE.md in purpose.

## The Pattern

### File Location and Naming

```
.claude/<plugin-name>.local.md
```

Examples:
- `.claude/cc-governance-skills.local.md`
- `.claude/fvtt-skills.local.md`

### Structure

```markdown
---
plugin: <plugin-name>
project: <project-name>
---

# <Plugin Name> - Project-Specific Context

This file extends the `<plugin-name>` plugin with <project>-specific information.

## <Section relevant to plugin's skills>

<Project-specific details>
```

### YAML Frontmatter

| Field | Purpose |
|-------|---------|
| `plugin` | Name of the marketplace plugin being extended |
| `project` | Name of the current project |

## What Belongs in Extension Files

### DO Include

1. **File paths** - Where plugin patterns are implemented in this project
   ```markdown
   | Skill | Implementation Files |
   |-------|---------------------|
   | `fvtt-performance-safe-updates` | `scripts/lib/update-queue.js`, `scripts/hooks.js` |
   ```

2. **Project conventions** - How general patterns apply here
   ```markdown
   ### Actor Types
   - `character` - Player characters
   - `crew` - Crew sheets
   ```

3. **Workflows** - Project-specific processes
   ```markdown
   ### Git Workflow
   - Feature branches → PR to `upstream/rc-1.1.0`
   - Use `--head ImproperSubset:branch-name` for cross-fork PRs
   ```

4. **Build commands** - Project-specific tool