Cloaked Design System / Review
Put the system to work. A source of truth earns trust in use. Test a real decision, a real implementation and a real handoff, with evidence another person can follow.
Review tasks Report a finding Change the source A WORKING REVIEW Give the system a real task. Choose a case for your role. Follow the current records through a working result, then show where the guidance holds up and where it falls short.
01
Product and design Choose and compose a real flow Design a protected-email flow with invalid input, pending work and successful confirmation.
Expected behavior and evidence Look for Choose Field, Input and Button from current records. Explain component choices and preserve the full state sequence. Bring back A working flow, source version/digest and a list of uncovered requirements. 02
React and coding agents Build beyond the curated examples Implement a metric Card with a delta, sectioned rows and a pressable footer using its current contract.
Expected behavior and evidence Look for Find the exact public API and all named Card stories. Preserve composition constraints, keyboard behavior, accessible list semantics and both themes. Bring back Type-check output, interaction results and a rendered comparison. 03
Vue, Swift and Kotlin Adapt without inventing parity Adapt a labeled input and primary action to the target framework.
Expected behavior and evidence Look for Separate shared design intent from React-specific API. Account for typography scaling, dimensions, safe areas and native semantics. Identify unimplemented adapters and unresolved token conversions. Bring back A compiled consumer, platform-specific accessibility checks and documented differences. 04
Figma and Claude Design Reconcile the design artifact Recreate a Card and form state from the current package and hand it to engineering.
Expected behavior and evidence Look for Use the current semantic token names and component IDs. Record the source version plus design-file/component identifiers. Report differences rather than assuming imported Figma approval establishes parity. Bring back A traceable artifact and a comparison of states, theme values and interactions. 05
Codex, Claude Code, Grok and Cursor Retrieve the same answer in every agent Ask for Card, an invalid input and dark-theme danger text through the available transport.
Expected behavior and evidence Look for Retrieve the same version, digest, specification and token values through JSON/Markdown. Return explicit gaps for unsupported platforms or unknown component/token names. Do not fall back silently to legacy CDS 4.0 values. Bring back The input task, returned component/token IDs, transport and digest. 06
Accessibility and platform reviewers Pressure-test the interaction Navigate search and the component galleries by keyboard, then review Motion with reduced motion and a narrow viewport.
Expected behavior and evidence Look for Focus stays visible and returns correctly when search closes. Every story remains reachable with a useful empty state. Motion starts only through explicit activation and respects preference changes. Bring back Keyboard results, target browser/device, theme, viewport and assistive-technology findings. Review evidence · fill in the result Copy template
{
"component_id": "",
"system_version": "0.2.0-preview.1",
"content_digest": "70ac710f4d22dce040e7ac593379ba8aca9dcb59a0b9c0f839819cae0e2bb721",
"platform": "",
"story_or_state": "",
"viewport_and_theme": "",
"reproduction_steps": "",
"expected_behavior": "",
"actual_behavior": "",
"severity": "",
"evidence": "",
"proposed_fix": ""
} 01 Propose a traceable change Name the user need, affected component/token, current version, changed behavior and impacted platforms. Include before/after states and a migration plan for breaking changes.
02 Review the implementation Change canonical source and its stories/specification together. Regenerate the site and agent records, run the checks, and obtain the required independent review.
03 Release and verify consumers Use the repository release workflow after all gates pass. Verify the deployed site reports the same content digest. Native/Vue/Figma adoption requires its own consumer evidence.
04 Preserve compatibility Deprecate before removing public tokens or APIs. Document replacements and consumer migration evidence. A site deployment does not silently approve or upgrade every downstream application.
This design-owned implementation is ready to try and review. It does not establish product approval. Imported specifications retain their original review status.
Inspect version 0.2.0-preview.1 ↗