Roan's Claude Code Plugins

A collection of Claude Code plugins including agents for code simplification, skills for WordPress development, and workflow automation.

Installation

Step 1: Add the Marketplace

First, add this plugin marketplace to Claude Code:

/plugin marketplace add https://github.com/roandegraaf/claude-code-plugins

Step 2: Install a Plugin

Then install the plugin you want:

Available Plugins

🐍 Python Simplifier

Automatically simplifies and refines Python code with PEP 8 compliance, Pythonic idioms, type hints, and more.

Install:

/plugin install python-simplifier@roans-cc-plugins

Features:

PEP 8 Compliance: Enforces Python style guide standards including proper indentation, line length, and naming conventions
Pythonic Idioms: Applies list/dict/set comprehensions, f-strings, context managers, and other Python best practices
Type Hints: Adds type annotations for function signatures and complex variables
Import Organization: Groups and sorts imports according to Python conventions
Code Clarity: Reduces nesting, eliminates redundancy, and improves naming

🦋 Flutter Simplifier

Automatically simplifies and refines Flutter/Dart code with Effective Dart compliance, Flutter best practices, and widget optimization.

Install:

/plugin install flutter-simplifier@roans-cc-plugins

Features:

Effective Dart Compliance: Enforces Dart style guide standards for formatting, naming, and structure
Flutter Best Practices: Applies const constructors, proper widget decomposition, and state management patterns
Widget Optimization: Reduces unnecessary rebuilds and improves widget tree efficiency
Code Clarity: Reduces nesting, eliminates redundancy, and improves naming

🍎 Swift Simplifier

Automatically simplifies and refines Swift 6 code with API Design Guidelines compliance, concurrency safety preservation, and idiomatic patterns.

Install:

/plugin install swift-simplifier@roans-cc-plugins

Features:

Swift API Design Guidelines: Enforces Apple's naming conventions (noun phrases, imperative verbs, fluent usage)
Concurrency Safety: Preserves all Swift 6 concurrency annotations (Sendable, actors, async/await, @MainActor)
Swift Best Practices: Applies guard statements, optional chaining, collection APIs, protocol-oriented design
Type Safety: Maintains generics, property wrappers, and memory modifiers
Code Clarity: Reduces nesting, eliminates redundancy, and improves naming

🐘 PHP WordPress Simplifier

Automatically simplifies and refines PHP WordPress plugin code with WPCS compliance, security best practices, and modern PHP patterns.

Install:

/plugin install php-wordpress-simplifier@roans-cc-plugins

Features:

WordPress Coding Standards: Enforces WPCS including naming conventions, Yoda conditions, proper spacing, and i18n
Security Best Practices: Ensures proper sanitization, escaping, nonce verification, and capability checks
Modern PHP: Applies PHP 7.4+ features like type declarations, null coalescing, and arrow functions
Plugin Architecture: Follows proper WordPress plugin structure with OOP and namespaces
Performance: Implements caching with transients and object cache, optimizes database queries
Code Clarity: Reduces nesting, eliminates redundancy, and improves naming

🔴 Laravel Simplifier

Automatically simplifies and refines Laravel PHP code with version-aware conventions (8.x-11.x), security best practices, and idiomatic patterns.

Install:

/plugin install laravel-simplifier@roans-cc-plugins

Features:

Version-Aware: Detects Laravel version from composer.json and applies appropriate conventions (8.x-11.x)
Laravel Standards: Enforces PSR-12 + Laravel naming conventions for controllers, models, routes, and database columns
Eloquent Best Practices: Query scopes, relationships, eager loading, version-appropriate accessor/mutator syntax
Security: Mass assignment protection, validation, authorization (Policies/Gates), CSRF, SQL injection prevention
Blade Templates: Components over @include, slots, typed props (Laravel 9+)
Architecture Respect: Works within existing patterns (Repository, Service, Action classes) without forcing changes
Code Clarity: Reduces nesting, eliminates redundancy, and improves naming

🌿 Sage WordPress Builder

Build WordPress websites using Roots Sage 10/11 with ACF Pro blocks, Tailwind CSS v4, Laravel Blade templating, and Vite.

Install:

/plugin install sage-wordpress-builder@roans-cc-plugins

Features:

ACF Blocks: Complete patterns for creating ACF blocks with BaseBlock, PHP classes, and Blade templates
Field Groups: Boilerplate for group_layout and group_reusable_content with standardized fields
Blade Components: Section wrapper and content components (subtitle, title, text, buttons)
Tailwind CSS v4: CSS-first configuration with spacing and background color conventions
Scroll Animations: GSAP + Lenis patterns with data-reveal-group for staggered animations
WordPress Standards: Escaping, naming conventions, and query patterns

Usage: This skill is automatically activated when working on Sage/WordPress projects. Claude will use these conventions when you ask to create ACF blocks, Blade components, or work with the Sage/Roots ecosystem.

🔄 Linear Workflow

Automate the Linear + Git/GitHub development workflow: pick up issues, create branches, ship PRs, merge and close the loop.

Install:

/plugin install linear-workflow@roans-cc-plugins

Prerequisites: Linear MCP server (linear-server) + GitHub MCP server (or gh CLI).

Commands:

/work <issue> — Pick up a Linear issue, create a branch, set status to In Progress, and plan implementation
/ship [msg] — Commit changes, push the branch, and create a PR linked to the Linear issue
/my-issues — View your assigned Linear issues grouped by status
/issue-status — Check sync status between Linear, Git, and GitHub PR
/merge — Merge the PR, mark the issue as Done, and clean up the branch

Usage: Run /work ENG-123 to start working on an issue. When ready, /ship to create a PR. After approval, /merge to complete the cycle. Use /my-issues to browse your backlog and /issue-status to check where things stand.

🚀 PHP 8.4 Migrator

Autonomously migrate Bedrock/Sage/ACF WordPress sites from PHP 7.4 to PHP 8.4 with team-based agent delegation.

Install:

/plugin install php84-migrator@roans-cc-plugins

Features:

4-Phase Migration: Automated scan → plan → fix → verify pipeline
Breaking Change Detection: Finds null safety issues, dynamic properties, implicit nullable params, deprecated functions across PHP 8.0–8.4
ACF-Aware: Type-aware null coalescing based on ACF field types (text → ?? '', repeater → ?: [], etc.)
Bedrock/Sage Support: Handles Composer dependencies, Blade templates, service providers, and Bud build pipeline
Dependency Matrix: Automatically upgrades Composer packages to PHP 8.4-compatible versions
Team-Based: Orchestrator delegates to parallel scanner, planner, fixer, and verifier subagents

Usage:

/php84-migrate /path/to/bedrock-site

🎨 Bootstrap to Tailwind Migrator

Autonomously migrate WordPress themes from Bootstrap 4 CSS to Tailwind CSS v4 with team-based agent delegation.

Install:

/plugin install bootstrap-to-tailwind@roans-cc-plugins

Features:

4-Phase Migration: Automated scan → plan → fix → verify pipeline
Grid Migration: Bootstrap flexbox grid (row/col-md-6) → Tailwind CSS Grid (grid grid-cols-12/col-span-6)
Utility Class Mapping: Exhaustive Bootstrap 4 → Tailwind v4 class mapping (display, flex, text, spacing, sizing)
SCSS Conversion: Bootstrap variables/mixins → CSS custom properties and @theme configuration
Build Pipeline: Gulp + node-sass → Tailwind CLI (keeps same output path, no WordPress enqueue changes)
JS Component Detection: Identifies Bootstrap JS usage (modals, dropdowns, collapse) and suggests CSS-only/Alpine.js replacements
Team-Based: Orchestrator delegates to parallel scanner, planner, fixer, and verifier subagents

Usage:

/tailwind-migrate /path/to/wordpress-theme

⚡ Ultrapowers

Tackle large tasks as a series of one-session "slices" so output quality never degrades from a bloated context. Brainstorm a high-level overview that acts as a guardrail, then loop implement → handoff → complete in fresh sessions — re-assessing what's left after each slice instead of planning everything up front.

Install:

/plugin install ultrapowers@roans-cc-plugins

Commands:

/brainstorm <idea> — Think through a task. Small ones are built inline; large ones get a high-level OVERVIEW.md (north star + a Definition of Done written as behavior scenarios that workers exercise, not just build) and a first NEXT_SLIDE.md
/implement [slug] — In a fresh session, build only the current slice from NEXT_SLIDE.md, guarded by the overview. When a slice splits into independent chunks, it may fan out parallel subagents to build them faster
/handoff [slug] — Log progress, then write the next slice — or route to /complete when the Definition of Done is met
/complete [slug] — Re-verify against the code, have an independent reviewer grade the diff in a fresh context, fold anything durable into CLAUDE.md, and archive the task docs. Items only a human can verify (deploys, hardware runs, paid live calls) end the report as a short "Your turn" list (action, then what working looks like), also saved as ACCEPTANCE.md, instead of stalling the task
/autopilot [slug] [review] — Run the whole loop autonomously via fresh per-slice slice-worker subagents until the Definition of Done is met; no iteration cap, no checkpoint stops. Pauses only to ask you a question, retries a crashed slice once, sends you a push notification when it stops or needs input, and never commits on its own. review pauses after every slice for approval. Worker status is mirrored to disk, so a dropped message never derails the loop
Auto-clear — A bundled mod refreshes the orchestrator's context after every slice: the orchestrator drops a marker, and the mod stops leftover workers, runs /clear and resumes the run with the same arguments, so nobody has to be at the keyboard. It won't resume when PROGRESS.md didn't grow since the last refresh. Requires Claude Code ≥ 2.1.287 (tested on 2.1.287) and an interactive session; elsewhere (-p, cloud) the skills fall back to continuation legs
Run panel — While /autopilot runs, a six-line pane opens on its own: the task, current slice number, elapsed time and pace per slice; Definition of Done progress with the next open item; the slice being built and for how long; what the worker is doing right now (file being edited, command running); how the last slice ended with its verification; and what is waiting on you (a question right now, checks at the end, deferred items). It survives auto-clear and closes when the task is archived
Disk-truth relay — The same mod attaches each worker's status/*.md file to its completion notification, so the orchestrator reads the authoritative result without nudging
Model split — slice-worker declares model: opus, so builders always run on Opus; the orchestrator, continuation legs, and every verifier/reviewer inherit the session model. Run on Fable and Fable orchestrates and verifies while Opus builds
/visualize <idea> — Spin up a token-frugal HTML mockup on a local server during a brainstorm, with optional click-to-pick options

Usage: Run /brainstorm add a billing dashboard to scope it, then /implement → /handoff in fresh sessions until done, finishing with /complete. Or hand the whole thing to /autopilot <slug> and let it run unattended. State lives in docs/slides/<slug>/, so you can stop and resume anytime, and the manual loop and /autopilot stay interchangeable mid-task.

✨ Osmo

Let the agent discover and integrate Osmo Supply resources — buttons, navigation menus, sliders and marquees, scroll/text/hover animations, cursors, loaders, page transitions, galleries, effects and CSS/JS snippets. The Vault is synced into a local markdown library (~/.osmo/library, one file per resource plus a searchable INDEX.md) containing the same content as Osmo's "Copy context for AI" button, so the agent can grep for a fitting resource and wire in its HTML/CSS/JS.

Made With GSAP effects are synced into the same library (mwg/ plus INDEX-mwg.md): each effect's final HTML/CSS/JS, its GSAP plugin dependencies and the full step-by-step tutorial. The sync logs in with MWG_EMAIL and MWG_PASSWORD from your shell environment; effects your membership doesn't include are skipped as locked.

Requires an Osmo membership (and a Made With GSAP membership for the MWG effects). The library stays on your machine and is never committed.

Install:

/plugin install osmo@roans-cc-plugins

Commands:

/osmo sync — Build or refresh the local library (~2 minutes, ~360 Osmo resources plus the Made With GSAP effects). Pass slugs to refresh only those
/osmo <what you need> — Search the index, shortlist candidates, read the best match and integrate it following Osmo's rules (keep data- attributes, keep the animation approach, load the listed external scripts)

Usage: Run /osmo sync once, then /osmo I need an infinite logo marquee for the hero or just build a frontend piece — the skill triggers on its own when an Osmo resource would fit.

📐 Dezzign

Redesign a client's existing website the ZekerZichtbaar way. /dezzign <url> crawls the old site with the Chrome DevTools MCP, builds the complete sitemap of the new one, asks what to keep and which style direction to use, picks fitting Osmo resources for the hero, nav, marquee, hover and transitions, then designs every page on a Claude Design canvas and pushes it to Figma. The house "stramien" — page skeleton, 60-odd section patterns and 5 named style directions, distilled from 11 sites we built — ships as reference material the skill reads one section at a time. A variant library of outside section patterns (swept from Mobbin, translated to house rules, written out in full so no Mobbin account is needed to use it; the source links do need one) plus a motion map of Made With GSAP and Osmo effects makes every page pick a signature moment and at least three non-default sections, so redesigns stop looking alike.

Requires an Osmo membership with a synced library, the Chrome DevTools MCP, the remote figma MCP authenticated, and the built-in design skill available in the session.

Install:

/plugin install dezzign@roans-cc-plugins

Commands:

/dezzign <url> — Crawl, sitemap, batched questions, Osmo picks, Claude Design canvas, Figma export. One artboard per fully designed page, wireframe outlines for the self-explanatory ones
/dezzign learn <url> — Fingerprint a newly built site into the reference set under the fixed measurement protocol, then propose stramien and style-direction updates instead of applying them

Usage: Run /dezzign https://oude-site-van-de-klant.nl and answer the three questions it batches; after a new site goes live, /dezzign learn <url> keeps the stramien current.

✂️ Context Diet

A mod that keeps unused MCP servers, skills and agents out of a project's context. Every session otherwise starts with every tool name, every MCP server's instructions and every skill listed, whether the project needs them or not. Measured on a WordPress-style project: 39k → 19k characters of listings, about 5k tokens less per session. Requires Claude Code ≥ 2.1.287 (tested on 2.1.287).

Zero setup. After your first prompt in a git project without a config, the mod fingerprints the project (top-level files, package.json/composer.json packages, the start of CLAUDE.md and README.md), asks Haiku which of your MCP servers, skills and agents are clearly irrelevant, and writes .claude/context-diet.json. A toast says what it hid; the diet applies from the next request. An existing file is never regenerated, so your edits stick.

Guardrails:

Anything your global or project CLAUDE.md mentions by name is never hidden
keep in ~/.claude/context-diet.json (or the project file) always beats a hide, for the tools you rely on everywhere: {"keep": ["context7", "chrome-devtools", "ultrapowers:*"]}
Hidden MCP tools stay reachable: a ToolSearch for them still finds them. Hiding a server does drop its MCP instructions, some of which are safety rules
Patterns take *; MCP entries are server names, skill entries skill names or plugin:*

Install:

/plugin install context-diet@roans-cc-plugins

Commands:

/diet — Which config files apply, what is hidden and kept, and how many characters each listing lost
/diet init — Regenerate the project config from scratch
/diet reload — Re-read the config after editing it by hand

Usage

Agents (python-simplifier, flutter-simplifier, swift-simplifier, php-wordpress-simplifier, laravel-simplifier)

Once installed, the simplifier agents will automatically analyze and refine your recently modified code. They operate proactively, applying improvements as you work.

Each agent focuses on:

Preserving Functionality - Never changes what the code does, only how it does it
Applying Language Standards - Enforces style guides and best practices for each language
Using Idiomatic Patterns - Applies language-specific idioms and modern patterns
Enhancing Clarity - Early returns, guard clauses, clear naming, reduced nesting
Maintaining Balance - Avoids over-simplification that reduces readability

Skills (sage-wordpress-builder)

Skills provide specialized knowledge and workflows. Claude automatically uses installed skills when the task matches the skill's description - no command needed. Just ask Claude to create an ACF block or work on a Sage project, and it will apply the conventions from the skill.

Workflow Plugins (linear-workflow)

Workflow plugins provide slash commands that automate multi-step development processes. Run /work, /ship, /merge, /my-issues, and /issue-status to drive the full Linear + Git/GitHub cycle without leaving Claude Code.

Migration Plugins (php84-migrator, bootstrap-to-tailwind)

Migration plugins provide autonomous, multi-phase migration pipelines. Run /php84-migrate or /tailwind-migrate with a path to your site/theme, and the orchestrator handles scanning, planning, fixing, and verification using parallel subagents.

Repository Structure

claude-code-plugins/
├── .claude-plugin/
│   └── marketplace.json       # Marketplace configuration
├── agents/
│   ├── python-simplifier.md          # Python agent definition
│   ├── flutter-simplifier.md         # Flutter agent definition
│   ├── swift-simplifier.md           # Swift agent definition
│   ├── php-wordpress-simplifier.md   # PHP WordPress agent definition
│   └── laravel-simplifier.md         # Laravel agent definition
├── skills/
│   └── sage-wordpress-builder/
│       ├── SKILL.md           # Skill definition
│       └── references/        # Reference documentation
│           ├── architecture.md
│           ├── acf-blocks.md
│           ├── acf-fields.md
│           ├── blade-components.md
│           ├── animations.md
│           └── tailwind.md
├── linear-workflow/
│   ├── .claude-plugin/
│   │   └── plugin.json           # Plugin metadata
│   ├── commands/
│   │   ├── work.md               # /work <issue>
│   │   ├── ship.md               # /ship [msg]
│   │   ├── my-issues.md          # /my-issues
│   │   ├── issue-status.md       # /issue-status
│   │   └── merge.md              # /merge
│   └── skills/
│       └── linear-workflow/
│           ├── SKILL.md           # Workflow conventions
│           └── references/
│               ├── branch-naming.md
│               └── pr-templates.md
├── php84-migrator/
│   ├── agents/
│   │   └── php84-migrator.md     # 4-phase orchestrator
│   ├── commands/
│   │   └── php84-migrate.md      # /php84-migrate [path]
│   └── skills/
│       └── php84-migration/
│           ├── SKILL.md
│           └── references/
│               ├── breaking-changes.md
│               ├── acf-patterns.md
│               ├── bedrock-sage.md
│               └── dependency-matrix.md
├── bootstrap-to-tailwind/
│   ├── agents/
│   │   └── tailwind-migrator.md  # 4-phase orchestrator
│   ├── commands/
│   │   └── tailwind-migrate.md   # /tailwind-migrate [path]
│   └── skills/
│       └── tailwind-migration/
│           ├── SKILL.md
│           └── references/
│               ├── class-mapping.md
│               ├── grid-migration.md
│               ├── scss-migration.md
│               ├── js-components.md
│               └── build-pipeline.md
├── ultrapowers/
│   ├── .claude-plugin/
│   │   └── plugin.json           # Plugin metadata
│   ├── agents/
│   │   └── slice-worker.md       # Per-slice subagent used by /autopilot
│   ├── hooks/
│   │   ├── hooks.json            # Registers the mod
│   │   └── register.js           # Auto-clear, disk-truth relay and run panel mod
│   ├── tests/                    # auto-clear, relay and panel tests (claude plugin test)
│   └── skills/
│       ├── brainstorm/SKILL.md   # /brainstorm <idea>
│       ├── implement/SKILL.md    # /implement [slug]
│       ├── handoff/SKILL.md      # /handoff [slug]
│       ├── complete/SKILL.md     # /complete [slug]
│       ├── autopilot/SKILL.md    # /autopilot [slug]
│       └── visualize/SKILL.md    # /visualize <idea>
├── osmo/
│   ├── .claude-plugin/
│   │   └── plugin.json           # Plugin metadata
│   ├── scripts/
│   │   ├── sync.py               # Syncs the Vault to ~/.osmo/library (stdlib only)
│   │   └── sync_mwg.py           # Syncs Made With GSAP effects into ~/.osmo/library/mwg
│   └── skills/
│       └── osmo/SKILL.md         # /osmo [sync|<what you need>]
├── dezzign/
│   ├── .claude-plugin/
│   │   └── plugin.json           # Plugin metadata
│   └── skills/
│       └── dezzign/
│           ├── SKILL.md          # /dezzign <url> | /dezzign learn <url>
│           └── references/       # The ZekerZichtbaar stramien
│               ├── stramien.md   # Page skeleton and section patterns, one heading per slot
│               ├── styles/       # 5 named style directions
│               ├── sites/        # _TEMPLATE.md + 11 site fingerprints
│               └── library/      # Mobbin-sourced variant patterns per slot + motion.md (MWG/Osmo map)
├── context-diet/
│   ├── .claude-plugin/plugin.json
│   ├── hooks/                    # hooks.json + register.js: the attachment filter mod
│   └── tests/diet.test.ts        # claude plugin test
├── README.md
└── LICENSE

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

License

MIT License - see LICENSE for details.

Author

Roan de Graaf Email: info@roandegraaf.com

Navigation Menu

Repository navigation

About

Repository files navigation

Roan's Claude Code Plugins

Installation

Step 1: Add the Marketplace

Step 2: Install a Plugin

Available Plugins

🐍 Python Simplifier

🦋 Flutter Simplifier

🍎 Swift Simplifier

🐘 PHP WordPress Simplifier

🔴 Laravel Simplifier

🌿 Sage WordPress Builder

🔄 Linear Workflow

🚀 PHP 8.4 Migrator

🎨 Bootstrap to Tailwind Migrator

⚡ Ultrapowers

✨ Osmo

📐 Dezzign

✂️ Context Diet

Usage

Agents (python-simplifier, flutter-simplifier, swift-simplifier, php-wordpress-simplifier, laravel-simplifier)

Skills (sage-wordpress-builder)

Workflow Plugins (linear-workflow)

Migration Plugins (php84-migrator, bootstrap-to-tailwind)

Repository Structure

Contributing

License

Author

About

Releases

Packages

Contributors

Languages

Name		Name	Last commit message	Last commit date
.agents/skills/skill-creator		.agents/skills/skill-creator
.claude-plugin		.claude-plugin
.claude/skills		.claude/skills
agents		agents
bedrock-sage-migrator		bedrock-sage-migrator
bootstrap-to-tailwind		bootstrap-to-tailwind
context-diet		context-diet
dezzign		dezzign
docs		docs
linear-workflow		linear-workflow
osmo		osmo
skills		skills
task-orchestrator		task-orchestrator
ultrapowers		ultrapowers
.gitignore		.gitignore
LICENSE		LICENSE
README.md		README.md

Latest commit

History

Folders and files

Repository files navigation

Roan's Claude Code Plugins

Installation

Step 1: Add the Marketplace

Step 2: Install a Plugin

Available Plugins

🐍 Python Simplifier

🦋 Flutter Simplifier

🍎 Swift Simplifier

🐘 PHP WordPress Simplifier

🔴 Laravel Simplifier

🌿 Sage WordPress Builder

🔄 Linear Workflow

🚀 PHP 8.4 Migrator

🎨 Bootstrap to Tailwind Migrator

⚡ Ultrapowers

✨ Osmo

📐 Dezzign

✂️ Context Diet

Usage

Agents (python-simplifier, flutter-simplifier, swift-simplifier, php-wordpress-simplifier, laravel-simplifier)

Skills (sage-wordpress-builder)

Workflow Plugins (linear-workflow)

Migration Plugins (php84-migrator, bootstrap-to-tailwind)

Repository Structure

Contributing

License

Author

About

Resources

Stars

Watchers

Forks

Releases

Packages

Contributors

Languages