Stats
Actions
Available In
Tags
Help us improve
Share bugs, ideas, or general feedback.
Plugin
improve
Process engineering methodology: maps process topology, makes directed fixes, runs improvement experiments, and accumulates process lint rules. Domain-agnostic — each plugin owns its own :improve skill for domain-specific knowledge.
$
npx claudepluginhub cosmicdreams/claude-plugins --plugin improvePopularity
Stars
Med: 0·Avg: 268
Installs
Med: 0·Avg: 1
What's Inside
Agents2
Optimizer
/optimizer
Autonomous hypothesis-driven performance optimization. Receives a target metric and codebase, generates its own hypotheses from measurement output, tests each via the ratchet, and iterates without human checkpoints.
process-engineer
/process-engineer
Process engineer that attaches to any running process (sprint, funnel, cron, background) to identify friction, make improvements, and accumulate expertise. Operates autonomously for low-risk fixes, runs experiments for uncertain improvements, and escalates structural changes for collaborative discussion. Use when you need to improve how a process, agent, skill, hook, or workflow is working.
Skills7
accessibility-scan
/accessibility-scan
Run a multi-tool accessibility audit (Pa11y + axe-core + Lighthouse) against a locally running site and output a JSON score tuple. Use when asked to "scan accessibility", "run a11y audit", "accessibility score", "measure accessibility", "a11y baseline", "accessibility-scan", or when the experiment loop needs a measurement step for accessibility improvements. Takes a base URL (typically a DDEV local site). Do NOT use for manual accessibility review or WCAG consulting -- this is an automated measurement tool.
attach
/attach
Map the topology of a process — discover which files, agents, skills, hooks, crons, and configurations constitute it. Produces a topology map that other improve skills use to know where to make changes. Use when first engaging with a process, when asked to "attach to" or "map" a process, or when you need to understand what a process consists of. Do NOT use for making changes — use improve:fix for that.
experiment
/experiment
Run an uncertain process improvement using the ratchet pattern: measure baseline, make a change, measure again, keep if better, revert if worse. For process improvements where the outcome is uncertain and you need evidence before committing. Do NOT use for known fixes — use improve:fix for those.
fix
/fix
Make a directed process change in the right place so it propagates to the running process. Handles locating the target file, making the edit, and verifying the change takes effect. Use when you know what needs to change — either from your own observation, a lint rule, or because the human pointed at the problem. Do NOT use for uncertain improvements — use improve:experiment for those.
lint
/lint
Check processes against known problem patterns (lint rules) and manage the lint ruleset. Provides global/default rules that apply across all domains. Domain plugins augment with their own rules via their :improve skill. Use to scan for known issues, add new rules from observations, promote/demote rules between confidence tiers, or review the current ruleset. Do NOT use for making fixes — use improve:fix for that.
Stats
Version1.3.0
LanguageJavaScript
Stars0
MaintenanceGood
Last Commit
Added
Available In
Safety Signals
Caution
Uses power tools
Uses Bash, Write, or Edit tools
Tags
Categories
Help us improve
Share bugs, ideas, or general feedback.
