dev-conventions

Claude Code Development Conventions

A Claude Code plugin marketplace that provides language-specific development conventions with token-efficient progressive disclosure.

Why a Plugin with Skills?

Skills use progressive disclosure — only the conventions relevant to your current work load into context:

Level	When Loaded	Token Cost
Skill metadata (name + description)	Always	~100 tokens per skill
SKILL.md body	When file context matches	~1,500 tokens on-demand
references/ patterns	When Claude needs them	Only when needed
Global CLAUDE.md	Every message	~1,400 tokens

Result: Working on SvelteKit? Only the SvelteKit skill body loads. Go, React, and Node.js skills stay dormant at ~100 tokens each.

Skills Included

Skill	Activates On	Covers
nodejs-conventions	.ts, .js, package.json, Express, Fastify, NestJS, Hono	node:test, Pino, Zod, Result pattern, thin controllers
react-conventions	.tsx, React components, hooks, TanStack Query, Zustand	Composition, state management, RHF+Zod, error boundaries
sveltekit-conventions	.svelte, +page.svelte, +page.server.ts, SvelteKit	Svelte 5 runes, routing, form actions, shadcn-svelte
go-conventions	.go, go.mod, go.sum	Error handling, table-driven tests, interfaces, concurrency

Installation

./install.sh

This will:

• Copy global/CLAUDE.md to ~/.claude/CLAUDE.md (global behavioral rules)
• Copy global/commands/ to ~/.claude/commands/ (global slash commands)
• Register this repo as a local Claude Code marketplace
• Install the dev-conventions plugin from it

Options

./install.sh --dry-run     # Preview changes without installing
./install.sh --uninstall   # Remove plugin and restore backups

Manual Installation

If you prefer not to use the install script:

# 1. Copy global rules and commands
cp global/CLAUDE.md ~/.claude/CLAUDE.md
mkdir -p ~/.claude/commands && cp global/commands/*.md ~/.claude/commands/

# 2. Register marketplace and install plugin
claude plugin marketplace add /path/to/claude-code-rules
claude plugin install dev-conventions@dev-conventions

Verify Installation

claude plugin list

You should see dev-conventions in the output.

Structure

.claude-plugin/
  marketplace.json                   # Marketplace manifest
global/
  CLAUDE.md                          # Global behavioral rules (installed to ~/.claude/)
  commands/
    task.md                          # /task slash command (installed to ~/.claude/commands/)
plugins/
  dev-conventions/
    .claude-plugin/
      plugin.json                    # Plugin manifest
    commands/
      convention.md                  # /dev-conventions:convention slash command
    skills/
      nodejs-conventions/
        SKILL.md                     # Core Node.js conventions
        references/patterns.md       # Detailed patterns (Express, Fastify, NestJS, Hono, etc.)
      react-conventions/
        SKILL.md                     # Core React conventions
        references/patterns.md       # Compound components, TanStack Query, forms, etc.
      sveltekit-conventions/
        SKILL.md                     # Core SvelteKit/Svelte 5 conventions
        references/patterns.md       # Form actions, hooks, adapters, Drizzle, etc.
      go-conventions/
        SKILL.md                     # Core Go conventions
        references/patterns.md       # HTTP handlers, middleware, database, logging, etc.

Customizing Conventions

Use the /dev-conventions:convention command to save preferences that persist across sessions:

/dev-conventions:convention use pino for logging in Node.js
/dev-conventions:convention prefer Zustand over Redux
/dev-conventions:convention use node:test not vitest for backend
/dev-conventions:convention always use Tailwind, never plain CSS

Preferences are saved to ~/.claude/conventions.md and referenced by the global CLAUDE.md.

Task Workflow

Use the /task command to execute a structured 4-phase workflow for any non-trivial change:

/task implement create beneficiary endpoint with full HTTP-to-corebank flow
/task fix login timeout on slow connections
/task refactor payment processing to use Stripe

The command runs four sequential phases, stopping after each for your approval:

1. Architecture & Planning — analyzes requirements, proposes implementation plan
2. Test Design — writes tests first (TDD), covering happy paths and edge cases
3. Implementation — implements the change, making all tests pass
4. Self-Review — reviews code for quality, error handling, and naming

Global Rules (CLAUDE.md)

The global rules are language-agnostic and apply to every session: