Explorar skills

Every interactive element needs a complete set of visual states — rest, hover, active/pressed, focus, disabled, and loading. States should be derived algorithmically from the base colour, not chosen arbitrarily. Use when designing buttons, links, inputs, or any clickable component.

Use when MCU firmware download, flashing, erase, verify, probe connection, boot mode, read protection, or programmer tool operations fail

Natural-language editor for .claude/quality/schedule-config.json. Users talk about maintenance scheduling in everyday language ("run audit twice a week", "turn off deep daydream", "switch dispatcher to 08:30") — this skill parses intent, validates against the schema, shows a concrete diff, asks for confirmation, and writes the change. WHEN TO USE: - User wants to change how often a job runs - User

Ship, measure, and learn effectively. Use when planning staged rollouts, setting up metrics hierarchies, running bet retrospectives, or executing GTM launches. Part of the Modern Product Operating Model collection.

Clerk authentication integration for Convex. Use when setting up Clerk auth, configuring ConvexProviderWithClerk, implementing Clerk webhooks for user sync, or troubleshooting Clerk-specific auth issues.

Use when creating, rewriting, or improving README files for public repositories

Use when integrating, porting, configuring, or debugging FlashDB KVDB or TSDB on MCU flash, filesystems, RTOS, or bare-metal projects

Index of the Modern Product Operating Model — a collection of composable product skills. Use when user wants an overview of all product skills, doesn't know which specific skill they need, or wants to understand how the product systems connect.

A brand's visual tone — playful or serious, rounded or angular — should be consistent across all UI elements. Shape language in typography, border-radius, and iconography communicates personality before a single word is read. Use when establishing a design system, choosing icon libraries, setting border-radius tokens, or reviewing visual consistency.

Periodic maintenance of institutional knowledge. Analyzes lessons for staleness, overlaps, and gaps. Keeps lessons.json healthy.

Related features and tasks — such as purchase flows, onboarding, or multi-step configuration — should be designed as natural, guided paths that feel coherent and fit the product hierarchy. Use wizards for complex sequential tasks. Use when designing flows, onboarding, checkout, setup sequences, or any multi-step user journey.

Post-mortem investigation for failed or stuck workflows. Analyzes git history and planning artifacts.