From maister
Updates or creates .maister project standards from conversation context, descriptions, or by syncing/merging from other projects' standards directories.
npx claudepluginhub skillpanel/maister --plugin maisterThis skill uses the workspace's default tool permissions.
Update or create standards in `.maister/docs/standards/` based on conversation context or a provided description. Automatically detects the best-matching category and file. Supports both baseline categories (global, frontend, backend, testing) and custom user-defined categories.
Updates or creates project standards in .maister/docs/standards/ from conversation context, explicit descriptions, or by syncing from another project. Auto-detects categories like frontend, backend, testing.
Manages .maister/docs/ directory: file operations, INDEX.md generation, CLAUDE.md integration for project docs and standards. Internal; invoked by maister:init, standards-update, standards-discover.
Establish a team standard end-to-end — creates ADR → rule → guide chain for codifying practices. Activate when user says 'make this a standard', 'establish a convention', 'codify this practice'. Do NOT activate for recording a one-off decision (use /archcore:decide) or feature planning (use /archcore:plan).
Share bugs, ideas, or general feedback.
Update or create standards in .maister/docs/standards/ based on conversation context or a provided description. Automatically detects the best-matching category and file. Supports both baseline categories (global, frontend, backend, testing) and custom user-defined categories.
/maister:standards-update # Detect from conversation
/maister:standards-update "always use React.memo for lists" # From description
/maister:standards-update --from=/path/to/other-project # Sync from another project
--from=PATH)When --from=PATH is provided, the skill switches to sync mode — importing standards from another project's .maister/docs/standards/ into the current project. This bypasses Phases 1-3 and uses a dedicated flow.
PATH/.maister/docs/standards/ exists. If not, inform the user and stop..maister/docs/standards/ exists in the current project. If not, offer to run /maister:init first.standards/*/ — list all categories and filesstandards/*/ — list all categories and files[category]/[file] with brief description of what it containsFor each selected standard:
### sections from source that don't exist locallyInvoke docs-operator subagent via Task tool (subagent_type: maister:docs-operator):
"Regenerate INDEX.md to include all newly added/updated standards. Verify CLAUDE.md integration."
Wait for docs-operator to complete, then immediately proceed to SYNC STEP 5.
Display: standards added, standards updated, standards skipped, and total count. Suggest reviewing the imported standards and committing.
When --from is NOT provided, the skill uses the standard detect-and-update flow below.
Step 1: Gather input
Step 2: Discover existing categories and files
Scan .maister/docs/standards/*/ to find all existing categories and standard files. This determines what's available — not limited to baseline categories.
Step 3: Match to category and file
Based on the topic detected, suggest the best-matching existing category and file. Consider:
Step 4: Present suggestion
Check if the target file exists:
No user prompt needed — just inform: "Updating existing standard: [name]" or "Creating new standard: [category/name]"
Each standard uses a
###heading with 1-10 lines description (excluding code snippets). Multiple standards per topic file. Split large topics into sub-topic files.
Invoke docs-operator subagent via Task tool (subagent_type: maister:docs-operator) with context:
For updates:
"Update documentation file: standards/[category]/[name].md. Current content: [content]. Add/change: [new conventions]. Integrate new practices, maintain markdown formatting, organize logically, preserve existing unless conflicts. Update INDEX.md entry with practice-specific description (enumerate actual practices, not generic category)."
For creates:
"Create documentation file: standards/[category]/[name].md. Category: [category]. Content: [conventions]. Create with proper markdown, organized sections, code examples. Add to INDEX.md with practice-specific description. Verify CLAUDE.md integration."
Wait for docs-operator to complete, then immediately proceed to Phase 5.
If .maister/docs/ doesn't exist, offer to run /maister:init first.