Structured, standards-aware development workflows for Claude Code
npx claudepluginhub skillpanel/maisterStructured, standards-aware development workflows for Claude Code
SkillPanelStructured, standards-aware development workflows for Claude Code
SkillPanelStructured, standards-aware development workflows for Claude Code
Describe what you want to build, and the plugin handles the rest - from specification through implementation to verification - while enforcing your project's coding standards at every step.
/plugin marketplace add SkillPanel/maister
/plugin install maister@maister-plugins
After installing, restart Claude Code (/exit and relaunch) to ensure the plugin is fully loaded.
Initialize your project to auto-detect coding standards and generate project documentation:
/maister:init
This scans your codebase and creates .maister/ with standards, docs, and task folders. May take a few minutes on larger projects.
If you have another project already using Maister, you can reuse its standards as a starting point:
/maister:init --standards-from=/path/to/other-project
/maister:development Add user profile page with avatar upload
Or just discuss your task with Claude and then run:
/maister:development
The plugin picks up context from your conversation - no arguments needed.
All artifacts are saved in .maister/tasks/ organized by type and date.
Every workflow command works without arguments. The plugin reads your current conversation to extract the task description and auto-detect the task type:
You: "The login page throws a 500 error when the session expires"
You: /maister:development
→ Auto-detects: bug fix, extracts description from conversation
You: /maister:standards-update
→ Scans conversation for patterns like "we always use..." or "prefer X over Y"
You can always be explicit when you prefer - arguments and flags simply override the auto-detection.
| Command | Use When |
|---|---|
/maister:development | Features, bug fixes, enhancements |
/maister:research | Research with synthesis and solution design |
/maister:performance | Optimizing speed or resource usage |
/maister:migration | Changing technologies or patterns |
/maister:product-design | Product and feature design |
Task type (feature/bug/enhancement) is auto-detected from context. Override with --type=feature|bug|enhancement if needed. Or use /maister:work as a single entry point that routes to the right workflow.
For smaller tasks that don't need a full workflow:
| Command | Use When |
|---|---|
/maister:quick-plan | You want a plan with standards awareness before coding |
/maister:quick-dev | You know what to do - just implement with standards applied |
/maister:quick-bugfix | Quick TDD-driven bug fix — write failing test, fix, verify |
This is the key differentiator. Maister doesn't just run workflows - it learns your project's conventions and enforces them:
/maister:init scans config files, source code, and documentation to auto-detect your coding standards/maister:standards-discover refreshes standards from your evolving codebase/maister:standards-update lets you add or refine standards manually, or sync from another project with --from=PATHStandards live in .maister/docs/standards/ and are indexed in .maister/docs/INDEX.md.
Important: Run workflows with auto-accept edits enabled. Do not use Claude Code's plan mode with workflows (see Best Practices below).
Want to try experimental features before they hit stable? Install from the beta channel:
# Add the beta marketplace
/plugin marketplace add SkillPanel/Maister#beta
Open Design — local-first design app exposed to coding agents over MCP. Install once with your agent's plugin command and projects/files/skills are reachable through stdio.
Claude Code plugins for the Slidev presentation framework
Bundled plugins for actuating and debugging the Chrome browser.