yehezkieldio

Use when running behavior-preserving refactor, de-slop, hard-cut, or code refinement passes; deciding whether a code change is earned; separating structural fixes from style churn; preserving domain complexity; validating package-local gates; and knowing when a coherent coding pass is complete.

Decide whether a software task is code time or not code time, then execute with evidence-backed restraint. Use when asked to optimize, refactor, clean up, harden, review, fix, or improve code; when a request could tempt speculative edits; when deciding whether to patch now, measure first, report findings only, or stop because the change would weaken correctness, contracts, security, or maintainability.

LobeHub Zustand store conventions. Use when editing src/store, store slices, public/internal actions, dispatch actions, flattenActions, optimistic updates, selectors, maps, or class action migration.

Use when finishing a feature, fixing a bug, before committing React code, or when the user wants to improve code quality or clean up a codebase. Checks for score regression. Covers lint, dead code, accessibility, bundle size, architecture diagnostics.

Build interfaces with design engineering craft — the intersection of design and code. Use this skill when the user asks to build UI components, interactive elements, animations, micro-interactions, or polished web experiences. Triggers on mentions of "design engineer", "interaction design", "micro-interactions", "craft", "polish", "delight", "animation", "motion design", "haptics", "toast", "command palette", "design system components", or requests for interfaces that feel alive, responsive, and meticulously detailed. This skill should also be used when the user wants to add invisible details, fine-tune interactions, or make something "feel right". Complements the frontend-design skill by focusing specifically on interaction quality, motion, and engineering craft.

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.

Refactor this Ataraxia Rust workspace's crate and module structure aggressively but safely. Use when the user asks to clean up project structure, decompose god files, reduce ad-hoc flat source directories, clarify crate boundaries, reorganize modules, or make the workspace easier to grow without changing behavior.