Studio
Studio/Design engineering

Design engineering, applied.

Start with the user outcome. Studio selects the smallest useful combination of architecture, systems, implementation, and proof, then stops before process becomes friction.

Current program

Renew the Studio platform

A user can understand, choose, and apply Studio’s UI systems without ambiguity, dead controls, inconsistent presentation, or responsive failure.

  1. 01

    Frame the Studio outcome

  2. 02

    Audit Studio as a working product and retire legacy authority

  3. 03

    Repair architecture and flow

  4. 04

    Apply Platform as the complete UI authority

  5. 05

    Map every visible responsibility and critical control

  6. 06

    Render and interact at every kit-swap viewport

  7. 07

    Validate candidate evidence

  8. 08

    Release and recheck the canonical production origin

Choose the capability you need.

The house lens stays constant. Mixes, skills, perspectives, and maintenance only appear when they change the work.

draft1.1.0-draft

Design Engineering Lens

Studio’s unified craft lens for judging interfaces: outcome first, structurally calm, spatially rhythmic, emotionally restrained, technically correct, and easy to recover from.

01

The user outcome is the north star; every visible object must help orientation, action, feedback, or recovery.

02

Structure beats decoration: layout, flow, hierarchy, and disclosure carry more product value than a prettier component.

03

Spatial rhythm is a contract: spacing, alignment, grid, and symmetry must make the screen feel inevitable instead of assembled.

04

Interaction should feel physical and interruptible: motion communicates state, never distracts from it.

05

Polish is correctness: readable type, touch targets, focus, containment, contrast, and empty/error/loading states are not optional.

06

Use the smallest system that gets the user to a delightful outcome; stop before maintenance bloat or diminishing returns.

07

Specificity beats prefab: every interface must make choices that belong to its user, product, content, kit, and context rather than repeating familiar AI defaults.

Active local program

Briarwick

The versioned Domain Journey Assessment preserves Briarwick’s product behavior and authority model while SPATIAL now owns the presentation layer through project-local facades.

prepared · v1.1.0
Operating model

Complex creation platform

Audit and repair product UX
Visual-language intent

SPATIAL

active
  1. 01

    Intent resolves to the correct selected object and Focus Session

  2. 02

    A blocked artifact explains and repairs its prerequisite

  3. 03

    A proof becomes an explicit human decision and intended deliverable

Kit adoption active · production release remains gated
Project program

Prepare the work without starting it.

A Program binds one Mix to a project, kit, and context. It produces a runbook and agent prompt, but no repository write or execution claim.

Capability pool
Anti-Slop Design LawDesign Engineering MaestroOutcome framingContext selectionExperience architectureLayout and flow compositionCanonical component mappingInterface content designKit applicationDesign implementationAccessibility validationResponsive validationVisual quality review
Perspectives
Product designerDesign systems architectFrontend engineerAccessibility engineerFirst-time userDesign Engineering LensProduct owner
Renew the Studio platform

A user can understand, choose, and apply Studio’s UI systems without ambiguity, dead controls, inconsistent presentation, or responsive failure.