satyrlord

Structured design critique across usability, hierarchy, consistency, and accessibility. Use when the user shares a Figma link, screenshot, mockup, or asks for design feedback ("review this design", "critique this screen", "what do you think of this UI?"). Use after design-router when a theme has been selected and applied.

Runs a disciplined ablation workflow for MixJam Electron (MJE) bugs to prove which changed files or layers are actually required for a fix. Use when an MJE import, playback, or UI bug has a known pass/fail check but several edits may be involved, or when the user asks which change actually fixed it, what can be removed, or for the smallest proven fix.

Creates or updates repository specs, acceptance criteria, durable decisions, and documentation for new work. Use when adding a feature or defining an ambiguous slice, when making architectural decisions or changing contracts (API, persistence, import, playback), or when recording durable context (glossary, conventions, trade-offs) for future engineers and agents.

Audits the MixJam Electron (MJE) codebase for dead TypeScript code, orphan files, and unused symbols across main and renderer processes, triages findings into live dead code or false positives, and optionally removes provably dead code with focused validation. Use for a dead-code audit, or for cleanup explicitly requested from analyzer findings.

Routes a requested UI visual direction to one bundled design theme. Use when building or restyling an interface that needs an explicit aesthetic.

Remove AI slop from every file in the repository while preserving behavior and genuine information.

Diagnoses hard bugs and performance regressions with a controlled feedback loop, and implements the fix only when requested. Use when the failure is flaky, not yet reproducible, still lacks a root cause, or needs measurement.

Reviews a change set against an unusually strict maintainability bar, emphasizing code-judo simplification, abstraction quality, the 1k-line rule, and spaghetti growth.

Run a long-form goal with judge-verified completion.

Creates or updates repository specs, acceptance criteria, durable decisions, and documentation for new work. Use when adding a feature or defining an ambiguous slice, when making architectural decisions or changing contracts (game state, leaderboard, audio, settings), or when recording durable context (decisions, glossary, conventions) for future engineers and agents.

Audits the MEMORYBLOX codebase for dead TypeScript code, orphan files, and unused symbols, triages findings into live dead code or false positives, and optionally removes provably dead code with focused validation. Use when the user asks for a dead-code scan, unused-code audit, orphan-file scan, unused-symbol triage, or cleanup from analyzer findings.

Remove AI-generated code slop from the current branch diff. Use when the user asks to deslop, clean up AI slop, remove unnecessary comments, strip defensive cruft, or flatten needless nesting.

Runs a disciplined diagnosis loop for hard bugs and performance regressions. Reproduce, minimise, hypothesise, instrument, fix, and regression-test. Use when the user says "diagnose this", the bug is flaky or not yet reproducible, root cause is unknown after triage, or a performance regression needs measurement before fixing.

Extremely strict maintainability review hunting code-judo restructurings — abstraction quality, the 1k-line rule, and spaghetti growth. Use when asked to review code, do a code review, audit changes, check for issues, or review uncommitted/staged changes. Covers diff-first review of pending changes and broader codebase audit.

Transfer session state to a fresh agent as a minimal, lossless state-transfer document.

Surface architectural friction in a codebase, package it as a visual HTML report, and grill through the strongest deepening opportunity.

Ablation test a hard bug to prove the smallest causal change set. Use when competing changes may explain a fix, results are intermittent, or the user needs a minimal proven repair.

Absorb a complete external Stellaris mod into StellarisPlus. Use the disclosed removal branch when reversing a credited absorption.

Full build the complete StellarisPlus release-validation sequence: quality gate, confirmed manual test, runtime log repair, and repair-authorized code review.

Handoff current work to another agent in a concise tmp/ artifact. Use when the user or another local skill requires resumable session context.

Merge local StellarisPlus files without changing load-order behavior. Use to classify folders by LIOS/FIOS/DUPL/MERGE and consolidate only proven-safe candidates.

Scan integrated Workshop mods against live Steam metadata and update only entries proven outdated.

Review StellarisPlus changes for merge readiness across Paradox Script, load-order, localisation, GFX/GUI, references, and documentation. The default branch is read-only; repair findings only with explicit authorization.

Log fix explicitly requested Stellaris runtime diagnostics by collecting or analyzing logs and repairing mod-owned errors. Do not collect logs when the user only describes a symptom; ask first.

Router for 67 bundled design themes. Use whenever building or restyling UI and a visual direction is needed — it maps the desired vibe (minimal, playful, retro, enterprise, glassmorphism, etc.) to the right theme file to load. Trigger on "design style", "make it look...", "UI theme", "visual direction", or any request to build a page/app with a specific aesthetic.

Produce a new album entry for the app. Use when asked to add, analyse, or create an album entry.

Remove AI slop from every file in the repo — code, docs, config, and data.

Extremely strict maintainability review hunting code-judo restructurings — abstraction quality, the 1k-line rule, and spaghetti growth.

Quality-gate execution for repository hygiene and release readiness. Use when the user asks to run a quality gate, clean all Problems panel issues, fix lint/test/coverage failures, or verify the branch meets strict 80%+ coverage thresholds without suppression.

Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.

Surface architectural friction in a codebase and apply deepening improvements.

Create Segmented Horizontal Bar Charts with TypeScript. Use when: building bar charts, creating segmented bars, visualizing proportional data, rendering stacked horizontal charts, adding data visualization components, displaying percentage breakdowns.