# OneOh Design System > The visual design and web development standard shared by every OneOh product. Read it before generating UI or front-end code for any OneOh product, so every product looks and behaves consistently. Each topic exists in Chinese (/llms/zh/) and English (/llms/en/) with identical content. Core rules: monochrome minimal, Apple-inspired; visual hierarchy never uses lines; Tailwind CSS only; bilingual parity; Lighthouse 100 across Performance, Accessibility, Best Practices and SEO. Directory layout: ``` /llms.txt this index /llms//theme.txt design tokens /llms//principles.txt design principles /llms//guidelines.txt visual & web development guidelines /llms//apps.txt application & admin interface guidelines /llms//backend.txt back-office system design (Stripe-aligned) /llms//performance.txt browser metric requirements /llms//testing.txt automated testing constraints = zh | en ``` Suggested reading order: principles → theme → guidelines → apps (for consoles, back offices and dashboards) → backend (for back-office system design) → performance → testing (before writing or running automated tests). ## 中文 - [设计原则](https://oneoh.cloud/llms/zh/principles.txt): 按优先级排列的硬性设计原则 - [视觉主题](https://oneoh.cloud/llms/zh/theme.txt): 颜色、字体、圆角、阴影、图标、标志的设计令牌 - [开发指南](https://oneoh.cloud/llms/zh/guidelines.txt): 技术栈、版式、组件、动效、双语、可访问性、自检清单 - [应用与后台界面](https://oneoh.cloud/llms/zh/apps.txt): 控制台与后台的版式例外、对话框交互、数据表格、表单控件、按钮文案、作业历史 - [后台系统设计](https://oneoh.cloud/llms/zh/backend.txt): 向 Stripe 对齐的资源标识、不可变事件、时间线、请求日志、高频数据分层(Valkey → 数据库 → 归档)、API 约定、系统监控 - [浏览器指标](https://oneoh.cloud/llms/zh/performance.txt): Lighthouse 与 Core Web Vitals 验收标准、实现规则、测量方法 - [测试约束](https://oneoh.cloud/llms/zh/testing.txt): 测试的运行节奏、耗时指标、共享昂贵准备、并行、等待与断言、测试取舍 ## English - [Design principles](https://oneoh.cloud/llms/en/principles.txt): non-negotiable design principles in priority order - [Visual theme](https://oneoh.cloud/llms/en/theme.txt): design tokens for color, type, radius, shadow, icons and logo - [Development guidelines](https://oneoh.cloud/llms/en/guidelines.txt): stack, layout, components, motion, i18n, accessibility, checklist - [Application & admin interfaces](https://oneoh.cloud/llms/en/apps.txt): layout exceptions, dialog interactions, data tables, form controls, button copy and job history for consoles and back offices - [Back-office system design](https://oneoh.cloud/llms/en/backend.txt): Stripe-aligned resource IDs, immutable events, timelines, request logs, high-frequency data tiering (Valkey → database → archives), API conventions and system monitoring - [Browser metrics](https://oneoh.cloud/llms/en/performance.txt): Lighthouse and Core Web Vitals targets, implementation rules, measurement - [Testing constraints](https://oneoh.cloud/llms/en/testing.txt): when to run tests, duration as an acceptance criterion, sharing expensive setup, parallelism, waiting and assertions, what to keep