design-patterns

Add the marketplace:

```bash

/plugin marketplace add bfmcneill/agi-marketplace

```

Install plugins individually (you choose which ones):

```bash

/plugin install core # Universal practices

/plugin install sveltekit # SvelteKit/Svelte 5

/plugin install python # Python with uv

```

core (v0.1.0)

Universal development practices that apply to all projects.

Skills:

• agent-behavior - Activity tracking in docs/activity/, working patterns
• versioning - Semver rules, package.json/pyproject.toml + git tag sync
• design-patterns - Creational, structural, behavioral patterns

sveltekit (v1.0.0)

SvelteKit with Svelte 5 and recommended stack.

Skills:

• sveltekit-builder - 105+ rules for Svelte 5, runes, SSR, forms, third-party (Kysely, Better Auth, shadcn-svelte, AI SDK)

python (v0.1.0)

Python development with modern tooling.

Skills:

• uv-workflow - uv package manager commands, workflows, gotchas

```

agi-marketplace/

├── .claude-plugin/

│ └── marketplace.json

├── core/

│ ├── .claude-plugin/plugin.json

│ └── skills/

│ ├── agent-behavior/

│ ├── versioning/

│ └── design-patterns/

├── sveltekit/

│ ├── .claude-plugin/plugin.json

│ └── skills/

│ └── sveltekit-builder/

├── python/

│ ├── .claude-plugin/plugin.json

│ └── skills/

│ └── uv-workflow/

└── README.md

```

Add a Lesson Learned

When you discover something useful, add it to the relevant skill:

```bash

# 1. Edit the skill

vim sveltekit/skills/sveltekit-builder/SKILL.md

# Or add a reference file:

vim sveltekit/skills/sveltekit-builder/references/new-pattern.md

# 2. Commit and push

git add . && git commit -m "Add lesson: [description]" && git push

# 3. Update in Claude Code

/plugin update sveltekit

```

Add a New Skill

```bash

# 1. Create skill directory

mkdir -p /skills/

# 2. Create SKILL.md with required frontmatter

cat > /skills//SKILL.md << 'EOF'

---

name: skill-name

description: Use when [triggering conditions]. Max 200 chars.

---

# Skill Name

• Trigger 1
• Trigger 2

[Your content here]

EOF

# 3. Optional: Add reference files

mkdir /skills//references

# 4. Commit, push, update

git add . && git commit -m "Add skill: skill-name" && git push

/plugin update

```

Add a New Plugin

```bash

# 1. Create plugin structure

mkdir -p new-plugin/.claude-plugin

mkdir -p new-plugin/skills

# 2. Create plugin.json

cat > new-plugin/.claude-plugin/plugin.json << 'EOF'

{

"name": "new-plugin",

"description": "Description here",

"version": "0.1.0",

"author": { "name": "your-name" },

"license": "MIT"

}

EOF

# 3. Add to marketplace.json

# Edit .claude-plugin/marketplace.json, add to plugins array:

# { "name": "new-plugin", "version": "0.1.0", "source": "./new-plugin" }

# 4. Add skills to new-plugin/skills/

# 5. Commit, push, install

git add . && git commit -m "Add plugin: new-plugin" && git push

/plugin install new-plugin

```

Version Bumps

When releasing updates, follow semver (see core/skills/versioning):

```bash

# 1. Update version in plugin.json

# PATCH: bug fixes (0.1.0 → 0.1.1)

# MINOR: new features (0.1.0 → 0.2.0)

# MAJOR: breaking changes (0.1.0 → 1.0.0)

# 2. Commit and tag

git add .

git commit -m "chore: bump to X.Y.Z"

git tag -a -vX.Y.Z -m "Release X.Y.Z"

git push && git push --tags

```

Quick Reference

| Task | Command |

|------|---------|

| Update installed plugin | /plugin update |

| Reinstall plugin | /plugin uninstall then /plugin install |

| List installed | /plugin → Installed tab |

| Check skill is loading | Ask Claude, check if skill influences response |

```yaml

---

name: skill-name # Must match directory name, max 64 chars

description: Use when ... # Max 200 chars, starts with "Use when"

---

# Skill Name

[Triggers and use cases]

[Tables, patterns]

[Or link to references/]

```

Constraints:

• name: lowercase, hyphens, matches directory
• description: max 200 chars, third person
• Body: under 500 lines (use references/ for more)

MIT