Aliolabadiena
UserA Claude Code orchestration engine: dispatcher + registry, scaffold/heal/self-improve, a styled terminal, and multi-instance lanes.
Categories
Indexed Skills (6)
frontend-design
Design distinctive, intentional user interfaces - not templated defaults. Use when building or restyling any user-facing UI (landing page, marketing site, dashboard, web app, component) or when asked to make something look better, polished, or more professional. Framework-agnostic.
plan-before-build
Turn a large, vague, or multi-file request into an agreed design and a concrete step-by-step plan before writing code. Use when the task is ambiguous, spans several files, or is a new feature, redesign, or refactor. Do NOT use for a small, clear, single-file change - just do that directly.
systematic-debugging
Find the root cause with evidence before proposing any fix. Use when something is broken or failing, a test is red, there is an error or stack trace, a crash, or a regression ("why does X happen", "it stopped working"). Do NOT use for greenfield feature work or an obvious known one-line typo.
verification-before-completion
Prove a claim with a fresh command run before saying it is done, fixed, passing, or working. Use before reporting completion, before a commit or PR, and before trusting a subagent's success report. Do NOT skip for "small" or "obvious" changes.
accessibility-audit
Run a focused WCAG 2.2 AA accessibility pass and remediate. Use when asked about accessibility, a11y, WCAG, screen-reader support, keyboard navigation, or color contrast. Deeper than the a11y gate inside the frontend-design skill.
design-review
Critique an existing UI against a design rubric and propose concrete fixes. Use when asked to review, critique, audit, or polish a UI, "does this look professional", or after a UI feature ships. The QA counterpart to the frontend-design skill.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.