Skills

Build and refine user interfaces with Tailwind CSS. Use when the user asks to build, design, style, or refine web UI — landing pages, dashboards, marketing sections, forms, buttons, cards, pricing tables, hero sections, testimonials, or Tailwind markup cleanup. Generates multiple design variations on exploratory requests.

Guide any engineering task — building, fixing, expanding, refactoring, investigating — like a senior engineer at a big company. Teaches the thinking process, not just rules. Study first, plan properly, implement with discipline. Use this skill whenever the user mentions "follow the patterns", "replicate the architecture", "proper system design", "production-ready plan", "do it properly", "don't hardcode", "build it like they would", "find the root cause", "fix it properly", "don't just patch it", "expand this feature", "refactor this", "how does this work", or asks for any engineering work to follow existing conventions exactly. Also trigger when the user is frustrated that previous work was half-baked, used hardcoded values, created workarounds, suppressed lints, or didn't follow the repo's architecture. Even if the user just says "plan this properly" or "I want it done right" or "check the codebase first", use this skill. When in doubt, prefer this skill — studying the codebase first never makes anything wo

Audit an implementation plan for Accessibility compliance. Use this skill when the user says "audit for accessibility", "a11y review this plan", "check accessibility", or any plan that adds interactive UI — buttons, dialogs, modals, forms, panels, trees, tabs, drag-and-drop, or custom widgets. Developer tools are notoriously poor at accessibility. This lens catches missing ARIA labels, broken keyboard navigation, trapped focus, insufficient contrast, and missing screen reader announcements that no other audit will find because they require thinking like a user who can't see the screen or use a mouse.

Audit an implementation plan through the eyes of a senior Backend/Rust Engineer. Use this skill when the user says "audit as backend", "backend review this plan", "review the Rust code", or any plan that involves Tauri commands, Rust crates, IPC protocol, sidecar processes, file system operations, terminal management, or backend state. This lens catches unsafe Rust patterns, error handling gaps, resource leaks, concurrency issues, and IPC protocol mistakes that frontend-focused audits miss entirely.

Audit an implementation plan through the eyes of a Design Engineer. Use this skill when the user says "audit as design engineer", "design review this plan", "review the design aspects", or any plan that involves UI changes, component styling, visual states, dark mode, colors, typography, spacing, or animations. Also trigger when reviewing plans that touch CSS, Tailwind classes, design tokens, or component visual structure. This lens catches visual inconsistencies, design system violations, and craft issues that other audits miss entirely.

Audit an implementation plan through the eyes of a Developer Experience (DX) Engineer. Use this skill when the user says "audit as DX", "DX review this plan", "review the developer experience", or any plan that adds user-facing features to a developer tool — CLI commands, error messages, configuration, onboarding, keyboard shortcuts, tool output, or API surfaces. Orbit is a developer tool; its users are developers. This lens catches the usability issues specific to developer tools that generic UX audits miss because they don't think like a developer using a tool.

Audit an implementation plan through the eyes of a senior Frontend Engineer. Use this skill when the user says "audit as frontend", "frontend review this plan", "review the React code", or any plan that involves React components, hooks, state management, Zustand stores, TypeScript types, CSS/Tailwind, bundle optimization, or rendering performance. This lens catches React anti-patterns, state management issues, type safety gaps, unnecessary re-renders, and bundle bloat that generalist audits miss.

Audit an implementation plan through the eyes of a Performance Engineer. Use this skill when the user says "audit for performance", "perf review this plan", "will this be fast", "check performance impact", or any plan that could affect runtime performance — new event listeners, state subscriptions, IPC calls, file I/O, streaming, rendering changes, process spawning, or features that run in long-lived sessions. This is NOT frontend render perf (that's frontend-eng). This is systems performance — memory over 8-hour sessions, IPC latency, streaming throughput, resource lifecycle. Desktop apps can't hide behind a page refresh.

Audit an implementation plan for Production Readiness. Use this skill when the user says "audit for production", "production review this plan", "will this work in prod", "is this production ready", or any plan that's about to ship — especially features involving data persistence, process lifecycle, error recovery, environment configuration, or user-facing workflows. This lens catches the failures that only appear in production — environment differences, missing error recovery, deployment gaps, and the "works on my machine" syndrome.

Audit an implementation plan through the eyes of a Repo Maintainer. Use this skill when the user says "audit as repo maintainer", "review conventions", "check code hygiene", "review the file structure", or any plan where you want to verify it follows the project's established patterns — barrel exports, file placement, naming conventions, import ordering, style reuse, code deduplication, and lint compliance. This lens catches the slow erosion of codebase health that individual feature reviews miss because each violation seems minor in isolation.

Audit an implementation plan through the eyes of a Systems/Structural Architect. Use this skill when the user says "audit as structural engineer", "architecture review this plan", "review the system structure", or any plan that introduces new modules, changes system boundaries, adds cross-cutting concerns, modifies dependency graphs, or reorganizes code between layers (frontend/backend/bridge). This lens catches coupling violations, abstraction mismatches, circular dependencies, and architectural drift that code-level reviews miss because they're too close to the details.

Audit an implementation plan through the eyes of a UX Engineer. Use this skill when the user says "audit as UX", "UX review this plan", "review the user experience", or any plan that changes how users interact with the product — new features, flow changes, navigation, onboarding, error states, modals, dialogs, or multi-step processes. This lens catches usability issues, broken mental models, missing feedback, and interaction patterns that look fine in code but confuse real users.

Run all 10 expert audit lenses sequentially, writing everything into ONE comprehensive document. Works in TWO modes — (1) Plan mode: provide a plan file path to audit a plan before implementation. (2) Repo mode: audit actual code changes (uncommitted changes, branch/PR vs main, or general repo health). Use this skill when the user says "full audit", "run all audits", "audit everything", "complete audit", "full spectrum audit", "10-lens audit", "audit the repo", "audit my changes", "audit this PR", or wants every expert perspective examined. This is the nuclear option — every lens, every perspective, one document.

Production scope gatekeeper v3 — catches secretly-MVP plans before they reach the audit pipeline. Use this skill when the user says 'fazxes', 'check scope', 'is this complete', or right after a plan is written and before it goes to /audit-plan. Hunts for buried scope reductions ('trade-offs accepted', 'for v1', 'future enhancement'), scope reduction by omission (problems stated but never addressed), vague confidence language ('this should work'), and approach issues (building new when extending existing systems would work). Also detects when revised plans silently drop previously-in-scope items. Binary PASS/FAIL with severity-rated fix list and scope delta on revisions. This is not a code auditor — it gates what enters the audit pipeline.

Clarify problems, bugs, and feature requests through a reflect-back interview before planning. Use this skill whenever the user describes an issue, bug, broken behavior, or a feature they want — BEFORE entering plan mode. Triggers on phrases like "this isn't working", "I'm seeing a bug", "something is wrong with", "I want to change how X works", "X is broken", "the problem is", "I'm having an issue with", "can you fix", or any description of unexpected behavior.

Generate production-grade Vitest tests from HTML elements captured in DevTools. Two-phase workflow (analysis → generation) with edge case discovery.

Create in-app stress tests that drive the real application pipeline from browser DevTools. No mocks — real state, real APIs, real UI. Works for any web app with observable state.

Create an in-app stress test that runs from browser DevTools console via window.__orbit_debug. Drives the real message pipeline (Tauri events, Zustand stores, Rust backend) with no mocks.

Write meaningful tests for TypeScript/React (Vitest) and Rust (cargo test) code.

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.