Current state layerAdopted
StudioPulse
Borrow the live-status grammar from ursb.me, but keep only four source-backed studio loops.
- Reference
- ursb.me status + data cards
- Target
- Home / About / Lab
Lab
Reusable patterns, interaction proofs, and component registry for the studio. This is where polished pieces become traceable building blocks.
Personal OS Zoo
A living homepage, not a dashboard.
A calibrated transfer from ursb.me: source-backed personal objects, guided questions, compact command grammar, and strict density guardrails.
Objects5
Prompts3
Routes4
Live postureCalm
AI boundaryGuided
Guided personal queryPrototype
AskMeTerminal
Use prompt chips and a terminal-like response to expose site logic without a full AI chat surface.
- Reference
- ursb.me intro chat
- Target
- Home / Contact / Lab
Provenance cueAdopted
DataSourceBadge
Every personal OS module should show where its content comes from and where it can be inspected.
- Reference
- ursb.me Data from ... pattern
- Target
- Projects / Knowledge / Uses
Developer object listPrototype
TerminalObjectList
Use command strings and compact rows for object lists, not decorative fake terminals.
- Reference
- ursb.me command rows
- Target
- Lab / Blog / Knowledge
Anti-dashboard ruleGuardrail
DensityGuardrail
Personal data is allowed only when it opens a real route, source, or decision.
- Reference
- learn-any-uiux flaw ledger
- Target
- Project map / Design system
Phase 515 components9 stable
Component registry
Reusable surfaces with visitor value, source, route, proof, and next-use context.- Categories
- 5
- Experiments
- 7
- Gates
- 4
Experiment timeline
Small interaction bets enter the studio only after they earn a real role.
- 01Component registryStable
Make reusable surfaces searchable, copyable, traceable, and understandable to a first-time visitor.
- 02Preview statesIterating
Let a selected component expose visitor value, source, route, reuse targets, quality proof, and import path.
- 03ComponentPreviewIterating
Render richer component examples when static metadata can no longer explain the interaction contract.
- 04ReactionBarPlanned
Add reader feedback only after content pages have enough repeat traffic to justify it.
- 05Signature interactionsIterating
Prototype Command Trace and Source Hover before any mascot or high-intensity visual effect.
- 06Reading focusIterating
Give long-form writing a subtle active-section lens, stable ref copy, and code-like reading trace.
- 07Personal OS ZooIterating
Calibrate Studio Pulse, guided prompts, source-backed modules, and density guardrails before expanding the homepage.
Quality gates
Rules for keeping the Lab useful as the personal OS grows.
No empty showcase objectsReal usage
Every component in Lab must have an active route, source file, visitor value, and explicit next-use context.
No overflow, no cramped labelsResponsive proof
Desktop and mobile layouts must be checked after every Lab-facing component change.
Docs and code move togetherTraceable decisions
Research, QA, deployment, GitHub, and Feishu records must stay connected to each phase.
No cute-only behaviorUseful interaction
Motion, copy, and micro-interactions must reveal state, reduce effort, or support navigation.