Where to add new code in the Deptex codebase — backend routes, shared libs, DB migrations, worker jobs, frontend pages/components. Read this before adding a feature so it lands in the right place and follows existing conventions.
The Deptex design SYSTEM — real tokens, color rules, and copy-this-file component recipes (buttons, pills, tables, dialogs, states). Read before writing ANY frontend markup; every recipe cites the canonical implementation to copy.
The craft principles behind Deptex UI — hierarchy, restraint, Sentry/Linear benchmarking, state completeness, motion, and the tab-by-tab "filter, don't redesign" working method. Read alongside frontend-design (the concrete system) before planning or reviewing…