Audits and fully configures how a website looks when shared (Open Graph, Twitter/X cards, WhatsApp/Discord/Slack previews) and in the browser (title, favicons, theme-color, web manifest), generating missing assets and verifying the result locally. Use when setting up link previews, og:image, favicons, social sharing…
Teach the user a new skill or concept across multiple sessions, using the current directory as a stateful teaching workspace (mission, curated resources, learning records, glossary, and beautiful HTML lessons). Use when the user says "teach me X", wants to learn a topic over time, or asks for a personalized lesson…
Pull the latest changes from main and merge them into the current working branch. Use when the user mentions updating their branch, syncing with main, pulling latest, refreshing from main, or merging main into their branch.
Forces running a fresh proof command and reading its output before any "done" / "fixed" / "works" / "passing" / "ready to commit" / "ready to merge" claim. Use when about to assert that a change succeeded, before committing, before opening a PR, or before marking a task as finished.
Heavyweight PR verification that produces a structured report: code review (delegates to miguel-review), test verification with gap analysis and execution, and upstream assumption validation. Use when the user mentions verify PR, verify my PR, PR verification, test plan for PR, or validate PR changes.
Surfaces the single most important blindspot in a plan, decision, or situation by checking whether the frame is right, generating candidates across 8 lenses (hidden constraints, false assumptions, second-order effects, stakeholders, blast radius, base rates, time horizon, counter-positions), then either committing to…
Write or rewrite content in a direct, personal, sensory style that feels human. Applies voice principles, bans AI-giveaway phrases, and enforces visual formatting rules. Use when writing blog posts, social media, website copy, emails, PR descriptions, commit messages, or any written content. Use when the user asks to…
Write and review developer documentation in Google style (developers.google.com/style): second person, active voice, present tense, sentence-case headings, timeless wording, inclusive and accessible language, and Google's word list. Use when drafting or editing READMEs, API reference, tutorials, quickstarts, how-to…
★not rated 2 5d agoA98 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: