antonioshaman

adapt

Adapt designs to work across different screen sizes, devices, contexts, or platforms. Ensures consistent experience across varied environments.

animate

Review a feature and enhance it with purposeful animations, micro-interactions, and motion effects that improve usability and delight.

audit

Perform comprehensive audit of interface quality across accessibility, performance, theming, and responsive design. Generates detailed report of issues with severity ratings and recommendations.

bolder

Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability.

clarify

Improve unclear UX copy, error messages, microcopy, labels, and instructions. Makes interfaces easier to understand and use.

colorize

Add strategic color to features that are too monochromatic or lack visual interest. Makes interfaces more engaging and expressive.

critique

Evaluate design effectiveness from a UX perspective. Assesses visual hierarchy, information architecture, emotional resonance, and overall design quality with actionable feedback.

delight

Add moments of joy, personality, and unexpected touches that make interfaces memorable and enjoyable to use. Elevates functional to delightful.

distill

Strip designs to their essence by removing unnecessary complexity. Great design is simple, powerful, and clean.

Data & Documents Listed

extract

Extract and consolidate reusable components, design tokens, and patterns into your design system. Identifies opportunities for systematic reuse and enriches your component library.

harden

Improve interface resilience through better error handling, i18n support, text overflow handling, and edge case management. Makes interfaces robust and production-ready.

karpathy

Four behavioural principles to reduce common LLM coding mistakes — surface assumptions, keep it simple, edit surgically, drive by verifiable goals. Apply when writing, reviewing, or refactoring code.

learn

Quick-capture a learning during a session without interrupting flow. Appends to the knowledge base immediately.

API & Backend Listed

normalize

Normalize design to match your design system and ensure consistency

onboard

Design or improve onboarding flows, empty states, and first-time user experiences. Helps users get started successfully and understand value quickly.

optimize

Improve interface performance across loading speed, rendering, animations, images, and bundle size. Makes experiences faster and smoother.

polish

Final quality pass before shipping. Fixes alignment, spacing, consistency, and detail issues that separate good from great.

prime

Load relevant knowledge from the knowledge base before starting work. Filters by affected files, tags, or work type to avoid context bloat.

Web & Frontend Listed

quieter

Tone down overly bold or visually aggressive designs. Reduces intensity while maintaining design quality and impact.

Code & Development Listed

review-with-kb

Code review that cross-references changes against the knowledge base — catches known gotchas, validates compliance with recorded decisions, and flags anti-pattern violations.

self-reflect

End-of-session reflection that extracts learnings, patterns, gotchas, and decisions into the knowledge base. Run after completing significant work to make future sessions smarter.

Web & Frontend Listed

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications. Generates creative, polished code that avoids generic AI aesthetics.

self-improvement

Captures learnings, errors, and corrections to enable continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects Claude ('No, that's wrong...', 'Actually...'), (3) User requests a capability that doesn't exist, (4) An external API or tool fails, (5) Claude realizes its knowledge is outdated or incorrect, (6) A better approach is discovered for a recurring task. Also review learnings before major tasks.

Data & Documents Listed

spec-writer

Generate structured software specifications for features, bug fixes, and products. Use when the user wants to create a spec, PRD, feature brief, requirements document, or when starting any new implementation that needs a specification first. Invoke via /spec-writer or when the user says "write a spec", "spec this out", "create a spec", "I need a spec for...", or describes a feature they want to build. Produces adaptive-complexity specs with Job Stories, Gherkin acceptance criteria, and three-tier boundaries. Output is a markdown file ready for agent execution or human review.