Bridge manifest · seed kr-ux-net-07

UX Engineering Courses Bridging Design Systems and Code

This page is the orientation spine for cohort 07-KR. Read it before week zero so critiques stay anchored in shared vocabulary—not personal taste.

System anatomy

We treat systems as layered organisms: semantic tokens, slot contracts, documentation rituals, and release cadences. Each layer gets explicit owners during paired labs so designers learning code and frontend developers improving UI systems stay aligned.

Semantic color ramps with documented intent, not just hex values.
Slot APIs describing default, busy, and error media.
Version notes that call out breaking vs additive changes.

Critique process

Critiques rotate facilitators weekly. Scribes capture decisions in a shared log; timers keep feedback under seven minutes per artifact. Mentors intervene only when evidence is missing—not when they dislike a palette.

Evidence pass

Tokens, motion references, and user snippets pinned before anyone speaks.

Synthesis

Scribe publishes action verbs within 24h so PM tools stay truthful.

Accessibility checks

Accessibility reviewers join twice per program. Checks emphasize keyboard flows, motion reduction, and captioning for async clips—always framed as sprint-ready tasks, not external reviewer theater.

Macro photograph of translucent interface layers stacked like acetate

Capstone previews

Capstones vary by track: token sheets, critique facilitation decks, or refactor plans. Each preview must include a limitation statement—what you did not validate and why—to keep portfolios honest.

Design Systems Anatomy Lab → publishable token sheet + slot contract.
Component Patterns in Production → three documented states with tests.
Portfolio Systems Narrative → two case studies with artifact photos.

Mentor bios (bridge leads)

Haneul Park

Guides token labs and release cadences. Expect blunt questions about naming collisions—bring your lint rules.

Sora Ahn

Leads accessibility reviews with bilingual annotations. Prefers motion notes with easing references, not vague “smooth” labels.

Jisoo Han

Stress-tests component APIs against messy datasets. Bring console errors—she treats them as design material.

Field reference

Editorial still from a recent bridge intensive—used for async briefings, not decoration.

Minimal desk arrangement with keyboard and sketchbook for systems work