What problem does it solve? Teams working on the order-ui React application risk inconsistent code style, naming, and architecture patterns across components, hooks, stores, and API services. This Skill ensures every piece of generated code follows the project's established conventions automatically. ## Core Features & Use Cases - Naming & Structure Rules: Enforces kebab-case file names, PascalCase exports, I-prefixed interfaces, and .store/.type/.schema file suffixes. - Framework Patterns: Provides canonical patterns for React components (FC<Props>), Zustand stores with persist middleware, react-hook-form with Zod resolvers, and React Query mutations. - Import & i18n Standards: Defines ESLint-enforced import ordering and requires react-i18next translation keys instead of hardcoded strings. - Use Case: When asked to create a new printer management feature, the Skill guides generation of printer-card.tsx, use-printer.ts, printer.store.ts, and printer.schema.ts files that all match the existing codebase style. ## Quick Start Write a new Zustand store and hook for managing orders following the project coding conventions.