What problem does it solve? When adding features to the order-ui codebase, developers often place files in inconsistent locations, breaking the established architecture. This Skill ensures every new API endpoint, page, component, hook, store, schema, or type lands in the correct directory following the project's conventions. ## Core Features & Use Cases - Directory Convention Reference: Documents the full src/ layout covering api/, app/, components/, hooks/, stores/, schemas/, types/, and utils/. - Step-by-Step File Creation Rules: Provides ordered checklists for adding API endpoints, system pages, shared components, Zod schemas, Zustand stores, and TypeScript types, including required barrel exports and route registration. - Printing Subsystem Guidance: Distinguishes the browser print flow (EJS invoice template via window.print) from network printer flows (TSPL/ZPL or ESC/POS print jobs with failure handling). - Use Case: When asked to add a new printer configuration page, the Skill directs creating src/app/system/config files, registering the lazy import in router/loadable.tsx, adding the route constant, and wiring hooks and query keys. ## Quick Start Use the file-structure skill to decide where to place a new chef-area feature component and its hook in the order-ui project.
