eric-way

Apply Eric's design standards. Use when designing, implementing, or reviewing UI visuals — landing pages, app UI, error feedback, icons, headings, page overscroll, or when choosing a visual direction from a design DNA spec in Eric's style.

Apply Eric's GitHub pull request review operations. Use when operating on GitHub PR changed-file review state, marking safe test-only files viewed, preparing a GitHub PR for review, or using gh GraphQL review mechanics.

Review code using Eric's standards. Use when the user asks for review, code review, frontend review, backend review, desktop review, React review, architecture review, PR review, or asks whether code matches Eric's style; prioritize concrete bugs, risks, overengineering, style drift, and missing focused tests.

Apply Eric's test-writing standards. Use when deciding whether to add tests, choosing unit vs integration coverage, writing focused regression or correctness tests, reviewing tests, or explaining test strategy.

Apply Eric's frontend coding standards. Use when implementing, refactoring, or reviewing frontend web/app UI code, TanStack Query usage, feature-folder organization, styling boundaries, app-vs-website UI decisions, frontend state, or frontend tests in Eric's style. For React-specific components, hooks, providers, memoization, effects, or local reducer work, also use $eric-react.

Stress-test product, technical, and domain-modeling plans before implementation in Eric's style. Use when the user asks to grill, challenge, validate, or sharpen a plan/design/domain model; when terminology, boundaries, invariants, or ADR-worthy decisions are fuzzy; or before implementing a feature where shared understanding matters.

Apply Eric's browser end-to-end testing standards. Use when a task needs a real browser, UI smoke test, screenshot capture, browser bug reproduction, Dockerized browser test run, or agent-browser based verification.

Apply Eric's quality-control standards. Use when setting up or fixing formatter, linter, type-check, compile, test, dependency, security, or CI gates; reproducing quality failures; or choosing boring project quality checks.

Apply Eric's React and TSX component standards. Use when implementing, refactoring, or reviewing React components, hooks, providers, JSX/TSX props, local component state, memoization, effects, or React-specific tests in Eric's style.

Apply Eric's backend coding standards. Use when implementing, refactoring, or reviewing TypeScript or Rust backend code, service/repository boundaries, transport handlers, Hono/Elysia APIs, Drizzle schemas and migrations, Rust domain models, typed errors, validation, adapters, or backend tests in Eric's style.

Apply Eric's desktop app standards. Use when implementing, refactoring, or reviewing Electron, Tauri, desktop renderer, local runtime, packaging, update, window/webview, IPC/router, generated contract, desktop data-fetching, or native integration code in Eric's style.

Apply Eric's JavaScript and TypeScript standards. Use when creating JS/TS/Node projects, installing dependencies, running package scripts, changing package-manager commands, or reviewing npm/pnpm/yarn/bun command usage.