Morgs32 Skills

Grill a fuzzy plan one question at a time (chat only), then synthesize a numbered design spec under the active project's established planning tree. Use when the user says /spec, wants a design spec, or wants grill + to-spec before implementation.

Explores ideas with pseudocode, stubs, and comments only—no architecture ownership, no compile-fixing, temporary broken state OK. Use when the user says spike, /spike, sketch, rough pass, explore options, or wants a first pass before they decide design.

Run a full Zerospin repo polish pass: fix formatting failures, lint errors and warnings, TypeScript/typecheck failures, and unit or workerd test failures across the whole repo. Use when the user says polish, repo polish, fix all lint warnings, make lint/typecheck/tests pass, run a full quality pass, or asks for whole-repo verification and fixes.

Adds comments that explain code: an overview above a function with numbered steps and matching inline checkpoints for multi-step methods, or a file-top block comment for specific behavior the user names. Use when the user says annotate, /annotate, say-so, /say-so, step annotations, file header explanation, or wants a concise walkthrough or behavior note.

Apply Morgan's shared TypeScript, Effect, RPC, runtime architecture, testing, naming, and code-shape conventions, including YAGNI and coordination-cost checks. Use when implementing or reviewing code in repositories whose guidance names $patterns, or when the user asks to follow or inspect the shared patterns.

Send the current user a Slack DM from Codex. Use when the user says "slack me", "Slack this to me", "DM me", "send me this in Slack", "message me the status", or otherwise asks Codex to deliver a summary, result, reminder text, link, or status update to the user's own Slack account.

Acts as an informed pair programmer: terse first-pass remarks, rabbit holes, and occasional alternative angles—exploration, not exhaustive review. Use when the user says rubber duck, /rubber-duck, think with me, bounce an idea, pair on a design, or wants an informal critique without a full review.

Make dense or needlessly indirect code understandable, then simplify one coherent slice at a time. Use for make-obvious; cleanup or slop review; prune, simplify, inline, or import cleanup; fix-casts or TypeScript assertion audits; and one-call wrappers or one-liner helpers that should be inlined. Do not use for generic tutorials or unbounded refactors without a concrete scope.

Pull or push the Git subtrees vendored under vendor/. Use when the user asks to update, sync, pull, push, publish, or inspect external vendors such as Effect.

Codify an agreed convention or reusable repository-specific lesson in the active project's {root}/llm-wiki/** guidance. Use after a code change, when the user names a local pattern, or with no prompt to preserve conclusions from the current chat. Do not use for shared skills or morgs32/llm-wiki.

Sync wiki/architecture workflow docs with source code: sequence diagrams, their Annotated workflow steps, Trigger steps, other mermaid diagrams, and nested citation bullets. Use when the user asks to update architecture docs, workflow docs, mermaid in wiki/architecture, annotated-step citations, or says update-architecture.