grimoire-meta

Plugin grimoire-meta from marketplace grimoire in jeffreytse/grimoire-core. Commands read from the repo's manifest — 28 days ago.

Skills (31)

• adapt-best-practice

  Use when the user wants to apply a practice but has specific constraints that differ from the canonical case — team size, industry regulation, budget, maturity level, technology stack, or organizational culture. Produces an adapted version that preserves the practice's core while fitting the user's

• analyze-best-practice-problem

  Use when the user presents a problem that isn't well-defined — goal is unclear, scope is unstated, or what's described looks like a symptom rather than a root cause. Asks clarifying questions one at a time until the problem boundary is clear, then produces a problem statement, problem space map, and

• apply-best-practice-driven-development

  Use when the user wants to systematically align any project or artifact to their stated best practice preferences — e.g., "apply BPDD", "align this project to our settings", "close the gap between our practices and reality", "enforce our best practices like TDD".

• apply-best-practice-profile

  Use when the user wants to activate a named set of best practices for a paradigm or methodology — e.g., "use OOP", "set profile to clean-architecture", "apply TDD practices", "switch to functional style".

• apply-best-practice-tree

  Use when a problem is too complex for a single skill but stays within one domain — match the best-fitting skill, let it decompose the problem, then recursively match sub-problems until each is covered by a best practice or resolved directly.

• audit-applied-best-practices

  Use when the user wants to inventory which best practices are already applied in their existing work — any artifact across any domain (codebase, document, design, music, finance, law, science, writing, marketing, and more) — and pin intentional choices as preferences that routing skills will respect

• audit-best-practice-domain

  Use when you need to assess the quality of all skills in a grimoire domain or sub-domain — before a release, after a bulk contribution, or when adopting a domain for the first time.

• check-best-practice-compliance

  Use when the user wants to check whether any artifact or work product aligns with their stated best practice preferences — e.g., "check compliance", "linter for best practices", "are we following our pinned practices?", "check this document against our standards".

• compare-best-practices

  Use when the user wants to choose between two or more practices that could apply to the same problem — or when suggest-best-practice surfaces multiple close-scoring options and the user needs help deciding. Produces a side-by-side comparison with trade-offs and a recommendation.

• configure-grimoire

  Use when the user wants to view, edit, remove, or validate their grimoire settings — including reading current preferences, changing or deleting a setting, switching a named profile, or checking grimoire.toml for contradictions and expired entries.

• deprecate-best-practice-skill

  Use when a grimoire skill has become outdated — the referenced tool no longer exists at scale, the source institution revised its position, a newer practice has achieved majority top-tier adoption that supersedes it, or the skill fails review-best-practice-skill criteria it once passed.

• design-best-practice-domain

  Use when adding a new domain or sub-domain to grimoire — whether starting a brand-new domain (health, finance, law), adding a new sub-domain to an existing domain, or deciding whether a new sub-domain is needed at all.

• discover-best-practices

  Use when the user mentions a field, role, or domain without a specific problem — or wants to know what best practices exist for their area before encountering a problem. Proactively surfaces available practices grouped by subdomain, with emphasis on practices people most commonly discover too late.

• explain-best-practice

  Use when the user wants to understand WHY a practice works — not just apply it. Covers the problem it solves, its origin, the evidence base, how the mechanism works, failure modes, and common misconceptions. Educational mode, not application mode.

• fix-best-practice-finding

  Use when the user wants to fix a specific compliance finding from a check-best-practice-compliance report — e.g., "fix this finding", "resolve violation #3", "fix the SRP violation in UserService", "close this linter error".

• install-grimoire

  Use when the user wants to install or uninstall grimoire skills by domain or individual skill, upgrade grimoire to the latest version, clean up broken symlinks, list what skills are available, or run a health check on the grimoire installation.

• learn-best-practice

  Use when the user wants to actually internalize an installed best practice — not just understand or apply it once, but build durable recall and independent competence so they can use it correctly later without an AI assistant present. Combines active-recall testing, spaced-review scheduling, and a p

• learn-grimoire

  Use when the user wants to get oriented on grimoire itself — what it is, why it exists, its core concepts, and how to actually use it day to day. For a brand-new user who just installed grimoire, or an existing user who has been using it without understanding the system underneath. Distinct from lea

• pin-best-practice-preference

  Use when the user wants to remember, save, or pin a specific best practice preference — either a new choice ("remember I prefer X for Y", "always use X", "pin X") or to promote existing session-level pins to project or global storage for future sessions ("save my session preferences", "persist my ch

• plan-best-practice-solution

  Use when a problem requires coordinating 2+ best practices in sequence — whether across one domain or many — e.g. "apply defensive programming", "launch a startup", "handle a workplace medical emergency", "going through a divorce while buying a house.

• resolve-best-practice-conflict

  Use when two or more installed grimoire skills give contradictory guidance for the same situation, or when the user wants to scan their preferences file proactively to find and rank conflicting skills before a conflict arises.

• review-best-practice-fit

  Use when the user already has a solution, plan, approach, or design and wants to know how well it aligns with best practices — including gaps, what's missing, and what to fix.

• review-best-practice-profile

  Use when the user wants to validate a practice profile before using or sharing it — e.g., "review my profile", "validate my-team.toml", "check this profile before sharing".

• review-best-practice-skill

  Use when evaluating whether a SKILL.md meets STANDARD.md criteria — for PR review of official grimoire-core contributions, self-review before submitting, auditing existing skills, or reviewing skills in a user package that has voluntarily adopted the standard.

• revise-best-practice-skill

  Use when an existing SKILL.md has review-best-practice-skill findings to address, a citation has become inaccurate, steps reference an outdated tool, or scope needs adjusting — splitting a skill that covers two concepts, or expanding one that is too shallow.

• share-best-practice-profile

  Use when the user wants to publish or share a practice profile — e.g., "share my team profile", "publish this profile", "open-source my backend-defaults profile".

• start-best-practice

  Use when responding to any user request — entry point into grimoire. Routes the input to the matching grimoire workflow (as listed in README.md), or exits silently if grimoire is not installed.

• suggest-best-practice

  Use when the user describes any situation, problem, goal, complaint, or question — including when they want to browse available best practices for a topic, don't know which domain applies, or don't know a best practice exists for their situation. Also use when the user starts any task or action with

• teach-best-practice

  Use when the user wants to explain, share, or advocate for a best practice with others — a team, manager, client, or stakeholder. Produces structured talking points, a brief explanation, or a presentation outline tailored to the audience's priorities and likely objections.

• write-best-practice-profile

  Use when the user wants to create a new practice profile — e.g., "create a profile for my team", "write an OOP profile", "make a backend-defaults profile".

• write-best-practice-skill

  Use when authoring a new SKILL.md to contribute to the official grimoire-core package, or when writing skills for a user package that has chosen to follow STANDARD.md.