oh-my-openagent-toolkit

Build repo-backed domain language before rewriting user-facing copy across UI, docs, CLI, API messages, notifications, and operator surfaces without becoming a primary route.

Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.

Project-only local skill fixture

Compatibility wrapper: Redirect to `/impeccable adapt`.

Compatibility wrapper: Redirect to `/impeccable animate`.

Compatibility wrapper: Redirect to `/impeccable layout`.

Compatibility wrapper: Redirect to `/impeccable audit`.

Compatibility wrapper: Redirect to `/impeccable bolder`.

Compatibility wrapper: Redirect to `/impeccable clarify`.

Compatibility wrapper: Redirect to `/impeccable colorize`.

Compatibility wrapper: Redirect to `/impeccable critique`.

Compatibility wrapper: Redirect to `/impeccable delight`.

Planned adjacent, non-primary: Improve contributor inner loops, onboarding, local setup ergonomics, and fast feedback without absorbing CI, deployment, or runtime operations.

Compatibility wrapper: Redirect to `/impeccable distill`.

Planned adjacent, non-primary: Deliver API and SDK-facing documentation guidance for design-first contracts, generated references, examples, and release-adjacent doc updates without widening into generic product docs.

Compatibility wrapper: Redirect to `/impeccable extract`.

Compatibility wrapper: Redirect to `/impeccable`.

Compatibility wrapper: Redirect to `/impeccable harden`.

Compatibility wrapper: Redirect to `/impeccable polish`.

Compatibility wrapper: Redirect to `/impeccable onboard`.

Compatibility wrapper: Redirect to `/impeccable optimize`.

Compatibility wrapper: Redirect to `/impeccable overdrive`.

Compatibility wrapper: Redirect to `/impeccable polish`.

Compatibility wrapper: Redirect to `/impeccable quieter`.

Planned adjacent, non-primary: Deliver versioning, changelog, publication, promotion, and rollback guidance for shipped artifacts without absorbing deployment or runtime operations.

Compatibility wrapper: Redirect to `/impeccable shape`.

Compatibility wrapper: Redirect to `/impeccable teach`.

Compatibility wrapper: Redirect to `/impeccable typeset`.

Clarify strategic direction before implementation by reframing ambiguous goals, comparing viable paths, and recommending the next route, skill, helper, or planning step without executing work.

Deliver browser UI, interaction flows, browser-rendered graphics guidance, and web design systems across framework-specific and runtime overlays without collapsing into a Next.js-only pack.

Deliver cross-platform and native mobile experiences across React Native, Flutter, SwiftUI, and Jetpack Compose without collapsing mobile work into a single framework.

Shape cross-stack architecture, API contracts, authentication flow, and integration boundaries for harness-native delivery.

Deliver language-agnostic database design, migration, performance, and reliability guidance across relational, document, and in-memory data systems.

Deliver application and platform security guidance for auth, authz, secure coding, secrets, vulnerability review, and compliance-adjacent hardening without tying decisions to one stack.

Deliver C and C++ systems work across native toolchains, CMake, testing, performance, and constrained targets without hiding ABI or platform assumptions.

Deliver C# and .NET backends with explicit API, validation, auth, async, and operational patterns centered on ASP.NET Core.

Deliver Go backends with clear handler, service, auth, validation, and concurrency patterns across Gin, Echo, and Fiber style services.

Deliver Java and Kotlin backends across Spring Boot, Quarkus, and Ktor while keeping contracts, validation, auth, and concurrency models explicit.

Deliver Node.js and TypeScript backends across NestJS and lighter HTTP frameworks without letting one framework own API, validation, auth, or service design.

Deliver Python backends across async FastAPI and Django or Flask service styles while keeping API design, validation, auth, and service behavior explicit.