Skills

Skills are community-curated guides that encode best practices for specific technologies, frameworks, or workflows. When you install a skill for Next.js, for example, Planu learns your project's preferred patterns for API routes, components, and testing — and injects that context into every spec it creates.

How Planu uses skills automatically

• After init_project, Planu detects your stack and suggests relevant skills
• Before implementing a repeatable pattern, Planu searches for matching skills
• Skills appear as inline hints in spec acceptance criteria

You never need to think about skills explicitly. Planu discovers and applies them for you.

Finding and installing skills

1. Ask your AI: "Search for nextjs skills"
   → Planu calls skill_search("nextjs")

2. Review the results and pick one
   → Planu shows title, description, install count

3. Ask: "Install skill-id XXX"
   → Planu calls skill_install("XXX")

That is it — three conversational steps and your stack conventions are loaded into every future spec.

Popular skill categories

Framework skills

Technology	What the skill encodes
Next.js	App Router conventions, Server Actions, API route patterns
Django	URL routing, serializers, middleware, ORM patterns
Rails	MVC conventions, Active Record, Hotwire patterns
Laravel	Eloquent, Blade, service providers, queue patterns
FastAPI	Pydantic models, dependency injection, async patterns
NestJS	Module structure, decorators, guards, interceptors

Database skills

Technology	What the skill encodes
Prisma	Schema conventions, migrations, relation patterns
SQLAlchemy	ORM session management, alembic migrations
Drizzle	Type-safe queries, schema definitions
TypeORM	Entity conventions, repository pattern

Auth patterns

Technology	What the skill encodes
NextAuth	Session strategies, provider setup, callbacks
Passport.js	Strategy configuration, session serialization
Supabase Auth	RLS policies, JWT handling, magic links

Testing patterns

Technology	What the skill encodes
Vitest	Unit and integration patterns, mocking conventions
Pytest	Fixture patterns, parametrize, async testing
Jest	Module mocking, snapshot conventions, coverage setup

CI/CD

Technology	What the skill encodes
GitHub Actions	Workflow structure, caching, matrix builds
GitLab CI	Pipeline stages, artifacts, environments

Design and brand

Category	What the skill encodes
Logo generation	Prompt patterns for consistent brand logos
OG images	Open Graph image conventions for social previews
Favicon	Multi-resolution favicon generation workflows

Creating your own skill

When your project has a repeatable pattern that no community skill covers, create one:

Ask: "Create a skill for [your pattern]"
→ Planu calls create_skill with your conventions
→ Skill saved to .claude/skills/ in your project

Your skill file lives in .claude/skills/ and is picked up automatically in every session.

Publishing to the registry

Once your skill is battle-tested, share it with the community:

Ask: "Publish my skill to the Planu registry"
→ Planu calls registry_publish
→ Available to the community

Published skills get an install count, a rating, and appear in skill_search results for every Planu user.

Skills vs Rules vs Hooks

	Skills	Rules	Hooks
Purpose	Best practices per technology	Always-on constraints	Event-triggered automation
Scope	Per project	Global or project	Global or project
Managed by	Community + you	You	You
Applied when	Spec is created	Every AI interaction	On git events

Use Skills to teach Planu your stack conventions. Use Rules to enforce non-negotiable policies. Use Hooks to automate repetitive actions triggered by git events like commits and pushes.