Obvious
One clear action per view. Labels say what happens next. Navigation stays reachable at every viewport.
A practical language for the products you prompt into existence: interface, motion, data, backend and the workflow that keeps every build honest.
High-contrast surfaces, one electric accent, direct manipulation and motion that explains what just happened. No ornamental noise. No silent wrong guesses.
One clear action per view. Labels say what happens next. Navigation stays reachable at every viewport.
Controls answer immediately. Drag follows the hand. Pinch and wheel preserve the focal point.
If automation cannot finish, say why and give the manual path. Fallback usefully or fail loudly.
Preview before commitment. Preserve originals. Make undo and recovery part of the design.
Tokens carry the decisions. Components encode the behavior. Desktop, tablet and mobile are designed as real states, not scaled copies.
#B9FF66#090B10#171B24#FF7B88:root {
--ld-accent: #b9ff66;
--ld-radius-l: 24px;
--ld-ease-out: cubic-bezier(.16,1,.3,1);
}Presses acknowledge. Panels orient. Loaders breathe. Gestures stay under the pointer. If movement explains nothing, remove it.
Immediate 0.97 scale response.
Soft ease-out, 10px travel max.
Calm progress without false precision.
A build is complete only when its failure path, responsive states, data policy and live revision have evidence.
User, job, success, devices and risk.
01Routes, states, tokens, schema and boundaries.
02One complete path, UI to database and back.
03Gestures, viewports, offline, vendors and failures.
04Real pixels at 1440, 820 and 390.
05Immutable build, direct routes and smoke proof.
06A modular monolith first. Typed service edges. PostgreSQL with real constraints. Provider code stays replaceable.
Tokens → primitives → feature views
ui/ · features/Pure rules → typed services → validated handlers
domain/ · server/Repositories → PostgreSQL → bounded workers
data/ · infra/Copy it into a build, or give the build brief to your coding agent. Tokens, components, motion, architecture, SQL conventions, backend rules and release checks are included.
Get Lakshan Dev Language 1.0 ↓lakshan-dev-language/
├── styles/ tokens · motion · components
├── docs/ foundations · workflow · architecture
├── database/ schema · conventions
├── backend/ API · security
└── templates/ build brief · release check