grok-toolkit

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

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.

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.

Structured critique and anti-slop review using personas, cognitive load analysis, and heuristics scoring. Best used as a companion to impeccable or after substantial implementation.

Deliver data and ML systems across pipelines, training, evaluation, model-serving, and accelerator-aware workloads while keeping reproducibility, latency, and artifact contracts explicit.

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

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

Deliver platform and delivery guidance for Docker, cloud foundations, infrastructure as code, CI/CD boundaries, observability, rollback, and release safety without claiming orchestration authority.

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.

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 immutable, concurrency-aware services and applications across Elixir, Scala, Haskell, Clojure, Erlang, and F# while keeping runtime and data-model choices explicit.

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.

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

Deliver PHP and Ruby application-platform work across Laravel, Symfony, and Rails while keeping routing, validation, data access, jobs, and service boundaries explicit.

Deliver evidence-oriented QA guidance for browser validation, accessibility, performance, security, and cross-browser coverage while pointing detailed thresholds and examples to shared reference assets.

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

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

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.

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

Deliver Rust systems work across services, CLIs, WASM, and FFI while keeping ownership, async runtime, safety, and performance constraints explicit.