ryux-frontend: Frontend implementation

Group Engineering · Delivery Gate area CODE QUALITY · RX-2.0. Levels are defined in ryux-core.

Connect design decisions to the code that ships them.

1. Detect the stack first: read package.json, the router, the styling approach, and two or three nearby components. Write in that stack. Do not assume React or Tailwind.
2. Semantic HTML and native controls before custom ones.
3. Components split by responsibility; state close to where it is used; derived values instead of duplicated state.
4. Tokens instead of magic numbers; no duplicate styles.
5. No invented logic: prices, limits, and permissions come from data or are marked as assumptions.
6. Dependencies only when they clearly earn their weight.
7. Performance: sized and lazy-loaded media; no heavy libraries for small effects.

Does not cover: visual decisions (see ryux-ui) or component reuse decisions (see ryux-design-system).