From wicked-garden
On-demand persona invocation system for applying named perspectives to any task. Use when: "invoke persona", "act as", "apply perspective", "use a persona", "persona:as", "define persona", "list personas", "custom persona", "review as <role>", "from the perspective of", "--persona flag"
npx claudepluginhub mikeparcewski/wicked-garden --plugin wicked-gardenThis skill uses the workspace's default tool permissions.
On-demand persona invocation for applying named perspectives to any task.
Provides Ktor server patterns for routing DSL, plugins (auth, CORS, serialization), Koin DI, WebSockets, services, and testApplication testing.
Conducts multi-source web research with firecrawl and exa MCPs: searches, scrapes pages, synthesizes cited reports. For deep dives, competitive analysis, tech evaluations, or due diligence.
Provides demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation for multi-location retailers managing 300-800 SKUs.
On-demand persona invocation for applying named perspectives to any task. Personas are behavioral modifiers — they change the lens through which a task is executed, not the tools available.
/wicked-garden:persona:as engineering "review this auth flow"
/wicked-garden:persona:list
/wicked-garden:persona:define pragmatic-tech-lead --focus "delivery over perfection"
/wicked-garden:persona:submit pragmatic-tech-lead
| Command | Purpose |
|---|---|
persona:as <name> <task> | Invoke a persona for any task |
persona:list [--role R] | List all available personas |
persona:define <name> --focus "..." [--save] | Create or update a custom persona |
persona:submit <name> | PR a custom persona to the repo |
Loaded from .claude-plugin/specialist.json — 8 specialists available as personas:
| Name | Role | Best for |
|---|---|---|
| engineering | engineering | Code quality, architecture, implementation |
| platform | devsecops | Security, CI/CD, infrastructure, compliance |
| product | product | Requirements, UX, design review, business strategy |
| qe | quality-engineering | Test strategy, acceptance criteria, quality gates |
| data | data-engineering | Pipeline design, ML guidance, analytics |
| delivery | project-management | Rollout, FinOps, milestone delivery |
| jam | brainstorming | Ideation, exploration, multi-perspective analysis |
| agentic | agentic-architecture | Agent safety, tool design, agentic patterns |
Create your own with persona:define. Stored in project-scoped DomainStore.
/wicked-garden:persona:define pragmatic-tech-lead \
--focus "delivery over perfection — ship iteratively, measure, adjust" \
--traits "direct,pragmatic,cost-aware" \
--role engineering
Use --save to promote to plugin-level cache for cross-project reuse:
/wicked-garden:persona:define my-persona --focus "..." --save
Each persona has rich characteristics that create a genuine perspective:
name — kebab-case identifier
description — one-line summary
focus — the lens this persona applies
traits — behavioral adjectives
role — category for --role filtering
personality — style, temperament, humor
constraints — non-negotiable rules (MUST follow)
memories — formative experiences that inform judgment
preferences — communication, code_style, review_focus, decision_making
Route any code review through a persona's lens:
/wicked-garden:engineering:review --persona platform
/wicked-garden:engineering:review --persona qe
Falls back to default senior-engineer if persona not found.
If specialist.json is unavailable, three built-in personas are always available:
When names collide across sources, higher priority wins:
custom (DomainStore) > cache (~/.claude/plugins/...) > builtin > fallback
This lets you override a built-in persona with a project-specific version.