@usesketchbook/cli 0.0.0-stage → 0.1.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.claude/commands/add.md +15 -0
- package/.claude/commands/check.md +5 -0
- package/.claude/commands/explain.md +6 -0
- package/.claude/commands/foundations.md +11 -0
- package/.claude/commands/import-tokens.md +15 -0
- package/.claude/commands/init.md +10 -0
- package/.claude/commands/kits.md +6 -0
- package/.claude/commands/roast-foundations.md +10 -0
- package/.claude/commands/start.md +6 -0
- package/.claude/commands/swap.md +6 -0
- package/.claude/commands/sync.md +6 -0
- package/.claude/commands/tour.md +5 -0
- package/.claude/hooks/guard-decisions.mjs +51 -0
- package/.claude/hooks/guard-generated.mjs +63 -0
- package/.claude/hooks/page-outline.mjs +41 -0
- package/.claude/hooks/run.mjs +36 -0
- package/.claude/rules/comment-minimalism.md +7 -0
- package/.claude/rules/contract-first.md +29 -0
- package/.claude/rules/figma-fidelity.md +42 -0
- package/.claude/rules/form-associated-controls.md +87 -0
- package/.claude/rules/no-ai-attribution.md +3 -0
- package/.claude/rules/planning-gate.md +13 -0
- package/.claude/rules/spec-is-source.md +6 -0
- package/.claude/rules/test-first.md +16 -0
- package/.claude/rules/tokens-through-the-harness.md +8 -0
- package/.claude/skills/a11y-checker/SKILL.md +301 -0
- package/.claude/skills/a11y-checker/agents/a11y-auditor.md +18 -0
- package/.claude/skills/a11y-checker/references/self-validation-checklist.md +180 -0
- package/.claude/skills/a11y-checker/references/wcag-checklist.md +141 -0
- package/.claude/skills/component-builder/SKILL.md +124 -0
- package/.claude/skills/component-builder/agents/parity-auditor.md +50 -0
- package/.claude/skills/contract-author/SKILL.md +156 -0
- package/.claude/skills/contract-author/agents/drafter.md +80 -0
- package/.claude/skills/contract-author/agents/extractor.md +62 -0
- package/.claude/skills/contract-author/agents/validator.md +50 -0
- package/.claude/skills/design-figma/SKILL.md +120 -0
- package/.claude/skills/design-figma/references/screenshots/01-guide.png +0 -0
- package/.claude/skills/design-figma/references/screenshots/02-foundations.png +0 -0
- package/.claude/skills/design-figma/references/screenshots/03-icons.png +0 -0
- package/.claude/skills/design-figma/references/screenshots/04-components-actions.png +0 -0
- package/.claude/skills/design-figma/references/screenshots/05-components-toggles-and-selection.png +0 -0
- package/.claude/skills/design-figma/references/screenshots/06-components-text-controls.png +0 -0
- package/.claude/skills/design-figma/references/screenshots/07-components-surfaces.png +0 -0
- package/.claude/skills/design-figma/references/screenshots/08-components-feedback-and-display.png +0 -0
- package/.claude/skills/design-figma/references/screenshots/09-components-navigation-and-disclosure.png +0 -0
- package/.claude/skills/design-figma/references/screenshots/10-components-data-and-layout.png +0 -0
- package/.claude/skills/design-figma/references/screenshots/11-library.png +0 -0
- package/.claude/skills/design-figma/references/screenshots/12-theme-matrix.png +0 -0
- package/.claude/skills/design-figma/references/screenshots/13-patterns.png +0 -0
- package/.claude/skills/design-figma/references/screenshots/README.md +34 -0
- package/.claude/skills/design-figma/references/screenshots/detail/doc-accessibility.png +0 -0
- package/.claude/skills/design-figma/references/screenshots/detail/doc-anatomy-tree.png +0 -0
- package/.claude/skills/design-figma/references/screenshots/detail/doc-header.png +0 -0
- package/.claude/skills/design-figma/references/screenshots/detail/doc-states-grid.png +0 -0
- package/.claude/skills/design-figma/references/screenshots/detail/doc-tokens.png +0 -0
- package/.claude/skills/design-figma/references/screenshots/detail/doc-variants-grid.png +0 -0
- package/.claude/skills/design-figma/references/screenshots/detail/foundation-color.png +0 -0
- package/.claude/skills/design-figma/references/working-method.md +94 -0
- package/.claude/skills/forge-me-a-skill/SKILL.md +178 -0
- package/.claude/skills/forge-me-a-skill/assets/SKILL-TEMPLATE.md +56 -0
- package/.claude/skills/foundations/SKILL.md +216 -0
- package/.claude/skills/foundations/agents/foundations-critic.md +37 -0
- package/.claude/skills/foundations/agents/token-mapper.md +40 -0
- package/.claude/skills/foundations/references/border-width.md +49 -0
- package/.claude/skills/foundations/references/color.md +86 -0
- package/.claude/skills/foundations/references/contrast.md +49 -0
- package/.claude/skills/foundations/references/density.md +44 -0
- package/.claude/skills/foundations/references/elevation.md +44 -0
- package/.claude/skills/foundations/references/iconography.md +44 -0
- package/.claude/skills/foundations/references/layout-grid.md +49 -0
- package/.claude/skills/foundations/references/motion.md +62 -0
- package/.claude/skills/foundations/references/opacity.md +48 -0
- package/.claude/skills/foundations/references/radius.md +48 -0
- package/.claude/skills/foundations/references/semantic-naming.md +58 -0
- package/.claude/skills/foundations/references/spacing-grid.md +64 -0
- package/.claude/skills/foundations/references/typography.md +74 -0
- package/.claude/skills/foundations/references/z-index.md +43 -0
- package/.claude/skills/hammock/SKILL.md +261 -0
- package/.claude/skills/hammock/assets/DEBT-LOG-TEMPLATE.md +11 -0
- package/.claude/skills/hammock/assets/DECISION-LADDER.md +27 -0
- package/.claude/skills/hammock/hooks/hammock-activate.mjs +33 -0
- package/.claude/skills/hammock/hooks/hammock-audit-runner.mjs +38 -0
- package/.claude/skills/hammock/hooks/hammock-config.mjs +78 -0
- package/.claude/skills/hammock/hooks/hammock-gate.mjs +43 -0
- package/.claude/skills/hammock/hooks/hammock-instructions.mjs +37 -0
- package/.claude/skills/hammock/hooks/hammock-mode-tracker.mjs +66 -0
- package/.claude/skills/hammock/hooks/hammock-runtime.mjs +59 -0
- package/.claude/skills/hammock/hooks/hammock-stop-gate.mjs +20 -0
- package/.claude/skills/hammock/hooks/hammock-subagent.mjs +23 -0
- package/.claude/skills/hammock/scripts/audit-simplicity.sh +91 -0
- package/.claude/skills/kits/SKILL.md +120 -0
- package/.claude/skills/onboarding/SKILL.md +171 -0
- package/.claude/skills/playwright-worker/SKILL.md +266 -0
- package/.claude/skills/review-rangers/SKILL.md +343 -0
- package/.claude/skills/review-rangers/assets/committee-member-template.md +44 -0
- package/.claude/skills/review-rangers/assets/mender-template.md +78 -0
- package/.claude/skills/review-rangers/assets/safety-guard-template.md +43 -0
- package/.claude/skills/security-guardian/SKILL.md +215 -0
- package/.claude/skills/security-guardian/assets/SECURE-CONTRIBUTING-CHECKLIST.md +67 -0
- package/.claude/skills/security-guardian/scripts/security-scan.sh +126 -0
- package/.claude/skills/web-components-best-practices/SKILL.md +154 -0
- package/.claude/skills/web-components-best-practices/references/api-and-interop-conventions.md +137 -0
- package/.claude/skills/web-components-best-practices/references/composition-patterns.md +178 -0
- package/.claude/skills/web-components-best-practices/references/performance-rules.md +196 -0
- package/.claude/skills/web-components-best-practices/references/platform-fundamentals.md +308 -0
- package/.githooks/commit-msg +9 -0
- package/.githooks/pre-commit +23 -0
- package/.githooks/pre-push +25 -0
- package/LICENSE +21 -0
- package/README.md +205 -2
- package/THIRD_PARTY_NOTICES.md +28 -0
- package/brand/sketchbook-icon.png +0 -0
- package/brand/sketchbook-icon.svg +2839 -0
- package/dist/index.d.ts +2226 -0
- package/dist/index.js +10589 -0
- package/dist/sketchbook.js +4798 -0
- package/docs/agent-compatibility.md +142 -0
- package/docs/cli.md +715 -0
- package/generated/css/fonts.css +2 -0
- package/generated/css/tokens.css +1245 -0
- package/generated/types/api.d.ts +138 -0
- package/generated/types/brand-config.d.ts +254 -0
- package/generated/types/contract.d.ts +197 -0
- package/generated/types/figma-practices.d.ts +26 -0
- package/generated/types/harness-config.d.ts +104 -0
- package/generated/types/registry.d.ts +16 -0
- package/harness/adapters/design/figma/compare.d.mts +1 -0
- package/harness/adapters/design/figma/compare.mjs +42 -0
- package/harness/adapters/design/figma/docs.d.mts +62 -0
- package/harness/adapters/design/figma/docs.mjs +679 -0
- package/harness/adapters/design/figma/icons.d.mts +3 -0
- package/harness/adapters/design/figma/icons.mjs +92 -0
- package/harness/adapters/design/figma/library.d.mts +51 -0
- package/harness/adapters/design/figma/library.mjs +595 -0
- package/harness/adapters/design/figma/patterns.d.mts +2 -0
- package/harness/adapters/design/figma/patterns.mjs +351 -0
- package/harness/adapters/design/figma/sync.d.mts +24 -0
- package/harness/adapters/design/figma/sync.mjs +216 -0
- package/harness/adapters/design/figma/variables.d.mts +136 -0
- package/harness/adapters/design/figma/variables.mjs +532 -0
- package/harness/adapters/design/figma/verify-runtime.mjs +19 -0
- package/harness/adapters/design/figma/zero.d.mts +9 -0
- package/harness/adapters/design/figma/zero.mjs +37 -0
- package/harness/agent/gemini-guard.d.mts +2 -0
- package/harness/agent/gemini-guard.mjs +95 -0
- package/harness/build/fonts.d.mts +14 -0
- package/harness/build/fonts.mjs +69 -0
- package/harness/build/index.d.mts +11 -0
- package/harness/build/index.mjs +35 -0
- package/harness/build/tokens-plain.d.mts +9 -0
- package/harness/build/tokens-plain.mjs +59 -0
- package/harness/build/tokens.d.mts +9 -0
- package/harness/build/tokens.mjs +76 -0
- package/harness/catalog/accordion/files/3386f68432b4c28277bb +8 -0
- package/harness/catalog/accordion/files/458f73bbdb2280a93792 +280 -0
- package/harness/catalog/accordion/files/4d7c5147b9926261b70a +41 -0
- package/harness/catalog/accordion/files/592212fb5c728cb562af +6 -0
- package/harness/catalog/accordion/files/5ae431f76cae09a91d25 +4 -0
- package/harness/catalog/accordion/files/5bbb11e9f8095ed054ff +96 -0
- package/harness/catalog/accordion/files/5fab7a341aef28356da3 +6 -0
- package/harness/catalog/accordion/files/736c8824f1022b4df6c8 +69 -0
- package/harness/catalog/accordion/files/76b5f3980a78fedb3311 +59 -0
- package/harness/catalog/accordion/files/76c16a81d99e363e956b +22 -0
- package/harness/catalog/accordion/files/7c3465ac910eaf16830a +6 -0
- package/harness/catalog/accordion/files/a025a789d6e548428b3b +47 -0
- package/harness/catalog/accordion/files/a632d819d1fa6422ca28 +108 -0
- package/harness/catalog/accordion/files/af4fe412342068d19100 +96 -0
- package/harness/catalog/accordion/files/b5152e94f69d686f66d4 +464 -0
- package/harness/catalog/accordion/files/c27cf9f1ab09bec315aa +8 -0
- package/harness/catalog/accordion/files/d404485af0224293b2d6 +69 -0
- package/harness/catalog/accordion/files/ec36cfafc8906915188a +8 -0
- package/harness/catalog/accordion/files/fe2916946450260c403a +23 -0
- package/harness/catalog/accordion/files/fe37ab65a9323b9b828b +10 -0
- package/harness/catalog/accordion/manifest.json +93 -0
- package/harness/catalog/alert/files/16a43bc5189d44e14292 +299 -0
- package/harness/catalog/alert/files/16eb63459233148e6a59 +42 -0
- package/harness/catalog/alert/files/47cebb310b907f59b96f +2 -0
- package/harness/catalog/alert/files/52150c86b71449888f16 +3 -0
- package/harness/catalog/alert/files/52cc35ea0d55324a9212 +4 -0
- package/harness/catalog/alert/files/5c30877339f63c1098e7 +3 -0
- package/harness/catalog/alert/files/67630242c9c940463652 +4 -0
- package/harness/catalog/alert/files/6ae7cb35ae4d69883a3b +79 -0
- package/harness/catalog/alert/files/6b631857d33e60b3b59e +177 -0
- package/harness/catalog/alert/files/919ddd492eb1fa90aadc +21 -0
- package/harness/catalog/alert/files/9cf980ba345db73d493b +41 -0
- package/harness/catalog/alert/files/a24ca0bc70f381d50059 +8 -0
- package/harness/catalog/alert/files/acbff53556d78aa71c4a +17 -0
- package/harness/catalog/alert/files/b1f8249847af028c520e +49 -0
- package/harness/catalog/alert/files/be66155fe522eb0f75e4 +80 -0
- package/harness/catalog/alert/files/d9376dbfc0c412d43f02 +21 -0
- package/harness/catalog/alert/files/e392d4a74e9d1b717ee1 +21 -0
- package/harness/catalog/alert/manifest.json +91 -0
- package/harness/catalog/aspect-ratio/files/19788b65a76cdaec18bf +1 -0
- package/harness/catalog/aspect-ratio/files/209c5411dde91bdcc849 +40 -0
- package/harness/catalog/aspect-ratio/files/2591d39bae9388ba807b +74 -0
- package/harness/catalog/aspect-ratio/files/4402c050863e9c25c737 +1 -0
- package/harness/catalog/aspect-ratio/files/836f9ffafb34278fe961 +73 -0
- package/harness/catalog/aspect-ratio/files/9078421b339ea5791f40 +32 -0
- package/harness/catalog/aspect-ratio/files/9f8655de70ea15e3229d +1 -0
- package/harness/catalog/aspect-ratio/files/b1beccd5cb1056d38428 +33 -0
- package/harness/catalog/aspect-ratio/files/d6fdd5d41eb32b1d9fd3 +159 -0
- package/harness/catalog/aspect-ratio/files/de9fd92e0ba9ea351caf +11 -0
- package/harness/catalog/aspect-ratio/files/fdf6f2d2beefd1d1dbe3 +19 -0
- package/harness/catalog/aspect-ratio/manifest.json +65 -0
- package/harness/catalog/avatar/files/014a11e7ae821825d703 +136 -0
- package/harness/catalog/avatar/files/0790f7bde37e48018f0c +6 -0
- package/harness/catalog/avatar/files/31b79bb9dfa043d497be +47 -0
- package/harness/catalog/avatar/files/51b9201acb088b52f64e +36 -0
- package/harness/catalog/avatar/files/539b1f887a74e5bcf719 +425 -0
- package/harness/catalog/avatar/files/5715cc2214da4f2d82aa +2 -0
- package/harness/catalog/avatar/files/5d1303dddb9208b8a106 +275 -0
- package/harness/catalog/avatar/files/65cc7536672c4026ea82 +10 -0
- package/harness/catalog/avatar/files/7054042709566df6d007 +46 -0
- package/harness/catalog/avatar/files/7384dd119b51fe23c6b6 +40 -0
- package/harness/catalog/avatar/files/89469dcd24022d7663b5 +18 -0
- package/harness/catalog/avatar/files/9029ce733b07f6335348 +61 -0
- package/harness/catalog/avatar/files/9d2ba42e187abe3a8145 +3 -0
- package/harness/catalog/avatar/files/9f6b4305e38cec8b8e14 +7 -0
- package/harness/catalog/avatar/files/a0bb48cb59aeb92c3810 +39 -0
- package/harness/catalog/avatar/files/a451ea354f9f77d8987d +8 -0
- package/harness/catalog/avatar/files/a9379bafbdd4b5b5d695 +67 -0
- package/harness/catalog/avatar/files/bff4bf72e38de7673f8e +1 -0
- package/harness/catalog/avatar/files/d3f78e882bc36f721115 +2 -0
- package/harness/catalog/avatar/files/d7e47a33b128e0e03ab7 +41 -0
- package/harness/catalog/avatar/files/e40b957b14019e761505 +80 -0
- package/harness/catalog/avatar/manifest.json +97 -0
- package/harness/catalog/badge/files/0018ed707d23b776b3b9 +346 -0
- package/harness/catalog/badge/files/28005cb14bde099080db +101 -0
- package/harness/catalog/badge/files/2a11f46e7524cfc8099b +38 -0
- package/harness/catalog/badge/files/2d62b3998a30444f4ebe +6 -0
- package/harness/catalog/badge/files/36c7e1d9da83aff58801 +1 -0
- package/harness/catalog/badge/files/58f7c66681cbe255fe9f +188 -0
- package/harness/catalog/badge/files/67b07d31508de5e0bb09 +6 -0
- package/harness/catalog/badge/files/8c4e02e4ba38e936bcc9 +1 -0
- package/harness/catalog/badge/files/920ec5021787522eafbb +1 -0
- package/harness/catalog/badge/files/9a8a242933ea67a605c2 +1 -0
- package/harness/catalog/badge/files/ae17c9db8f67fddf17e4 +92 -0
- package/harness/catalog/badge/files/b4fd13485d1010240f16 +43 -0
- package/harness/catalog/badge/files/cf52421cee4f018981d3 +37 -0
- package/harness/catalog/badge/files/ddac5819e1ed88cb2e03 +12 -0
- package/harness/catalog/badge/manifest.json +69 -0
- package/harness/catalog/breadcrumb/files/10c965db958092f69cca +26 -0
- package/harness/catalog/breadcrumb/files/17521ad2cbc3514221af +7 -0
- package/harness/catalog/breadcrumb/files/24012e0492e093ddee3f +21 -0
- package/harness/catalog/breadcrumb/files/269b4f59060369e2689d +10 -0
- package/harness/catalog/breadcrumb/files/2991c2998d868bde74af +50 -0
- package/harness/catalog/breadcrumb/files/551a25d7280214170b8c +93 -0
- package/harness/catalog/breadcrumb/files/78f75efba91a8ad5f90f +24 -0
- package/harness/catalog/breadcrumb/files/8083e6bfcb1cebb4f9af +26 -0
- package/harness/catalog/breadcrumb/files/810adc630d7d7d41f42d +8 -0
- package/harness/catalog/breadcrumb/files/90712a337d693eacb94d +415 -0
- package/harness/catalog/breadcrumb/files/9bdd89a2adc4b6878b6f +27 -0
- package/harness/catalog/breadcrumb/files/a8692cf836f911223481 +79 -0
- package/harness/catalog/breadcrumb/files/ae82c56d4144711f9ab5 +207 -0
- package/harness/catalog/breadcrumb/files/b5c54c838715e9cd134a +6 -0
- package/harness/catalog/breadcrumb/files/b8b4c12d89f8ab647b5e +30 -0
- package/harness/catalog/breadcrumb/files/c2e3f8f6e4cb9fc735a8 +21 -0
- package/harness/catalog/breadcrumb/files/d713aa4dccbb037a0e12 +26 -0
- package/harness/catalog/breadcrumb/files/f47fc1574cfce8f9448b +66 -0
- package/harness/catalog/breadcrumb/files/f5cc0c4e34882f901b1a +8 -0
- package/harness/catalog/breadcrumb/manifest.json +89 -0
- package/harness/catalog/button/files/0cff7f90b517fc2c5a87 +5 -0
- package/harness/catalog/button/files/0d1f72f94e7ce318e921 +76 -0
- package/harness/catalog/button/files/1a21ad2c3bcaad6b4114 +1 -0
- package/harness/catalog/button/files/1b6ed7bb8c564c65bbaa +107 -0
- package/harness/catalog/button/files/23017794095f7b922f0b +1 -0
- package/harness/catalog/button/files/2460af04d1ef41c23154 +246 -0
- package/harness/catalog/button/files/284457fc8187e1fdbf44 +40 -0
- package/harness/catalog/button/files/506cb8a95609ba0d2d3a +1 -0
- package/harness/catalog/button/files/5803b77577535ac55a89 +44 -0
- package/harness/catalog/button/files/5854b02c74605818b042 +1 -0
- package/harness/catalog/button/files/5e1469fe306037cd9573 +1 -0
- package/harness/catalog/button/files/609be73e1c7a8bcdc550 +1 -0
- package/harness/catalog/button/files/66bb1fb61fe6aad35c1c +1 -0
- package/harness/catalog/button/files/6b986f514e833629d08a +56 -0
- package/harness/catalog/button/files/962687149a672a920383 +197 -0
- package/harness/catalog/button/files/d61eff9f7bd5360fe661 +1 -0
- package/harness/catalog/button/files/d6888f505d4934c73e87 +573 -0
- package/harness/catalog/button/files/e6f6ca2db758ab78f21d +1 -0
- package/harness/catalog/button/files/f328806fe07f25cdd07a +177 -0
- package/harness/catalog/button/manifest.json +93 -0
- package/harness/catalog/button-group/files/0044c16e6d6408d70f97 +21 -0
- package/harness/catalog/button-group/files/322bb11b902b9b5e38f4 +3 -0
- package/harness/catalog/button-group/files/47d4b9403faec8dec952 +78 -0
- package/harness/catalog/button-group/files/4bda2f3cc2a97b49bf59 +51 -0
- package/harness/catalog/button-group/files/6afe96e91fc22fd70152 +4 -0
- package/harness/catalog/button-group/files/7474213871cfec7877de +61 -0
- package/harness/catalog/button-group/files/7c7ad2130eddf9a1513b +16 -0
- package/harness/catalog/button-group/files/80dc20a145bf1531dba0 +270 -0
- package/harness/catalog/button-group/files/91da6c854f746349f833 +4 -0
- package/harness/catalog/button-group/files/a33602cbe19396ffaeed +4 -0
- package/harness/catalog/button-group/files/b8999a731d121b733b2a +21 -0
- package/harness/catalog/button-group/files/c3af09f47753a0346516 +2 -0
- package/harness/catalog/button-group/files/d27c685fdbf67bd48901 +118 -0
- package/harness/catalog/button-group/files/d7e1964ea5ad56231d79 +155 -0
- package/harness/catalog/button-group/files/f01251791f5d7d6c788f +59 -0
- package/harness/catalog/button-group/manifest.json +85 -0
- package/harness/catalog/card/files/06ad3458251f83352e77 +5 -0
- package/harness/catalog/card/files/18fbc68e099aee86c684 +10 -0
- package/harness/catalog/card/files/216f192af043ae2ff617 +12 -0
- package/harness/catalog/card/files/3017f6933cd6283eb287 +27 -0
- package/harness/catalog/card/files/34e2673bc64b4a8ff39b +21 -0
- package/harness/catalog/card/files/3a96ab06d75a85124b5c +26 -0
- package/harness/catalog/card/files/3e54fb5eea171a3ceaad +21 -0
- package/harness/catalog/card/files/4aa88fa70afaceb9a9c7 +129 -0
- package/harness/catalog/card/files/51aab65ffd59c813f578 +1 -0
- package/harness/catalog/card/files/54df6b8d56bd1617895c +21 -0
- package/harness/catalog/card/files/58d44e64ec398d29b56f +7 -0
- package/harness/catalog/card/files/5ef69696b5505bcb1141 +4 -0
- package/harness/catalog/card/files/6d671f1ec19ae75aa88c +73 -0
- package/harness/catalog/card/files/96d54fab0818dfa63590 +21 -0
- package/harness/catalog/card/files/9e14107badcfb8170367 +40 -0
- package/harness/catalog/card/files/a2d5bf1b906370fca975 +21 -0
- package/harness/catalog/card/files/d1ac11b32e7096b3a30c +77 -0
- package/harness/catalog/card/files/d6e226f85f6fc54b0843 +280 -0
- package/harness/catalog/card/files/f31279c9c4b076d443e4 +45 -0
- package/harness/catalog/card/manifest.json +95 -0
- package/harness/catalog/checkbox/files/0283c841689d3ff22707 +2 -0
- package/harness/catalog/checkbox/files/032a72d3b72243fb1727 +131 -0
- package/harness/catalog/checkbox/files/081ef8a0412aab604edd +200 -0
- package/harness/catalog/checkbox/files/094fcc1fb431fef1a872 +2 -0
- package/harness/catalog/checkbox/files/0bf1d698bdc46c1d48d7 +3 -0
- package/harness/catalog/checkbox/files/1c5b1af093b60c82b66f +128 -0
- package/harness/catalog/checkbox/files/3c6f39c5e3fb569afef1 +1 -0
- package/harness/catalog/checkbox/files/46d2afe4c15499ae96e9 +449 -0
- package/harness/catalog/checkbox/files/544c5ff7f9890dad205e +4 -0
- package/harness/catalog/checkbox/files/61cfac6c6dc653b57285 +2 -0
- package/harness/catalog/checkbox/files/6b5bfa718a15d2057b59 +4 -0
- package/harness/catalog/checkbox/files/6cbd9776d028f943b331 +4 -0
- package/harness/catalog/checkbox/files/73a07a998134dacd7693 +19 -0
- package/harness/catalog/checkbox/files/7d229530ecebdd879488 +60 -0
- package/harness/catalog/checkbox/files/865113d4527ee380dd0e +3 -0
- package/harness/catalog/checkbox/files/8a74f72a3a84af71476b +92 -0
- package/harness/catalog/checkbox/files/8b37e9d23015ab5cfe0d +2 -0
- package/harness/catalog/checkbox/files/95c5c2505dd092c9f742 +2 -0
- package/harness/catalog/checkbox/files/b86afb2a41ded28f69cb +62 -0
- package/harness/catalog/checkbox/files/d08b3c8bc03cafe6db78 +2 -0
- package/harness/catalog/checkbox/manifest.json +97 -0
- package/harness/catalog/collapsible/files/0ef860186a5d77f0a02c +19 -0
- package/harness/catalog/collapsible/files/10acfcd2eebb1f54921e +62 -0
- package/harness/catalog/collapsible/files/1ecfe2f1f1d99815477f +7 -0
- package/harness/catalog/collapsible/files/30c5ce1473315a1690d8 +154 -0
- package/harness/catalog/collapsible/files/4d256e6719507cfe8374 +4 -0
- package/harness/catalog/collapsible/files/563ee7ce5fce1f77ee5f +4 -0
- package/harness/catalog/collapsible/files/80a66bc01fbd7557bc5c +7 -0
- package/harness/catalog/collapsible/files/902584654862eec8d0f0 +56 -0
- package/harness/catalog/collapsible/files/90fb6b218f5837e2b9af +4 -0
- package/harness/catalog/collapsible/files/91d5114689dc3d3813fc +31 -0
- package/harness/catalog/collapsible/files/93f866f818a699d0d579 +88 -0
- package/harness/catalog/collapsible/files/996628c9381baa5dd9a2 +42 -0
- package/harness/catalog/collapsible/files/a38a70b8f5bd307fb7ec +3 -0
- package/harness/catalog/collapsible/files/b1d517e0bb72963d6efe +63 -0
- package/harness/catalog/collapsible/files/bc6adfb746c3e16ed828 +1 -0
- package/harness/catalog/collapsible/files/e8da0cd63c0b7de97808 +50 -0
- package/harness/catalog/collapsible/files/ea39495978fcf333dbc3 +10 -0
- package/harness/catalog/collapsible/files/f26dc650128b402e1f3e +308 -0
- package/harness/catalog/collapsible/manifest.json +85 -0
- package/harness/catalog/command/files/0045480291f5bcda1ed0 +134 -0
- package/harness/catalog/command/files/0921b5a7161362e4aa0b +8 -0
- package/harness/catalog/command/files/1760a0a4a6d9b15611fb +27 -0
- package/harness/catalog/command/files/388b9f83faadc3d8a362 +27 -0
- package/harness/catalog/command/files/38d604b586eb1cbe1097 +11 -0
- package/harness/catalog/command/files/3a0c6f69905ab1130fdf +11 -0
- package/harness/catalog/command/files/456e5a0414963d6ad66c +599 -0
- package/harness/catalog/command/files/64edd35c308b3381280b +30 -0
- package/harness/catalog/command/files/6c02d111b386d13fb42a +81 -0
- package/harness/catalog/command/files/732b73ef77332148d537 +11 -0
- package/harness/catalog/command/files/78882bb1d7f63990f8f3 +34 -0
- package/harness/catalog/command/files/7919eff639d8d4a7a256 +11 -0
- package/harness/catalog/command/files/7b73f21bcb5aeebb9d03 +1 -0
- package/harness/catalog/command/files/7b947271b77c5c2e6cbe +60 -0
- package/harness/catalog/command/files/7e6923a2a26e59263a69 +131 -0
- package/harness/catalog/command/files/7f21e62085004b5eb6c9 +161 -0
- package/harness/catalog/command/files/81ccfcb263444082e797 +716 -0
- package/harness/catalog/command/files/825c406546cdca148c9e +177 -0
- package/harness/catalog/command/files/92c96df2ebb179f5316c +29 -0
- package/harness/catalog/command/files/95ffd3cdb86f53120c3a +63 -0
- package/harness/catalog/command/files/a193dbe4cee5f63a29b7 +33 -0
- package/harness/catalog/command/files/b932ab68d82bce66de9c +56 -0
- package/harness/catalog/command/files/d301eb28bc3eb9808c69 +7 -0
- package/harness/catalog/command/files/e2f22dbe376ac580dd4f +11 -0
- package/harness/catalog/command/files/ff05f6bdc626c33bff6d +3 -0
- package/harness/catalog/command/manifest.json +121 -0
- package/harness/catalog/dialog/files/033143a3f05a03f9f557 +21 -0
- package/harness/catalog/dialog/files/0ba6cb9c741f4d6cc29f +1 -0
- package/harness/catalog/dialog/files/14e66fa2f397d81a4b5a +6 -0
- package/harness/catalog/dialog/files/15288bbad2fe7f0623e6 +557 -0
- package/harness/catalog/dialog/files/1607fa09941fa5b61b53 +1 -0
- package/harness/catalog/dialog/files/1ed1da7f60f54af79479 +21 -0
- package/harness/catalog/dialog/files/225b9e06f0defd4497a0 +151 -0
- package/harness/catalog/dialog/files/2eeaa795a0cfde395eb0 +30 -0
- package/harness/catalog/dialog/files/308156c5a7b6cfd183c7 +12 -0
- package/harness/catalog/dialog/files/3d71ca97986f4a6aa575 +29 -0
- package/harness/catalog/dialog/files/52461a94deafc1ddbb9e +1 -0
- package/harness/catalog/dialog/files/6595bcd27d3f2570d8fe +8 -0
- package/harness/catalog/dialog/files/6d2764adad162ecaf567 +1 -0
- package/harness/catalog/dialog/files/6f633326e4a606394eb9 +1 -0
- package/harness/catalog/dialog/files/73841e4e2d52a9ce1739 +99 -0
- package/harness/catalog/dialog/files/95a098053c36283f35ba +706 -0
- package/harness/catalog/dialog/files/96b143a067ceb693bbc2 +1 -0
- package/harness/catalog/dialog/files/a7247129c0b4c3f2809a +10 -0
- package/harness/catalog/dialog/files/ae31f52c79fac0a4a415 +21 -0
- package/harness/catalog/dialog/files/b0df9c2c22c03da30f17 +12 -0
- package/harness/catalog/dialog/files/bb1d44dcb521ae95d625 +30 -0
- package/harness/catalog/dialog/files/be32860a4c355d40cba1 +169 -0
- package/harness/catalog/dialog/files/beb1ca0148c74df4adae +79 -0
- package/harness/catalog/dialog/files/c14b3ca0336a4dfd750c +53 -0
- package/harness/catalog/dialog/files/d1612776ba9473008a59 +1 -0
- package/harness/catalog/dialog/files/ea2b7035753857ef50b3 +88 -0
- package/harness/catalog/dialog/files/f844b44e34e2bbd10ce8 +148 -0
- package/harness/catalog/dialog/manifest.json +127 -0
- package/harness/catalog/direction/files/02506a3763c0825c1b2e +4 -0
- package/harness/catalog/direction/files/02cfc0e8be9401edca36 +76 -0
- package/harness/catalog/direction/files/103e6063fccaaf929d1b +26 -0
- package/harness/catalog/direction/files/255fe8b7f16e99e2b8dd +91 -0
- package/harness/catalog/direction/files/75f8f89d2292a8284167 +1 -0
- package/harness/catalog/direction/files/8b99e167ec2c974cc2a9 +7 -0
- package/harness/catalog/direction/files/8fca474498a374fe7da7 +18 -0
- package/harness/catalog/direction/files/c69ce45deb5ff6ef0953 +155 -0
- package/harness/catalog/direction/files/e953ad5071ef37e0b922 +16 -0
- package/harness/catalog/direction/files/ee8a89015d44a06d8310 +51 -0
- package/harness/catalog/direction/files/f4dcc74509fba14c2f9b +32 -0
- package/harness/catalog/direction/manifest.json +64 -0
- package/harness/catalog/empty/files/12d5b75e9a7e69f7ebf3 +21 -0
- package/harness/catalog/empty/files/26c34047865703e941ae +21 -0
- package/harness/catalog/empty/files/584ac0d314cc5b04bd28 +75 -0
- package/harness/catalog/empty/files/61ec4e1f6bf74d4ea2e1 +3 -0
- package/harness/catalog/empty/files/69428ce8fd6924fe5c93 +4 -0
- package/harness/catalog/empty/files/6adc280f5247c6c59c04 +21 -0
- package/harness/catalog/empty/files/8bfb9f9a62a0adc52b29 +35 -0
- package/harness/catalog/empty/files/93bd9aa2a51cd2be900a +128 -0
- package/harness/catalog/empty/files/94eb6f0ebcb67e5ff82e +12 -0
- package/harness/catalog/empty/files/97c8f20352efd114453f +6 -0
- package/harness/catalog/empty/files/a36428ac1e039fa1ac08 +3 -0
- package/harness/catalog/empty/files/ad3c27417ff9f17d29c5 +21 -0
- package/harness/catalog/empty/files/b26b9b829d659c172afa +21 -0
- package/harness/catalog/empty/files/b531aec20772267bb1f0 +1 -0
- package/harness/catalog/empty/files/bf9f7c6d54893538934d +26 -0
- package/harness/catalog/empty/files/cc3b7ef917a187686d23 +92 -0
- package/harness/catalog/empty/files/efeb91d03e24e277c4a1 +299 -0
- package/harness/catalog/empty/files/f27a2ed4bc56de043dbd +55 -0
- package/harness/catalog/empty/manifest.json +87 -0
- package/harness/catalog/field/files/14f219e6b80e72e5c3bb +34 -0
- package/harness/catalog/field/files/1b59c2405c87e7172caa +4 -0
- package/harness/catalog/field/files/1de85848606fad492a52 +534 -0
- package/harness/catalog/field/files/245f94156a26a4f69b7d +9 -0
- package/harness/catalog/field/files/2b3cd42da8f154db221c +4 -0
- package/harness/catalog/field/files/35b3f29fc98483b4c80f +38 -0
- package/harness/catalog/field/files/475a598be605bbadb769 +4 -0
- package/harness/catalog/field/files/4a38ec4400cf7d298644 +21 -0
- package/harness/catalog/field/files/4ff10d27a916182c1738 +9 -0
- package/harness/catalog/field/files/652049b91be028101cf9 +21 -0
- package/harness/catalog/field/files/6adeae4eb58d78ea9f30 +95 -0
- package/harness/catalog/field/files/6e692b7158a826bbb947 +4 -0
- package/harness/catalog/field/files/7d6b6a3ab1daebba7cb8 +97 -0
- package/harness/catalog/field/files/98f5ffd7c690677bb092 +5 -0
- package/harness/catalog/field/files/ab27c00164159d57b0dd +30 -0
- package/harness/catalog/field/files/afa021fa0a297ad1fe23 +21 -0
- package/harness/catalog/field/files/aff6e70b48d33ce18356 +58 -0
- package/harness/catalog/field/files/b17a1e6ee355f3a6196f +21 -0
- package/harness/catalog/field/files/b4cce9970056872f98aa +39 -0
- package/harness/catalog/field/files/bb70812c4e051c4d318c +101 -0
- package/harness/catalog/field/files/cf526a36ce845c550978 +6 -0
- package/harness/catalog/field/files/d413eed2b0a4706d87dd +9 -0
- package/harness/catalog/field/files/d55783ea6832f7a48404 +183 -0
- package/harness/catalog/field/files/de723d33b8f3cc3a1ae6 +17 -0
- package/harness/catalog/field/files/f386f1400a0c1d04e219 +125 -0
- package/harness/catalog/field/manifest.json +115 -0
- package/harness/catalog/index.json +54 -0
- package/harness/catalog/input/files/01c8e9c337c9d9ec3b56 +157 -0
- package/harness/catalog/input/files/0374ecc1c70cfbeb5477 +94 -0
- package/harness/catalog/input/files/130029580ebe2410854d +62 -0
- package/harness/catalog/input/files/2e4f4f932ac53b3ed0f8 +92 -0
- package/harness/catalog/input/files/3928022bc657cfd275c8 +473 -0
- package/harness/catalog/input/files/45aea55aede567795da6 +38 -0
- package/harness/catalog/input/files/5d05203ba89dfffc5672 +5 -0
- package/harness/catalog/input/files/63785352f2e1083afad0 +3 -0
- package/harness/catalog/input/files/74013a390a4a820194f2 +56 -0
- package/harness/catalog/input/files/7f39502d3fb907d14714 +3 -0
- package/harness/catalog/input/files/9a072aedd4835d8302d0 +3 -0
- package/harness/catalog/input/files/a310eb8a50ef91f63464 +5 -0
- package/harness/catalog/input/files/ab7eccdc1ed0cf9e8d2a +3 -0
- package/harness/catalog/input/files/b8f3934a052b4cb749da +1 -0
- package/harness/catalog/input/files/bfe480c8577cbf45dd5e +142 -0
- package/harness/catalog/input/files/c7482318af88664d7dcc +4 -0
- package/harness/catalog/input/files/f3896b6e9d2f4b53cc9c +3 -0
- package/harness/catalog/input/manifest.json +85 -0
- package/harness/catalog/input-group/files/00e50817aba414d9cd26 +3 -0
- package/harness/catalog/input-group/files/076784d5a4d149a44604 +3 -0
- package/harness/catalog/input-group/files/1d30879d1a4a72c33976 +3 -0
- package/harness/catalog/input-group/files/25d5b296213c3ac34b13 +2 -0
- package/harness/catalog/input-group/files/2da272dd920815dd5684 +447 -0
- package/harness/catalog/input-group/files/2e421f3362b888bab4d0 +5 -0
- package/harness/catalog/input-group/files/31c747b37bb6426dbbb7 +5 -0
- package/harness/catalog/input-group/files/41ec212906edd2e8e5f6 +98 -0
- package/harness/catalog/input-group/files/4f58492af1ce660b817b +34 -0
- package/harness/catalog/input-group/files/50448668b22389f37e97 +3 -0
- package/harness/catalog/input-group/files/6dbdcc0f9ff4528070b8 +97 -0
- package/harness/catalog/input-group/files/736d8c18cf1f33b5a7d5 +2 -0
- package/harness/catalog/input-group/files/7a3f6facbfe0d6195355 +3 -0
- package/harness/catalog/input-group/files/89ff063e7666df8098d8 +83 -0
- package/harness/catalog/input-group/files/ac985a386a91e19f9bbd +2 -0
- package/harness/catalog/input-group/files/b28e3e20d39324fd7f46 +93 -0
- package/harness/catalog/input-group/files/d5410b5113479f8b7f5a +21 -0
- package/harness/catalog/input-group/files/d99f61d638ee95464394 +186 -0
- package/harness/catalog/input-group/files/dbcb5f1aaac679c86a53 +173 -0
- package/harness/catalog/input-group/files/e6305cb8959817cf07fc +18 -0
- package/harness/catalog/input-group/files/ee589db1ea581d588e63 +4 -0
- package/harness/catalog/input-group/files/f83225fa83f2339011cb +64 -0
- package/harness/catalog/input-group/manifest.json +109 -0
- package/harness/catalog/item/files/04bdde2b5e1615d12955 +322 -0
- package/harness/catalog/item/files/09e2e736a8375f63fcf0 +19 -0
- package/harness/catalog/item/files/0dcc0cfc1e2a47e99544 +26 -0
- package/harness/catalog/item/files/21166b7276e7422f4972 +163 -0
- package/harness/catalog/item/files/35c23f28a6a9400e68c6 +26 -0
- package/harness/catalog/item/files/3e55d032c524ad0b1754 +12 -0
- package/harness/catalog/item/files/46382bf1b58c54e07592 +6 -0
- package/harness/catalog/item/files/491e8d8a0c271e52640e +80 -0
- package/harness/catalog/item/files/4d77cb5e587c6a028b13 +521 -0
- package/harness/catalog/item/files/4f2a05a2ac90709e7ff7 +10 -0
- package/harness/catalog/item/files/56ba8284f9cb60bb1053 +21 -0
- package/harness/catalog/item/files/6b6cd3a9537fdf1354ea +3 -0
- package/harness/catalog/item/files/6c7bf2dfbdd32fe8f83a +21 -0
- package/harness/catalog/item/files/708ec3155d305b04654b +21 -0
- package/harness/catalog/item/files/79290f32b79c661a51d9 +26 -0
- package/harness/catalog/item/files/7d2530628a9e032f8bd6 +3 -0
- package/harness/catalog/item/files/a08b24c7c2fb10cad015 +46 -0
- package/harness/catalog/item/files/a47cfe69078455a32fbe +21 -0
- package/harness/catalog/item/files/a710a25ff17451cbdd00 +21 -0
- package/harness/catalog/item/files/b017a0cb71b5d5e73ab4 +11 -0
- package/harness/catalog/item/files/bcafcd71b96bae09e7e5 +21 -0
- package/harness/catalog/item/files/bf28d448b752a46831a0 +2 -0
- package/harness/catalog/item/files/c15f9be937068f7e1304 +1 -0
- package/harness/catalog/item/files/cb016b0cef50fdd305b1 +74 -0
- package/harness/catalog/item/files/cc7eec49d7f8f8c405b9 +3 -0
- package/harness/catalog/item/files/f5a8ad3f67b72a12fc48 +89 -0
- package/harness/catalog/item/manifest.json +119 -0
- package/harness/catalog/kbd/files/0ac105576d98be3d9e38 +3 -0
- package/harness/catalog/kbd/files/16d922c45b58989ddc86 +209 -0
- package/harness/catalog/kbd/files/1961ef478e61504f5c56 +1 -0
- package/harness/catalog/kbd/files/1a00b9bc0991be4b3318 +42 -0
- package/harness/catalog/kbd/files/255034504e8b67636ac2 +3 -0
- package/harness/catalog/kbd/files/268b00d6dcba45995ab3 +73 -0
- package/harness/catalog/kbd/files/2e7b2a85ecc2605cfe09 +16 -0
- package/harness/catalog/kbd/files/4d3887237a475f16d9f4 +22 -0
- package/harness/catalog/kbd/files/6f02f0895e7dd3bb032d +1 -0
- package/harness/catalog/kbd/files/8c47d035d84342a21cc4 +7 -0
- package/harness/catalog/kbd/files/97e104896e092af6b35b +22 -0
- package/harness/catalog/kbd/files/9b4ed30c2c7457a659b5 +2 -0
- package/harness/catalog/kbd/files/ba6e45ce6b38bf9c70e8 +40 -0
- package/harness/catalog/kbd/files/bf22ec90d5d876dffc8c +123 -0
- package/harness/catalog/kbd/files/cc42ed656bc00ebb6c52 +35 -0
- package/harness/catalog/kbd/manifest.json +73 -0
- package/harness/catalog/kits/dashboard/files/11a5797c4c9189b59fbe +134 -0
- package/harness/catalog/kits/dashboard/files/1aef0eaaad65d944a99f +98 -0
- package/harness/catalog/kits/dashboard/files/63cde4f28d1c141c401d +840 -0
- package/harness/catalog/kits/dashboard/files/864acc7ce20f541cf67c +17 -0
- package/harness/catalog/kits/dashboard/files/9cf4417e1eb89438b975 +49 -0
- package/harness/catalog/kits/dashboard/files/f84f0cf6a41afc21b64f +49 -0
- package/harness/catalog/kits/dashboard/files/ff7f571bbb2487b3ec23 +77 -0
- package/harness/catalog/kits/dashboard/manifest.json +52 -0
- package/harness/catalog/kits/data-table/files/1786ba4d3e0dba1d6a1f +19 -0
- package/harness/catalog/kits/data-table/files/36bac8f8e53119768b2e +154 -0
- package/harness/catalog/kits/data-table/files/460135fc626b5c2e7c33 +21 -0
- package/harness/catalog/kits/data-table/files/4cb7b4e9113b8414562f +106 -0
- package/harness/catalog/kits/data-table/files/5bafa7b36216f575d9cd +61 -0
- package/harness/catalog/kits/data-table/files/9cbb532f9f52b5b1b1cb +128 -0
- package/harness/catalog/kits/data-table/files/b5d5d7f18347734138e0 +607 -0
- package/harness/catalog/kits/data-table/files/d5dd11475a87206462f1 +95 -0
- package/harness/catalog/kits/data-table/manifest.json +56 -0
- package/harness/catalog/kits/docs-article/files/4cc9189b0d6a2bd7f59a +67 -0
- package/harness/catalog/kits/docs-article/files/642e7bd0b80a4a207c44 +73 -0
- package/harness/catalog/kits/docs-article/files/7f36cb5f0d4f5e103bde +18 -0
- package/harness/catalog/kits/docs-article/files/be0fb62d1c30dee65c74 +86 -0
- package/harness/catalog/kits/docs-article/files/c2018b502a8094818d8f +113 -0
- package/harness/catalog/kits/docs-article/files/dbc2840f315f672e1d74 +594 -0
- package/harness/catalog/kits/docs-article/manifest.json +50 -0
- package/harness/catalog/kits/form-states/files/0ef2ffae9d6f232f45e9 +124 -0
- package/harness/catalog/kits/form-states/files/437cb4c87ea365713cdd +68 -0
- package/harness/catalog/kits/form-states/files/88252259f19ed675a0dc +2099 -0
- package/harness/catalog/kits/form-states/files/96f75e622f16e97f3ea4 +62 -0
- package/harness/catalog/kits/form-states/files/b0b51ebf587b21fd89a1 +137 -0
- package/harness/catalog/kits/form-states/files/b52fb2fc480f0c6352bd +14 -0
- package/harness/catalog/kits/form-states/manifest.json +52 -0
- package/harness/catalog/kits/onboarding/files/322cf4dfc2ee0a035d85 +18 -0
- package/harness/catalog/kits/onboarding/files/3468d9690d9a781191ec +20 -0
- package/harness/catalog/kits/onboarding/files/6b468153260c66cd0413 +16 -0
- package/harness/catalog/kits/onboarding/files/7921743050eaf6de1a3d +73 -0
- package/harness/catalog/kits/onboarding/files/ae75e02daf70b4c8592f +105 -0
- package/harness/catalog/kits/onboarding/files/ce466020247ecf1ff5fe +119 -0
- package/harness/catalog/kits/onboarding/files/e669d75a65f4d15d8289 +352 -0
- package/harness/catalog/kits/onboarding/files/ea5a042d41c4a9418b24 +4 -0
- package/harness/catalog/kits/onboarding/manifest.json +53 -0
- package/harness/catalog/kits/profile/files/0fdd3c14afbdadcf1969 +16 -0
- package/harness/catalog/kits/profile/files/4a3c9a0031274cf07290 +43 -0
- package/harness/catalog/kits/profile/files/4aeca453e4792abf29de +520 -0
- package/harness/catalog/kits/profile/files/5b58bb5f93ecf12d69ff +96 -0
- package/harness/catalog/kits/profile/files/75b211244911b7cc480a +49 -0
- package/harness/catalog/kits/profile/files/881ef28864ed23ed93c8 +64 -0
- package/harness/catalog/kits/profile/files/cefb8073e21695cbf74b +42 -0
- package/harness/catalog/kits/profile/manifest.json +48 -0
- package/harness/catalog/kits/settings/files/0383a2564061dcf126a5 +70 -0
- package/harness/catalog/kits/settings/files/1a5d639c6803e7d03acc +119 -0
- package/harness/catalog/kits/settings/files/4344224a795d1beca0e8 +36 -0
- package/harness/catalog/kits/settings/files/6d38306218413c650752 +45 -0
- package/harness/catalog/kits/settings/files/9c61262f2fcf7346afce +43 -0
- package/harness/catalog/kits/settings/files/b4a7a4ccdc59465b8de5 +486 -0
- package/harness/catalog/kits/settings/files/d2ebbd6e94570b2c6434 +17 -0
- package/harness/catalog/kits/settings/files/ec7bce34a9f863882799 +33 -0
- package/harness/catalog/kits/settings/manifest.json +55 -0
- package/harness/catalog/kits/sign-in/files/0457945d67f57a0956b0 +22 -0
- package/harness/catalog/kits/sign-in/files/1778d506d6768426a33a +22 -0
- package/harness/catalog/kits/sign-in/files/276055c567cb979af600 +19 -0
- package/harness/catalog/kits/sign-in/files/361745a3ed43c753c615 +444 -0
- package/harness/catalog/kits/sign-in/files/552bdad5ce7559849e81 +17 -0
- package/harness/catalog/kits/sign-in/files/5ccdff5683e7c3fc7b66 +110 -0
- package/harness/catalog/kits/sign-in/files/5f8c4d12ea47ece52a44 +38 -0
- package/harness/catalog/kits/sign-in/files/ca224349b746c530f922 +110 -0
- package/harness/catalog/kits/sign-in/files/e50f092f7e5fa4ef4c22 +19 -0
- package/harness/catalog/kits/sign-in/manifest.json +55 -0
- package/harness/catalog/label/files/0d724d49f7d1d2ec7efc +1 -0
- package/harness/catalog/label/files/178c6bba6c9e90425d21 +2 -0
- package/harness/catalog/label/files/18342988a5792fb0bcad +170 -0
- package/harness/catalog/label/files/211d54defefbe5e94796 +37 -0
- package/harness/catalog/label/files/5340c9b911a7a4a11c69 +28 -0
- package/harness/catalog/label/files/59f0a37653f1e78ed28b +1 -0
- package/harness/catalog/label/files/6121a0a7157378c0fa2d +104 -0
- package/harness/catalog/label/files/905f249fb255abf67c32 +2 -0
- package/harness/catalog/label/files/92ba7e766a8e1b5a3cf0 +64 -0
- package/harness/catalog/label/files/977a534f8794467a47f2 +219 -0
- package/harness/catalog/label/files/aab49456f22f22d12017 +85 -0
- package/harness/catalog/label/files/c54411858ebf34a8cb54 +2 -0
- package/harness/catalog/label/files/c77857f888aab7f682af +3 -0
- package/harness/catalog/label/files/edf861c1fdb33efb3d2d +2 -0
- package/harness/catalog/label/files/eeafe176d4d778cc9380 +2 -0
- package/harness/catalog/label/files/f422c1d852b88024b703 +14 -0
- package/harness/catalog/label/manifest.json +79 -0
- package/harness/catalog/native-select/files/04dd3d3b7e52db816e7a +94 -0
- package/harness/catalog/native-select/files/0d1a9ad329393ddab564 +121 -0
- package/harness/catalog/native-select/files/13dbbc7bf43082986000 +10 -0
- package/harness/catalog/native-select/files/1da077d928618138c4b8 +200 -0
- package/harness/catalog/native-select/files/2113975ac7413cb45a61 +47 -0
- package/harness/catalog/native-select/files/744dbce3cb9ffb538c60 +83 -0
- package/harness/catalog/native-select/files/77300579b27d8b8dbfb8 +10 -0
- package/harness/catalog/native-select/files/9974bd4a983ce6e468ec +12 -0
- package/harness/catalog/native-select/files/c0626646c03aeb3ad93c +189 -0
- package/harness/catalog/native-select/files/c16f89dd4efac798101b +10 -0
- package/harness/catalog/native-select/files/c4b2e491bc54d6525edd +10 -0
- package/harness/catalog/native-select/files/cc71e265ac8c728163a0 +10 -0
- package/harness/catalog/native-select/files/ccc07dd1b217b5f634f0 +472 -0
- package/harness/catalog/native-select/files/d2f8e83f878359d164ec +10 -0
- package/harness/catalog/native-select/files/d6d4ee4692af5da60764 +19 -0
- package/harness/catalog/native-select/files/dafc51f382ef061a8113 +1 -0
- package/harness/catalog/native-select/files/ed3efff65cc3a8fb38e5 +12 -0
- package/harness/catalog/native-select/files/efb122a6a12da738c520 +10 -0
- package/harness/catalog/native-select/files/f3ce547f443bdf09f4ba +10 -0
- package/harness/catalog/native-select/files/fd1ad0d903b8ef4bacf7 +11 -0
- package/harness/catalog/native-select/manifest.json +97 -0
- package/harness/catalog/pagination/files/04910095041172b5656d +25 -0
- package/harness/catalog/pagination/files/13f03f9f29240862e939 +56 -0
- package/harness/catalog/pagination/files/18d235614c5082754f87 +90 -0
- package/harness/catalog/pagination/files/2772d7dca5a9b736fa27 +129 -0
- package/harness/catalog/pagination/files/2d6272cfbd3cd586ab9a +41 -0
- package/harness/catalog/pagination/files/393ce6151781df4f73b1 +7 -0
- package/harness/catalog/pagination/files/4178ae22ed24b8b0b2e3 +61 -0
- package/harness/catalog/pagination/files/60027b10f4f6405b078b +14 -0
- package/harness/catalog/pagination/files/60e0a8630f1f1b0c9860 +14 -0
- package/harness/catalog/pagination/files/636bdc45e5b52eb2fc36 +45 -0
- package/harness/catalog/pagination/files/73cef46d42733ef6d11b +41 -0
- package/harness/catalog/pagination/files/932e0ff1f3e4e70c7664 +19 -0
- package/harness/catalog/pagination/files/95f794d2b6a64320b411 +196 -0
- package/harness/catalog/pagination/files/a7618526ce3fc0595aa8 +46 -0
- package/harness/catalog/pagination/files/af2f75c1c60f40148e41 +30 -0
- package/harness/catalog/pagination/files/dc3354029b3743fa4607 +34 -0
- package/harness/catalog/pagination/files/f737799eba73ede286c6 +505 -0
- package/harness/catalog/pagination/manifest.json +81 -0
- package/harness/catalog/progress/files/06cd5195c1465d18cf67 +1 -0
- package/harness/catalog/progress/files/124314b4921167293987 +1 -0
- package/harness/catalog/progress/files/3f37f1d3cb4dfc6c6fe2 +1 -0
- package/harness/catalog/progress/files/46b8ec7859c9c59094a8 +1 -0
- package/harness/catalog/progress/files/52bb3ada2f1d1325d95a +43 -0
- package/harness/catalog/progress/files/683d8646b127ec5dd66e +2 -0
- package/harness/catalog/progress/files/98f3165379840778060d +129 -0
- package/harness/catalog/progress/files/9d3d72f2c3df4816a72f +38 -0
- package/harness/catalog/progress/files/ac4c4532f20085614826 +220 -0
- package/harness/catalog/progress/files/b1cf02fc7ecba00d0a5d +57 -0
- package/harness/catalog/progress/files/b9d67aae522deb2f2874 +82 -0
- package/harness/catalog/progress/files/ba1f86715e56b9d87904 +1 -0
- package/harness/catalog/progress/files/c0f9aa5c1b828ae95458 +21 -0
- package/harness/catalog/progress/files/cce615b40b94edc2bd0a +75 -0
- package/harness/catalog/progress/files/fbdbab9c99c0e52e7e93 +1 -0
- package/harness/catalog/progress/manifest.json +73 -0
- package/harness/catalog/radio-group/files/0524023470cd6e82adc8 +79 -0
- package/harness/catalog/radio-group/files/105409e5b8bba6c04d90 +9 -0
- package/harness/catalog/radio-group/files/15d87655c6fce7cbdd87 +7 -0
- package/harness/catalog/radio-group/files/1ab7aeaf41bd11881118 +8 -0
- package/harness/catalog/radio-group/files/1ac26e4aaaf55d172a29 +140 -0
- package/harness/catalog/radio-group/files/1f92eedd59d862a251bc +89 -0
- package/harness/catalog/radio-group/files/2e172c357c5ad16851b0 +7 -0
- package/harness/catalog/radio-group/files/2f70078682b30a266fdb +279 -0
- package/harness/catalog/radio-group/files/3ba2bc3ba6f029b80ca0 +7 -0
- package/harness/catalog/radio-group/files/6a5408af78fb93544257 +11 -0
- package/harness/catalog/radio-group/files/6d46f6c13443b681492a +87 -0
- package/harness/catalog/radio-group/files/85a4b3266a6a1d28e98e +17 -0
- package/harness/catalog/radio-group/files/8bc1af58d460a1f08417 +7 -0
- package/harness/catalog/radio-group/files/924c3130eda5e6a89b8c +85 -0
- package/harness/catalog/radio-group/files/965cd8ee2804c8db885f +2 -0
- package/harness/catalog/radio-group/files/9aed7c5fa69a16e32877 +7 -0
- package/harness/catalog/radio-group/files/b517f83f11efd06cecc6 +9 -0
- package/harness/catalog/radio-group/files/b5794de89d7617056bd7 +7 -0
- package/harness/catalog/radio-group/files/cf90166db3ba9acc2194 +52 -0
- package/harness/catalog/radio-group/files/df1cd5a2eb01d19cbecf +394 -0
- package/harness/catalog/radio-group/files/f0716924e08378be93db +7 -0
- package/harness/catalog/radio-group/manifest.json +101 -0
- package/harness/catalog/scroll-area/files/0609007de03faf1c3d0f +46 -0
- package/harness/catalog/scroll-area/files/1908a334d6f3a4dbf6c0 +21 -0
- package/harness/catalog/scroll-area/files/1e8f68bf069a5f387c34 +83 -0
- package/harness/catalog/scroll-area/files/41b80c94f170ea511175 +44 -0
- package/harness/catalog/scroll-area/files/4a42e479847375dcc3f9 +25 -0
- package/harness/catalog/scroll-area/files/4ca03842475a792cb0c1 +40 -0
- package/harness/catalog/scroll-area/files/55e014a395adc19f6cef +265 -0
- package/harness/catalog/scroll-area/files/60bc5ea08ee21de46d13 +123 -0
- package/harness/catalog/scroll-area/files/85a4352c5d2fceab3803 +19 -0
- package/harness/catalog/scroll-area/files/a3cd2f01d235d82495fb +2 -0
- package/harness/catalog/scroll-area/files/ade2527a8f6accd9b730 +6 -0
- package/harness/catalog/scroll-area/files/b2e8b1702898b8ca3833 +93 -0
- package/harness/catalog/scroll-area/files/da73cf074c32dc1be5f1 +61 -0
- package/harness/catalog/scroll-area/files/ebca80ece3c535585b1d +41 -0
- package/harness/catalog/scroll-area/files/f6fc569d113d49be8d9b +61 -0
- package/harness/catalog/scroll-area/manifest.json +73 -0
- package/harness/catalog/separator/files/374b9df00179421eddf2 +3 -0
- package/harness/catalog/separator/files/4e8122ded69b8f101fb2 +43 -0
- package/harness/catalog/separator/files/6d7eafd5d259b4a18d8c +168 -0
- package/harness/catalog/separator/files/84cb34e3692a988ae594 +27 -0
- package/harness/catalog/separator/files/9290cde82ff35a18d670 +3 -0
- package/harness/catalog/separator/files/a9afc792add2b428f1e8 +3 -0
- package/harness/catalog/separator/files/b35a57ea93c2a3cb70f8 +77 -0
- package/harness/catalog/separator/files/cf582f7054769bcef6eb +5 -0
- package/harness/catalog/separator/files/d1d489b25ae8086dd004 +11 -0
- package/harness/catalog/separator/files/d8a31d391f75f3a61fb3 +37 -0
- package/harness/catalog/separator/files/dd83a998ab6abc4d4a62 +1 -0
- package/harness/catalog/separator/files/eb2517d531a9906643d7 +47 -0
- package/harness/catalog/separator/files/f9759af59a3ba93dae9b +127 -0
- package/harness/catalog/separator/manifest.json +65 -0
- package/harness/catalog/sidebar/files/02c393cb36580af098d9 +23 -0
- package/harness/catalog/sidebar/files/0baeb5c4c8b7893d5fcf +756 -0
- package/harness/catalog/sidebar/files/1703dc3e2ad661ccbf64 +744 -0
- package/harness/catalog/sidebar/files/184473a92ca8fb31600e +29 -0
- package/harness/catalog/sidebar/files/1a887b38be934ce59719 +55 -0
- package/harness/catalog/sidebar/files/33842af58a18280c36aa +57 -0
- package/harness/catalog/sidebar/files/3e189ffc0c2682c10cf2 +187 -0
- package/harness/catalog/sidebar/files/42912dae260a1877fca7 +7 -0
- package/harness/catalog/sidebar/files/4e5ba4ef0af42f6a7adb +249 -0
- package/harness/catalog/sidebar/files/4ecc4d8ff1bf3d164a8b +21 -0
- package/harness/catalog/sidebar/files/508f864b7864c8394ca3 +27 -0
- package/harness/catalog/sidebar/files/5e75aef8fec95baad132 +90 -0
- package/harness/catalog/sidebar/files/68079b1aea589468b91b +21 -0
- package/harness/catalog/sidebar/files/7fc791d49df7f259257b +155 -0
- package/harness/catalog/sidebar/files/88cc94ff5db8b8216376 +7 -0
- package/harness/catalog/sidebar/files/91d221fdce2c9e43bd8c +16 -0
- package/harness/catalog/sidebar/files/a80295e689cbd36a473f +84 -0
- package/harness/catalog/sidebar/files/a84bff2047ae8764783d +29 -0
- package/harness/catalog/sidebar/files/b82a3010959395a48e1a +49 -0
- package/harness/catalog/sidebar/files/bc1e527aadf296b8d0ff +21 -0
- package/harness/catalog/sidebar/files/bcbd1ae5b1fd97c72c53 +11 -0
- package/harness/catalog/sidebar/files/c964f937cad048b84944 +92 -0
- package/harness/catalog/sidebar/files/daaaa332bc0d9d13ed98 +21 -0
- package/harness/catalog/sidebar/files/e4218aaf235e989cbd53 +21 -0
- package/harness/catalog/sidebar/files/ee8db7c1694c46686557 +26 -0
- package/harness/catalog/sidebar/files/f673ab38a8d4ae19f321 +31 -0
- package/harness/catalog/sidebar/manifest.json +129 -0
- package/harness/catalog/skeleton/files/01ba4719c80b6fe911b0 +1 -0
- package/harness/catalog/skeleton/files/0e6d882ff78e3beba2d6 +30 -0
- package/harness/catalog/skeleton/files/376c8cba27f74bac0cb9 +39 -0
- package/harness/catalog/skeleton/files/4612f603a58593ca55e0 +11 -0
- package/harness/catalog/skeleton/files/4d046332fd9d8d606983 +163 -0
- package/harness/catalog/skeleton/files/96d701044834f6a5836a +111 -0
- package/harness/catalog/skeleton/files/a634338190d8728efc1c +1 -0
- package/harness/catalog/skeleton/files/bbaabfa0b8dc2e8ea11a +74 -0
- package/harness/catalog/skeleton/files/c67fd2e5aaaba5a9d580 +28 -0
- package/harness/catalog/skeleton/files/cbccb00a131579632ae9 +27 -0
- package/harness/catalog/skeleton/manifest.json +57 -0
- package/harness/catalog/slider/files/055538028b3345e43a11 +214 -0
- package/harness/catalog/slider/files/0cb5c203dad3b98de5e0 +1 -0
- package/harness/catalog/slider/files/1ae10a01eb873280ce12 +4 -0
- package/harness/catalog/slider/files/1f79672390fd6db74fee +21 -0
- package/harness/catalog/slider/files/25dc6781375bc2c2df6d +482 -0
- package/harness/catalog/slider/files/393ec10fdb971be991de +72 -0
- package/harness/catalog/slider/files/424492d24591aef531e6 +4 -0
- package/harness/catalog/slider/files/42e0ad202b32731e7a02 +3 -0
- package/harness/catalog/slider/files/4cb5517efb58b1879afd +59 -0
- package/harness/catalog/slider/files/659100cf11a1d05b2c89 +3 -0
- package/harness/catalog/slider/files/668e93dad3504e8ef610 +95 -0
- package/harness/catalog/slider/files/71e517cb9c92a75885f5 +3 -0
- package/harness/catalog/slider/files/7657bd9ab41538c35120 +3 -0
- package/harness/catalog/slider/files/81017d93f3ad7c324811 +5 -0
- package/harness/catalog/slider/files/8b0655afa86f8d9dc2bc +177 -0
- package/harness/catalog/slider/files/a7488bb1ada74ac621e6 +3 -0
- package/harness/catalog/slider/files/b45d4e5cb309bcc465a5 +285 -0
- package/harness/catalog/slider/files/c9a088fbd66f42f4564d +4 -0
- package/harness/catalog/slider/files/ce3046c912906d11badf +6 -0
- package/harness/catalog/slider/files/d5508e45254809067beb +3 -0
- package/harness/catalog/slider/files/ee1caf9ef1db1c4f926e +3 -0
- package/harness/catalog/slider/files/f764bc666d741a7bf39f +3 -0
- package/harness/catalog/slider/manifest.json +101 -0
- package/harness/catalog/spinner/files/01ba4719c80b6fe911b0 +1 -0
- package/harness/catalog/spinner/files/0fee74c552acfcd09b79 +77 -0
- package/harness/catalog/spinner/files/2a5417a598cfa5c61d41 +77 -0
- package/harness/catalog/spinner/files/38ff39afe202b65ee51b +32 -0
- package/harness/catalog/spinner/files/56c45ae3c12de700ab2e +30 -0
- package/harness/catalog/spinner/files/6df67fa7b71cc2d5a264 +1 -0
- package/harness/catalog/spinner/files/6f49277820d19b30bf3e +30 -0
- package/harness/catalog/spinner/files/72eebb972f647017cb66 +161 -0
- package/harness/catalog/spinner/files/a21c624000065c68760a +1 -0
- package/harness/catalog/spinner/files/bf8438f942deebfd1eb1 +59 -0
- package/harness/catalog/spinner/files/c8addaaad7e52c7db0ae +34 -0
- package/harness/catalog/spinner/files/e445cd25a2db6a2e2a8b +1 -0
- package/harness/catalog/spinner/manifest.json +65 -0
- package/harness/catalog/switch/files/00386133e411f7f9f2b6 +4 -0
- package/harness/catalog/switch/files/0c1c3cb6e26d717784fc +2 -0
- package/harness/catalog/switch/files/3fc789ad053403f6c0a9 +20 -0
- package/harness/catalog/switch/files/44df1872eb49ea4e1e08 +483 -0
- package/harness/catalog/switch/files/49d0024b39574e56612f +3 -0
- package/harness/catalog/switch/files/592404eea89d590aca7a +2 -0
- package/harness/catalog/switch/files/6805184e8897c82550c4 +65 -0
- package/harness/catalog/switch/files/7a9c672629fef0bd0dec +2 -0
- package/harness/catalog/switch/files/8733d3a60ffcb6ade494 +210 -0
- package/harness/catalog/switch/files/910ca4e571bb756e4687 +4 -0
- package/harness/catalog/switch/files/92d0e744cb47aecc36bc +126 -0
- package/harness/catalog/switch/files/a195aa181ef4d92ffe20 +47 -0
- package/harness/catalog/switch/files/a6b8c28ba62b79ec987d +2 -0
- package/harness/catalog/switch/files/c365a534cf1a1122900d +2 -0
- package/harness/catalog/switch/files/df46601cb34ccf35b908 +1 -0
- package/harness/catalog/switch/files/e65b2ec11fa9a263d727 +153 -0
- package/harness/catalog/switch/files/ea1e13f86f2d9ea47d84 +93 -0
- package/harness/catalog/switch/files/eff1c0d843da2d594748 +4 -0
- package/harness/catalog/switch/files/f7eb67e0d31b393f05ae +3 -0
- package/harness/catalog/switch/files/fa365adda5b6c224f55f +4 -0
- package/harness/catalog/switch/manifest.json +101 -0
- package/harness/catalog/table/files/06a72c7ea0badb1cdb70 +83 -0
- package/harness/catalog/table/files/0c9127bfdbcb6b684d41 +9 -0
- package/harness/catalog/table/files/11aa2b5da6eff1bc677e +481 -0
- package/harness/catalog/table/files/218ac7260a0b3b039f4a +26 -0
- package/harness/catalog/table/files/4a4cf995bf282ff92770 +26 -0
- package/harness/catalog/table/files/4eb3d1edab7042aa14fe +36 -0
- package/harness/catalog/table/files/63d442facdfea1c86c66 +8 -0
- package/harness/catalog/table/files/7793bcf9af64c209d082 +59 -0
- package/harness/catalog/table/files/847886ae5dea29b33a82 +159 -0
- package/harness/catalog/table/files/9256f0a7cd82969c9563 +26 -0
- package/harness/catalog/table/files/a2c392393c5570977487 +98 -0
- package/harness/catalog/table/files/c3c72c2b5b63f99435d6 +32 -0
- package/harness/catalog/table/files/c7052cd9cf1d37957359 +26 -0
- package/harness/catalog/table/files/cf536589682b899cbbc8 +36 -0
- package/harness/catalog/table/files/e066a67b247e4ff773ed +72 -0
- package/harness/catalog/table/files/e64bfc90653d920c40cf +26 -0
- package/harness/catalog/table/files/ee2c6aa6812c21964fc3 +37 -0
- package/harness/catalog/table/files/efc084da8f3e1ca4bb1e +20 -0
- package/harness/catalog/table/files/f63191bea2943e7e8646 +26 -0
- package/harness/catalog/table/manifest.json +95 -0
- package/harness/catalog/tabs/files/07313e4500aa9db5bea9 +295 -0
- package/harness/catalog/tabs/files/0e09bb234c2d987563c5 +44 -0
- package/harness/catalog/tabs/files/21d28a1591efd7f95f0c +7 -0
- package/harness/catalog/tabs/files/3af8b9df88190e5769e3 +179 -0
- package/harness/catalog/tabs/files/417c2aab1ac8fc02bea8 +97 -0
- package/harness/catalog/tabs/files/5a911ebff6c576edf6e2 +7 -0
- package/harness/catalog/tabs/files/648e7828551135a79fe0 +506 -0
- package/harness/catalog/tabs/files/695a8dbd85e48a6df664 +7 -0
- package/harness/catalog/tabs/files/6baa7760f7e987f3ef6a +21 -0
- package/harness/catalog/tabs/files/73e91381aa7e8daf88a7 +49 -0
- package/harness/catalog/tabs/files/7aae2037e305f96b0b32 +12 -0
- package/harness/catalog/tabs/files/84a3fabd049bcd7acfdc +7 -0
- package/harness/catalog/tabs/files/a5164ae6a24abaec4ac6 +57 -0
- package/harness/catalog/tabs/files/a6bbaee4752f6c2390e2 +82 -0
- package/harness/catalog/tabs/files/ba5b8143d45ad81e1c60 +55 -0
- package/harness/catalog/tabs/files/bf00a8f1a90c35508882 +7 -0
- package/harness/catalog/tabs/files/c0984c7ad455c6b0cc4c +7 -0
- package/harness/catalog/tabs/files/ccdbaeb3df0390b93d29 +6 -0
- package/harness/catalog/tabs/files/cdea93ffff588335d13f +7 -0
- package/harness/catalog/tabs/files/edec052d6f4e11eb127b +4 -0
- package/harness/catalog/tabs/files/f3d876e31487d62c6b73 +72 -0
- package/harness/catalog/tabs/manifest.json +101 -0
- package/harness/catalog/textarea/files/0a144b3a4ff8b760723f +3 -0
- package/harness/catalog/textarea/files/1179ca65c96f2c4c7a62 +20 -0
- package/harness/catalog/textarea/files/3823c388f816fde1b42a +4 -0
- package/harness/catalog/textarea/files/3a82f5bd2f742c0e128c +1 -0
- package/harness/catalog/textarea/files/3b4902e2330b9e9e9cab +3 -0
- package/harness/catalog/textarea/files/43436aab74885a39c202 +5 -0
- package/harness/catalog/textarea/files/4d71c9cadff18e09886a +91 -0
- package/harness/catalog/textarea/files/62d0c969f21365d6b1b1 +5 -0
- package/harness/catalog/textarea/files/669e6acaa0b92e26f625 +3 -0
- package/harness/catalog/textarea/files/7045c50006094d7fc509 +60 -0
- package/harness/catalog/textarea/files/7077fee35ef05f1bbe4a +94 -0
- package/harness/catalog/textarea/files/814e737b0611c5065988 +445 -0
- package/harness/catalog/textarea/files/bc3570e5272f5184ad9e +3 -0
- package/harness/catalog/textarea/files/ce80d7e5afc76abd4959 +59 -0
- package/harness/catalog/textarea/files/cf73481c223c131e6c11 +3 -0
- package/harness/catalog/textarea/files/ece8fd9c92b58896f533 +187 -0
- package/harness/catalog/textarea/files/fa6d6b7547b43d802c91 +149 -0
- package/harness/catalog/textarea/manifest.json +85 -0
- package/harness/catalog/toggle/files/06e728076ff3708d9731 +1 -0
- package/harness/catalog/toggle/files/101275fbf8e9a92f05bd +350 -0
- package/harness/catalog/toggle/files/25c5c34ba3643df243fe +1 -0
- package/harness/catalog/toggle/files/4ff925b4bd7f7a54adbf +53 -0
- package/harness/catalog/toggle/files/552756c181edbe2ea36e +1 -0
- package/harness/catalog/toggle/files/7ca72db6ef05e84c818d +2 -0
- package/harness/catalog/toggle/files/86a49ecdda597c2abc1f +96 -0
- package/harness/catalog/toggle/files/c69429348ba9b2349c41 +1 -0
- package/harness/catalog/toggle/files/caa7211387429abff9ad +1 -0
- package/harness/catalog/toggle/files/cc3e62779d904733edbb +18 -0
- package/harness/catalog/toggle/files/d29935b92deece7918e8 +1 -0
- package/harness/catalog/toggle/files/dc0582c85be71895b397 +102 -0
- package/harness/catalog/toggle/files/e1dd7f07ac462c85e350 +1 -0
- package/harness/catalog/toggle/files/e50481803ad0d9f7c606 +1 -0
- package/harness/catalog/toggle/files/e5de72e6307749961d2b +50 -0
- package/harness/catalog/toggle/files/e98252325970f8f0de47 +6 -0
- package/harness/catalog/toggle/files/ebd668effb5c2ec9b74f +85 -0
- package/harness/catalog/toggle/files/ecd68b4d77b8b659e0cd +192 -0
- package/harness/catalog/toggle/manifest.json +89 -0
- package/harness/catalog/toggle-group/files/0fa34763f042c43ce73b +4 -0
- package/harness/catalog/toggle-group/files/190b8f8c8a7ae50ab17d +88 -0
- package/harness/catalog/toggle-group/files/19433a77dc520968adc7 +82 -0
- package/harness/catalog/toggle-group/files/2962515e0df1a6578234 +2 -0
- package/harness/catalog/toggle-group/files/599a5a04bc484ca3b63a +4 -0
- package/harness/catalog/toggle-group/files/5a8079fac7a37e9643e4 +3 -0
- package/harness/catalog/toggle-group/files/65b5cdec43bfefa463f5 +5 -0
- package/harness/catalog/toggle-group/files/6f6c143c8a199c913076 +4 -0
- package/harness/catalog/toggle-group/files/838108eb3fe1ef7caf97 +172 -0
- package/harness/catalog/toggle-group/files/9871546bf65ecfd8194e +85 -0
- package/harness/catalog/toggle-group/files/a43866348a36242e2b4e +17 -0
- package/harness/catalog/toggle-group/files/b39b752eca28b0def9f6 +4 -0
- package/harness/catalog/toggle-group/files/bd424f103ce11b4028bf +24 -0
- package/harness/catalog/toggle-group/files/c6d49c47cbca3721c6e0 +14 -0
- package/harness/catalog/toggle-group/files/cb207321ae902ad2316b +4 -0
- package/harness/catalog/toggle-group/files/d0677f0dfb61de88dd9e +278 -0
- package/harness/catalog/toggle-group/files/e1c72518f6c3a4cb47f6 +130 -0
- package/harness/catalog/toggle-group/files/ebcee45fa104cfa89d4f +55 -0
- package/harness/catalog/toggle-group/files/ed9cb4818db1e6341ad9 +565 -0
- package/harness/catalog/toggle-group/files/f846b21b23d9e132fded +4 -0
- package/harness/catalog/toggle-group/manifest.json +111 -0
- package/harness/catalog/typography/files/0a4d3686784349f2a671 +2 -0
- package/harness/catalog/typography/files/1004765ed611a2862d32 +1 -0
- package/harness/catalog/typography/files/2db24ae6bcb2f89eb7b6 +99 -0
- package/harness/catalog/typography/files/4b963f90bb762c552cf8 +2 -0
- package/harness/catalog/typography/files/4fb45c7c4e74d67c5bf5 +38 -0
- package/harness/catalog/typography/files/677a3d8e4ce6c2ac5f7f +28 -0
- package/harness/catalog/typography/files/6eb835a9f4bcf45c33f1 +2 -0
- package/harness/catalog/typography/files/70c577bc4141d2234973 +23 -0
- package/harness/catalog/typography/files/71af48bf10a9799ce540 +2 -0
- package/harness/catalog/typography/files/7dbdb256dedc6d4e8c42 +56 -0
- package/harness/catalog/typography/files/abe12ca3a7a166b0b4fb +222 -0
- package/harness/catalog/typography/files/b3b312ffd5ecb243853a +13 -0
- package/harness/catalog/typography/files/c47ff3172fe052fda28f +134 -0
- package/harness/catalog/typography/files/ea5ccd6abd4866523ab5 +335 -0
- package/harness/catalog/typography/files/ebb2f1791031cad5c2fc +70 -0
- package/harness/catalog/typography/manifest.json +73 -0
- package/harness/checks/a1-api.d.mts +4 -0
- package/harness/checks/a1-api.mjs +97 -0
- package/harness/checks/c1-contracts.d.mts +4 -0
- package/harness/checks/c1-contracts.mjs +92 -0
- package/harness/checks/c2-contract-tokens.d.mts +4 -0
- package/harness/checks/c2-contract-tokens.mjs +28 -0
- package/harness/checks/c3-parity.d.mts +4 -0
- package/harness/checks/c3-parity.mjs +68 -0
- package/harness/checks/d1-design-drift.d.mts +4 -0
- package/harness/checks/d1-design-drift.mjs +51 -0
- package/harness/checks/d3-design-docs.d.mts +4 -0
- package/harness/checks/d3-design-docs.mjs +66 -0
- package/harness/checks/d4-design-realization.d.mts +4 -0
- package/harness/checks/d4-design-realization.mjs +38 -0
- package/harness/checks/data/reference-phrases.json +35 -0
- package/harness/checks/f1-foundations.d.mts +4 -0
- package/harness/checks/f1-foundations.mjs +70 -0
- package/harness/checks/g1-generated.d.mts +4 -0
- package/harness/checks/g1-generated.mjs +156 -0
- package/harness/checks/h1-claude-layer.d.mts +4 -0
- package/harness/checks/h1-claude-layer.mjs +40 -0
- package/harness/checks/h2-typescript-sources.d.mts +5 -0
- package/harness/checks/h2-typescript-sources.mjs +33 -0
- package/harness/checks/k1-patterns.d.mts +4 -0
- package/harness/checks/k1-patterns.mjs +183 -0
- package/harness/checks/m1-docs-coverage.d.mts +4 -0
- package/harness/checks/m1-docs-coverage.mjs +63 -0
- package/harness/checks/o1-propagation.d.mts +4 -0
- package/harness/checks/o1-propagation.mjs +34 -0
- package/harness/checks/p1-prefix.d.mts +4 -0
- package/harness/checks/p1-prefix.mjs +55 -0
- package/harness/checks/r1-registry.d.mts +4 -0
- package/harness/checks/r1-registry.mjs +54 -0
- package/harness/checks/run.d.mts +10 -0
- package/harness/checks/run.mjs +122 -0
- package/harness/checks/s1-screen-reader.d.mts +4 -0
- package/harness/checks/s1-screen-reader.mjs +44 -0
- package/harness/checks/t1-tokens-valid.d.mts +9 -0
- package/harness/checks/t1-tokens-valid.mjs +77 -0
- package/harness/checks/t2-aliases.d.mts +4 -0
- package/harness/checks/t2-aliases.mjs +39 -0
- package/harness/checks/t3-modes.d.mts +4 -0
- package/harness/checks/t3-modes.mjs +21 -0
- package/harness/checks/t4-usage.d.mts +4 -0
- package/harness/checks/t4-usage.mjs +51 -0
- package/harness/checks/t5-literals.d.mts +4 -0
- package/harness/checks/t5-literals.mjs +24 -0
- package/harness/checks/t6-contrast.d.mts +14 -0
- package/harness/checks/t6-contrast.mjs +110 -0
- package/harness/checks/t7-interface.d.mts +4 -0
- package/harness/checks/t7-interface.mjs +96 -0
- package/harness/checks/types.d.mts +61 -0
- package/harness/checks/types.mjs +6 -0
- package/harness/checks/w1-white-label.d.mts +4 -0
- package/harness/checks/w1-white-label.mjs +143 -0
- package/harness/checks/x1-decisions.d.mts +15 -0
- package/harness/checks/x1-decisions.mjs +63 -0
- package/harness/cli/commands/add.d.mts +134 -0
- package/harness/cli/commands/add.mjs +53 -0
- package/harness/cli/commands/api.d.mts +87 -0
- package/harness/cli/commands/api.mjs +110 -0
- package/harness/cli/commands/audit-css.d.mts +108 -0
- package/harness/cli/commands/audit-css.mjs +23 -0
- package/harness/cli/commands/audit-decisions.d.mts +49 -0
- package/harness/cli/commands/audit-decisions.mjs +71 -0
- package/harness/cli/commands/audit-page.d.mts +34 -0
- package/harness/cli/commands/audit-page.mjs +28 -0
- package/harness/cli/commands/brand.d.mts +124 -0
- package/harness/cli/commands/brand.mjs +65 -0
- package/harness/cli/commands/check.d.mts +81 -0
- package/harness/cli/commands/check.mjs +36 -0
- package/harness/cli/commands/docs.d.mts +20 -0
- package/harness/cli/commands/docs.mjs +24 -0
- package/harness/cli/commands/doctor.d.mts +73 -0
- package/harness/cli/commands/doctor.mjs +113 -0
- package/harness/cli/commands/explain.d.mts +21 -0
- package/harness/cli/commands/explain.mjs +16 -0
- package/harness/cli/commands/generate.d.mts +16 -0
- package/harness/cli/commands/generate.mjs +17 -0
- package/harness/cli/commands/help.d.mts +50 -0
- package/harness/cli/commands/help.mjs +54 -0
- package/harness/cli/commands/icons.d.mts +61 -0
- package/harness/cli/commands/icons.mjs +45 -0
- package/harness/cli/commands/init.d.mts +236 -0
- package/harness/cli/commands/init.mjs +184 -0
- package/harness/cli/commands/kits.d.mts +91 -0
- package/harness/cli/commands/kits.mjs +65 -0
- package/harness/cli/commands/list.d.mts +48 -0
- package/harness/cli/commands/list.mjs +38 -0
- package/harness/cli/commands/prefix.d.mts +32 -0
- package/harness/cli/commands/prefix.mjs +24 -0
- package/harness/cli/commands/presets.d.mts +49 -0
- package/harness/cli/commands/presets.mjs +30 -0
- package/harness/cli/commands/propagate.d.mts +25 -0
- package/harness/cli/commands/propagate.mjs +66 -0
- package/harness/cli/commands/remove.d.mts +66 -0
- package/harness/cli/commands/remove.mjs +32 -0
- package/harness/cli/commands/selftest.d.mts +20 -0
- package/harness/cli/commands/selftest.mjs +21 -0
- package/harness/cli/commands/status.d.mts +51 -0
- package/harness/cli/commands/status.mjs +70 -0
- package/harness/cli/commands/swap.d.mts +40 -0
- package/harness/cli/commands/swap.mjs +29 -0
- package/harness/cli/commands/sync.d.mts +280 -0
- package/harness/cli/commands/sync.mjs +194 -0
- package/harness/cli/commands/tokens.d.mts +270 -0
- package/harness/cli/commands/tokens.mjs +342 -0
- package/harness/cli/commands/upgrade.d.mts +99 -0
- package/harness/cli/commands/upgrade.mjs +78 -0
- package/harness/cli/docs.d.mts +1 -0
- package/harness/cli/docs.mjs +53 -0
- package/harness/cli/interactive.d.mts +22 -0
- package/harness/cli/interactive.mjs +125 -0
- package/harness/cli/known-commands.json +150 -0
- package/harness/cli/known.d.mts +9 -0
- package/harness/cli/known.mjs +31 -0
- package/harness/cli/planned-commands.json +20 -0
- package/harness/cli/registry.d.mts +5 -0
- package/harness/cli/registry.mjs +34 -0
- package/harness/cli/run.d.mts +22 -0
- package/harness/cli/run.mjs +108 -0
- package/harness/cli/types.d.mts +88 -0
- package/harness/cli/types.mjs +1 -0
- package/harness/cli.d.mts +2 -0
- package/harness/cli.mjs +22 -0
- package/harness/commands/add.d.mts +11 -0
- package/harness/commands/add.mjs +71 -0
- package/harness/commands/audit-css.d.mts +70 -0
- package/harness/commands/audit-css.mjs +171 -0
- package/harness/commands/bootstrap.d.mts +163 -0
- package/harness/commands/bootstrap.mjs +517 -0
- package/harness/commands/brand.d.mts +70 -0
- package/harness/commands/brand.mjs +220 -0
- package/harness/commands/catalog.d.mts +149 -0
- package/harness/commands/catalog.mjs +521 -0
- package/harness/commands/explain.d.mts +1 -0
- package/harness/commands/explain.mjs +76 -0
- package/harness/commands/init.d.mts +44 -0
- package/harness/commands/init.mjs +77 -0
- package/harness/commands/prefix.d.mts +19 -0
- package/harness/commands/prefix.mjs +139 -0
- package/harness/commands/start.d.mts +75 -0
- package/harness/commands/start.mjs +154 -0
- package/harness/commands/swap.d.mts +23 -0
- package/harness/commands/swap.mjs +30 -0
- package/harness/commands/tokens-import.d.mts +105 -0
- package/harness/commands/tokens-import.mjs +598 -0
- package/harness/commands/tokens.d.mts +175 -0
- package/harness/commands/tokens.mjs +989 -0
- package/harness/commands/upgrade.d.mts +45 -0
- package/harness/commands/upgrade.mjs +181 -0
- package/harness/generators/foundation.d.mts +52 -0
- package/harness/generators/foundation.mjs +275 -0
- package/harness/generators/links.d.mts +42 -0
- package/harness/generators/links.mjs +203 -0
- package/harness/generators/overrides.d.mts +10 -0
- package/harness/generators/overrides.mjs +40 -0
- package/harness/kits/index.json +158 -0
- package/harness/lib/agent-config.d.mts +23 -0
- package/harness/lib/agent-config.mjs +109 -0
- package/harness/lib/agent-diagnostics.d.mts +25 -0
- package/harness/lib/agent-diagnostics.mjs +139 -0
- package/harness/lib/api.d.mts +166 -0
- package/harness/lib/api.mjs +222 -0
- package/harness/lib/audits.d.mts +3 -0
- package/harness/lib/audits.mjs +14 -0
- package/harness/lib/claude-layer.d.mts +59 -0
- package/harness/lib/claude-layer.mjs +312 -0
- package/harness/lib/color.d.mts +17 -0
- package/harness/lib/color.mjs +89 -0
- package/harness/lib/css.d.mts +25 -0
- package/harness/lib/css.mjs +64 -0
- package/harness/lib/decisions.d.mts +14 -0
- package/harness/lib/decisions.mjs +65 -0
- package/harness/lib/design/compare-runtime.mjs +58 -0
- package/harness/lib/design/compare.d.mts +57 -0
- package/harness/lib/design/compare.mjs +153 -0
- package/harness/lib/design/components.d.mts +29 -0
- package/harness/lib/design/components.mjs +52 -0
- package/harness/lib/design/description.d.mts +25 -0
- package/harness/lib/design/description.mjs +57 -0
- package/harness/lib/design/doc-text.d.mts +137 -0
- package/harness/lib/design/doc-text.mjs +63 -0
- package/harness/lib/design/docs.d.mts +80 -0
- package/harness/lib/design/docs.mjs +343 -0
- package/harness/lib/design/library.d.mts +91 -0
- package/harness/lib/design/library.mjs +248 -0
- package/harness/lib/design/parity.d.mts +8 -0
- package/harness/lib/design/parity.mjs +42 -0
- package/harness/lib/design/patterns.d.mts +48 -0
- package/harness/lib/design/patterns.mjs +90 -0
- package/harness/lib/design/plan.d.mts +20 -0
- package/harness/lib/design/plan.mjs +120 -0
- package/harness/lib/design/realize.d.mts +51 -0
- package/harness/lib/design/realize.mjs +86 -0
- package/harness/lib/design/recipes-more.d.mts +2 -0
- package/harness/lib/design/recipes-more.mjs +461 -0
- package/harness/lib/design/recipes.d.mts +12 -0
- package/harness/lib/design/recipes.mjs +285 -0
- package/harness/lib/design/sync.d.mts +80 -0
- package/harness/lib/design/sync.mjs +163 -0
- package/harness/lib/design/tokens.d.mts +55 -0
- package/harness/lib/design/tokens.mjs +243 -0
- package/harness/lib/design/verify.d.mts +84 -0
- package/harness/lib/design/verify.mjs +158 -0
- package/harness/lib/design-docs.d.mts +73 -0
- package/harness/lib/design-docs.mjs +38 -0
- package/harness/lib/files.d.mts +21 -0
- package/harness/lib/files.mjs +99 -0
- package/harness/lib/icons.d.mts +24 -0
- package/harness/lib/icons.mjs +67 -0
- package/harness/lib/installed.d.mts +16 -0
- package/harness/lib/installed.mjs +121 -0
- package/harness/lib/interface.d.mts +62 -0
- package/harness/lib/interface.mjs +201 -0
- package/harness/lib/page-outline.d.mts +2 -0
- package/harness/lib/page-outline.mjs +19 -0
- package/harness/lib/propagation.d.mts +20 -0
- package/harness/lib/propagation.mjs +91 -0
- package/harness/lib/renames.d.mts +22 -0
- package/harness/lib/renames.mjs +78 -0
- package/harness/lib/schema.d.mts +16 -0
- package/harness/lib/schema.mjs +63 -0
- package/harness/lib/tokens.d.mts +56 -0
- package/harness/lib/tokens.mjs +136 -0
- package/harness/manifest.json +65 -0
- package/harness/standards/borderWidth.json +20 -0
- package/harness/standards/breakpoints.json +36 -0
- package/harness/standards/contrast.json +53 -0
- package/harness/standards/density.json +85 -0
- package/harness/standards/elevation.json +118 -0
- package/harness/standards/iconSizes.json +33 -0
- package/harness/standards/layoutGrid.json +31 -0
- package/harness/standards/letterSpacing.json +35 -0
- package/harness/standards/lineHeight.json +39 -0
- package/harness/standards/motion.json +281 -0
- package/harness/standards/neutrals.json +62 -0
- package/harness/standards/opacity.json +24 -0
- package/harness/standards/radius.json +50 -0
- package/harness/standards/rampMethods.json +126 -0
- package/harness/standards/resolve.d.mts +154 -0
- package/harness/standards/resolve.mjs +209 -0
- package/harness/standards/semanticRoles.json +76 -0
- package/harness/standards/spacing.json +141 -0
- package/harness/standards/typeScale.json +119 -0
- package/harness/standards/weights.json +39 -0
- package/harness/standards/zIndex.json +58 -0
- package/harness/starters/blank.json +9 -0
- package/harness/starters/foundations.json +9 -0
- package/harness/starters/from-codebase.json +12 -0
- package/harness/starters/import.json +11 -0
- package/harness/starters/library+kits.json +9 -0
- package/harness/starters/library.json +9 -0
- package/harness/starters/pick.json +9 -0
- package/harness/templates/CLAUDE.md +30 -0
- package/harness/templates/brand-links.json +234 -0
- package/harness/templates/move-to-claude-INSTALL.md +43 -0
- package/harness/templates/project/.agents/skills/sketchbook/SKILL.md +10 -0
- package/harness/templates/project/.aiassistant/rules/sketchbook.md +7 -0
- package/harness/templates/project/.claude/settings.json +104 -0
- package/harness/templates/project/.codex/hooks.json +19 -0
- package/harness/templates/project/.codex/sketchbook-guard.mjs +57 -0
- package/harness/templates/project/.gemini/settings.json +16 -0
- package/harness/templates/project/.gemini/sketchbook-guard.mjs +15 -0
- package/harness/templates/project/.github/copilot-instructions.md +3 -0
- package/harness/templates/project/.github/hooks/sketchbook-guard.mjs +68 -0
- package/harness/templates/project/.github/hooks/sketchbook.json +12 -0
- package/harness/templates/project/.storybook/main.ts +12 -0
- package/harness/templates/project/.storybook/preview.ts +38 -0
- package/harness/templates/project/.trae/rules/sketchbook.md +7 -0
- package/harness/templates/project/AGENT-WORKFLOWS.md +53 -0
- package/harness/templates/project/AGENTS.md +10 -0
- package/harness/templates/project/GEMINI.md +3 -0
- package/harness/templates/project/THIRD_PARTY_NOTICES.md +28 -0
- package/harness/templates/project/docs/getting-started.md +64 -0
- package/harness/templates/project/eslint-plugins.d.ts +7 -0
- package/harness/templates/project/eslint.config.js +44 -0
- package/harness/templates/project/gitignore +47 -0
- package/harness/templates/project/harness.config.json +50 -0
- package/harness/templates/project/package-lock.json +8400 -0
- package/harness/templates/project/playwright/fixtures.ts +2 -0
- package/harness/templates/project/playwright/helpers/a11y.ts +165 -0
- package/harness/templates/project/playwright/helpers/elements.ts +1 -0
- package/harness/templates/project/playwright/helpers/events.ts +51 -0
- package/harness/templates/project/playwright/helpers/forms.ts +53 -0
- package/harness/templates/project/playwright/helpers/foundations.ts +36 -0
- package/harness/templates/project/playwright/helpers/patterns.ts +89 -0
- package/harness/templates/project/playwright/helpers/storybook.ts +24 -0
- package/harness/templates/project/playwright/helpers/styles.ts +18 -0
- package/harness/templates/project/playwright/helpers/tokens.ts +70 -0
- package/harness/templates/project/playwright/playwright.config.ts +28 -0
- package/harness/templates/project/playwright/tests/foundations/color.behavior.spec.ts +59 -0
- package/harness/templates/project/playwright/tests/foundations/families.behavior.spec.ts +28 -0
- package/harness/templates/project/playwright/tests/foundations/motion.behavior.spec.ts +32 -0
- package/harness/templates/project/playwright/tests/foundations/pages.behavior.spec.ts +54 -0
- package/harness/templates/project/playwright/tests/foundations/samples.behavior.spec.ts +36 -0
- package/harness/templates/project/playwright/tests/screen-reader/stories.spec.ts +95 -0
- package/harness/templates/project/prettier.config.ts +16 -0
- package/harness/templates/project/spec/api.json +319 -0
- package/harness/templates/project/spec/decisions/DECISIONS.md +854 -0
- package/harness/templates/project/spec/registry.json +272 -0
- package/harness/templates/project/spec/schemas/api.schema.json +158 -0
- package/harness/templates/project/spec/schemas/brand-config.schema.json +753 -0
- package/harness/templates/project/spec/schemas/contract.schema.json +678 -0
- package/harness/templates/project/spec/schemas/figma-practices.schema.json +49 -0
- package/harness/templates/project/spec/schemas/harness-config.schema.json +89 -0
- package/harness/templates/project/spec/schemas/registry.schema.json +29 -0
- package/harness/templates/project/spec/tokens/contrast.json +90 -0
- package/harness/templates/project/spec/tokens/overrides.json +4 -0
- package/harness/templates/project/src/controllers/labelled-by.ts +56 -0
- package/harness/templates/project/src/controllers/name-warning.ts +28 -0
- package/harness/templates/project/src/controllers/relink.ts +46 -0
- package/harness/templates/project/src/controllers/roving-focus.ts +88 -0
- package/harness/templates/project/src/mixins/form-associated.ts +117 -0
- package/harness/templates/project/src/mixins/native-control.ts +111 -0
- package/harness/templates/project/src/stories/contract.ts +61 -0
- package/harness/templates/project/src/stories/foundations/BorderWidth.stories.ts +19 -0
- package/harness/templates/project/src/stories/foundations/Color.stories.ts +126 -0
- package/harness/templates/project/src/stories/foundations/Density.stories.ts +35 -0
- package/harness/templates/project/src/stories/foundations/Elevation.stories.ts +19 -0
- package/harness/templates/project/src/stories/foundations/IconSizes.stories.ts +28 -0
- package/harness/templates/project/src/stories/foundations/LayoutGrid.stories.ts +52 -0
- package/harness/templates/project/src/stories/foundations/Motion.stories.ts +105 -0
- package/harness/templates/project/src/stories/foundations/Opacity.stories.ts +19 -0
- package/harness/templates/project/src/stories/foundations/Radius.stories.ts +21 -0
- package/harness/templates/project/src/stories/foundations/Spacing.stories.ts +66 -0
- package/harness/templates/project/src/stories/foundations/Typography.stories.ts +94 -0
- package/harness/templates/project/src/stories/foundations/ZIndex.stories.ts +40 -0
- package/harness/templates/project/src/stories/foundations/families.ts +35 -0
- package/harness/templates/project/src/stories/foundations/page.ts +150 -0
- package/harness/templates/project/src/stories/foundations/tokens.ts +126 -0
- package/harness/templates/project/src/stories/glob.d.ts +6 -0
- package/harness/templates/project/src/stories/raw.d.ts +4 -0
- package/harness/templates/project/src/styles/_a11y.scss +33 -0
- package/harness/templates/project/src/utils/focus-wrap.ts +33 -0
- package/harness/templates/project/src/utils/safe-href.ts +16 -0
- package/harness/templates/project/tsconfig.json +24 -0
- package/harness/templates/project/tsconfig.stories.json +6 -0
- package/harness/templates/project/tsconfig.tools.json +12 -0
- package/harness/templates/project/tsup.config.ts +22 -0
- package/harness/templates/semantic/base.tokens.json +570 -0
- package/harness/templates/semantic/dark.tokens.json +98 -0
- package/harness/templates/semantic/light.tokens.json +99 -0
- package/harness/test/TEST.md +256 -0
- package/harness/test/agent-config.test.d.mts +1 -0
- package/harness/test/agent-config.test.mjs +80 -0
- package/harness/test/agent-diagnostics.test.d.mts +1 -0
- package/harness/test/agent-diagnostics.test.mjs +86 -0
- package/harness/test/agent-guidance.test.d.mts +1 -0
- package/harness/test/agent-guidance.test.mjs +25 -0
- package/harness/test/bootstrap.test.d.mts +1 -0
- package/harness/test/bootstrap.test.mjs +835 -0
- package/harness/test/build.test.d.mts +1 -0
- package/harness/test/build.test.mjs +217 -0
- package/harness/test/checks.test.d.mts +1 -0
- package/harness/test/checks.test.mjs +711 -0
- package/harness/test/claude-layer.test.d.mts +1 -0
- package/harness/test/claude-layer.test.mjs +125 -0
- package/harness/test/claude-live.test.d.mts +1 -0
- package/harness/test/claude-live.test.mjs +160 -0
- package/harness/test/cli.test.d.mts +1 -0
- package/harness/test/cli.test.mjs +236 -0
- package/harness/test/codex-guard.test.d.mts +1 -0
- package/harness/test/codex-guard.test.mjs +111 -0
- package/harness/test/codex-instructions.test.d.mts +1 -0
- package/harness/test/codex-instructions.test.mjs +43 -0
- package/harness/test/codex-live.test.d.mts +1 -0
- package/harness/test/codex-live.test.mjs +90 -0
- package/harness/test/copilot-guard.test.d.mts +1 -0
- package/harness/test/copilot-guard.test.mjs +117 -0
- package/harness/test/copilot-live.test.d.mts +1 -0
- package/harness/test/copilot-live.test.mjs +113 -0
- package/harness/test/design.test.d.mts +1 -0
- package/harness/test/design.test.mjs +1023 -0
- package/harness/test/docs-reference.test.d.mts +1 -0
- package/harness/test/docs-reference.test.mjs +83 -0
- package/harness/test/fixtures/import/shadcn-theme.css +51 -0
- package/harness/test/fixtures/import/tokens-studio.json +83 -0
- package/harness/test/fonts.test.d.mts +1 -0
- package/harness/test/fonts.test.mjs +48 -0
- package/harness/test/foundations.test.d.mts +1 -0
- package/harness/test/foundations.test.mjs +238 -0
- package/harness/test/gemini-guard.test.d.mts +1 -0
- package/harness/test/gemini-guard.test.mjs +124 -0
- package/harness/test/gemini-live.test.d.mts +1 -0
- package/harness/test/gemini-live.test.mjs +116 -0
- package/harness/test/golden/brand.default.json +18 -0
- package/harness/test/golden/tokens.default.css +407 -0
- package/harness/test/helpers.d.mts +28 -0
- package/harness/test/helpers.mjs +43 -0
- package/harness/test/hooks.test.d.mts +1 -0
- package/harness/test/hooks.test.mjs +192 -0
- package/harness/test/opencode-live.test.d.mts +1 -0
- package/harness/test/opencode-live.test.mjs +93 -0
- package/harness/test/package-lifecycle.test.d.mts +1 -0
- package/harness/test/package-lifecycle.test.mjs +73 -0
- package/harness/test/package.test.d.mts +1 -0
- package/harness/test/package.test.mjs +69 -0
- package/harness/test/portable-decisions.test.d.mts +1 -0
- package/harness/test/portable-decisions.test.mjs +99 -0
- package/harness/test/portable-outline.test.d.mts +1 -0
- package/harness/test/portable-outline.test.mjs +39 -0
- package/harness/test/prefix.test.d.mts +1 -0
- package/harness/test/prefix.test.mjs +66 -0
- package/harness/test/preset-docs.test.d.mts +8 -0
- package/harness/test/preset-docs.test.mjs +217 -0
- package/harness/test/propagate.test.d.mts +1 -0
- package/harness/test/propagate.test.mjs +108 -0
- package/harness/test/reference.d.mts +6 -0
- package/harness/test/reference.mjs +62 -0
- package/harness/test/safety.test.d.mts +1 -0
- package/harness/test/safety.test.mjs +479 -0
- package/harness/test/starters.test.d.mts +1 -0
- package/harness/test/starters.test.mjs +504 -0
- package/harness/test/sync-reference.d.mts +9 -0
- package/harness/test/sync-reference.mjs +50 -0
- package/harness/test/tokens.test.d.mts +1 -0
- package/harness/test/tokens.test.mjs +549 -0
- package/harness/test/wall.d.mts +1 -0
- package/harness/test/wall.mjs +57 -0
- package/package.json +150 -4
- package/scripts/audit.mjs +25 -0
- package/scripts/build-barrel.mjs +16 -0
- package/scripts/build-catalog.mjs +7 -0
- package/scripts/build-harness.mjs +107 -0
- package/scripts/build-schema-types.mjs +21 -0
- package/scripts/build-styles.mjs +61 -0
- package/scripts/discover-components.mjs +63 -0
- package/spec/schemas/api.schema.json +158 -0
- package/spec/schemas/brand-config.schema.json +753 -0
- package/spec/schemas/contract.schema.json +678 -0
- package/spec/schemas/figma-practices.schema.json +49 -0
- package/spec/schemas/harness-config.schema.json +89 -0
- package/spec/schemas/registry.schema.json +29 -0
|
@@ -0,0 +1,854 @@
|
|
|
1
|
+
# Decisions
|
|
2
|
+
|
|
3
|
+
Design-system decisions for this installation, newest first (harness format). Accepted decisions are read-only; change one by adding a new entry that supersedes it. The harness's own decision log (D-001 to D-039) lives in the "Sketchbook — Harness spec" doc, Decisions tab.
|
|
4
|
+
|
|
5
|
+
## Index
|
|
6
|
+
- Foundations: SB-0111, SB-0110, SB-0109, SB-0107, SB-0106, SB-0064, SB-0063, SB-0058, SB-0050, SB-0044, SB-0043, SB-0042, SB-0041, SB-0040, SB-0029, SB-0027, SB-0026, SB-0025, SB-0024
|
|
7
|
+
- Incidents (error log): SB-0072, SB-0067, SB-0059, SB-0049, SB-0019, SB-0018, SB-0016, SB-0015, SB-0014, SB-0013
|
|
8
|
+
- Docs: SB-0112, SB-0096, SB-0095, SB-0094, SB-0093, SB-0092, SB-0091, SB-0090, SB-0089, SB-0074, SB-0034, SB-0033
|
|
9
|
+
- Process: SB-0122, SB-0120, SB-0119, SB-0117, SB-0116, SB-0114, SB-0113, SB-0099, SB-0098, SB-0097, SB-0088, SB-0086, SB-0085, SB-0084, SB-0083, SB-0082, SB-0081, SB-0080, SB-0079, SB-0078, SB-0077, SB-0076, SB-0075, SB-0073, SB-0071, SB-0070, SB-0068, SB-0066, SB-0065, SB-0062, SB-0061, SB-0057, SB-0053, SB-0052, SB-0051, SB-0048, SB-0046, SB-0039, SB-0038, SB-0037, SB-0028, SB-0023, SB-0022, SB-0020, SB-0017, SB-0011, SB-0010, SB-0008, SB-0003, SB-0002
|
|
10
|
+
- Theme: SB-0110, SB-0109, SB-0107, SB-0106, SB-0105, SB-0104, SB-0100, SB-0055, SB-0054, SB-0047, SB-0036, SB-0021, SB-0004
|
|
11
|
+
- Components: SB-0121, SB-0118, SB-0115, SB-0108, SB-0103, SB-0102, SB-0101, SB-0087, SB-0060, SB-0045, SB-0012, SB-0009, SB-0007, SB-0006, SB-0005
|
|
12
|
+
- Patterns: SB-0069, SB-0032, SB-0031, SB-0030
|
|
13
|
+
|
|
14
|
+
---
|
|
15
|
+
|
|
16
|
+
### SB-0122 · 2026-11-17 · Component APIs speak the canonical vocabulary; no aliases
|
|
17
|
+
**Status:** proposed
|
|
18
|
+
**Supersedes:** SB-0078
|
|
19
|
+
**Context:** This supersedes SB-0078 in part: its "contracts keep their code names" and its alias list; the vocabulary, A1 and the design-file naming stand. SB-0078 kept the shadcn/ui code names behind aliases in `spec/api.json`, so code said `variant="default"`, `size="sm"`, `checked`, `error`, `invalid`, `open`, `value-change` while contracts, patterns and the design file said `primary`, `small`, `selected`, `errorMessage`, `validation`, `expanded`, `change`. Check A1 warned on 36 props, 3 events and 31 state keys. The package is not published yet, so a rename breaks no consumer.
|
|
20
|
+
**Decision:** Every component's public API uses the canonical names of `spec/api.json`, and no component prop, event or state key needs an alias (`aliases` keeps only `field-set.legend`, an element's label content): size `medium | small | large | tiny` (+ `icon-*`), variant `primary | secondary | tertiary | ghost` (Toggle and ToggleGroup `ghost | tertiary`), `selected` (Checkbox, Switch, Toggle; Toggle's `change` detail `{ selected }`), `readOnly`, `errorMessage` (attribute `error-message`), `validation` (`none | error`, Field, InputGroup), `expanded` (Collapsible, SidebarProvider; Dialog keeps `open`), `selection` (Accordion, ToggleGroup), events `change` (Accordion, Tabs) and `sb-toggle` (Collapsible, SidebarProvider), Button slots and parts `leading-icon` / `trailing-icon` (the anatomy names `icon-start` / `icon-end` stay: they name the design-file layers and token lookups), Typography `kind`, Alert `feedback` (`neutral | danger`). The three SB-0078 proposals (Toggle variants, Alert feedback, Typography kind) are confirmed. A state key is canonical as the kebab-case title or a key listed in `states.canonicalKeys` (`Focus`: `focus-visible`, the keyboard-focus `:state()` hook, and `focus-within`). Token names keep their steps (`button.height.sm`); `recipes.mts` maps canonical values to them (`tokenStep`). Extensions (`destructive`, `link`, `line`, `type`, …) stay.
|
|
21
|
+
**Why:** One name per idea in code, contracts, patterns and the design file; the alias count was debt that only grew harder to pay once the package ships.
|
|
22
|
+
**Watch out:** UI and theme still follow shadcn/ui, the API names do not: a shadcn example needs its names translated (`variant="outline"` is `tertiary`). Item and Empty media's no-box look reads `primary`. A consumer of a pre-release build must rename attributes and listen for `change` / `sb-toggle`.
|
|
23
|
+
|
|
24
|
+
### SB-0121 · 2026-11-17 · The design file may bind a spacing-scale step where the styles multiply the unit
|
|
25
|
+
**Status:** accepted
|
|
26
|
+
**Context:** ToggleGroup's gap is `calc(var(--sb-toggle-group-spacing-unit) * spacing)`; Onboarding uses `spacing="2"` (separate items) since the Nov 15 reflow fix. A design-file gap binds one variable and variables cannot multiply, so the set could only draw the joined bar, and check T4 refuses a contract token the styles do not use. Every spacing preset (`harness/standards/spacing.json`) is linear: step N is N x base and `space.unit` is step 1.
|
|
27
|
+
**Decision:** A library recipe may bind a step of the spacing scale (`space.N`) where the component's styles compute `space.unit x N`, and only for the pairs listed in `SCALE_BINDINGS` (`harness/lib/design/recipes.mts`, today `toggle-group: space.2`). ToggleGroup gets a design option `Spacing` (`0 | 2`, contract `$extensions["design.figma"]`): `0` is the joined bar, `2` draws separate items with every corner and border and the gap bound to `space.2`. FG9 (bindings are contract tokens) and FG12 / `parityOf` (bound tokens are styled) accept exactly those pairs; FG16 proves both looks.
|
|
28
|
+
**Why:** The value is exact in every brand (the scale is unit x N by construction), and nothing else in the drawn library leaves the component's own tokens.
|
|
29
|
+
**Watch out:** A custom spacing scale that is not linear breaks the equality; a new spacing value drawn in the file needs its step added to `SCALE_BINDINGS` and to the option's values.
|
|
30
|
+
|
|
31
|
+
### SB-0120 · 2026-11-16 · Gates run locally, not on GitHub Actions
|
|
32
|
+
**Status:** accepted
|
|
33
|
+
**Context:** `.github/workflows/ci.yml` (PR #18) ran on every PR and every push to main: checks on Node 22 and 24, and a Playwright job. By mid-November it had used 90% of the 2,000 free Actions minutes in the month. The owner wants the project to cost $0.
|
|
34
|
+
**Decision:** The workflow is removed and Actions is turned off for the repository. Every push runs the fast gates in `.githooks/pre-push`: the checks, the maintainer checks, `test:harness`, `typecheck` and `lint`. Before a merge, the owner runs `npm run verify` on a clean tree. It is the former CI list: check, harness tests, typecheck, the stale-output diff, lint, npm audit, the static Storybook and the component specs.
|
|
35
|
+
**Why:** Same gates, no hosted minutes. Splitting them keeps each push fast and saves the Storybook and Playwright minutes for the merge.
|
|
36
|
+
**Watch out:** Only the local Node and OS run now. Node 22 and Linux are no longer covered, and Linux CI is where #18 found a Dialog width assumption that macOS overlay scrollbars hid. Before a release, run `npm run verify` once under Node 22. `git push --no-verify` skips the hook; nothing on the server catches it.
|
|
37
|
+
|
|
38
|
+
### SB-0119 · 2026-11-16 · The harness is TypeScript, compiled in place
|
|
39
|
+
**Status:** accepted
|
|
40
|
+
**Context:** The components are strict TypeScript, but the harness (about 18k lines of `.mjs`: CLI, checks, generators, adapters, tests) is untyped and reads untyped JSON (contracts, brand config, tokens) in 62 files. Node's type stripping cannot run the installed CLI (it skips `node_modules`, and Node 22.12 to 22.17 needs a flag); 21 harness files locate the engine root and their data by a path relative to their own file.
|
|
41
|
+
**Decision:** Harness and `scripts/` sources are `.mts`, compiled by `tsc` (`scripts/build-harness.mjs`, `tsconfig.harness.json`) next to the source: `x.mts` becomes `x.mjs`, so every `import './x.mjs'`, `bin`, hook and doc path stays valid while `.mjs` and `.mts` files coexist during the migration. While a `.mts` still imports a hand-written `.mjs`, `tsc` (with `allowJs`) emits into `node_modules/.cache` and only the output of each `.mts` is copied next to its source, so the `.mjs` is never overwritten. A generated `.gitignore` per tree lists exactly the compiled outputs; a `.npmignore` makes the package ship them and not the sources; `harness/` also ships each module's `.d.mts`, so a project's `#harness/*` imports are typed. The Claude hooks (`.claude/hooks/`, `.claude/skills/*/hooks/`) compile the same way, and `settings.json` runs each through the hand-written launcher `.claude/hooks/run.mjs`: a fresh clone builds once on the first hook, and without output or sources a guard blocks the edit (exit 2) instead of letting it through. The build runs before `npm run check`, `generate`, `test:harness` and `sketchbook`, and in the pre-commit hook; there is no install-time script (B15). Types for JSON come from `spec/schemas` (`generated/types/`). The tool configs are TypeScript too (`prettier.config.ts`, `.storybook/*.ts`), so `engines` is `^22.18 || >=24`, where every supported Node strips types natively; `eslint.config.js` stays JavaScript with `// @ts-check`, type-checked by `npm run typecheck`, because ESLint 10 loads a `.ts` config only through jiti or an unstable flag (`docs/simplicity-debt.md`). Check H2 (source repo only: it skips where there is no `scripts/build-harness.mjs`) fails on any `.mjs` under `harness/`, `scripts/` or the hook folders that no `.mts` beside it compiles, except an allowlist kept in the check with a reason each: `scripts/build-harness.mjs` (bootstraps the build), `.claude/hooks/run.mjs` (the launcher), and `harness/lib/design/compare-runtime.mjs` and `harness/adapters/design/figma/verify-runtime.mjs` (inlined byte for byte into Figma scripts). Tests BH1 to BH8, H-L1 to H-L3 and the H2 case in `checks.test.mts` prove the pipeline.
|
|
42
|
+
**Why:** Types stop whole classes of errors at build time, but they are erased at runtime; compiling in place keeps the engine working from `node_modules`, with no loader, on every supported Node, and with no path rewrites.
|
|
43
|
+
**Watch out:** Running `node harness/...mjs` directly after editing an `.mts` uses stale output until `npm run build:harness`; a fresh clone has no compiled output until its first `npm run` of one of those scripts. Replaces the "compile to `dist/`" wording of the migration plan. A new hand-written module fails H2 until it is converted or allowlisted.
|
|
44
|
+
|
|
45
|
+
### SB-0118 · 2026-11-16 · Modal surfaces wrap Tab inside the page
|
|
46
|
+
**Status:** accepted
|
|
47
|
+
**Supersedes:** SB-0102
|
|
48
|
+
**Context:** This replaces only SB-0102's Watch out on native Tab and on a manual screen-reader pass; the rest of SB-0102 stands. SB-0102 accepted the native modal's Tab behavior: from the last control, focus may pass through the browser's own controls before coming back. The Sidebar drawer already wrapped with its own script. In the stable review of the overlays the owner asked for every remaining finding to be fixed at the source, this one included. SB-0102 also asked for a manual screen-reader pass, which SB-0113 replaced with automated screen-reader views.
|
|
49
|
+
**Decision:** Dialog and the Sidebar drawer keep Tab inside the page: Tab from the last control goes to the first, Shift+Tab from the first goes to the last. Both use one helper, `src/utils/focus-wrap.ts`. It lists the tabbable elements and treats focus inside a component's shadow root as focus on its host, so a slotted sb-input or the Dialog's built-in close button counts. The native modal still provides the top layer, the inert page, Escape and focus restore. Screen-reader checks for these components are the automated views and the Chromium accessibility tree (SB-0113), not a manual pass.
|
|
50
|
+
**Why:** The APG modal pattern and the reference wrap inside the page. One helper keeps the two overlays identical, and the next overlay can reuse it. Accepted by the owner on 2026-11-16.
|
|
51
|
+
**Watch out:** The helper wraps only at the ends; between them the browser's own order applies. The tabbable list is read again on every Tab press, so content whose tabbability changes stays current. A control that handles Tab itself and calls preventDefault keeps it.
|
|
52
|
+
|
|
53
|
+
### SB-0117 · 2026-11-15 · A page written from the components gets its outline checked when it is written
|
|
54
|
+
**Status:** accepted
|
|
55
|
+
**Context:** Value benchmark round 6: Sonnet built a settings page from sb-* components in 10 of 10 runs, and all 10 failed axe `page-has-heading-one` (3 also `landmark-one-main` and `region`). The Card contract already says to put a real heading inside sb-card-title; 7 sessions read it and ignored it. No run ran `sketchbook check`: they built the page and stopped, so a check they must remember to run does not reach them.
|
|
56
|
+
**Decision:** A PostToolUse hook on Edit, Write and MultiEdit (`.claude/hooks/page-outline.mjs`) reads the written file when it is `.html` or `.htm`, a full document (`<html` or `<body`) and uses at least one `<{prefix}-` element (prefix from `harness.config.json`, default `sb`). HTML comments are ignored. It requires a level-1 heading (`<h1`, or `role="heading"` with `aria-level="1"`) and a main landmark (`<main` or `role="main"`); on a miss it exits 2 with what to do and the axe rule ids, which Claude Code shows to the agent; otherwise it is silent. It ships in the Claude layer like the guard hooks. Approved by the owner on 2026-11-15.
|
|
57
|
+
**Why:** The gate fires at the moment the page is written, with no step for the agent to remember, and the message names the exact fix. Silent on success, it adds nothing to the always-on context (H1).
|
|
58
|
+
**Watch out:** It is a static check, not axe: it does not render the page, see shadow DOM, heading order or landmarks other than main, and a heading or main built by script is missed. It runs only in Claude Code sessions with the Claude layer installed; other agents, editors and CI do not run it. A fragment (no `<html` or `<body`) is never checked.
|
|
59
|
+
|
|
60
|
+
---
|
|
61
|
+
|
|
62
|
+
### SB-0116 · 2026-11-14 · A check never runs code the project brought, and an upgrade never overwrites without a yes
|
|
63
|
+
**Status:** accepted
|
|
64
|
+
**Context:** The project scan found that check H1 ran every hook command in the project's `.claude/settings.json` through `sh -c` with the full environment to measure its output, so `sketchbook check` or the pre-commit hook in a cloned, untrusted project ran that project's shell. `sketchbook upgrade --from <folder>` replaced harness-owned files, local edits included, without asking, while a git URL needed `--yes`. The package also ships its build tools as runtime dependencies.
|
|
65
|
+
**Decision:** H1 runs a hook only when it is `node "${CLAUDE_PROJECT_DIR}/.claude/<hooks|skills>/..."` on a file identical to the engine's copy, as `node <file>` (no shell) with only `PATH`, `HOME` and a scratch `CLAUDE_PROJECT_DIR`. Any other hook is not run and is reported as not measured. A folder upgrade that would write refuses without `--yes`, like a git URL, and lists the files. The build tools stay runtime dependencies: the package is the engine plus a reference library, and an app depends on the team's own package, which `init` creates with `lit` only (README).
|
|
66
|
+
**Why:** A check is something people run on code they have not reviewed (a fresh clone, a pre-commit hook); measuring context is not worth executing it. One confirmation rule for every upgrade source, with git as the undo. Splitting the package would cost a repository restructure for the minority who install the reference components directly.
|
|
67
|
+
**Watch out:** A team's own hooks still add to the always-on context but H1 no longer counts them: leave room in `contextBudget`. Editing a shipped hook makes it unmeasured until it matches the engine again.
|
|
68
|
+
|
|
69
|
+
### SB-0115 · 2026-11-14 · Link components drop script URLs from href
|
|
70
|
+
**Status:** accepted
|
|
71
|
+
**Context:** The project scan found eight elements that render a native `<a>` from an `href` prop (button, badge, item, breadcrumb link, pagination link, previous and next, sidebar menu button), bound straight into the template. Lit does not sanitize URLs, so an app that passes a user-supplied link renders `javascript:` as a script sink.
|
|
72
|
+
**Decision:** Every `href` goes through `safeHref()` (`src/utils/safe-href.ts`). It drops `javascript:`, `vbscript:` and `data:` URLs after removing the tab, newline and control characters browsers ignore inside a scheme, renders the `<a>` without `href`, and logs a console warning naming the URL. Every other value passes unchanged. A behavior spec per element proves a script URL is not rendered.
|
|
73
|
+
**Why:** A blocklist of the script-capable schemes closes the XSS sink without breaking legitimate links (`sms:`, `ftp:`, app schemes such as `slack:`) that an allowlist would refuse. This matches how React 19 and Angular treat `javascript:` URLs.
|
|
74
|
+
**Watch out:** A blocked link stops being a link: it leaves the tab order, which is visible in development through the warning. This is defense in depth, not a substitute for the app validating the URLs it stores. A new element that renders `href` must use `safeHref()` too.
|
|
75
|
+
|
|
76
|
+
### SB-0114 · 2026-11-13 · The Claude layer stays within +50% of a bare session
|
|
77
|
+
**Status:** accepted
|
|
78
|
+
**Context:** The value benchmark measured the Claude layer at about 16.7k tokens of fixed context per session and +18% to +88% cost per task over files plus the CLI, with QA depth as its only measured gain. The hammock hooks injected the whole skill at session start, on every prompt and in every subagent; every rule loaded in every session; review-rangers spawned 4 to 6 full agents per review.
|
|
79
|
+
**Decision:** The harness costs at most +50% per task over the same task with files and the CLI only. Always-on context is small and stable: hooks inject a short card once (session start, resume, clear, compact, subagent start), never per prompt; task-specific rules load by `paths:`; skill descriptions stay at most 400 characters; rarely used skills are slash-only. Agent briefs declare a model, and review committees are sized by risk. Check H1 enforces the description cap, the brief model and a byte budget for always-on context (`harness.config.json` `contextBudget`); `docs/research/value-benchmark/scripts/fixed-context.mjs` measures it, with one ablation arm per layer.
|
|
80
|
+
**Why:** Cost is the main pain point of the harness, and the measured overhead bought nothing outside QA depth. Anthropic's guidance and the upstream skills hammock came from (ponytail, caveman) inject once and load the rest on demand.
|
|
81
|
+
**Watch out:** A scoped rule is in context only once a matching file is read; skills that start such work name the rule so it still applies. The budget is bytes, a proxy; the benchmark is the real measure and should be rerun after a large change to the Claude layer.
|
|
82
|
+
|
|
83
|
+
### SB-0113 · 2026-11-13 · Screen-reader checks are automated as stored views of Chrome's accessibility tree; no manual pass
|
|
84
|
+
**Status:** accepted
|
|
85
|
+
**Context:** Command, Dialog and Sidebar each recorded a manual screen-reader pass (VoiceOver, NVDA) as owed before beta. The owner decided passes will not be run by hand and asked for an automated check across the whole harness. Playwright's own `ariaSnapshot` walks the DOM: it misses the accessible description, the modal state, `aria-activedescendant` and focus, and it lists the page behind a modal dialog, which a screen reader cannot reach.
|
|
86
|
+
**Decision:** The screen-reader view is read from Chrome's computed accessibility tree over the DevTools protocol (`screenReaderView` in `playwright/helpers/a11y.ts`): roles, names, descriptions, values and the announced states, after two frames so the tree is current. `aria-current` is read from the element, since the protocol has no property for it. Two layers store views as reviewable text: every story of every component and kit (`playwright/tests/screen-reader/stories.spec.ts`, views beside each component's spec in `__screen-reader__/stories/`, so `sketchbook add` carries them), and, for every component whose contract binds a key that changes what is announced, a behavior-spec test that presses those keys (`expectScreenReaderView`). Both fail on an unnamed control. Check S1 enforces it offline for every shipped component. The manual passes owed by Command, Dialog and Sidebar are replaced by these views.
|
|
87
|
+
**Why:** It covers what a manual pass mostly catches (name, role, state, description, focus, the active item, what a modal hides) on every change, in every project, with no screen reader installed.
|
|
88
|
+
**Watch out:** It is Chromium's tree only, and it is not speech: wording, verbosity, double speech, announcement timing and position in set ("2 of 3", absent from the protocol) are not checked. Speech-level tests (Guidepup driving VoiceOver or NVDA) stay an option for the composite widgets. A changed view is a review item, not an automatic pass: read the diff before `--update-snapshots`.
|
|
89
|
+
|
|
90
|
+
### SB-0112 · 2026-11-13 · A doc grid wraps into bands when a variant does not fit its cell
|
|
91
|
+
**Status:** accepted
|
|
92
|
+
**Context:** Review of Components · Overlays: the States grids of Dialog (Open: a 512 surface on its backdrop, 544) and Sidebar (Open: a 256 panel plus the trigger, 288) gave every column an equal share of the card, and the wide variants were cropped or overflowed, against SB-0091.
|
|
93
|
+
**Decision:** The blueprint gives each grid the fixed width of its widest variant (`drawnWidth`: width tokens, paddings and gaps; text, fill-width layers and nested instances count as nothing). The Figma adapter keeps as many columns per band as leave that width inside the cell padding (`matrixColumns`), and the grid draws band after band, each with its own head row; the verify expects the cells in that order. A grid that fits keeps one band, so the other docs draw as before. Fit-to-cell (SB-0090) still applies to components that reflow.
|
|
94
|
+
**Why:** A grid stays readable and complete at doc width without shrinking an example below its own width.
|
|
95
|
+
**Watch out:** The width is a lower bound from the default density; a variant wide only through its text or a nested instance is not seen, and a variant wider than one full-width column still takes the cell's width.
|
|
96
|
+
|
|
97
|
+
### SB-0111 · 2026-11-13 · The standard letter-spacing preset gains widest; breakpoints default to tailwind
|
|
98
|
+
**Status:** accepted
|
|
99
|
+
**Context:** font.letter-spacing.key (SB-0107) aliases font.letter-spacing.widest and size.breakpoint.narrow (SB-0110) aliases breakpoint.md. The standard letter-spacing preset had no widest step and breakpoints had no default, so `sketchbook tokens scratch`, a new project without those keys, or a switch to the standard preset dropped tokens the semantic layer aliases (harness tests K2, K15, K18).
|
|
100
|
+
**Decision:** The standard letter-spacing preset (the catalog default) gains `widest: 0.1em` (owner choice over re-pointing the key to `wide` or changing the default). Breakpoints default to the tailwind preset: a brand.config without `breakpoints` now emits breakpoint.* (harness/standards/resolve.mjs no longer skips it).
|
|
101
|
+
**Why:** Every preset a team can pick keeps the steps the shipped semantic tokens alias, so components installed from the catalog always resolve; both changes only add tokens.
|
|
102
|
+
**Watch out:** Existing projects gain five breakpoint foundation tokens and, on the standard preset, one letter-spacing step at the next generate; nothing existing changes value.
|
|
103
|
+
|
|
104
|
+
### SB-0110 · 2026-11-13 · New semantic token size.breakpoint.narrow
|
|
105
|
+
**Status:** accepted
|
|
106
|
+
**Context:** Sidebar switches to a drawer below a narrow viewport (sidebar contract Q4); the owner chose a token over a literal.
|
|
107
|
+
**Decision:** Add size.breakpoint.narrow (dimension) with base "{breakpoint.md}" (sketchbook tokens add).
|
|
108
|
+
**Why:** A role name ("narrow") lets components agree on one switch point while the foundation step stays replaceable through the breakpoints preset (SB-0109).
|
|
109
|
+
**Watch out:** CSS: light 0 changed, 1 added, 0 removed. Components using changed semantic tokens: none yet (Sidebar through sidebar.breakpoint).
|
|
110
|
+
|
|
111
|
+
### SB-0109 · 2026-11-13 · breakpoints uses the tailwind preset
|
|
112
|
+
**Status:** accepted
|
|
113
|
+
**Context:** Sidebar needs a viewport breakpoint, and media queries cannot read custom properties. The owner chose a breakpoint token with a build step over a documented literal (sidebar contract Q4).
|
|
114
|
+
**Decision:** brand.config.json breakpoints = { "preset": "tailwind" } (Five breakpoints) via sketchbook tokens preset breakpoints tailwind. Source: https://tailwindcss.com/docs/responsive-design. The style build (scripts/build-styles.mjs, also used by check G1 and sketchbook prefix) inlines a component length token written as `var(--sb-…)` inside an `@media` query with its resolved value; anything else in a media query fails the build. Scripts read the same token at runtime with getComputedStyle, so there is no second constant.
|
|
115
|
+
**Why:** The breakpoint follows the brand like every other foundation, stays checked by T4 (the component token is used) and needs no literal; inlining only media preludes keeps every other variable live.
|
|
116
|
+
**Watch out:** CSS: light 0 changed, 5 added, 0 removed. A changed breakpoint reaches components only after a rebuild (sketchbook generate or propagate), unlike other tokens that update live.
|
|
117
|
+
|
|
118
|
+
### SB-0108 · 2026-11-12 · Composite pitfalls found reviewing Command
|
|
119
|
+
**Status:** accepted
|
|
120
|
+
**Context:** The Command review (review-rangers, LOW: no blocker, accessibility risks) found pitfalls that will recur in every composite that filters slotted children or links roles across shadow roots (Select, Combobox, Menu, Sidebar).
|
|
121
|
+
**Decision:** (1) Element-reference ARIA (`ariaActiveDescendantElement`, `ariaControlsElements`) fails silently where unsupported, so a component that depends on it warns once in the console and its contract states the browser floor. (2) axe sees a combobox-to-listbox link only through an ID, so element-reference links need a scoped, counted exemption in the behavior spec, never a blanket rule filter. (3) A parent that re-filters on child changes must observe property sets too: child props it reads are reflected, and the observer includes `characterData` when text is a fallback value. (4) A focus design that moves the indicator to an active option must keep a visible indicator on the field when no option is active (WCAG 2.4.7).
|
|
122
|
+
**Why:** Each failure is invisible in a default run: the tests pass in Chromium, axe passes with the filter, and a framework setting properties never triggers the observer.
|
|
123
|
+
**Watch out:** Behavior specs for these composites read state with `expect.poll`, not one-shot evaluates, and keep one axe test per story; under load one-shot reads and multi-story tests time out.
|
|
124
|
+
|
|
125
|
+
### SB-0107 · 2026-11-12 · New semantic token font.letter-spacing.key
|
|
126
|
+
**Status:** accepted
|
|
127
|
+
**Context:** Command shows keyboard shortcuts with wide letter spacing (0.1em in the visual reference); no semantic token covered it (command contract Q1, approved by the owner).
|
|
128
|
+
**Decision:** Add font.letter-spacing.key (dimension) with base "{font.letter-spacing.widest}" (sketchbook tokens add).
|
|
129
|
+
**Why:** A role named for shortcut text lets Kbd share it later; it aliases the foundation step added by SB-0106, so it follows the letter-spacing standard.
|
|
130
|
+
**Watch out:** CSS: light 0 changed, 1 added, 0 removed. Components using changed semantic tokens: none (Command will use it through command.shortcut.letter-spacing). Short uppercase-free text only; not for body copy.
|
|
131
|
+
|
|
132
|
+
### SB-0106 · 2026-11-12 · typography.letterSpacing uses the tailwind preset
|
|
133
|
+
**Status:** accepted
|
|
134
|
+
**Context:** The standard preset stops at wide (0.025em); Command's shortcut text needs 0.1em (command contract Q1, approved by the owner).
|
|
135
|
+
**Decision:** brand.config.json typography.letterSpacing = { "preset": "tailwind" } (Six steps) via sketchbook tokens preset letter-spacing tailwind. Source: https://tailwindcss.com/docs/letter-spacing.
|
|
136
|
+
**Why:** The tailwind preset keeps tight, normal and wide at the same values and adds tighter, wider and widest, so nothing existing changes.
|
|
137
|
+
**Watch out:** CSS: light 0 changed, 3 added, 0 removed. Components using changed semantic tokens: none. Three new foundation variables must reach the design file (sketchbook propagate, then the Figma token scripts).
|
|
138
|
+
|
|
139
|
+
### SB-0105 · 2026-11-12 · color.primary set to #874F1B
|
|
140
|
+
**Status:** accepted
|
|
141
|
+
**Supersedes:** SB-0104
|
|
142
|
+
**Context:** The brand color is chosen by the person. #A71824 (red) read confusingly; #DA6403 (orange) failed the 4.5:1 text standard for brand links on white (3.62:1), so the check refused it. #874F1B passes every contrast pair without re-pointing any link token.
|
|
143
|
+
**Decision:** brand.config.json color.primary = "#874F1B" (sketchbook tokens set color.primary #874F1B). The 11-step brand ramp (50 to 950) is generated by the documented OKLCH method (harness/standards/rampMethods.json).
|
|
144
|
+
**Why:** The person chose the color; the ramp and the contrast pairs are generated from it, so every consumer that changes the brand gets the same checks (T6, F1) on its own color.
|
|
145
|
+
**Watch out:** CSS: light 11 changed, 0 added, 0 removed; dark 1 changed. Components using changed semantic tokens: avatar, badge, button, checkbox, empty, item, progress, radio-group, slider, switch. Brand text on white is checked by the contrast pair color.primary on color.background (T6, every mode).
|
|
146
|
+
|
|
147
|
+
### SB-0104 · 2026-11-12 · color.primary set to #A71824
|
|
148
|
+
**Status:** superseded
|
|
149
|
+
**Superseded by:** SB-0105 (the brand color changed twice before it was accepted)
|
|
150
|
+
**Context:** PROPOSAL: what prompted the change (roast finding, brand, product need).
|
|
151
|
+
**Decision:** brand.config.json color.primary = "#A71824" (sketchbook tokens set color.primary #A71824).
|
|
152
|
+
**Why:** PROPOSAL: the trade-off accepted, with the standard's source link.
|
|
153
|
+
**Watch out:** CSS: dark 2 changed, 0 added, 0 removed; light 2 changed, 11 added, 0 removed. Components using changed semantic tokens: avatar, badge, button, checkbox, empty, item, progress, radio-group, slider, switch. PROPOSAL: accessibility limits close to the edge, and who must review.
|
|
154
|
+
|
|
155
|
+
### SB-0103 · 2026-11-12 · Add Command
|
|
156
|
+
**Status:** accepted
|
|
157
|
+
**Context:** The docs site needs a search palette: a field that filters grouped pages, arrows to move, Enter to go, an empty state, shown inside a dialog. The visual reference's Command covers it.
|
|
158
|
+
**Decision:** Add Command (spec/components/command/) as eight elements sharing state through context (the dialog version is the composition sb-dialog > sb-command, not a part). DOM focus stays in the search field (role combobox); the active item is exposed with aria-activedescendant set as an element reference (ariaActiveDescendantElement) from the field to the sb-command-item host, plus ariaControlsElements to the listbox. Filtering is built in (every term must appear in value or keywords, case and accent insensitive, document order kept) and can be turned off with filter=manual. Choosing fires sb-select with { value }. A polite status announces the result count. Not form-associated: the search text is never submitted.
|
|
159
|
+
**Why:** SB-0009 rules out ID references across shadow roots, and moving DOM focus to the items breaks typing; element references from a shadow root outward resolve, as Tabs already relies on. A built-in substring rule meets the docs need with no consumer code; manual leaves room for remote search without an API change.
|
|
160
|
+
**Watch out:** Screen-reader output for element-reference aria-activedescendant needs a manual pass (VoiceOver, NVDA). Deviations from the reference: Home/End move the caret (APG), matches are not ranked, the active item adds an inset ring (accent fill alone is about 1.1:1), the shortcut on the active item uses accent-foreground. Two semantic tokens are missing (list maximum height, shortcut letter spacing).
|
|
161
|
+
|
|
162
|
+
### SB-0102 · 2026-11-12 · Add Dialog
|
|
163
|
+
**Status:** accepted
|
|
164
|
+
**Context:** The docs site needs a modal search palette (a Command inside a Dialog), and edit and confirm dialogs come next. The library has no overlay yet.
|
|
165
|
+
**Decision:** Add Dialog (spec/components/dialog/) as eight elements: `sb-dialog` (owns `open`, fires `sb-toggle` and a cancelable `sb-cancel` before Escape or a backdrop click closes), `sb-dialog-trigger` and `sb-dialog-close` (role-less wrappers around a slotted control), `sb-dialog-content` (the surface, built-in close Button with `hideCloseButton` and a translatable `closeLabel`), `sb-dialog-header`, `sb-dialog-footer`, `sb-dialog-title`, `sb-dialog-description`. The surface is the platform's modal dialog (`<dialog>` with `showModal()` in the content's shadow root, slotted content). The title names it and the description describes it through element references (`ariaLabelledByElements` / `ariaDescribedByElements`), with an `aria-label` copy of the title where unsupported; host `aria-label` on the content names a dialog with no title. The title host is a level 2 heading through ElementInternals.
|
|
166
|
+
**Why:** The native modal dialog gives the top layer, an inert page, Escape and focus restore with no focus-trap script (SB-0007, native first). SB-0009 rules out ID references across shadow roots; element references from a shadow root out to the light DOM resolve, as Accordion's region already relies on. Alternatives: a script focus trap with a portal (re-implements the platform), compose-only close (no visible close by default, against the APG).
|
|
167
|
+
**Watch out:** Native Tab from the last control may pass through the browser's own controls before wrapping (the APG and the reference wrap inside the page). A native modal does not lock page scroll, so the component locks the document element while open. `<form method="dialog">` does not close it. The backdrop and max-width tokens exist (color.overlay, size.dialog.max-width). On narrow screens the footer stacks in DOM order (the visual reference reverses it). Deferred: non-modal, alert dialog, sheet, animation, sticky header and footer. Screen-reader output for the element-reference name needs a manual pass (VoiceOver, NVDA).
|
|
168
|
+
|
|
169
|
+
### SB-0101 · 2026-11-12 · Add Sidebar
|
|
170
|
+
**Status:** accepted
|
|
171
|
+
**Context:** The docs-site shell needs a navigation sidebar: a named landmark with a header, labelled groups of links, the current page marked, optional collapse, and an off-canvas drawer on narrow viewports. SB-0030 kept sidebar layouts out of the kits until the component exists.
|
|
172
|
+
**Decision:** PROPOSAL: add Sidebar (spec/components/sidebar/) as eleven custom elements with the reference's names: provider, sidebar, header, content, footer, group, group label, menu, menu item, menu button, trigger. The provider owns the wide-viewport `open` state (alias of `expanded`, as Collapsible) and shares it through context (SB-0007); `collapsible` is `offcanvas` | `none` (extension). The panel is one native nav landmark named by `label`; menus are lists of links with `aria-current="page"` on the active one; groups are named by their label through element references; the trigger is a disclosure button that references the panel through `ariaControlsElements`, never an ID (SB-0009). Below the breakpoint the panel becomes a native modal dialog drawer (inert page, Escape, focus back to the trigger).
|
|
173
|
+
**Why:** It is the smallest set the docs shell needs plus what is cheap and coherent; a provider keeps the trigger outside the panel without ID wiring; native nav, links and dialog give the semantics without scripts. Deferred: end side, floating and inset looks, icon collapse, rail, actions, badges, skeleton, sub-menus, cookie persistence, keyboard shortcut.
|
|
174
|
+
**Watch out:** The surface, panel widths and backdrop use their own tokens (color.sidebar, color.sidebar-foreground, color.sidebar-border, size.sidebar.width, size.sidebar.drawer-width, the color.overlay shared with Dialog). The breakpoint is a token, not a literal: sidebar.breakpoint (size.breakpoint.narrow, SB-0110) is inlined into the media query at build time and read at runtime by the provider (SB-0109), so a changed breakpoint needs a rebuild. `collapsible=none` still gives a drawer on narrow viewports (the reference turns it off).
|
|
175
|
+
|
|
176
|
+
### SB-0100 · 2026-11-12 · New semantic token size.brand.mark
|
|
177
|
+
**Status:** accepted
|
|
178
|
+
**Context:** The brand icon mark sits in the Figma doc headers; at size.icon.xl (24) it was too small to read, and that token sizes every icon in the system.
|
|
179
|
+
**Decision:** Add size.brand.mark (dimension) with base "{size.56}" (sketchbook tokens add).
|
|
180
|
+
**Why:** A dedicated token lets the mark grow (44 or 56) without resizing icons; the Header keeps its other tokens. The mark is a logo, not an icon, so it does not follow the icon scale.
|
|
181
|
+
**Watch out:** CSS: light 0 changed, 1 added, 0 removed. Components using changed semantic tokens: none. The mark is decorative (empty alt in Storybook, no text role); the header title still names the doc. Switching to 44 means changing the alias to {size.44}.
|
|
182
|
+
|
|
183
|
+
### SB-0099 · 2026-11-11 · A project runs the engine from node_modules, Claude installs the staged Claude layer, and an existing app adopts the design system as a folder
|
|
184
|
+
**Status:** accepted
|
|
185
|
+
**Supersedes:** SB-0098
|
|
186
|
+
**Context:** SB-0098 (proposed) copied the engine into every new project as a workaround and listed its follow-ups: the engine from node_modules, adopt mode, repair when init runs again, the schemas out of the team's `spec/`, trimming the inherited decision log, and a publishable package name. The person also asked that the Claude layer not be written into `.claude/` directly: Claude should install it, so a team's existing `.claude/` is merged with judgment, and `init` should say so.
|
|
187
|
+
**Decision:** (1) A new project depends on the engine package (devDependency; its name is read from the engine's package.json, its spec is `^<version>`, a source checkout's `file:` path, or `--engine <spec>`). No `harness/` or `scripts/` is copied: the engine reads its own files (schemas, kit index, icon catalog), the project's npm scripts call `sketchbook` (new `generate` and `selftest` commands), the pre-commit hook runs `node_modules/.bin/sketchbook check`, and Playwright files import the engine through the subpath import `#harness/*`. (2) The Claude layer (skills, commands, rules, hooks, their settings) is staged in `move-to-.claude/` with an `INSTALL.md` written for Claude: copy, merge `settings.json` by hook command without removing the team's entries, run H1 and `doctor`, delete the folder. `init` ends by naming that step; H1 checks the staged layer and warns until it is installed; `doctor` reports it. (3) `init --adopt` in an existing app builds the design system in `design-system/` (or `--dir`), adds one `<folder>:check` npm script to the app's package.json in its own indentation when absent, never sets the app repository's hooks, and says what line its own hook can call; without `--adopt` a folder with files is still refused. (4) `init` again in a project, with no options, repairs: it restores missing harness-owned and setup files, reports edited ones, never overwrites, and sets `core.hooksPath` at a repository root. `upgrade` without `--from` in such a project refreshes the harness-owned files from the installed engine (after `npm update`). (5) The schemas stay in `spec/schemas/` here; checks and commands read the installed engine's copies, and the manifest lists the six files as exact harness paths so a project's editor-hint copies are refreshed (pinned globs no longer protect exact harness paths). (6) A new project's decision log starts empty and receives only the default decisions its installed contracts cite, again on every `add`; new team decisions are numbered after every default id.
|
|
188
|
+
**Why:** The engine in node_modules makes `npm update` the upgrade and keeps engine code out of team repositories, with nothing lost: the sandboxed retest runs every command, the commit gate, typecheck, the behavior tests and the harness's own tests from the installed package. Claude, not a script, is the right installer for a `.claude/` folder a team may already own. A design system kept in its own folder is the common monorepo shape and never writes over an app's files.
|
|
189
|
+
**Watch out:** Until the package is published, pass `--engine <tarball|git URL>` (simplicity debt, 2026-11-11). In an app repository the design system's hooks fire only in a Claude Code session started in its folder (`move-to-.claude/INSTALL.md`). Renaming the package is one edit to package.json's `name`.
|
|
190
|
+
|
|
191
|
+
---
|
|
192
|
+
|
|
193
|
+
### SB-0098 · 2026-11-11 · The first CLI install copies the engine into the project; an existing repository gets a design-system folder
|
|
194
|
+
**Status:** superseded
|
|
195
|
+
**Superseded by:** SB-0099 (the engine now runs from node_modules; the copy was the interim step)
|
|
196
|
+
**Context:** SB-0097 (proposed) wants the engine to run from node_modules. The baseline (docs/research/cli-distribution-baseline/) and a code read found about 15 places that reach engine files through the project instead: the pre-commit hook (`node harness/checks/run.mjs`), `check --fix` (relative script paths), the build scripts' main guards (`scripts/build-barrel.mjs`, `build-styles.mjs`), `harness/cli/docs.mjs` and `known.mjs` (write beside themselves), `upgrade` (needs `harness/manifest.json` in the project), check K1 (`harness/kits/index.json`), the schemas in `spec/schemas/` (read by `checks/run.mjs`, A1, `brand`, `tokens`, and named by every contract's `$schema`), `lib/icons.mjs` (resolves `lucide-static` from the project), the Playwright helper and two foundation specs (import `../../harness/lib/`), the npm scripts and the slash commands (`node harness/cli.mjs`). Separately, in an existing product repository `init` overwrote the app's `src/index.ts` and check P1 failed on the app's own CSS (baseline F17, F18).
|
|
197
|
+
**Decision:** (1) Until those places resolve from the engine, `sketchbook init` in a new or empty folder copies the harness-owned files (`harness/manifest.json` "harness") from the installed package into the project, with the project template (`harness/templates/project/`, the former test skeleton, kept equal to this repo by R1), a neutral `harness.config.json` (design off, `catalog.source` false, `harnessVersion`), a project `package.json` (the engine's scripts and dependencies, without `prepare`), `CLAUDE.md` and a generated `docs/harness.md`; it builds all of it in a stage beside the folder, runs every check there, and moves it in only when they pass. `upgrade` keeps managing the copied files through the manifest. (2) In a folder that already has files and no `harness.config.json`, `init` writes nothing and offers `--dir <folder>`: the design system lives in its own folder inside the repository. (3) `init` sets `core.hooksPath .githooks` only when the project is a repository root (it runs `git init` when there is none); inside another repository it leaves that repository's hooks alone and says the commit gate is not active. (4) The package ships `harness/`, `scripts/`, the Claude layer and `.githooks`, and the engine's run-time imports are dependencies. (5) Project commands outside a project answer "Not a Sketchbook project" with the init fix, and check H1 runs the Claude-layer guard in every project.
|
|
198
|
+
**Why:** A copy behaves exactly like the clone that works today, so nothing the harness guarantees is lost while the CLI becomes the way in; moving to node_modules is then a refactor of known places, not a precondition. A separate folder is the only way to add the harness to a product repository without writing over its files until adopt mode exists.
|
|
199
|
+
**Watch out:** Follow-ups, each its own decision: the engine from node_modules (the places above), adopt mode for existing repositories (barrel path, P1 scope, per-file ownership of `.claude/`), repair when `init` runs again, the schemas out of `spec/` (baseline F10), trimming the inherited decision log (`docs/simplicity-debt.md`), and a publishable package name. Unverified: whether Claude Code started at an app's root loads `design-system/.claude/`; until it is, open Claude Code in the design-system folder (init says so).
|
|
200
|
+
|
|
201
|
+
---
|
|
202
|
+
|
|
203
|
+
### SB-0097 · 2026-11-11 · One sketchbook init installs the whole harness from the package, then explains it
|
|
204
|
+
**Status:** accepted
|
|
205
|
+
**Superseded in part by:** SB-0099 (the Claude layer is staged in `move-to-.claude/` for Claude to install instead of being written into `.claude/`; adopt mode exists)
|
|
206
|
+
**Context:** Today a team gets the harness only by forking or cloning this repo. The npm package ships `harness/cli.mjs` without its imports, `upgrade` protects `.claude/settings.json`, and nothing creates a project. A baseline run of the CLI in an empty folder, an existing product repo and a clone (docs/research/cli-distribution-baseline/) records 26 findings, among them a crashing package (F1, F2), no project skeleton (F3), non-atomic `init` and `upgrade` (F6, F7), inactive hooks (F13, F14), and an overwritten app entry point in an existing repo (F17).
|
|
207
|
+
**Decision:** (1) `sketchbook init` is the only setup command and always installs everything the harness needs: engine, Claude layer (rules, skills, commands, agent briefs, hooks merged into `.claude/settings.json` by key), git hook (`core.hooksPath`), quality setup (Storybook, Playwright config and helpers), adapters, config and spec skeleton. There is no partial install; a feature a team does not use is turned off in config (for example `adapters.design.tool: none`), not left out. `--start` still chooses only the content (components, kits, foundations). (2) After installing, `init` explains everything it installed, grouped by area, generated from the install manifest and the existing frontmatter: in the terminal, in a generated `docs/harness.md` and in the `--json` envelope. (3) `init` runs `npm install` and `playwright install chromium` itself, shown in the dry run; external needs it cannot install (MCP servers, Node version) are listed with the exact command and verified by `doctor`. (4) The engine runs from `node_modules` and is never edited by the team; the Claude layer is copied into the project and is the team's to edit, with install-time hashes so changes are detected. (5) Running `init` again in a Sketchbook project repairs only: it restores missing harness files and reports edited ones, never overwriting them; `upgrade` stays the way to a newer version and reads from the installed package. (6) The first version runs in an empty or dedicated folder. Existing product repos get an adopt mode later, in which the harness owns a sub-tree and never the app's own files. Once accepted and built, this supersedes the parts of SB-0048 (ownership and upgrade source) and SB-0045 (catalog as the only install source) that it changes.
|
|
208
|
+
**Why:** Starting from a fork is an extra step that the CLI can remove without weakening anything: one command that always installs the complete harness cannot produce a partial harness, so every guarantee (checks, guards, hooks, the pre-commit gate, the command-name guard) holds in every project. Generating the explanation from what was installed keeps it true.
|
|
209
|
+
**Watch out:** The baseline must be fixed first in this order: packaging (F1, F2), project templates that never copy this repo's config (F3, F12), one transaction for `init` with a dry run that tests the same preconditions (F5, F6, F7), shared component source and schemas that a project can receive (F9, F10), and how catalog citations of SB decisions resolve in a new project (F11). The guard that every `sketchbook` command named in `.claude/` exists must run in every project's `npm run check`, since an edited Claude layer and a newer engine can drift. Acceptance test: `init` in an empty folder reproduces this repo's harness-owned files.
|
|
210
|
+
|
|
211
|
+
---
|
|
212
|
+
|
|
213
|
+
### SB-0096 · 2026-11-11 · Design-file-only options are a namespaced extension of the contract, and the generators draw them
|
|
214
|
+
**Status:** accepted
|
|
215
|
+
**Supersedes:** SB-0095
|
|
216
|
+
**Context:** SB-0095 added options to five sets in place (Tabs, Breadcrumb, Card, Item, Table), and the recipes and registry could not express them, so a rebuild or `sync describe` would have dropped them. Contracts are closed (`additionalProperties: false`), so an exception had no sanctioned place. The doc spec for design systems keeps its kinds closed and gives one namespaced `$extensions` hatch; An open-schema design system leaves its schema open and writes design-only axes as free text, which nothing checks.
|
|
217
|
+
**Decision:** Supersedes the "Watch out" of SB-0095 only (the options existed only in the file); the rest of SB-0095 stands. A contract may carry one extra section, `$extensions`, whose keys are dotted namespaces (check C1). The `design.figma` namespace holds `options`: `{ name, kind: boolean | enum, default, shows, reason, set? }`. A boolean is a show switch for the layers its `shows` names (`*` matches within a layer name); an enum is a variant axis (Tabs `Active`). `set` names an element set. Every option needs a `reason`. The library model draws all optional layers, binds each shown layer to its switch with the declared default, and fails when an option shows no layer. A layer under an option is explained by that option in the parity report; other design-only layers stay in `spec/api.json` `layers`, and the Card `Action` slot is a region. Code generators, stories and specs ignore the section.
|
|
218
|
+
**Why:** A design-only exception belongs to one component and needs a reason a check can read; a closed contract with one namespaced hatch keeps the code-facing fields strict (an open schema cannot say what is an exception), and the options are no longer lost on rebuild.
|
|
219
|
+
**Watch out:** The five contracts changed, so their design realizations need a fresh read-back (`sync verify-library`, then `sync realize`). The gap in the Table's first cell (select, avatar, name) is bound to `Table/Cell/padding`: the kit uses `space.stack.sm`, which is the same value (`space.2`), and a Table token keeps the binding inside the contract (FG9, FG12). If the two ever diverge, the Table needs its own token and styles for it.
|
|
220
|
+
|
|
221
|
+
### SB-0095 · 2026-11-11 · The library round: Tabs, Breadcrumb, Card, Item and Table gain the options the stories use, edited in place
|
|
222
|
+
**Status:** accepted
|
|
223
|
+
**Context:** SB-0094's parity check listed what the library could not draw: a third tab and a selected second tab, a middle breadcrumb item, a card header action, an item avatar, and a table with more rows, columns, status badges and a person cell. The person asked for them to be fixed in the library, in place.
|
|
224
|
+
**Decision:** Added to the existing component sets, so every instance keeps working: TabsList gets a Third switch and an Active axis (1, 2, 3); Breadcrumb gets Middle and Ellipsis switches and a `link-middle` item; Card gets an Action slot in a header row (hidden until a layout fills it); Item gets Avatar and Icon switches and an `avatar-media` layer; Table gets Row 3 to 6, Column 4 and 5, Status text and Status badge, Person, Select and Wide first column switches, and a hidden spacer cell for the wide column. Item's default and muted variants have a transparent border, and Empty is centered, as the code and the recipe say. Pattern layouts name these through `show`, `text` and a layout `axes` extra (`{"Active": "2"}`), and the runtime accepts a variant name that starts with the requested one, `key@end` to right-align a text layer, and shows a slot only when the layout fills it.
|
|
225
|
+
**Why:** The gaps were in the library, not the layouts; a layout cannot draw a part its component does not have, and an instance cannot be resized or reordered below its own level.
|
|
226
|
+
**Watch out:** These edits are in the file, not yet in the generators: the component recipes (`harness/lib/design/recipes*.mjs`) and the API registry (`spec/api.json` layers, properties and axes) do not know them, so a rebuild of those sets would drop them and `sync describe` / `sync realize` will report drift until they are updated (debt log). 12 of 21 pattern states match Storybook after this round.
|
|
227
|
+
|
|
228
|
+
### SB-0094 · 2026-11-11 · Patterns in the design file follow the source, then the code, then Storybook, and a parity check proves it
|
|
229
|
+
**Status:** accepted
|
|
230
|
+
**Context:** The eight pattern kits were drawn in the design file from `pattern.json` layouts, and the person found them "too different" from Storybook: pages not centered, footers and badges not at the end, wrong heading sizes, stacked buttons drawn as a row, empty placeholders leaving gaps, corners square on the outside of joined groups. A read-back of structure and text could not see any of it.
|
|
231
|
+
**Decision:** Order of authority is the source data (`pattern.json`, contracts), then the code (the story and kit CSS), then Storybook, then the design file; when they disagree the design file changes, and so does the layout if it contradicts the code. Layouts carry the CSS layout rules: `align` (`center-x`, `end`, `top`, `between`, `center`), `width` as a grid span, `height` (`hug`, `fill`), `rule` (a border hairline), `surface`, `hide`, and percentages for a named layer (`indicator: "66.67%"`). `sketchbook sync compare` renders every state from Storybook, reads the drawn screens back and diffs texts (missing, extra, moved, order, content edges); `docs/design-docs/parity.md` is its report. A difference no layout can fix is a library gap, recorded with `sync stamp note`. Joined groups (ButtonGroup, ToggleGroup) bind their outer corners to the component's radius token after any segment is hidden. Pasting runs through a runtime stored once in the file's plugin data, so a pattern call carries only its own data.
|
|
232
|
+
**Why:** Storybook is what people see and the code is what ships; a design file that only matches its own spec drifts without anyone noticing, and a corner bound to a literal or the zero token breaks the radius mode the file exists to show.
|
|
233
|
+
**Watch out:** Eight of 21 states match today; the rest differ by library gaps listed in each pattern's progress note (Tabs triggers, Card header action, Item avatar, Table rows and cells, Breadcrumb items, Empty and AspectRatio content, right-to-left mirroring of library parts). Fixing those is a follow-up that edits the library in place. Rule: `.claude/rules/figma-fidelity.md`.
|
|
234
|
+
|
|
235
|
+
### SB-0093 · 2026-11-10 · The nested radius rule covers containers only; the anatomy tree steps down per level
|
|
236
|
+
**Status:** accepted
|
|
237
|
+
**Context:** Follow-up to SB-0092: the anatomy tree nested `radius.surface` inside `radius.surface`, and the Guide's Sync status listed repo folders. The person confirmed the rule is for containers, not pills, and that the folder line is not needed.
|
|
238
|
+
**Decision:** Anatomy nodes take a radius by depth: `radius.surface`, `radius.control`, `radius.small`, `radius.xsmall` (deeper stays xsmall). The inset (`space.inset.md`) has no token pair that adds up, so the rule there is "each inner container is one radius step smaller". Pills, swatches and the logo keep their own radius. The Guide drops "Where things live".
|
|
239
|
+
**Why:** An outer corner is always the larger one; a shared file lists no repo folders.
|
|
240
|
+
**Watch out:** FG29 checks the tree list descends and that tags stay `radius.pill`.
|
|
241
|
+
|
|
242
|
+
### SB-0092 · 2026-11-10 · Doc headers sit inset with concentric corners, name no repo path, and the Guide shows the last sync date
|
|
243
|
+
**Status:** accepted
|
|
244
|
+
**Context:** Review of the docs (clearest in dark mode): every Header touched the edges of a square Doc, so a rounded cover sat on a sharp frame; the header line showed a repo path (`spec/components/<name>/contract.md`), which leaks the repo layout in a shared file; the Guide's Sync status showed a token hash nobody can read.
|
|
245
|
+
**Decision:** A rounded layer inside another has the smaller radius, outer = inner + the inset between them. The Doc gets `radius.large` (14) and a Top wrapper with `space.inset.sm` (8) around the Header, which gets `radius.small` (6). The header line is the fixed shell label `header.link.label` ("Auto-generated from the agnostic framework"); the blueprint keeps the source path for `sketchbook docs`. The Guide reads "Last token sync: <date> UTC" from the sync stamp, adding a note when the spec changed since.
|
|
246
|
+
**Why:** Concentric corners read as one object; a shared design file should not expose repo paths; a date says how fresh the file is.
|
|
247
|
+
**Watch out:** Test FG29 resolves the three tokens, so a radius or spacing preset that breaks the sum fails the build and needs a new pair. The anatomy tree still nests same-radius boxes (`radius.surface` inside `radius.surface`).
|
|
248
|
+
|
|
249
|
+
### SB-0091 · 2026-11-10 · Batch 0 is "Actions", and no example in the design file may be cropped
|
|
250
|
+
**Status:** accepted
|
|
251
|
+
**Context:** Review of all component docs: the Pagination example was cut at both ends (a fixed 320 root holding 338 of links), and the "Core" page held Button, Input and Spinner, which share nothing but the order they were built in.
|
|
252
|
+
**Decision:** Batch 0 is "Actions" (Button, ButtonGroup); Input joins Text controls and Spinner joins Feedback and display, next to Progress and Skeleton. A component root hugs its content unless the content can reflow to a fixed width; an empty slot fills its parent; the library verify reports any variant whose content is larger than its frame; Theme matrix cells are 416 wide, room for the widest variant (Pagination at Spacious density) inside the cell padding.
|
|
253
|
+
**Why:** A cropped example documents a component that does not exist; a page named after its role helps people find a component.
|
|
254
|
+
**Watch out:** A wider component than 368 at Spacious needs a wider matrix cell (`MATRIX_CELL_WIDTH`); a doc grid gives a wide instance the cell's width, which only works for components that reflow.
|
|
255
|
+
|
|
256
|
+
### SB-0090 · 2026-11-10 · Accessibility is highlighted in every renderer, fields fit their grid cell, and a component doc reads without a design tool
|
|
257
|
+
**Status:** accepted
|
|
258
|
+
**Context:** Core review of SB-0089: the accessibility attributes did not stand out in the code or the rules, Input instances spilled out of their grid cells (and the Error state sat higher than the others), and the person asked that the doc be part of the tool-agnostic design (the ASCII spec) and work from the CLI, not only as a Figma lesson.
|
|
259
|
+
**Decision:** The blueprint marks what to highlight, tool-neutral: `accent` on the Rule cells and `marks` ([line, start, end] of every `role`, `aria-*`, `aria*` property and `tabindex`) on each code card; the shell token is `code.highlight` (`color.info`, 4.95:1 or more on `color.muted` and `color.card` in both modes). In a grid, content sits at the top of its cell and an instance wider than the cell takes the cell's width. `sketchbook docs <component>` prints the doc in the wireframe notation of `docs/design-docs/` (terminal color for the highlight), `--json` the blueprint any adapter reads; `docs/design-docs/anatomy.md` and `components.md` carry every rule.
|
|
260
|
+
**Why:** One thread from contract rule to implementation, readable at a glance; a grid stays a grid whatever the component width; the design is defined by the spec and the blueprint, and Figma is one renderer of it.
|
|
261
|
+
**Watch out:** Fit-to-cell relies on the component's own auto layout to reflow; a set built with fixed children would clip, so each batch is checked by eye.
|
|
262
|
+
|
|
263
|
+
### SB-0089 · 2026-11-10 · Component docs show Variants and States grids from the library set, and accessibility as contract rules plus the real source
|
|
264
|
+
**Status:** accepted
|
|
265
|
+
**Context:** The component doc blueprint drew one matrix from the contract's `variantMatrix`, whose names are code names, while the library sets use the registry's Figma axes, so instances could not be found; and Button alone has 220 variants. In the Core pilot review the person asked for one frame per anatomy part, for real code instead of rules styled as code, and for wider pills.
|
|
266
|
+
**Decision:** `componentDoc` reads the library model (`libraryModel`): a Variants grid of the look axes at rest (first look axis as rows, last as columns, middle ones joined in the row) and a States grid (first look axis as rows, Rest plus each other state value as columns, only that axis changed); with fewer than two look axes only the States grid is drawn, its Rest column being the variants. Element sets (`spec/api.json` `sets`) are drawn in their component's doc as an Elements section. Anatomy is a frameless Tree whose outermost part is the container. Accessibility is a Rule/Contract table from the contract, then one CodeBlock per source file holding, verbatim, the class members that set a role, `aria-*` or `tabindex`, in the design font of `font.family.code`. Tags take `tag.padX` (`space.stack.md`) left and right. `sketchbook sync components <batch>` writes the pastes and a read-only verify that checks every cell's variant.
|
|
267
|
+
**Why:** The grids keep every look and every state readable at doc width (Button: 48 + 30 cells instead of 220), with names that resolve to the drawn variants; the real source shows how accessibility is implemented, which the contract states only as rules.
|
|
268
|
+
**Watch out:** A component that sets its semantics outside class members (a module-level helper) shows no code block; Card, AspectRatio, Kbd, Typography, Empty, Badge and Direction set none today.
|
|
269
|
+
|
|
270
|
+
### SB-0088 · 2026-11-10 · The Theme matrix shows every set under the corner combinations, plus a Live column
|
|
271
|
+
**Status:** accepted
|
|
272
|
+
**Context:** The Theme matrix was specified for batch 0 only (Button, Input, Spinner) as preview cards, and the docs renderer could not draw component instances. UI decisions are reviewed on this page before any documentation, so it has to show the whole library under the theme axes.
|
|
273
|
+
**Decision:** `themeMatrixDoc` builds a Live column (no mode pinned) and the corner combinations, every theme axis at its first and last value (8 today: Light/Dark x Sharp/Pill controls x Compact/Spacious), and one row per drawn set with its representative variants: the first non-state axis varied, every other axis at its first value, at most 6. The Figma renderer (`sketchbook sync theme-matrix`) pins every axis collection on each cell, not on whole columns, so rows stay aligned under any density; rows are split over several pastes and a read-only script checks the pins and the instance counts.
|
|
274
|
+
**Why:** The corners are the extremes of every axis, so most problems (contrast in dark, clipping in compact, radius in pill) show there; the Live column covers any other combination without drawing all 24.
|
|
275
|
+
**Watch out:** A new theme axis doubles the corners; a set whose first non-state axis has many values shows only the first 6 (Typography shows H1 to Blockquote).
|
|
276
|
+
|
|
277
|
+
### SB-0087 · 2026-11-10 · Avatar fallback and group count use border gray with foreground text
|
|
278
|
+
**Status:** accepted
|
|
279
|
+
**Context:** The fallback and the group count followed shadcn's `bg-muted` with `muted-foreground` text. Our `muted` is neutral-50 (SB deviation for muted-foreground contrast), so the circle read as transparent on white and disappeared on muted panels.
|
|
280
|
+
**Decision:** `avatar.fallback.bg` and `avatar.count.bg` point at `{color.border}` (neutral-200 light, neutral-800 dark); their text points at `{color.foreground}`. A deviation from shadcn.
|
|
281
|
+
**Why:** A visible but light gray, as the review asked; `muted-foreground` on neutral-200 is 3.77:1, below the 4.5:1 text minimum, while `foreground` passes in both modes.
|
|
282
|
+
**Watch out:** `color.border` is used here as a fill; if the border color is retuned, the avatar fill follows it.
|
|
283
|
+
|
|
284
|
+
### SB-0086 · 2026-11-10 · Content regions are native slots, free with a few preferred components
|
|
285
|
+
**Status:** accepted
|
|
286
|
+
**Context:** Regions people fill with their own content (a card's body and footer, an open accordion's content, a tab panel, row actions) were drawn as sample text, so placing real content meant detaching the instance or covering the sample.
|
|
287
|
+
**Decision:** `spec/api.json` `regions` registers each region (`<component>.<layer the recipe draws>` with a slot name, a meaning and optional preferred component folders; A1 checks the preferred names). The tool-neutral model turns the layer into a slot named after it (Figma ties the layer name to the property), keeps the anatomy part for parity, and strips any property binding or exposure inside it. The Figma finish adds one SLOT property per set with the region's meaning as its description and the preferred components' keys as preferred values, with no minimum or maximum, and links the region's frame in every variant; verify expects a SLOT layer with that reference. Regions now: Card Content and Footer (prefers Button), Accordion and Collapsible Content, Tabs Panel, Empty Content, ScrollArea, AspectRatio and Direction Content, Item Actions (prefers Button). AspectRatio and Direction draw a content frame filling the box, since a slot cannot be the top layer; Item draws its actions row (`item.actions.gap`, no longer drift) with a sample Button. Recorded as the `content-regions` aspect (`native-slot`) in `spec/figma-practices.json`.
|
|
288
|
+
**Why:** A slot takes any layer without detaching, so the instance stays linked to the library; preferred values point to the usual content without forbidding the rest.
|
|
289
|
+
**Watch out:** Nothing inside a slot can carry a property, so a sample there has no text property; a recipe that needs one must keep it outside the region. Linking a slot re-lays the variant out and can flip a stretched absolute layer (a focus ring) above it; finish resets flipped absolute layers and verify reports any left (this also caught and fixed the Avatar fallback, flipped since its first build).
|
|
290
|
+
|
|
291
|
+
### SB-0085 · 2026-11-10 · Nested library instances with properties are exposed, under readable names
|
|
292
|
+
**Status:** accepted
|
|
293
|
+
**Context:** Group components (ToggleGroup, ButtonGroup, FieldSet, FieldGroup, ItemGroup) nest instances of other library components. Closed, their properties could only be changed by selecting each nested layer, and the layers read as part names (`item`, `field-other`).
|
|
294
|
+
**Decision:** The tool-neutral model (`harness/lib/design/library.mjs`) marks every nested library instance whose component has properties (a variant axis, or a text, boolean or swap property) as exposed and names it after the component with its index among siblings of the same component (`Toggle 1`, `Button 2`). The Figma build sets `isExposedInstance` on it; verify reads the exposure back; parity counts an exposed instance as explained, so it needs no `spec/api.json` `layers` entry. An instance without properties (Spinner, Kbd) stays closed under its part name. Recorded as the `exposed-instances` aspect (`expose-with-names`) in `spec/figma-practices.json`.
|
|
295
|
+
**Why:** A designer sets each item of a group from the parent's panel, where the names say which item is which; exposing an instance with nothing to set would add an empty entry.
|
|
296
|
+
**Watch out:** A layer name is now generated for exposed instances, so a recipe must not rely on a nested instance's part name for property wiring.
|
|
297
|
+
|
|
298
|
+
### SB-0084 · 2026-11-10 · Underlined text has its own style, variables and text layer in the design file
|
|
299
|
+
**Status:** accepted
|
|
300
|
+
**Context:** The link underline on hover stayed code-only: formatting on a text layer bound to a TEXT property is shared by every variant, so underlining one Button label underlined all 220, and no style carried an underline.
|
|
301
|
+
**Decision:** Every typography role gets an underlined twin composite (`text-style.<role>-underline`, `textDecoration: underline`), pushed as its own variable group in Semantic - Typography and a text style with decoration UNDERLINE. A variant that underlines its label (a variant with its own `underline-offset`, today Button and Badge link on hover) draws a second text layer `<part>-underline` on the twin style, bound to its own TEXT property named in `spec/api.json` (`figma.underline`, "Underlined label text"); the regular label hides in that variant. Recorded as the `text-decoration` aspect (`twin-style-and-layer`) in `spec/figma-practices.json`.
|
|
302
|
+
**Why:** A separate style keeps the underline a system value instead of a hand override, and a separate layer and property keep each variant's formatting its own.
|
|
303
|
+
**Watch out:** Figma cannot bind the decoration offset to a variable, so `<component>.link.underline-offset` stays recorded as drift with that reason. Inline links inside body text (Empty, Item descriptions) are not drawn as twins.
|
|
304
|
+
|
|
305
|
+
### SB-0083 · 2026-11-10 · Zeros are bound by default in every generated design-file UI, with no command of its own (supersedes the command in SB-0082)
|
|
306
|
+
**Status:** accepted
|
|
307
|
+
**Context:** SB-0082 added `sketchbook sync zeros` to bind zeros in sets already drawn. Binding a zero is not a task to run: it is how every generated piece of UI is drawn.
|
|
308
|
+
**Decision:** One shared runtime (`harness/adapters/design/figma/zero.mjs`) is part of every script the Figma adapter writes: library build, finish and layout, the docs (guide and foundations) and the icons. Each binds the zeros it drew (0 padding, gap, counter-axis gap of a wrapping layout and corners of auto-layout frames, components and sets, and the unused sides of a one-sided stroke) to the semantic zero of its kind before it returns. `sync zeros` is removed. The library verify keeps failing on an unbound 0.
|
|
309
|
+
**Why:** A default cannot be forgotten; a command can.
|
|
310
|
+
**Watch out:** A future generator (a new doc kind, the theme matrix, component docs) gets the same behavior by including `ZERO_RUNTIME` and calling `bindZeros` on what it drew; FG21 fails for a generator that does not.
|
|
311
|
+
|
|
312
|
+
### SB-0082 · 2026-11-10 · Every zero the design file draws is bound (supersedes the scope of SB-0081)
|
|
313
|
+
**Status:** accepted
|
|
314
|
+
**Context:** SB-0081 bound only the zeros a component draws on purpose. In the file that left about 6,000 zeros typed as numbers (a frame's default padding and gap, square corners), so a designer inspecting a component saw no zero token applied.
|
|
315
|
+
**Decision:** Every frame and component the renderer draws binds each 0 padding, gap and corner (and the unused sides of a one-sided stroke) to the semantic zero of its kind, at build. `sketchbook sync zeros` writes a script that binds them in place in sets already drawn, without a rebuild (looks do not change). The library verify fails on any such 0 left unbound. Recipes no longer mark zeros one by one. Supersedes the "Watch out" of SB-0081.
|
|
316
|
+
**Why:** A zero is a value like any other; leaving most of them unlinked hid the tokens the user asked for.
|
|
317
|
+
**Watch out:** Instances are not touched (their values come from their own component). A frame with fixed width or height keeps its size; only padding, gap, corners and stroke sides are bound.
|
|
318
|
+
|
|
319
|
+
### SB-0081 · 2026-11-10 · Zero is a token: a semantic none step per kind, bound in the design file
|
|
320
|
+
**Status:** accepted
|
|
321
|
+
**Context:** Only the foundation had zeros (space.0, radius.none, border.width.0; opacity had none), so the semantic scales started above 0 and the design file wrote literal zeros where a component draws nothing on purpose: the square inner corners of a joined group, the unused sides of a one-sided stroke, the gap of a joined group. Figma reports those as unlinked values.
|
|
322
|
+
**Decision:** (1) The opacity standard gains a 0 step. (2) The semantic layer has one zero per kind: `space.none`, `border-width.none`, `opacity.none`, and `radius.square` (named square because `radius.none` is the foundation step and the layers share one namespace). They are in the semantic template a new install copies. (3) The Figma renderer binds every zero it draws on purpose to them (a `ZERO` map beside the layout tokens): square corners, unused stroke sides and joined gaps (`z` in a recipe). (4) The library verify ignores the zero variables in its node lines and reports any such zero left unbound. Practice `zero-values` adopts `bound-none-step`.
|
|
323
|
+
**Why:** Every value the file draws is then a token, scales read from 0, and a designer never second-guesses an unlinked 0.
|
|
324
|
+
**Watch out:** Frames whose padding or gap is 0 by default (nothing to space) are not bound; only zeros a component draws on purpose are. A team renaming a zero token renames it through `sketchbook tokens rename`, and the renderer's `ZERO` map follows the new name.
|
|
325
|
+
|
|
326
|
+
### SB-0080 · 2026-11-10 · Element sets and a checked design realization
|
|
327
|
+
**Status:** accepted
|
|
328
|
+
**Context:** The library had one Figma set per contract, so elements with styles of their own (the Field set, group, legend, separator and title; a Kbd or Item group; the ButtonGroup separator; the line Tabs list) were never drawn, and "the library is done" could not be shown: `realizations.design` stayed empty in every contract and nothing listed which styled tokens the file leaves out, or why.
|
|
329
|
+
**Decision:** (1) `spec/api.json` `sets` names the elements drawn as sets of their own, `<component>.<element>`; the set is `<component>/<element>` in every `sketchbook sync` command, named after its element (FieldSet), built from the element's anatomy and props with its component's tokens, and follows its component in every drawn list (describe, verify-library, layout). A1 refuses a set whose component has no such element. (2) `sketchbook sync verify-library --ingest <file>` records each set's read-back with the contract hash in `generated/design/library-verify.json`. (3) `sketchbook sync realize` writes `realizations.design`: the sets and their variant counts, one coverage line per set, and status complete only when every set read back clean against the current contract and every token the styles use is drawn or recorded in `realizations.design.drift` with the reason it is not. (4) Check D4 holds a complete realization to that, and fails a drift entry on a token the file now draws. (5) The contract hash that marks a component for redrawing leaves `realizations` out: writing the outcome back is not a change to draw.
|
|
330
|
+
**Why:** What is drawn, what is not and why is then recorded in the contract and kept true by a check, not by memory; a team removing or adding an element set changes the registry, not the renderer.
|
|
331
|
+
**Watch out:** Drift reasons are written by a person (or an agent with the person's review) in the contract; `sync realize` keeps them and only rewrites status, properties and coverage. A rebuilt set must be read back again before its component can stay complete.
|
|
332
|
+
|
|
333
|
+
### SB-0079 · 2026-11-09 · Design-file practices are registered in spec/figma-practices.json
|
|
334
|
+
**Status:** accepted
|
|
335
|
+
**Context:** How a component is drawn in a design file (state axes, optional parts, text properties, helper components, nesting, page layout, descriptions) was decided case by case while building the library, with assumptions. Three libraries were studied for their approach: Carbon v11, Helsinki 6.0.0 and a third product system that is not named in this repository.
|
|
336
|
+
**Decision:** (1) `spec/figma-practices.json` lists each aspect with the options the studied libraries use and the one Sketchbook adopts, with the reason; `sketchbook api practices [aspect]` shows it and check A1 fails on an adopted option that does not exist or a source that is not listed. (2) Adopted: State holds only interaction states, with validity, availability and on/off as their own axes; optional parts and text use the registry's content names (`Description`, `Description text`); helper components only when a piece is shared by two or more components; composed parts nest the library component; the contract's visible content is drawn; one Library page; descriptions are sectioned and generated. (3) The third source is cited only as `reference-c`, with no name, link or component names; its approach is written as Sketchbook's own. (4) A Figma component description is generated from contract.md, contract.json and the registry, never written in the file.
|
|
337
|
+
**Why:** The approach is recorded once, checkable and open to change per aspect, instead of living in a build script or in my assumptions; the descriptions are what a design tool's MCP hands to an agent, so they must come from the source files.
|
|
338
|
+
**Watch out:** The studied files were read for approach only; nothing is copied. An aspect's adoption can change by a new decision, and the sets already drawn follow it only when rebuilt (the improvement step).
|
|
339
|
+
|
|
340
|
+
### SB-0078 · 2026-11-09 · One API vocabulary, registered in spec/api.json and checked by A1
|
|
341
|
+
**Status:** accepted
|
|
342
|
+
**Context:** Prop names, values, state keys, event names and the property names in the design file were spelled several ways (`readonly`, `checked` and `pressed` for the same idea, `sm | lg` next to `small | large`, a different Figma property list written by hand in each contract). Nothing in the harness knew what a valid name was.
|
|
343
|
+
**Decision:** (1) `spec/api.json` is the vocabulary: canonical props (`variant` as `primary | secondary | tertiary | ghost`, `feedback`, `size` as `tiny | small | medium | large`, `selection`, `validation`, and the booleans `disabled`, `readOnly`, `selected`, `indeterminate`, `expanded`, `open`, `loading`, `required`), content (`label`, `leadingIcon`, `trailingIcon`), interaction states (`Rest | Hover | Focus | Press | Loading`; look-changing booleans are their own `False | True` axes in a design file, Disabled only at Rest) and events (`change`, `input`, `click`, plus custom events carrying the element prefix). (2) Where a component's code spells a name differently, `aliases` map it, with a value map; deliberate component-specific names are `extensions`, each with a reason. Contracts keep their code names, so check C3 and the web components are unchanged: nothing breaks. (3) Check A1 fails on any prop, value, event or state key that is not registered and warns with the alias count; `sketchbook api list|check|explain` shows the table. (4) The design adapters take property and value names from this registry, not from text written per contract.
|
|
344
|
+
**Why:** One file defines what each name means and how it is drawn, so Figma, docs and code stop drifting; keeping the code names behind aliases makes the gap visible and measurable without a breaking change.
|
|
345
|
+
**Watch out:** An alias is debt: the count should only go down, and migrating a component's API means removing its aliases in the same change. Entries marked `proposal` in the registry (`orientation`, the typography `kind`, Alert's `feedback`, the `ghost` mapping for Toggle) are not confirmed.
|
|
346
|
+
|
|
347
|
+
### SB-0077 · 2026-11-09 · Icons are a layer: spec/icons.json, one Figma component set per icon
|
|
348
|
+
**Status:** accepted
|
|
349
|
+
**Context:** Components use Lucide icons, but the SVGs were inlined in 21 story files and the design file had no icons at all, so a component with an icon slot had nothing to swap in.
|
|
350
|
+
**Decision:** (1) `spec/icons.json` lists the icons the system uses (Lucide, ISC): name, category, aliases and the SVG geometry. It is team-owned; `sketchbook icons list|add|remove` edits it, and `add` reads `lucide-static` (a devDependency) so a design sync needs no dependency. (2) `sketchbook sync icons` writes use_figma scripts that draw an `Icons` page: one component set per icon named `category / name`, a `Size` variant per `size.icon.*` token (`sm`, `default`, `lg`, `xl`; named by role so a preset change renames nothing), width and height bound to that token, one `Vector` child per variant with only a stroke, bound to `color.foreground`. One drawing scales with the size and so does its stroke, as in code. (3) An icon already on the page is kept, so a re-run only adds. (4) Components take icons through instance-swap properties (`iconStart`, `iconEnd`), never redrawn.
|
|
351
|
+
**Why:** One list means stories, contracts and the design file name the same icons; naming variants by token role keeps them stable when the icon-size preset changes; a stroke-only vector bound to a color variable lets the host component recolor it, like `currentColor`.
|
|
352
|
+
**Watch out:** The icons are not hand-tuned per size (a size is a scaled copy). Removing an icon from the catalog does not delete it from the design file. Categories are the team's own, not Lucide's.
|
|
353
|
+
|
|
354
|
+
### SB-0076 · 2026-11-09 · Figma file organization: Layer - Domain collections, every token reaches the file, styles fully bound
|
|
355
|
+
**Status:** accepted
|
|
356
|
+
**Supersedes:** SB-0075
|
|
357
|
+
**Context:** The first Figma push (SB-0075 (3)) named collections after the payload (Foundation, Mode, Shape, Density, Semantic, Component) and variables after token paths. The owner found it too messy next to a mature in-house design system, whose files group variables by layer and domain, colors by role and typography by text style, and bind text styles to variables. 69 tokens (durations, easings, em letter spacing) had no variable and shadows were effect styles with raw values.
|
|
358
|
+
**Decision:** Supersedes SB-0075 (3) only; the rest of SB-0075 stands. (1) Collections are `Layer - Domain`: `Primitives - Color`, `Primitives - Global` (hidden), `Semantic - Color` (Light/Dark), `Semantic - Shape`, `Semantic - Density` (one mode per preset), `Semantic - Global`, `Semantic - Typography`, `Components`. Variable names are the token path with capitalized groups (`Space/Inset/md`); semantic colors are grouped by role from their scopes (`Color/Background|Text|Stroke/*`); a preset's foundation steps sit under `Radius/Scale`; a text role's parts under the role (`Body/size`). Code syntax stays the CSS variable. (2) Every spec token reaches the file: durations and em spacing as numbers, easings as `cubic-bezier()` strings, all without scopes; `sync tokens` reports coverage and test F1 fails on any token left out. (3) Text styles bind family, size, weight, line height and letter spacing to `Semantic - Typography` variables (line height and letter spacing resolved to pixels, family a real font from `adapters.design.fonts`); effect styles bind color, offsets, blur and spread to `Elevation/<Step>/*` variables that alias `Shadow/*` primitives. (4) Role scopes on colors (fills, text, strokes, read from the token name). (5) `sync stamp tokens` saves what reached the file (`generated/design/figma/pushed.json`) and the next `sync tokens` writes only what changed (`--full` for all); scripts are compacted to stay under the 50,000-character call limit. The file was rebuilt once (old collections deleted with the owner's consent before anything was bound) and verified: 26,616 values over 24 combinations, 0 mismatches.
|
|
359
|
+
**Why:** Designers find a variable by layer and domain, not by payload origin; binding every style field means a token change reaches every text and shadow; full coverage means Dev Mode shows every token the code has.
|
|
360
|
+
**Watch out:** Figma names no longer equal token paths, so verify keys by collection and name from the model and maps back to tokens. The role of a semantic color comes from its name (`-foreground` is text, `border`, `ring`, `input` are strokes); a new color that fits neither is a fill until named otherwise. After this rebuild the upsert-only rule applies again: never delete a bound variable.
|
|
361
|
+
|
|
362
|
+
### SB-0075 · 2026-11-09 · Figma is the design tool; Penpot dropped; one variable collection per theme axis
|
|
363
|
+
**Status:** accepted
|
|
364
|
+
**Supersedes:** SB-0008
|
|
365
|
+
**Context:** Penpot was too slow for documentation at this size: every plugin call got slower with the shapes on the page, a call over about 40 seconds got the tab throttled, and a theme switch re-laid-out every bound shape (about 20 seconds per combination). The owner decided to drop Penpot entirely and go Figma-only.
|
|
366
|
+
**Decision:** Supersedes SB-0008 and the Penpot-specific parts of SB-0010, SB-0051 and SB-0074 (5). (1) The Penpot adapter, the `design-penpot` skill, the `from-design-file` starter and the `penpot` import format are removed; `tokens import --from dtcg` reads a folder of sets as well. (2) Tool-neutral design logic (token payload with theme axes, contracts, generic component plan, doc blueprints, stamp, read-back comparison, progress register) lives in `harness/lib/design/`; `harness/adapters/design/figma/` turns it into `use_figma` scripts. Stamp, verify and progress files are `generated/design/{stamp,verify,progress}.json`. (3) Variables: one collection per theme axis (`Mode`, `Shape`, `Density`; one mode per theme, the brand default first) and one single-mode collection per layer (`Foundation` hidden from publishing, `Semantic`, `Component`); a token lives in exactly one collection, aliases cross collections and resolve with the node's mode for the target collection, so a component variable follows Shape and Density. Every variable has scopes (none for foundation, line heights and font stacks) and WEB code syntax `var(--<prefix>-…)`. Typography composites are text styles bound to the size variable; shadows are effect styles. (4) Scripts upsert by name and never delete: a removed or retyped variable is reported, not recreated. (5) `sync verify` resolves every variable for every combination of modes in one read-only call (no canvas switching) and compares with the spec; D1 fails on a mismatch.
|
|
367
|
+
**Why:** Figma models theme axes natively (collections with modes, set per frame) and resolves cross-collection aliases per node, so one binding proves all 24 combinations; reading values instead of switching themes makes verify seconds, not minutes.
|
|
368
|
+
**Watch out:** A collection with several modes needs a paid Figma plan (the file must live in it). Deleting a variable in Figma unbinds every node that used it: rename with `sketchbook tokens rename`, never delete and recreate. Figma cannot bind a line-height ratio or a CSS font stack: text styles take the ratio as a percent and the first family of the stack Figma has (else Inter).
|
|
369
|
+
|
|
370
|
+
### SB-0074 · 2026-11-09 · Design files document themselves from one tool-agnostic shell; Mode, Shape and Density are theme groups
|
|
371
|
+
**Status:** accepted
|
|
372
|
+
**Context:** The first Penpot sync drew small `[sb] X . docs` panels beside each component on one page: no header, no container, no order, values typed in the renderer, and no way to see the system switch look. A reference file (the Android UI Kit) showed what good documentation is: one shell (Header, then Body), flex layouts everywhere, every fill and size a token, one page per area.
|
|
373
|
+
**Decision:** (1) The doc shell is data in `spec/design-docs.json` (regions, token roles, grid spans, a fading ring pattern in the Header, page order and flow) with a readable ASCII view in `docs/design-docs/`; a renderer never types a value (checks T7 and D3 keep every token real; `tokens rename` follows). The one absolute is `adapters.design.docs.width` in `harness.config.json`. (2) Docs sit side by side, left to right, on every page. (3) A component doc has a Matrix of its variants (real library instances, excluded combinations left visibly empty), an anatomy Tree of nested boxes, an accessibility CodeBlock on one left margin, and its tokens as Tags grouped by category; all content comes from the contract. (4) Look switching is three theme groups, Mode (brand.config modes), Shape (radius presets) and Density (density presets), generated from the standards catalog through the same brand and links engine the code build uses: each theme holds the linked semantic tokens plus the foundation tokens its presets change, and the brand's own preset is active. (5) `sync verify` activates every combination of one theme per group (24 today) and compares the values Penpot resolves with the spec computed for that combination; a mismatch fails D1.
|
|
374
|
+
**Why:** One shell makes every doc readable the same way and makes a second design tool a renderer, not a re-explanation; theme groups prove the tokens work (a bound shape re-themes live) without 24 hand-made copies; deriving values from the catalog means the design file and the code cannot disagree.
|
|
375
|
+
**Watch out:** Penpot limits (SB-0010 and `docs/design-docs/tool-mapping.md`): a long plugin call gets the tab throttled (draw docs in parts, one verify combination per call), `resize()` makes a board fixed so hug sizing must be set again, a gradient stop cannot be bound to a token (the pattern is stepped-opacity rings), and the system font stack is not available. A stale value can survive an interrupted theme switch: toggle a theme away and back, or re-sync. Components without a hand-written recipe are built by a generic planner from their contract (`generic.mjs`), which infers token bindings from names; check a new component's doc before trusting it.
|
|
376
|
+
|
|
377
|
+
### SB-0073 · 2026-11-09 · Skills own their agents; one skill standard (forge-me-a-skill)
|
|
378
|
+
**Status:** accepted
|
|
379
|
+
**Context:** The Claude layer packaged work two ways: ten skills in two frontmatter formats with free-form bodies, and four top-level agents in `.claude/agents/` that each belonged to one skill (contract-author already kept its phases as briefs in its own folder). The accessibility skill listed as needed (WCAG 2.2 checks tied to the Storybook a11y addon and the axe helper in the behavior specs) was missing.
|
|
380
|
+
**Decision:** Supersedes the agent locations in SB-0037 and SB-0043. (1) There is no `.claude/agents/`: a role another agent runs is a brief in the owning skill's `agents/` folder, launched with the `Agent` tool as a general-purpose agent whose prompt is the brief plus its inputs (`foundations/agents/` critic and mapper, `a11y-checker/agents/a11y-auditor`, `component-builder/agents/parity-auditor`, `contract-author/agents/` extractor, drafter, validator). (2) `forge-me-a-skill` defines one standard: frontmatter `name`, `description` with `Trigger:`, `metadata` (author, version, changelog, auto-invoke, allowed-tools); sections When to use, Critical patterns, Decision tree, optional extras, Commands, Resources; folders agents, assets, hooks, references, scripts. Every skill was rewritten to it, and `harness/test/claude-layer.test.mjs` enforces it. (3) `a11y-checker` joins, ported white-label and merged with the a11y-auditor.
|
|
381
|
+
**Why:** One place per role and one shape per skill: a reader (or an agent) finds a skill's roles, rules and commands in the same spot every time, and a test keeps it that way.
|
|
382
|
+
**Watch out:** A brief launched this way gets no tool allowlist from the platform; its `tools` frontmatter is a declared contract the launching skill tells the agent to keep, and the read-only briefs say what they never edit. `harness/manifest.json` keeps `.claude/agents/**` as harness-owned so `sketchbook upgrade` lists an older install's leftover agent files under "Gone upstream, kept here" instead of skipping them silently; delete them once the skill briefs are in.
|
|
383
|
+
|
|
384
|
+
### SB-0072 · 2026-11-09 · Incident: token staging and upgrades could overwrite the team's work
|
|
385
|
+
**Status:** incident
|
|
386
|
+
**Context:** The second review round found two data-loss paths that passed every check. Token commands (SB-0065) compared the live tree with the stage at the end of the run, then wrote the stage over every differing file and deleted every file the stage lacked: anything saved or created under spec, src, playwright, docs, .storybook, brands or the catalog while a command ran (an editor's autosave, a parallel agent) was reverted or deleted. `upgrade` (SB-0062) wrote `harness/manifest.json` like any harness file, so the first upgrade installed the upstream ownership rules and the second let upstream overwrite team and shared files, `package.json` scripts included (code execution).
|
|
387
|
+
**Decision:** Fixed by SB-0070 (staging works from a snapshot and refuses on conflict; upgrades never write the manifest or a pinned list of team files). Each path has a harness test that fails on the old code (K24, S36).
|
|
388
|
+
**Why:** A command that writes files must only write what it read and owns; a race or an upstream must not be able to widen that.
|
|
389
|
+
**Watch out:** Any new command that stages a copy follows the same rule: diff against what it copied in, check the target is unchanged before writing, roll back on error.
|
|
390
|
+
|
|
391
|
+
### SB-0071 · 2026-11-09 · init refuses before it writes; --yes never detaches the catalog
|
|
392
|
+
**Status:** accepted
|
|
393
|
+
**Context:** Review round: `init` with brand options regenerated without the stale-links guard token commands use (SB-0065), silently reverting hand edits to brand-linked semantic tokens; `init --start blank --primary "#ff0000"` exited 1 on the removal refusal after it had already written brand.config, the foundation, tokens.css and the snapshot. In the catalog source repo `--yes` (meant to confirm removals) also detached the catalog (SB-0061), and the detached repo kept the note "This repo is the source of harness/catalog".
|
|
394
|
+
**Decision:** Supersedes SB-0061 in part. (1) `init` plans the starter and runs every refusal before writing anything: removals need `--yes`; brand options, or a starter with a foundations patch, refuse while a linked token differs from its link unless `--yes` (a dry run lists them as `staleLinks`); a bad brand answer is refused before a prefix rewrite. `--yes` is now accepted with brand options alone. (2) In the source repo only `--detach-catalog` sets `catalog.source` to false, with the same loud warning; `--yes` never does. Detaching rewrites `catalog.note` to say what is true afterwards.
|
|
395
|
+
**Why:** A refused command must leave the tree as it was, and one flag must not confirm two unrelated risks.
|
|
396
|
+
**Watch out:** A team repo copied from Sketchbook now detaches only with `--detach-catalog`; scripts that relied on `--yes` keep the catalog tracked (G1 then asks for `catalog:build` after component edits). In the source repo `kits remove` still exits 1 until `npm run catalog:build` (logged in docs/simplicity-debt.md).
|
|
397
|
+
|
|
398
|
+
### SB-0070 · 2026-11-09 · Token staging diffs against its own snapshot; upgrades never take ownership from upstream
|
|
399
|
+
**Status:** accepted
|
|
400
|
+
**Context:** See the incident SB-0072: token commands wrote over and deleted files changed during the run; `upgrade` installed the upstream `harness/manifest.json`.
|
|
401
|
+
**Decision:** (1) `runPlan` copies the staged paths file by file and records each file's content hash. What changed is the stage against that snapshot, never against the live tree; a file deletion only reaches files that were in the snapshot. Before copying back, each target's live content must still equal its snapshot (or still be absent); otherwise the command exits 1, writes nothing and lists the files (`data.conflict`). Every target is backed up before it is written and all are restored on any error. (2) `upgrade` never writes `harness/manifest.json` or `.claude/settings*.json`, and never writes `brand.config.json`, `harness.config.json` (apart from `harnessVersion`), `package.json`, `package-lock.json`, `spec/**`, `src/**`, `brands/**` or `playwright/tests/**` even when both manifests call them harness-owned; they are listed as protected. The upstream manifest's glob differences are reported (`data.manifest`) for a merge by hand. Supersedes SB-0062 (1) in part: a widened upstream manifest no longer takes effect on a second upgrade.
|
|
402
|
+
**Why:** The snapshot is the only record of what the command read; ownership rules taken from the side being installed are no rules.
|
|
403
|
+
**Watch out:** A token command that races an edit to one of its own targets now fails and must be re-run. Legitimate ownership changes upstream need a hand edit of `harness/manifest.json`.
|
|
404
|
+
|
|
405
|
+
### SB-0069 · 2026-11-08 · The data table kit reflows at 320px
|
|
406
|
+
**Status:** accepted
|
|
407
|
+
**Context:** The full-house review (accessibility lens, Blocker A11Y-1) measured the Data Table kit at 320 CSS px: grid items kept the table's min-content width, so the scroll area never scrolled and the whole page did (main 522px wide), failing WCAG 1.4.10 Reflow. No kit spec ran at a narrow width. The owner approved the fix.
|
|
408
|
+
**Decision:** The kit's grid is one `minmax(0, 1fr)` column and its children may shrink (`min-inline-size: 0`), so only the table scrolls, inside `sb-scroll-area`. Its spec checks every state at 320px (no page overflow, title on screen) and that the table overflows its scroll area there.
|
|
409
|
+
**Why:** Zoomed and small-screen users must reach the title, search and main action without horizontal scrolling; only the table may scroll.
|
|
410
|
+
**Watch out:** Other kits and Foundations pages are not yet tested at 320px; the review found the Onboarding kit and five Foundations pages overflowing (open items).
|
|
411
|
+
|
|
412
|
+
### SB-0068 · 2026-11-08 · Harness tests run on a reference project built from harness-owned files
|
|
413
|
+
**Status:** accepted
|
|
414
|
+
**Context:** Review round: the harness tests (harness/test/**, replaced by `sketchbook upgrade`) built their fixtures by copying the team's live spec/, src/, docs/ and configs, so they assumed this repo's content (35 components, 8 kits, default semantic names, catalog.source true). After `init --start blank --yes` `npm run check` passed but `npm run test:harness` (run by CI) failed about 17 tests; after `--start library --yes` about 4; unlinking a token failed the templates test.
|
|
415
|
+
**Decision:** `fixture()` copies a reference project assembled once per test process (`harness/test/reference.mjs`) from harness-owned files only: a pinned skeleton in `harness/test/fixtures/reference/` (configs, registry, schemas, decisions, shared src/playwright/.storybook files), `golden/brand.default.json`, the semantic and brand-link templates through the generator, and every catalog component and kit installed as `add` and `kits add` do. Harness parts (`harness`, `.claude`, `scripts`, `.githooks`) come from the install. Tests about this repo itself (catalog.source true, single brand, its own docs) run only where `catalog.source` is true and skip elsewhere. S34 builds the reference with no team files present; S35 runs the affected tests after `init --start blank` and `library`.
|
|
416
|
+
**Why:** Harness tests prove the harness, not the team's current content; a team that starts blank or edits its tokens must still have a green CI.
|
|
417
|
+
**Watch out:** The skeleton is pinned: a catalog contract that cites a new decision needs it added to the pinned `DECISIONS.md` (X1 fails in the baseline until then), and a change to the shared src/playwright files reaches the tests only when copied there.
|
|
418
|
+
|
|
419
|
+
### SB-0067 · 2026-11-08 · Incident: motion specs assumed the default motion preset
|
|
420
|
+
**Status:** incident
|
|
421
|
+
**Context:** The proof matrix applied the Material-like motion preset; Accordion and Collapsible failed "height animates with the motion token" because the specs expected `0.2s`. Spinner and Skeleton also hard-coded `1s`/`2s` and passed only because the loop duration happened to match. SB-0054 moved lengths to tokens but not times.
|
|
422
|
+
**Decision:** A `tokenSeconds(el, token, factor)` helper resolves time tokens; the four motion specs compare against the component's own duration token. Verified on the default brand and under the Material-like preset (49 of 49 each).
|
|
423
|
+
**Why:** A spec that only passes for one brand is not white-label (SB-0019).
|
|
424
|
+
**Watch out:** No check flags a new hard-coded `'NNpx'` or `'N.Ns'` expectation yet; the proof matrix (several presets) is what catches it. Logged in docs/simplicity-debt.md.
|
|
425
|
+
|
|
426
|
+
### SB-0066 · 2026-11-08 · Token renames are logged in spec/tokens/renames.json
|
|
427
|
+
**Status:** accepted
|
|
428
|
+
**Context:** Review round: `sketchbook tokens rename` rewrote the project, but nothing remembered the rename, so a component or kit installed later from the catalog (still naming the old token) would break T7 with no way to translate it.
|
|
429
|
+
**Decision:** Every rename appends `{ "from", "to", "date" }` to `spec/tokens/renames.json` (created with `{ "$description", "renames": [] }`), oldest first. The file is a team-owned source like the other `spec/tokens` files (staged and copied back by token commands); T7 only checks its shape (a `renames` array of entries with two token paths and a `YYYY-MM-DD` date). Catalog installs read it to translate incoming components and kits (SB-0059..62, `harness/lib/renames.mjs`).
|
|
430
|
+
**Why:** A rename is a migration the rest of the system must be able to replay, and the log is the only place that knows the order.
|
|
431
|
+
**Watch out:** Editing or reordering the log changes how future installs are translated; only `sketchbook tokens rename` should append to it. A rename back (`b -> a` after `a -> b`) is two entries, replayed in order.
|
|
432
|
+
|
|
433
|
+
### SB-0065 · 2026-11-08 · Token commands stage, check, then apply; names the generator owns are reserved
|
|
434
|
+
**Status:** accepted
|
|
435
|
+
**Context:** Review round on `sketchbook tokens`: a dry run returned before the token checks, so it approved changes the real run then rejected; a real run wrote in place and left the tree modified (plus a proposed decision) when the checks or the build failed; an unrelated token command silently reverted a hand edit to a brand-linked token; a no-op re-run still proposed a record and listed unchanged files; `add`/`rename` could take a name whose CSS variable another token builds, or a path the generator makes under another brand (`rename color.primary color.brand` while primary is neutral); and `set` walked `__proto__`/`constructor` segments.
|
|
436
|
+
**Decision:** (1) `runPlan` applies every plan on a temporary stage (token sources and outputs plus the stories, specs, patterns, docs, brands, kits and catalog the checks read), regenerates, rebuilds tokens, brands, interface and catalog, and runs T1–T7, G1, F1 there. A dry run reports the result (`ok: false` with the errors when they fail); a real run copies back only files whose content changed, and only when the checks pass; a build error is reported with the underlying T1–T3 errors. (2) The decision record is proposed only after the checks pass and only when a file changed; `changed` lists exact files. (3) Before staging, a linked token whose value differs from its link refuses the command unless `--yes`; every command reports `links.changed` and `overrides` (kept, added, dropped). (4) `add` and `rename` refuse a path whose CSS variable another token builds, a path or group any implemented preset of any family generates, and the color ramps the generator owns (`brand`, `neutral`, `white`, `black`, every role ramp and accent); `add` validates `--type`, literal values and aliases first. (5) `__proto__`, `prototype` and `constructor` are refused as key or path segments.
|
|
437
|
+
**Why:** A dry run that predicts a different result than the real run, or a refused run that leaves half a change behind, teaches people to skip the dry run and to distrust the checks.
|
|
438
|
+
**Watch out:** Every token command now copies the project's token, source and catalog folders to a temp directory (seconds on a large repo; K18 takes about twice as long). The `--yes` flag now has two meanings (confirm `overrides reset --all`; let links overwrite hand edits). Reserved names are computed from the presets catalog, so a new preset can reserve a semantic name that exists today (T1 reports the clash).
|
|
439
|
+
|
|
440
|
+
### SB-0064 · 2026-11-08 · Contrast links never fall back silently; T6 holds links to their surfaces; one CSS variable per token
|
|
441
|
+
**Status:** accepted
|
|
442
|
+
**Context:** Review round on the token CLI: a color link whose ramp had no step meeting the contrast target fell back to the preferred step without a word (`nearest(...) ?? pref` in `links.mjs`), so a stricter target could ship unreadable text with every check green; T6 only checked `contrast.json` and contract pairs, so a link's `alsoOn` surfaces and the declared pairs could drift apart; and two paths that differ only in dots and dashes (`size.control.sm`, `size.control-sm`) built the same CSS variable, the later one silently winning.
|
|
443
|
+
**Decision:** (1) A color link (solid, foreground or text) with no passing step keeps the preferred step and reports a missing entry naming the ramp, target and surfaces, so T7 fails and G1 warns, and `validateBrand` refuses a brand change that causes it. (2) T6 adds a text pair for every color link (not `foreground`) on each `alsoOn` surface, sourced from `spec/tokens/brand-links.json`, unless already declared. (3) T1 rejects two token paths, in any layers, that build the same `--<prefix>-…` variable.
|
|
444
|
+
**Why:** A promise the generator cannot keep must be visible where the checks look, and every promise a link makes about contrast is a pair T6 can prove.
|
|
445
|
+
**Watch out:** Under the default AA brand nothing moves (golden byte-identical). A brand with stricter fine targets now fails T7 until it picks a ramp with more range, changes the `alsoOn` backgrounds, or deletes the link to own the token.
|
|
446
|
+
|
|
447
|
+
### SB-0063 · 2026-11-08 · G1 proves every generated output and the foundation snapshot; hand reverts and deletions settle overrides
|
|
448
|
+
**Status:** accepted
|
|
449
|
+
**Context:** Review round: G1 compared only outputs that existed (a deleted `src/index.ts`, `docs/cli.md`, `known-commands.json` or `*.styles.ts` passed, as did an orphan `*.styles.ts`, a foundation file the generator does not make, and `tokens.<x>.css` or `brands.css` with no brand). Without `generated/foundation.snapshot.json` the generator could not tell hand edits from its output and silently dropped them; a hand revert to the generated value kept the old override (regenerate put the edit back), and a hand-deleted hand-added token came back.
|
|
450
|
+
**Decision:** (1) G1 fails on a missing output whose source is in the project (`src/index.ts` when `src/components` exists; `docs/cli.md` and `known-commands.json` when `harness/cli` exists; each `.scss`'s `.styles.ts`), on a `*.styles.ts` without its `.scss`, on a `spec/tokens/foundation/*.tokens.json` the generator does not make, on `generated/css/tokens.<x>.css` without `brands/<x>.brand.json`, on `brands.css` with no brands, and on a snapshot that is missing or differs from `generate(brand.config)`. (2) Without a snapshot, the generator records every value that differs from its output as an override and every unknown token as hand-added. (3) A file value equal to the generated value drops the token's override; a recorded token missing from its (existing) file drops its override. Both are reported as dropped.
|
|
451
|
+
**Why:** A rebuild check that skips missing outputs, or a generator that loses edits it cannot place, fails silently, which is the one failure mode the harness exists to prevent.
|
|
452
|
+
**Watch out:** Regenerating without a snapshot after changing brand.config records the old values as overrides; review `sketchbook tokens overrides list` and reset the ones you did not mean. Deleting a whole foundation file does not drop its overrides (the generator writes it back with them).
|
|
453
|
+
|
|
454
|
+
### SB-0062 · 2026-11-08 · Upgrades need both manifests; brand use validates first and clears overrides
|
|
455
|
+
**Status:** accepted
|
|
456
|
+
**Context:** `upgrade` classified files with the upstream manifest only, so an upstream could call `brand.config.json`, `package.json` or `.claude/**` harness-owned and overwrite them, and the CLI then ran the checks from the code it had just written; a git URL was cloned and applied without a look. `brand use` wrote brand.config.json before validating it, overwrote edits saved in no brand file, and carried foundation overrides into a brand whose `brand build` ignores them.
|
|
457
|
+
**Decision:** (1) A file is harness-owned only when both the project's and the upstream `harness/manifest.json` say so; one-sided claims are listed as "ownership differs — merge by hand" and not written. `.claude/settings*.json` is never written. A git URL needs `--yes` (a dry run is the report-only look and prints the resolved commit); `git clone -- <url>`, and `--from` may not start with `-`. Checks run after an upgrade only with `--yes`. (2) `brand use` validates the brand (schema, resolver, alias coverage: `validateBrand`) before writing, dry run included; without `--yes` it refuses when brand.config.json matches no `brands/*.brand.json` apart from name, or when overrides exist. Overrides belong to the active brand.config only, so `--yes` clears them (listed in the output); it refuses while a semantic token aliases a hand-added foundation token.
|
|
458
|
+
**Why:** Ownership is a promise to the team; one side of the upgrade must not be able to rewrite it. Clearing keeps tokens.css equal to what `brand build` makes for that brand.
|
|
459
|
+
**Watch out:** A legitimate widening of harness globs upstream takes two upgrades (the new manifest is written first, then both agree). Overrides a team wants on several brands must be put in each brand's config.
|
|
460
|
+
|
|
461
|
+
### SB-0061 · 2026-11-08 · The catalog source repo stays the source: init, prefix and catalog:build respect catalog.source
|
|
462
|
+
**Status:** accepted
|
|
463
|
+
**Context:** Any `init --start` set `catalog.source` to false, which silently switched off catalog freshness (G1) in Sketchbook itself; `prefix <new>` left the catalog on the old prefix and G1 only noted it; `catalog:build` (part of `npm run generate` and `check --fix`) crashed in a team repo after `--start blank` and would otherwise rebuild the shipped catalog from the team's remaining components, dropping what `add` restores.
|
|
464
|
+
**Decision:** `init --start` keeps `catalog.source: true` unless `--detach-catalog`, or `--yes` with a warning that says what was turned off. `prefix` rebuilds the catalog when source is true, and G1 treats a catalog prefix that differs from harness.config.json as an error there. `buildCatalog` (and so `catalog:build`) is a no-op unless `catalog.source` is true. `prefix` refuses a reserved word (aria, data, x, on, xml, xlink) or a word already used as `<word>-`, `--<word>-` or `<Word>Name` in its scope, since renaming back would rewrite those (docs/cli.md is generated and skipped).
|
|
465
|
+
**Why:** The catalog is either followed (source repo) or frozen (team repo); nothing should flip one into the other by side effect.
|
|
466
|
+
**Watch out:** A team repo created by copying Sketchbook must detach once (`--detach-catalog` or `--yes`); until then G1 asks for `catalog:build` after component edits.
|
|
467
|
+
|
|
468
|
+
### SB-0060 · 2026-11-08 · Catalog installs are verified, all or nothing, and carry token renames; removals that lose work need --yes
|
|
469
|
+
**Status:** accepted
|
|
470
|
+
**Context:** Install wrote each manifest path and blob as given (a `../` path or a kit path of `.` would write or delete outside the unit), wrote unit by unit (a failure left half an install), and copied units that still named semantic tokens renamed since (`tokens rename`), so `add button` broke after a rename. `remove` and `kits remove` deleted team-made and customized units without asking.
|
|
471
|
+
**Decision:** Every manifest path must stay under the project and inside its unit's folders, every hash must be 20 hex characters and match its blob, kit ids and paths must match `^[a-z0-9-]+$` and `^src/patterns/[a-z0-9-]+$`. Units are staged in memory (prefix rewrite, then the renames recorded in `spec/tokens/renames.json`, applied in order by `harness/lib/renames.mjs` with the `tokens rename` text rules), written together with the registry, then rebuilt; any failure restores every touched file and the generated outputs. `remove` refuses without `--yes` a component not in the catalog or customized (compared with what an install would write now) and only promises `sketchbook add` brings it back when true; `kits remove` does the same for an edited kit, then rebuilds and runs the component checks plus K1 and G1. In the source repo G1 also re-hashes every blob, compares index.json with a fresh build and flags units with no eligible component.
|
|
472
|
+
**Why:** The catalog is data that travels between repos (upgrades); it is checked like input, and a command that can only restore the catalog's version must not delete anything else silently.
|
|
473
|
+
**Watch out:** The rollback covers one `add` or `kits add`; `init --start` still removes and installs in steps (its removals are confirmed with `--yes`). Renames are re-applied to every install: a new token that reuses a renamed-away name is renamed too.
|
|
474
|
+
|
|
475
|
+
### SB-0059 · 2026-11-08 · Incident: catalog and brand commands could delete or overwrite the team's work
|
|
476
|
+
**Status:** incident
|
|
477
|
+
**Context:** The review round found data-loss paths: `sketchbook remove` deleted team-made and customized components with no confirmation and claimed `sketchbook add` would restore them; `kits remove` deleted edited kits; after `tokens rename`, installing from the catalog failed halfway; `brand use` overwrote unsaved brand.config.json edits; `upgrade` let an upstream reclassify team files and overwrite them; `catalog:build` in a team repo would rewrite the shipped catalog.
|
|
478
|
+
**Decision:** Fixed by SB-0060 (verified, atomic installs with renames; `--yes` for removals the catalog cannot undo), SB-0061 (catalog source handling) and SB-0062 (upgrade ownership, brand use). Each path has a harness test that fails on the old code (S22–S33).
|
|
479
|
+
**Why:** Commands that write files are the harness's hands; they must refuse rather than guess when work could be lost.
|
|
480
|
+
**Watch out:** New mutating commands follow the same rule: list what is at risk in `--dry-run`, refuse without `--yes`, and say honestly how to get it back.
|
|
481
|
+
|
|
482
|
+
### SB-0058 · 2026-11-08 · Every catalog preset applies: validation follows the brand links, text colors follow the contrast target
|
|
483
|
+
**Status:** accepted
|
|
484
|
+
**Context:** The harness promises that every foundation preset in the catalog can be applied from the CLI, but `tokens preset motion <id>` was refused for every motion preset except `tailwind-like` (its own help example `material-like` included), `tokens preset z-index named-layers` was refused, and `contrast wcag-aaa` applied with 42 T6 errors. The motion and z presets already declare roles (`duration.fast/normal/slow/loop`, `easing.standard/enter/exit/linear`; `base`, `dropdown`, `sticky`, `overlay`, `modal`, `toast`) and `brand-links.json` already re-points `motion.*` and `layer.*` to them on every generate; the refusal came from `validateBrand`, which looked for the semantic layer's current aliases (`{duration.200}`, `{easing.in}`, `{z.10}`) in the new foundation before the links moved them. Every other family keeps one shape across its presets (same type steps, space keys, weights, shadows), so it was never refused.
|
|
485
|
+
**Decision:** (1) `validateBrand` (used by `tokens set`, `preset`, `scratch`) applies the brand links to a copy of the semantic files with the new brand, then refuses only an alias still missing after that, or a link the new brand breaks (a preset lacking a role a link uses; a link that already failed before is not blamed on the change). A partial custom scale is still refused. (2) A new link kind `{ "from": "color", "ramp": "neutral", "part": "text", "step": { "light": 500, "dark": 400 }, "alsoOn": [...] }` picks, per mode, the ramp step nearest the preferred one whose contrast on every `alsoOn` background (alias or literal) meets the brand's text target. `color.muted-foreground` uses it on background, card, popover and muted; `color.destructive` and its foreground add `color.card` to `alsoOn`. Under AA nothing moves (default output byte-identical, golden test); under AAA they darken or lighten. (3) Test K18 applies every implemented preset of every family through `planPreset` + `runPlan` and requires T1–T7, G1 and F1 without errors; `semanticRoles` is the only family without a brand.config key (roles are chosen with `color.roles`).
|
|
486
|
+
**Why:** Roles in the catalog plus links are the existing contract between presets of different shapes and the semantic layer; validation now judges the outcome the generator will actually produce, instead of a stale snapshot, and contrast becomes a role the link enforces instead of a hand fix after every AAA switch.
|
|
487
|
+
**Watch out:** `color.muted-foreground` now follows brand.config: a value imported or edited by hand is re-pointed on generate (delete its link to own it). A new motion or z preset must define every role in `brand-links.json` or it is refused with the missing role. A brand that sets stricter fine targets than its preset (e.g. `targets.ui: 4.5`) can still fail T6, since borders are not linked.
|
|
488
|
+
|
|
489
|
+
### SB-0057 · 2026-11-08 · What the Sketchbook round leaves for later
|
|
490
|
+
**Status:** accepted
|
|
491
|
+
**Context:** The foundations studio, starters, catalog, kits, brands and the agent-friendly CLI landed. Some planned or researched options were not built, and saying so beats docs that imply they exist.
|
|
492
|
+
**Decision:** Not built this round, kept as described options: alternative component adapters (vanilla custom elements, Stencil) and test adapters (Web Test Runner) — `swap` covers tokens and design only; the Figma design adapter (SB-0008 stands); colour ramp methods other than OKLCH (`tailwind-11`, `radix-12`, `m3-tonal`, `contrast-targeted` are catalogued, not generated); Penpot themes per brand; copying local font files into the package; APCA as a gate (information only). The split of the reference's Tier 2 and Tier 3 components stays an owner decision.
|
|
493
|
+
**Why:** Each is useful but none blocks a team starting or editing its system; building them now would widen the surface faster than the checks and tests can cover it.
|
|
494
|
+
**Watch out:** Skills and docs must call these "not available yet"; the preset-docs guard and the CLI allowlist keep them from being presented as working commands or presets.
|
|
495
|
+
|
|
496
|
+
### SB-0055 · 2026-11-08 · Brand-sensitive layout found by the non-default proof
|
|
497
|
+
**Status:** accepted
|
|
498
|
+
**Context:** Running the specs under compact density, the 8px grid, sharp radius and the major-third scale (SB-0054) passed after the assertions followed tokens, but it showed three places where the layout itself, not a spec, depends on the brand.
|
|
499
|
+
**Decision:** (1) `sb-input-group` is a `min-height` shell and its addons pad with `space.stack.xs`, a spacing step: under `grid-8` the shell grows past `size.control.default` (42px against 32px), so its specs assert "at least the control height". (2) Under `radius.sharp` every "only the outer corners are rounded" assertion compares to the radius token and so holds trivially; the corner pattern is proven only by the default brand. (3) Breakpoint-driven specs (Empty padding at 768px, Breadcrumb gap at 640px) keep viewports far from both breakpoints presets. Author-set sizes (a story's 20px flex row, rem-sized skeletons, scroll-area heights) stay literal.
|
|
500
|
+
**Why:** The specs state what the CSS promises; where the CSS promises less under a brand, the spec says so instead of pinning a number, and the gap is written down.
|
|
501
|
+
**Watch out:** A team on `grid-8` or `grid-10` sees taller input groups than its control height; fixing it means giving the addon its own `space.control.padding-y.*` token (a contract change, not done here). A breakpoints preset with a breakpoint between 600 and 1024px would move the Empty and Breadcrumb viewports into the wrong side.
|
|
502
|
+
|
|
503
|
+
### SB-0054 · 2026-11-08 · Behavior specs read brand-dependent sizes from the tokens, proven under a non-default brand
|
|
504
|
+
**Status:** accepted
|
|
505
|
+
**Context:** SB-0019 and SB-0021 left the specs asserting the default brand's numbers (36px controls, 16px padding, 12px gaps), so a compact, 8px-grid or sharp install failed 56 of 701 specs on its own components.
|
|
506
|
+
**Decision:** `playwright/helpers/tokens.ts` gains `tokenPx` (a length token as a number, for boundingBox comparisons), `tokenNumber` (unitless tokens such as weights) and `tokenLineHeight` (a line-height token as laid out, given its font-size token). Every expectation that depends on density, the spacing grid, the type scale, radius or border width now names the component token the SCSS uses (`--sb-<component>-*`); literals stay for 0px, ARIA counts, story-authored sizes and viewport sizes. The proof is a scratch install with `sketchbook tokens preset density compact`, `spacing grid-8`, `radius sharp`, `typeScale major-third`, then `npm run check`, `build-storybook` and the full Playwright run, which passes 701 of 701 next to the default brand's 701.
|
|
507
|
+
**Why:** White-label means behavior specs must hold for any brand; the token is the one number the component and the spec share.
|
|
508
|
+
**Watch out:** The proof is run by hand (SB-0055 lists what it cannot cover); a new spec with a `'NNpx'` expectation silently re-couples the suite to the default brand, and no check catches it yet.
|
|
509
|
+
|
|
510
|
+
### SB-0053 · 2026-11-08 · The command allowlist is generated from the registry plus planned entries
|
|
511
|
+
**Status:** accepted
|
|
512
|
+
**Context:** SB-0038 kept `harness/cli/known-commands.json` by hand until the CLI registry existed; it now exists, while other builders still ship commands (tokens, brand, kits, upgrade, doctor, remove, list, audit-css, `init --start`) in parallel.
|
|
513
|
+
**Decision:** `harness/cli/known.mjs` generates `known-commands.json` from the registry (`name`, `summary`, optional `subcommands` and `starters` on a command module) merged with `harness/cli/planned-commands.json` (commands and starters the plan names but the registry lacks, marked `planned: true`). A registry command wins over its planned entry; subcommands are the union. `npm run build:cli-docs` (part of `npm run generate`) writes it and G1 rejects a stale copy.
|
|
514
|
+
**Why:** The guard then proves "built" for everything in the registry, and "planned" only for what is explicitly listed as such.
|
|
515
|
+
**Watch out:** Delete a planned entry when its command lands (the union keeps it harmless if forgotten, but `planned` then hides nothing). A command module without `subcommands` accepts any second word in docs.
|
|
516
|
+
|
|
517
|
+
### SB-0052 · 2026-11-08 · Bare sketchbook opens a menu over the same registry
|
|
518
|
+
**Status:** accepted
|
|
519
|
+
**Context:** Newcomers should not need to memorize commands (plan 2.6), and the menu must not become a second CLI that drifts.
|
|
520
|
+
**Decision:** `sketchbook` with no arguments, when stdin and stdout are terminals, opens a `node:readline` menu built from the registry: groups, then commands, then a prompt per argument and option (current values from `status` as hints; Enter keeps them). Read-only commands run at once; mutating commands with `--dry-run` show the dry run first and apply only on `y`; other mutating commands ask before running. Every run goes through `dispatch`, so the menu can do nothing the CLI can't. Without a TTY, or with `--json`, bare `sketchbook` prints help.
|
|
521
|
+
**Why:** One registry feeds help, docs, the allowlist and the menu; agents and CI never hit a prompt.
|
|
522
|
+
**Watch out:** Free-text answers are split on spaces for variadic arguments; quoting is not parsed. The menu has no command-specific pickers (presets, starters) beyond each argument's description.
|
|
523
|
+
|
|
524
|
+
### SB-0051 · 2026-11-08 · Penpot gets typography composites, foundations boards and a scripted read-back
|
|
525
|
+
**Status:** accepted
|
|
526
|
+
**Context:** The token push skipped nothing composite except letter spacing, but the spec has no typography composites, Penpot had no foundations boards, and `sync --verify` was a manual procedure with a hand-written `penpot.verify.json`.
|
|
527
|
+
**Decision:** (1) The push adds a `semantic/typography` set: one Penpot `typography` token `text-style.<role>` per semantic `font.size.<role>`, referencing the role's family, size, weight and (number) line-height tokens; an absolute line height becomes a ratio and em letter spacing becomes px for that size. DTCG `typography` tokens, if a team adds them, map too. Shadows stay as before (spread clamped, SB-0010). (2) `sketchbook sync foundations [pages]` writes `foundations.js`, building `[sb] Foundations · Color | Typography | Spacing | Radius | Elevation` from the same payload, every sample bound to its token, replacing earlier `[sb] Foundations*` boards; plus `cleanup-legacy.js` (delete `[ds] ` shapes on every page). (3) `sketchbook sync verify` (or `sync --verify`) writes the read-only `verify.js`; `sync verify --ingest <file>` compares its JSON per mode with the spec and writes `penpot.verify.json` (`{mismatches:[{token, mode, penpot, spec}]}`), which D1 already fails on.
|
|
528
|
+
**Why:** One payload feeds tokens, boards and the comparison, so the design file cannot drift unnoticed; a scripted read-back replaces a hand-written verdict.
|
|
529
|
+
**Watch out:** Penpot themes apply to the whole file, so bound swatches show the active Mode only; each semantic swatch also carries static spec chips per mode for comparison. Composites (shadow, typography) are not compared on ingest. Letter-spacing primitives stay in the repo (em). None of the scripts has run against a live file yet: the first run may need API fixes.
|
|
530
|
+
|
|
531
|
+
### SB-0050 · 2026-11-08 · The font source generates fonts.css, separate from tokens.css
|
|
532
|
+
**Status:** accepted
|
|
533
|
+
**Context:** `typography.family` names a font but nothing loaded it; teams bring Google Fonts, a hosted stylesheet or self-hosted files.
|
|
534
|
+
**Decision:** `typography.source` (`kind: google | url | local | none`, plus `family`, `weights`, `display`, `url`, `path` or `files[]`, and `mono`) generates `generated/css/fonts.css` in the token build for any token adapter: google is one `@import` of the css2 URL with the weights in use (`source.weights`, else the generated `font.weight` scale) and `display=swap`; url is `@import url(...)`; local is one `@font-face` per listed file (paths used as given, not copied; one `path` is treated as a variable font over the weight range); none (the default) is a comment-only file. Storybook imports it before `tokens.css`; the package exports `./fonts.css`. G1 keeps it fresh.
|
|
535
|
+
**Why:** Loading belongs in its own file so `tokens.css` stays byte-identical for the default config and a consumer can self-host instead of importing ours.
|
|
536
|
+
**Watch out:** Google returns an error for weights a family lacks: set `source.weights` then. Copying local files into `generated/fonts/` is not done; the paths must resolve where the CSS is served.
|
|
537
|
+
|
|
538
|
+
### SB-0049 · 2026-11-08 · Incident: check --json output was cut at 64 KB on a pipe
|
|
539
|
+
**Status:** incident
|
|
540
|
+
**Context:** With two brands, `sketchbook check --json` printed invalid JSON: the report grew past 64 KB and both `harness/checks/run.mjs` and `harness/cli.mjs` called `process.exit()` right after writing it, which drops what is still buffered for a pipe.
|
|
541
|
+
**Decision:** Both set `process.exitCode` and let Node exit on its own, so stdout flushes. Tests that read CLI output spawn with a large `maxBuffer`.
|
|
542
|
+
**Why:** Agents and CI read the envelope; a truncated envelope looks like a crash of the command, not of its output.
|
|
543
|
+
**Watch out:** Never `process.exit()` after a large write; anything that keeps the event loop alive (a timer, an open server) now delays the exit instead of being cut.
|
|
544
|
+
|
|
545
|
+
### SB-0048 · 2026-11-08 · Upgrades replace harness-owned files only
|
|
546
|
+
**Status:** accepted
|
|
547
|
+
**Context:** Teams edit their copy (spec, components, docs) and still want newer checks, skills and catalog from upstream; copying a whole newer checkout over theirs would erase their work.
|
|
548
|
+
**Decision:** `harness/manifest.json` lists harness-owned globs (`harness/**`, `.claude/{skills,agents,commands,rules,hooks}/**`, `.githooks/**`, `scripts/**`, `docs/cli.md`), team-owned ones (`spec/**`, `src/**`, `brands/**`, `brand.config.json`, `harness.config.json`, `playwright/tests/**`, `docs/**`) and shared ones (`package.json`, configs, `.storybook/**`, playwright helpers, README, CLAUDE.md). An exact harness path beats a team glob, a team glob beats a harness glob. `sketchbook upgrade --from <folder|git-url> [--dry-run]` (a URL is cloned with depth 1 into a temp folder) writes added and changed harness-owned files, lists team-owned and shared files that differ (never writes them), lists harness files gone upstream (kept, not deleted), records `harnessVersion` from the source manifest in harness.config.json and runs the checks. `sketchbook doctor` reports the starter, versions, installed vs catalog vs customized components, kits, brands, overrides, design sync and failing checks, read-only.
|
|
549
|
+
**Why:** The research rule (dry run first, keep user edits apart from what upstream owns, a doctor pass after every change) with git as the undo; deleting files we no longer ship could take a team's own skill with them.
|
|
550
|
+
**Watch out:** Shared files (package.json, lockfile) need a hand merge and `npm install`; upgrade says so. A team edit inside a harness-owned file (a check, a skill) is overwritten: such changes belong in team-owned files or upstream.
|
|
551
|
+
|
|
552
|
+
### SB-0047 · 2026-11-08 · Several brands share one semantic interface; one brand stays the default
|
|
553
|
+
**Status:** accepted
|
|
554
|
+
**Context:** Some teams theme several products from one system; most have one brand, and their tokens.css must not change because brands exist as a feature.
|
|
555
|
+
**Decision:** A brand is `brands/<name>.brand.json` with the brand.config.json schema. `sketchbook brand add <name> [--from current|<brand>]`, `brand list`, `brand use <name>` (copies it into brand.config.json, regenerates and checks) and `brand build`, which writes `generated/css/tokens.<name>.css` (standalone, same variables and semantic links as tokens.css) and `generated/css/brands.css` (every brand under `[data-brand="<name>"]`, specificity above the default `:root`). Each brand's foundation comes from the generator without the repo's foundation overrides (overrides belong to the active brand.config.json); the team's semantic files and links are shared. T6 checks every declared pair for every brand with that brand's contrast standard; G1 keeps the brand files fresh; `npm run generate` and component installs rebuild them. Storybook shows a Brand toolbar only when brands exist. Without `brands/`, nothing is written (tokens.css byte-identical, test S14).
|
|
556
|
+
**Why:** One interface means components never know which brand they are in; scoped and standalone files cover both one-page multi-brand demos and per-product builds.
|
|
557
|
+
**Watch out:** A brand with different modes than the semantic files falls back to the role's template for the missing mode. Penpot themes per brand are not built yet (deferred).
|
|
558
|
+
|
|
559
|
+
### SB-0046 · 2026-11-08 · Starters are data; init --start makes the project match one
|
|
560
|
+
**Status:** accepted
|
|
561
|
+
**Context:** Eight ways to start (SB-0039) need one deterministic command, re-runnable, that never destroys a team's work silently.
|
|
562
|
+
**Decision:** `harness/starters/<id>.json` = `{ id, title, for, foundations (brand.config patch or null), components ('all' | 'none' | [names]), kits ('all' | 'none' | [ids]), next[] }`. `sketchbook init --start <id> [--components a,b] [--from <file>] [--yes]` removes kits and catalog components the starter does not include, installs the rest from the catalog (dependencies and a kit's components first), merges the foundations patch, records `starter` and sets `catalog.source: false` in harness.config.json, rebuilds and checks. Removing anything needs `--yes` (dry run shows the plan); components the team made (not in the catalog) are never removed. `import`, `from-design-file` and `from-codebase` keep the library and kits and add their step: `tokens import` when that command exists (else its next command), the read-only Penpot extract steps (design-penpot skill), and `sketchbook audit-css <path|glob>`, which clusters a product's colors by OKLab distance (< 0.03 joins, most used first), font sizes, spacing (base grid 8/4/2 fitting 80% of values), radii and shadows into `generated/import/codebase.proposal.json` (same input, same bytes). The brand flags of `init` work as before and with `--start`.
|
|
563
|
+
**Why:** Data starters are easy to add and test; refusing to delete without `--yes` keeps the command safe to run twice; proposals keep import starters from overwriting a team's decisions.
|
|
564
|
+
**Watch out:** `blank` leaves Storybook with Foundations pages only; behavior specs of removed components go with them. The audit reads literal values only (no computed styles, no CSS-in-JS).
|
|
565
|
+
|
|
566
|
+
### SB-0045 · 2026-11-08 · The reference components are a content-addressed catalog
|
|
567
|
+
**Status:** accepted
|
|
568
|
+
**Context:** `add` only scaffolded empty contracts, so a team that started small could not get a reference component back, and nothing could take one out cleanly.
|
|
569
|
+
**Decision:** `npm run catalog:build` writes `harness/catalog/<name>/manifest.json` for every beta or stable component (contract files, code without generated `.styles.ts`, behavior specs, parity and a11y audits named `<name>-YYYY-MM-DD`) with `dependsOn` from the contract plus `uses` (other components its stories and specs render, e.g. card uses button), and each file's bytes under `files/<sha256 prefix>`; kits in `harness/kits/index.json` get the same under `harness/catalog/kits/<id>/`. Blobs have no extension, so lint, typecheck, Storybook and the prefix codemod never see them. `sketchbook add <name>` installs a missing component and what it needs (rewriting the prefix when the project's differs), sets the registry from the manifest, rebuilds and runs C1–C3, P1, R1, T2, T4; `--blank` keeps the scaffold. `sketchbook remove <name>` refuses while an installed component or kit needs it, naming them; otherwise deletes the files, sets the registry to planned and rebuilds. `sketchbook list [--installed|--available]` and `kits list|add|remove` read the same data. G1 compares the catalog with the repo only where `harness.config.json` has `catalog.source: true` (the repo it is built from); after `init --start` components are the team's, and doctor reports which ones they customized. K1 accepts an index entry that is not installed while the catalog holds it.
|
|
570
|
+
**Why:** Content-addressed blobs make freshness a hash comparison and keep shipped copies out of every tool's way; `uses` matters because contracts declare only code dependencies, while stories and specs fail without the components they render.
|
|
571
|
+
**Watch out:** Rebuild the catalog after changing a component in the source repo (G1 says so). A component's decision records stay in this log after removal (history, not files of the unit).
|
|
572
|
+
|
|
573
|
+
### SB-0044 · 2026-11-08 · Renames rewrite every named use; removals and imports never break the interface
|
|
574
|
+
**Status:** accepted
|
|
575
|
+
**Context:** Renaming a semantic token by hand broke stories, specs and `.storybook` silently, and nothing stopped a removal of a token components still used.
|
|
576
|
+
**Decision:** `sketchbook tokens rename <old> <new>` rewrites the semantic files (node and every alias), `brand-links.json` (keys and `alsoOn`), contracts (component token values and contrast pairs), `spec/tokens/contrast.json`, and CSS variables plus exact quoted token paths in stories, specs, patterns (`src/patterns/**`, CSS included) and `.storybook`; then rebuilds and runs the token checks. It does not touch `harness/templates/semantic/*` or prose in docs. `tokens remove` refuses while anything depends on the token (aliases, links, contracts, contrast pairs, files) and prints that impact. `tokens scratch` rewrites only `brand.config.json` (answered foundations only) and keeps every semantic file, so the interface survives.
|
|
577
|
+
**Why:** A rename is an interface change; doing it in one deterministic step, verified by T7, is the only way it stays safe.
|
|
578
|
+
**Watch out:** Templates keep the shipped names, so a fresh install from templates uses the old name until the team syncs templates. Variable names built at runtime (template strings) cannot be rewritten or checked.
|
|
579
|
+
|
|
580
|
+
### SB-0043 · 2026-11-08 · Token imports are deterministic proposals mapped by name, color distance and size clustering
|
|
581
|
+
**Status:** accepted
|
|
582
|
+
**Context:** Teams bring tokens as DTCG / Tokens Studio files, Penpot exports or CSS custom properties, named in their own words.
|
|
583
|
+
**Decision:** `sketchbook tokens import <file> --from dtcg|penpot|css` normalizes tokens to `{path, type, value, mode?}` (Tokens Studio legacy `value`/`type`, `$themes` decide modes; Penpot import folders or files; CSS `:root` vs `.dark` / `[data-theme=dark]`) and writes `generated/import/<name>.proposal.json` with `mapping[{from, to, confidence, reason, apply}]` and `unmapped[]`. Heuristics: exact path first; color ramps (`name.<step>`) become the brand (by name, or because the imported primary is one of its steps within OKLab distance 0.02), the neutral (by name or chroma < 0.03), the danger accent or another accent; semantic colors match by role words folded through synonyms (bg/background, fg/text/on-x/foreground, brand/primary, danger/error/destructive, subtle/muted, focus/ring, surface/card…); radius base from lg/md/default or the median; spacing grid from the largest base dividing at least 80% of the values; a custom type scale only from 8+ sizes. Component token sets are skipped. `import apply` applies entries with `apply: true` and confidence >= 0.6, writes brand-linked tokens only through the foundation, never deletes a token, then rebuilds and checks.
|
|
584
|
+
**Why:** A proposal the person (or the token-mapper agent) reviews keeps every component working; deterministic heuristics make the proposal reproducible.
|
|
585
|
+
**Watch out:** Translucent imported colors are kept but skipped by T6; low-confidence entries (accents, neutral tint, type scale) need a human yes.
|
|
586
|
+
|
|
587
|
+
### SB-0042 · 2026-11-08 · sketchbook tokens is one registry command with subcommands and one mutation pipeline
|
|
588
|
+
**Status:** accepted
|
|
589
|
+
**Context:** Eleven token operations (set, preset, presets, diff, impact, add, remove, rename, import, scratch, overrides) needed the CLI registry conventions without eleven top-level commands.
|
|
590
|
+
**Decision:** One registry module (`harness/cli/commands/tokens.mjs`) declares `subcommands[]` (help and `docs/cli.md` list them) and `cssVarArgs` (an argument like `--sb-color-border` stays a positional). Each mutating subcommand is a plan run by one pipeline: `--dry-run` applies it to a temporary copy to show the real CSS diff; otherwise write, regenerate (foundation + links), build, write `spec/tokens/interface.json`, run T1–T7, G1 and F1, print the per-mode CSS diff and the components affected, and propose an SB record under Theme unless `--no-record`. `tokens set` validates against the schema, the catalog and the semantic aliases (a partial custom scale is refused); a `.preset` key replaces its sibling fine overrides. The shared `proposeDecision` moved to `harness/lib/decisions.mjs`.
|
|
591
|
+
**Why:** Introspect before mutate and verify outputs, the same way for every token change.
|
|
592
|
+
**Watch out:** Dry runs copy `spec/` and the generated token outputs, so they cost about a second.
|
|
593
|
+
|
|
594
|
+
### SB-0041 · 2026-11-08 · F1: foundations follow their declared standard, as warnings
|
|
595
|
+
**Status:** accepted
|
|
596
|
+
**Context:** Presets can produce values that break common practice (a perfect-fourth scale gives a 10px xs used by control text) without failing any check.
|
|
597
|
+
**Decision:** Check F1 warns (never fails) when a spacing value is off the declared grid (multiples of the base or its half step, which the presets declare), the type scale is not monotonic, a semantic `font.size.body|control|caption|label*` token resolves below 12px, `font.line-height.body` is below 1.5, a component's SCSS animates without reduced-motion handling (the media query or the `respect-reduced-motion` mixin), or contrast targets are weaker than WCAG AA. Each warning names the fix.
|
|
598
|
+
**Why:** Teams may step off a standard on purpose; the warning makes it a visible, recorded choice instead of an accident.
|
|
599
|
+
**Watch out:** The engine's golden test is also called F1 in harness/test; the check id lives in a separate namespace (harness/checks/run.mjs).
|
|
600
|
+
|
|
601
|
+
### SB-0040 · 2026-11-08 · The semantic interface is computed and guarded by T7
|
|
602
|
+
**Status:** accepted
|
|
603
|
+
**Context:** Contracts, brand links, contrast pairs, stories, specs, `.storybook` and patterns depend on semantic tokens; a rename or deletion broke them silently.
|
|
604
|
+
**Decision:** `npm run generate` writes `spec/tokens/interface.json`: every semantic token those users reference (directly, through CSS variables, or through semantic aliases), whether it lives in base or in every mode, and who uses it (by kind). G1 keeps it fresh. Check T7 fails when an interface token is missing where it was recorded, a used token exists nowhere, a brand link's source or target is missing (G1 only warns), or a `var(--<prefix>-…)` or quoted `'--<prefix>-…'` in stories, specs, `.storybook` or `src/patterns` names no token (variables the file declares itself are local).
|
|
605
|
+
**Why:** Closes the silent break on rename: every reference outside component CSS is now checked.
|
|
606
|
+
**Watch out:** Editing a story that starts using a new token needs `npm run generate` (G1 says so). Test fixtures copy `.storybook`.
|
|
607
|
+
|
|
608
|
+
### SB-0039 · 2026-11-08 · Onboarding recommends a starter from what the team already has
|
|
609
|
+
**Status:** accepted
|
|
610
|
+
**Context:** Onboarding assumed everyone starts from the default library and asked six brand questions. Teams arrive with nothing, with tokens, with a Penpot file or with a product, and want everything from a blank page to a full library with templates.
|
|
611
|
+
**Decision:** The `onboarding` skill (and `/start`) asks who the person is and where they start, recommends one of eight starters (`blank`, `foundations`, `library`, `library+kits`, `pick`, `import`, `from-design-file`, `from-codebase`) with the reason, runs `sketchbook init --start <starter>` after a dry run, and hands off to the `foundations` skill (guided) or `sketchbook add`. Existing assets win: a team with tokens, a design file or a product is recommended the matching import starter; someone new with nothing is recommended `library`. Template kits get their own `kits` skill and `/kits`.
|
|
612
|
+
**Why:** The harness is the first draft of a team's system, not ours; learning their existing decisions beats replacing them, and a newcomer learns fastest by changing foundations on real components.
|
|
613
|
+
**Watch out:** The starters and kits commands are built in parallel; the skill tells the agent to confirm options with `sketchbook help <cmd>` until they land.
|
|
614
|
+
|
|
615
|
+
### SB-0038 · 2026-11-08 · The Claude layer may only name known CLI commands
|
|
616
|
+
**Status:** accepted
|
|
617
|
+
**Context:** Skills and commands describe CLI commands that are being built in parallel; prose can drift from the CLI or invent commands that never existed, and a skill without valid frontmatter silently fails to load.
|
|
618
|
+
**Decision:** `harness/cli/known-commands.json` lists every `sketchbook` command and subcommand (and every `--start` starter) the plan names. A harness test fails when any file in `.claude/` names a `sketchbook …` or `node harness/cli.mjs …` command outside that list, or when a skill or agent lacks `name` (matching its folder or file) and `description`, or a command lacks `description`.
|
|
619
|
+
**Why:** Docs that can't invent commands keep agents from running commands that do not exist; the test proves it can reject an invented command.
|
|
620
|
+
**Watch out:** The list is hand-kept until the CLI registry (`harness/cli/commands/*.mjs`) exists; then generate it from the registry. Planned commands are marked `planned`, so the guard proves "planned", not "built".
|
|
621
|
+
|
|
622
|
+
### SB-0037 · 2026-11-08 · Roasts and imports are proposals made in a fresh context
|
|
623
|
+
**Status:** accepted
|
|
624
|
+
**Context:** A critique written by the same agent that just helped choose the foundations tends to confirm them, and an import mapping applied straight away can quietly drop interface tokens components rely on.
|
|
625
|
+
**Decision:** `roast` mode spawns the `foundations-critic` agent with no conversation history; it is read-only on tokens and config and writes ranked findings with evidence to `docs/foundations-reviews/<date>.md`. `import` mode runs `sketchbook tokens import` (a proposal under `generated/import/`) and the `token-mapper` agent, which writes only a mapping file there; nothing is applied until the person approves `sketchbook tokens import apply`.
|
|
626
|
+
**Why:** An unanchored read finds what the author can't see; a reviewed proposal keeps every component working through an import.
|
|
627
|
+
**Watch out:** The critic's findings are opinions with evidence, not check failures; a finding the team rejects is recorded with its reason in a decision record.
|
|
628
|
+
|
|
629
|
+
### SB-0036 · 2026-11-08 · One Foundations studio replaces token-ramps; overrides are kept, not lost
|
|
630
|
+
**Status:** accepted
|
|
631
|
+
**Context:** Only color had a skill (`token-ramps`), and it said a hand edit to a foundation file would be lost on the next brand change, while the generator actually keeps such edits as flagged overrides. Every other foundation could only be changed by hand.
|
|
632
|
+
**Decision:** The `foundations` skill covers every foundation (one reference each: color, typography, spacing and grid, radius, elevation, motion, density, layout grid, icons, z-index, contrast, semantic naming) in six modes (guided, preset, expert, import, scratch, roast). Changes go through `brand.config.json` or `sketchbook tokens` (rule `tokens-through-the-harness`); every session ends with `sketchbook tokens diff` and `impact`, the Storybook `Foundations/<Page>`, a proposed decision record and an offer to sync Penpot. The color method moved to `references/color.md` and says the truth: hand edits survive as overrides (check exits 2) until moved into brand.config or reset.
|
|
633
|
+
**Why:** Teams must be able to redo any foundation from the harness, with the standards and their trade-offs at hand; a skill that contradicts the code teaches the wrong fix.
|
|
634
|
+
**Watch out:** Preset ids in the references come from the research draft; the catalog (`sketchbook tokens presets`) is authoritative if ids are renamed.
|
|
635
|
+
|
|
636
|
+
### SB-0034 · 2026-11-08 · Foundations contrast is recomputed in the page and cross-checked in node
|
|
637
|
+
**Status:** accepted
|
|
638
|
+
**Context:** The Color page shows the ratio of every pair in `spec/tokens/contrast.json` per mode. The harness color math (`harness/lib/color.mjs`) is node ESM and not part of the browser bundle.
|
|
639
|
+
**Decision:** The page carries a small browser-safe port of the WCAG 2.x ratio (6-digit hex only) and shows ratio, minimum per kind (text 4.5:1, large text and UI 3:1) and a Pass/Fail word. A behavior spec recomputes every pair with the harness code and requires the page to match to six decimals and to agree on the verdict.
|
|
640
|
+
**Why:** The page must follow token edits live without a build step, and the spec keeps the two implementations from drifting. Check T6 stays the gate; the page only explains it.
|
|
641
|
+
**Watch out:** Colors with alpha (8-digit hex) show "n/a"; if semantic colors gain alpha, both the port and T6 need compositing.
|
|
642
|
+
|
|
643
|
+
### SB-0033 · 2026-11-08 · Storybook Foundations pages read the token files, not a list
|
|
644
|
+
**Status:** accepted
|
|
645
|
+
**Context:** Foundations docs written by hand go stale as soon as a preset or a `tokens set` changes a value, and other builders are adding tokens (success, warning, info) in parallel.
|
|
646
|
+
**Decision:** `src/stories/foundations/` renders twelve pages (`Foundations/<Page>`) from the DTCG files through Vite `import.meta.glob` (foundation, semantic per mode, generated component tokens, contrast pairs, prefix). A token belongs to the page whose prefix in `families.ts` matches the longest leading part of its path; tables list every token with its CSS variable, alias, resolved value and one-step users. Samples use the values from the JSON, the page chrome uses semantic tokens. Specs require each page to list exactly the tokens the harness loader finds for its family and to pass axe in light and dark.
|
|
647
|
+
**Why:** One source: an edit, a new step or a new token file shows up on the page with no story change, and globs tolerate a missing file. Membership by prefix keeps new tokens under known families automatic.
|
|
648
|
+
**Watch out:** A token under a brand-new top-level family (not in any page's prefixes) is on no page; add the prefix to `families.ts`. Samples follow the JSON immediately, but components only follow after `npm run tokens:build` regenerates tokens.css.
|
|
649
|
+
|
|
650
|
+
### SB-0032 · 2026-11-08 · Pattern specs load the color mode before render and read headings in reading order
|
|
651
|
+
**Status:** accepted
|
|
652
|
+
**Context:** The first run of the pattern specs failed axe color contrast in dark mode on tabs, toggles, badges and inputs. The specs had switched `data-theme` after the story rendered, as the Card spec does, and axe measured colors while the components' color transitions were still running. Separately, the order of headings from Chromium's full accessibility tree is not document order, so an h2 could be reported before the h1.
|
|
653
|
+
**Decision:** `playwright/helpers/patterns.ts` opens a story with the toolbar global (`&globals=theme:dark`), so the Storybook decorator sets the mode before the first render; it then waits for every element's `updateComplete`. Headings are collected by walking the flattened tree (shadow roots and slots) in the page, skipping `display: none` and `visibility: hidden`; landmarks still come from the accessibility tree, where order does not matter.
|
|
654
|
+
**Why:** It tests what a person sees when the page opens in that mode, without timing waits, and the outline check matches reading order.
|
|
655
|
+
**Watch out:** Component specs that flip `data-theme` after render and then run axe would hit the same transition race; none do today (Card only compares token colors).
|
|
656
|
+
|
|
657
|
+
### SB-0031 · 2026-11-08 · Check K1 keeps patterns on the system; W1 and P1 scan patterns too
|
|
658
|
+
**Status:** accepted
|
|
659
|
+
**Context:** The plan asks that kits use only `sb-*` components and semantic tokens, checked deterministically. T4 and T5 read component SCSS only; W1 and P1 read `.ts`/`.scss` under `src`, so pattern CSS, `pattern.json` and READMEs were unchecked.
|
|
660
|
+
**Decision:** New check K1: every `<sb-*>` tag in a kit's stories is a contract tag or element; `pattern.json` has `name`, `summary`, `components`, `landmarks`, `a11y`, `states`, lists exactly the tags the stories use and one state per story export; stories have no inline `style=` or `<style>`; kit CSS references only semantic tokens (a component or foundation token is an error), redefines no `--sb-*` token, and has no color, length, time or z-index literal (the T5 rules, now shared from `harness/lib/css.mjs`; `sketchbook-allow-literal` turns one into a warning); `harness/kits/index.json` lists each kit with the same title and summary and the component folders it uses. W1 also scans `src/patterns/**/*.{css,json,md}`; P1 also scans `.css`.
|
|
661
|
+
**Why:** A kit that reaches for a component token or a hex value breaks on the next rebrand without any test noticing; a stale `pattern.json` or index would mislead the `kits add` command that reads them.
|
|
662
|
+
**Watch out:** Layout measures with no token (column widths, page heights) use `ch`, `%` and `vh`, which the literal rules do not match; keep them to layout, never to spacing or type. K1 reads tags from stories only, so markup built outside the story file is not seen.
|
|
663
|
+
|
|
664
|
+
### SB-0030 · 2026-11-08 · Template kits are patterns in src/patterns, one stylesheet each
|
|
665
|
+
**Status:** accepted
|
|
666
|
+
**Context:** Phase 2.5 adds template kits for the `library+kits` starter: page patterns composed of the 35 components. The research picked eight (sign-in/sign-up, settings, data table, dashboard, profile, docs article, onboarding with empty states, form-states gallery).
|
|
667
|
+
**Decision:** Each kit is a folder `src/patterns/<kit>/` with `<Kit>.stories.ts` (title `Patterns/<Kit>`, full-screen layout, one story per state), `<kit>.css` imported by the story, every class named after the kit (`.sign-in`, `.sign-in__form`), `pattern.json` (contract-light) and `README.md`. Pages use plain landmarks and headings (`main`, `header`, `nav`, `form`, `section`, h1-h3); a heading inside a card or empty-state title is a real `h1`/`h2` reset to inherit the title's type. `harness/kits/index.json` is the catalog for a later `sketchbook kits add`; it lists component folder names, not tags, so `sketchbook prefix` does not have to rewrite it. Behavior and axe specs live in `playwright/tests/patterns/<kit>.behavior.spec.ts`.
|
|
668
|
+
**Why:** One stylesheet per kit (rather than inline styles) is what a team copies into its app, and it is what K1 can read with the same parser as component CSS. Kits add no components and no tokens, so they cannot drift from the system.
|
|
669
|
+
**Watch out:** No Penpot boards for kits yet (the plan lists them; deferred). Kits that need a control the system lacks (a dialog, a sidebar) are out of scope until that component exists.
|
|
670
|
+
|
|
671
|
+
### SB-0029 · 2026-11-08 · Contrast targets follow WCAG 2.2; APCA stays informational
|
|
672
|
+
**Status:** accepted
|
|
673
|
+
**Context:** brand.config named `WCAG21-AA` / `WCAG21-AAA` and T6 kept its own table of ratios. The contrast numbers are unchanged in WCAG 2.2, and APCA is a candidate for a future standard, not a requirement.
|
|
674
|
+
**Decision:** The contrast family in the catalog has `wcag-aa` (default) and `wcag-aaa`, with `WCAG21-AA` and `WCAG21-AAA` kept as aliases, so existing configs work unchanged. T6 and the role-color links read the targets from the resolver (`contrast.targets` can tighten them). APCA Lc values are catalogued and shown in T6 info when `contrast.apca` is true; they never fail a check.
|
|
675
|
+
**Why:** One source for the targets, named after the current standard, and no silent change for existing installs.
|
|
676
|
+
**Watch out:** AAA is hard to meet with saturated brand colors; the links move role colors to a passing step where one exists, otherwise T6 fails with the nearest passing step.
|
|
677
|
+
|
|
678
|
+
### SB-0028 · 2026-11-08 · The CLI is a registry of commands with a JSON envelope
|
|
679
|
+
**Status:** accepted
|
|
680
|
+
**Context:** `harness/cli.mjs` was one if/else chain: no machine-readable output, no dry runs, help only in a header comment, and nothing to introspect the project or the presets.
|
|
681
|
+
**Decision:** Each command is a module in `harness/cli/commands/` exporting name, group, summary, args, options, examples, mutates, dryRun and run; `harness/cli.mjs` only dispatches (node:util parseArgs, unknown options rejected). Every command takes `--json` and prints `{ok, command, changed, warnings, errors[{file, msg, fix}], next, data?}`; exit 0 ok, 1 failed, 2 ok with flags. New read-only `status` and `presets [family]`; `--dry-run` on add, init, prefix, swap and sync; `sketchbook help [command]` and `docs/cli.md` come from the registry (`npm run build:cli-docs`, part of `npm run generate`; G1 keeps it fresh). Human output of the existing commands is unchanged, except errors also print their fix.
|
|
682
|
+
**Why:** Agents and CI need one parseable shape and a way to look before they change anything; generated docs cannot drift from the CLI. Conventions adapted from CLI-Anything (Apache-2.0), no code used.
|
|
683
|
+
**Watch out:** `add` moved to `harness/commands/add.mjs` (still re-exported by `harness/cli.mjs`). `sketchbook check --json` wraps the check report in `data`; `npm run check:json` still prints the bare report. The interactive mode and the `tokens` group come later.
|
|
684
|
+
|
|
685
|
+
### SB-0027 · 2026-11-08 · Success, warning and info are semantic roles in every mode
|
|
686
|
+
**Status:** accepted
|
|
687
|
+
**Context:** The semantic layer had only destructive as a status color, so accents such as success or warning had nowhere to go, and components or patterns needing them would have hard-coded ramps.
|
|
688
|
+
**Decision:** `color.success`, `color.warning`, `color.info` and their `-foreground` tokens exist in light and dark (and the templates), linked in brand-links.json to roles from the semanticRoles catalog. A role takes the accent named in `color.roles`, else the accent with the catalog's default name (danger, green, amber, blue), else the catalog seed color, whose ramp is generated. Each `-foreground on role` pair is in `spec/tokens/contrast.json` and passes AA. Accents may not take a semantic color name (a path is a token or a group); the generator says so. This is the one planned change to the default output: tokens.css gains the green, amber and blue ramps and the six role variables per mode; nothing else moves (golden test updated in the same commit).
|
|
689
|
+
**Why:** Status colors are part of almost every product; giving them roles with contrast guarantees keeps components and kits off raw ramps.
|
|
690
|
+
**Watch out:** Warning on its own solid uses dark text by design. The role solids are not required to reach 4.5:1 on the page background, so use them as fills or icons with text, not as text color, unless a contract pair proves it.
|
|
691
|
+
|
|
692
|
+
### SB-0026 · 2026-11-08 · Foundation = generator(brand.config) + overrides, and G1 proves it
|
|
693
|
+
**Status:** accepted
|
|
694
|
+
**Context:** Hand-added foundation tokens were erased on the next `tokens:generate`, overrides could only be added, and nothing noticed when brand.config.json changed without regenerating.
|
|
695
|
+
**Decision:** The generator keeps tokens added by hand and records them in `spec/tokens/overrides.json` (`added: true`) next to edited values; overrides of tokens the generator no longer makes are dropped and reported, and ones that match the generated value again are settled. `harness/generators/overrides.mjs` gives `listOverrides`, `resetOverride(path)` and `resetAll()`. `tokens:generate` prints the overrides it keeps. G1 rebuilds the foundation from brand.config.json plus overrides.json and rejects any foundation file that differs, and rejects linked semantic tokens that are stale.
|
|
696
|
+
**Why:** Outputs must be reproducible from their sources; a hand edit is legitimate only once it is recorded. G1 now catches a config change that was never regenerated.
|
|
697
|
+
**Watch out:** A hand edit to a foundation file fails G1 until `npm run tokens:generate` records it (the fix says so). A hand-added token inside a group with a different `$type` keeps its own `$type`.
|
|
698
|
+
|
|
699
|
+
### SB-0025 · 2026-11-08 · Semantic links are declared in brand-links.json and applied on every tokens:generate
|
|
700
|
+
**Status:** accepted
|
|
701
|
+
**Context:** Re-pointing semantic tokens at the brand was hard-coded (primary, destructive, control heights), ran only on `init`, and skipped missing tokens silently. Light and dark were told apart by `modes[0]` in one place and the name `light` in another.
|
|
702
|
+
**Decision:** `spec/tokens/brand-links.json` (template in `harness/templates/`) lists each semantic token that follows brand.config and its rule: `{from: "color", role, part}` for role colors, `{from: density|radius|motion|elevation|icons|z, role}` for the rest. `harness/generators/links.mjs` applies it on every `tokens:generate` (so `init` gets it too). A link whose semantic token or foundation target is missing is reported by the generator and as a G1 warning. Modes are `"light"`, `"dark"` or `{name, role}`; the role (light or dark, default: dark only for a mode named dark) picks ramp steps and the `prefers-color-scheme` block. A mode without a template starts from its role's template. Role colors move to the nearest ramp step whose readable foreground meets the text target.
|
|
703
|
+
**Why:** One declarative place for "what follows the brand"; teams unlink a token by deleting its entry instead of fighting a script. Every regenerate leaves the semantic layer consistent with the config.
|
|
704
|
+
**Watch out:** A linked token edited by hand is overwritten on the next regenerate (G1 flags it as stale first); delete its link to own it. `semantic-brand.mjs` and its exported `applyBrandToSemantic` are gone.
|
|
705
|
+
|
|
706
|
+
### SB-0024 · 2026-11-08 · Foundations come from a standards catalog; brand.config v2 picks presets
|
|
707
|
+
**Status:** accepted
|
|
708
|
+
**Context:** Most foundations were tables inside `foundation.mjs` (mono font, weights, line heights, letter spacing, shadows, motion, z, opacity, borders, sizes), `baseSize` was ignored under the default scale, radius had three fixed styles and accents other than danger did nothing.
|
|
709
|
+
**Decision:** `harness/standards/<family>.json` holds 19 preset families (spacing, typeScale, lineHeight, letterSpacing, weights, rampMethods, neutrals, semanticRoles, contrast, radius, elevation, motion, density, layoutGrid, breakpoints, iconSizes, zIndex, opacity, borderWidth); each preset has id, label, values, description in our words, source URL and `verified`. `harness/standards/resolve.mjs` turns brand.config into concrete values: every foundation key is optional and accepts a preset id, `{preset}`, `{custom}` and fine overrides merged over the preset. brand.config v2 adds `typography.mono/lineHeights/letterSpacing/weights/source`, `color.roles`, radius `base`/custom px, `elevation`, `motion`, `density` objects, `contrast.preset`, `grid`, `breakpoints`, `icons`, `z`, `opacity`, `border`. Only the OKLCH ramp method is implemented; the others are catalogued as future. The v1 config keeps working and the default config produces byte-identical outputs (golden test `harness/test/golden/tokens.default.css`).
|
|
710
|
+
**Why:** Teams pick known standards instead of editing generator code, and the harness can name where each value came from. Defaults reproduce the shipped system, so nothing moves until a team chooses.
|
|
711
|
+
**Watch out:** Spacing keys are multipliers of the base (space.4 = 4 x base), so an 8 px unit doubles every distance. Presets marked `verified: false` are our own or approximations; their source is a pointer, not a copy. `typography.source` is recorded only; fonts.css comes later.
|
|
712
|
+
|
|
713
|
+
### SB-0023 · 2026-11-08 · The project is Sketchbook
|
|
714
|
+
**Status:** accepted
|
|
715
|
+
**Context:** The harness was called ds-portable with the `ds` prefix. The owner named it Sketchbook: the first draft of a design system, made to be edited or redone.
|
|
716
|
+
**Decision:** Package and CLI `sketchbook`; element and CSS prefix `sb` (`sb-button`, `--sb-color-primary`, `SbButton`); decision ids SB-NNNN (renumbered from DS-NNNN, ids only); browser global `Sketchbook`; env `SKETCHBOOK_PORT` and `SKETCHBOOK_FORBIDDEN_TERMS`; local list `.sketchbook-forbidden-terms`; literal marker `sketchbook-allow-literal`; Penpot shapes `[sb]`. Earlier entries keep their wording.
|
|
717
|
+
**Why:** One name everywhere. The CLI is not `sb` because that is an old Storybook command name; the marker no longer starts with the prefix, so a later `sketchbook prefix` rename cannot break it.
|
|
718
|
+
**Watch out:** The Penpot file still holds `[ds]` shapes until the next sync deletes them; consumers of the old bundle global `dsPortable` must switch to `Sketchbook`.
|
|
719
|
+
|
|
720
|
+
### SB-0022 · 2026-11-08 · Stable needs an a11y verdict and a person; an unavailable design tool is skipped
|
|
721
|
+
**Status:** accepted
|
|
722
|
+
**Context:** The spec makes accessibility part of done and puts a person before stable, but R1 only asked for a parity audit and a synced design file. `adapters.design.available: false` was written by init and then ignored by sync and D1.
|
|
723
|
+
**Decision:** R1 moves a component to stable only when its latest `docs/a11y-audits/<name>-<date>.md` says `Verdict: ready` and carries an `Approved-by:` line. `ds sync` refuses to run, and D1 reports nothing, while the design adapter is unavailable or not Penpot.
|
|
724
|
+
**Why:** The gate can now reject what the principle promises. A team without a working design tool keeps every other command.
|
|
725
|
+
**Watch out:** No component is stable yet, so the stable gate is untested on real components; the first promotion should be watched.
|
|
726
|
+
|
|
727
|
+
### SB-0021 · 2026-11-08 · Density and the smallest radius follow brand.config
|
|
728
|
+
**Status:** accepted
|
|
729
|
+
**Context:** The alignment review found `density` had no effect after install: control heights were fixed in the semantic layer. The checkbox corner aliased the 4px spacing step, so it ignored `radius.style`.
|
|
730
|
+
**Decision:** `ds init` re-points `size.control.sm/default/lg` to the density's heights, like it re-points primary. The foundation gets `radius.xs` (preset minus 6px), and the semantic token is renamed `radius.xsmall` (path collision with the foundation `radius.xs`, see SB-0014).
|
|
731
|
+
**Why:** Every brand.config input must change the output; a setting that does nothing breaks the beginner's trust in the config.
|
|
732
|
+
**Watch out:** Behavior specs still assert the comfortable control heights (36px and so on); a compact or spacious install needs those size assertions read from tokens, as radius now is.
|
|
733
|
+
|
|
734
|
+
### SB-0020 · 2026-11-08 · White-label guard catches copied reference text and private brand names
|
|
735
|
+
**Status:** accepted
|
|
736
|
+
**Context:** W1 caught the reference's name but not its words: three contract leads were copied from the reference's docs. Its brand list was empty, so a stale design script with a company name passed, and `generated/` was never scanned.
|
|
737
|
+
**Decision:** W1 rejects any contract that contains a phrase from `harness/checks/data/reference-phrases.json` (case and spacing ignored), scans `generated/` for brand names, and reads extra brand names from an untracked `.ds-forbidden-terms` file or `DS_FORBIDDEN_TERMS`. Eight contract leads were rewritten in our own words.
|
|
738
|
+
**Why:** The visual reference is for look and naming only (D-036); the guard has to see copying, not just mentions. Private brand names can be guarded without being written into the shipped repo.
|
|
739
|
+
**Watch out:** The phrase list only knows what a review found; extend it when a new copy is caught.
|
|
740
|
+
|
|
741
|
+
### SB-0019 · 2026-11-08 · Incident: a rebranded install failed six of its own behavior specs
|
|
742
|
+
**Status:** incident
|
|
743
|
+
**Context:** The white-label proof (fresh clone, new primary, font and round radius) passed every check, but six specs (Alert, Card, Empty, Item) failed: they asserted the default brand's radius in px.
|
|
744
|
+
**Decision:** Specs read lengths from tokens with the `tokenLength` helper, as colors already did with `tokenColor`.
|
|
745
|
+
**Why:** A test that only passes for one brand is not white-label.
|
|
746
|
+
**Watch out:** Assertions on control heights and paddings are still in px; see SB-0021.
|
|
747
|
+
|
|
748
|
+
### SB-0018 · 2026-11-08 · Incident: production builds shipped components that never upgraded
|
|
749
|
+
**Status:** incident
|
|
750
|
+
**Context:** `package.json` `sideEffects` listed only `src/components/**`. The bundler treated the barrel `src/index.ts` and `tokens.css` as side-effect free and dropped them, so the static Storybook (and any consumer bundle importing the package for registration) defined no elements. Every CI-style behavior test timed out. The dev server doesn't tree-shake, so local runs hid it; CI had never run (no remote).
|
|
751
|
+
**Decision:** `sideEffects` lists the barrel, every component file and the token CSS. A harness test requires every file that calls `customElements.define`, the barrel and `tokens.css` to match a pattern.
|
|
752
|
+
**Why:** Registration is a side effect; the build must never be allowed to drop it.
|
|
753
|
+
**Watch out:** Run the behavior suite against the static build (`CI=true`) before a release, not only against the dev server.
|
|
754
|
+
|
|
755
|
+
### SB-0017 · 2026-11-08 · The element and CSS prefix is rebrandable
|
|
756
|
+
**Status:** accepted
|
|
757
|
+
**Context:** `harness.config.json` names the prefix (`ds`) and the harness reads it, but component sources, contracts, stories, tests and docs spelled `ds-`, `--ds-` and `Ds*` by hand, so changing the config broke everything.
|
|
758
|
+
**Decision:** Keep `ds` as the shipped default and rebrand with a codemod: `ds prefix <new>` (or `ds init --prefix <new>`) rewrites tags, custom properties and `Ds*` identifiers in sources, contracts, tests and docs, updates the config and rebuilds generated files; check P1 rejects component sources whose element names or custom properties ignore the configured prefix.
|
|
759
|
+
**Why:** Rewriting the source keeps the code readable and greppable; a runtime prefix would make every tag, selector and test string dynamic. P1 keeps a half-done or hand-made rename from passing.
|
|
760
|
+
**Watch out:** The codemod is text-based: names that merely start with `ds-` (`ds-portable`, `ds-allow-literal`) are kept on purpose; the decision log, `generated/` and the harness's own tests are not rewritten, and the Penpot file needs a re-sync after a rename (D1 warns).
|
|
761
|
+
|
|
762
|
+
### SB-0016 · 2026-11-08 · Incident: four stories crashed after the docs-page change
|
|
763
|
+
**Status:** incident
|
|
764
|
+
**Context:** Docs pages were switched to render each contract.md; four story files used the helper without importing it.
|
|
765
|
+
**Decision:** Fixed the imports; `npm run typecheck` now also typechecks stories (tsconfig.stories.json).
|
|
766
|
+
**Why:** Stories were excluded from typecheck, and lint can't see undefined names in TypeScript, so 42 behavior tests timed out instead of a fast, clear error.
|
|
767
|
+
**Watch out:** The pre-commit hook runs the checks, not the behavior tests; run `npm run test:component` before committing changes to stories or helpers.
|
|
768
|
+
|
|
769
|
+
### SB-0015 · 2026-11-08 · Incident: two builders gave the same semantic token different values
|
|
770
|
+
**Status:** incident
|
|
771
|
+
**Context:** Parallel builders both added `space.stack.xs` and `space.stack.lg` with different values.
|
|
772
|
+
**Decision:** Kept the first meaning, gave the other intent new names (`space.stack.tight`, `space.stack.loose`) and re-pointed those contracts; merges stop on any value clash instead of picking a side.
|
|
773
|
+
**Why:** Picking a side would silently resize components that were already tested.
|
|
774
|
+
**Watch out:** The stack scale now has near-duplicates (xs/snug, lg/xl); consolidate it in one change with every affected contract.
|
|
775
|
+
|
|
776
|
+
### SB-0014 · 2026-11-08 · Incident: brand ramp and semantic token shared a path
|
|
777
|
+
**Status:** incident
|
|
778
|
+
**Context:** With a brand color, the foundation ramp was `color.primary.*` while `color.primary` is a semantic token; Style Dictionary merged them and lost references, so every rebrand failed.
|
|
779
|
+
**Decision:** The brand ramp is `color.brand.*`; check T1 rejects any path that is both a token and a group.
|
|
780
|
+
**Why:** Our own resolver used flat paths and could not see the collision; only the merging build did.
|
|
781
|
+
**Watch out:** Name new foundation groups so they never equal a semantic token path.
|
|
782
|
+
|
|
783
|
+
### SB-0013 · 2026-11-08 · Incident: tokens.css header closed its own comment
|
|
784
|
+
**Status:** incident
|
|
785
|
+
**Context:** The generated header read "spec/components/*/contract.json"; the `*/` ended the comment early and browsers dropped the whole `:root` rule, so no token applied.
|
|
786
|
+
**Decision:** Neutral header text and a regression test that the first rule is the `:root` selector.
|
|
787
|
+
**Why:** PostCSS is lenient and parsed it; only a browser showed the failure.
|
|
788
|
+
**Watch out:** Never put glob paths in generated CSS comments.
|
|
789
|
+
|
|
790
|
+
### SB-0012 · 2026-11-08 · Radio Group: native radios, the group owns the semantics
|
|
791
|
+
**Context:** Each ds-radio-group-item renders a native radio in its own shadow root, so the browser sees every radio as a group of one.
|
|
792
|
+
**Decision:** The ds-radio-group element is form-associated (name, value, required, validity) and owns the roving tab stop; it sets checked, tabindex, aria-posinset and aria-setsize on its items. Toggle Group uses aria-pressed buttons (not radios) in single mode because a pressed item can be cleared.
|
|
793
|
+
**Why:** Keeps native radio semantics per item while the group restores what the shadow boundary hides (arrow keys, one tab stop, set position, group validity).
|
|
794
|
+
**Watch out:** Chromium's accessibility tree doesn't expose posinset/setsize for these; tests assert the DOM attributes.
|
|
795
|
+
|
|
796
|
+
### SB-0011 · 2026-11-08 · Owner pre-approves all remaining waves
|
|
797
|
+
**Context:** The owner asked to complete every phase without being asked (2026-11-08).
|
|
798
|
+
**Decision:** The planning gate still runs (contract, check, plan.md for every component), but each plan is recorded as approved by this decision instead of a per-wave approval. Test-first, checks, parity audit and review before beta are unchanged.
|
|
799
|
+
**Why:** Keep the gate's artifacts and quality bar while removing the wait.
|
|
800
|
+
**Watch out:** Decisions a plan would normally ask about are taken with the recommendation and listed in that plan's open questions as answered, so the owner can revisit them.
|
|
801
|
+
|
|
802
|
+
### SB-0010 · 2026-11-08 · First Penpot sync: what the adapter learned
|
|
803
|
+
**Context:** First real sync of tokens, Spinner, Button (44 variants) and Input (3 states) to the scratch file "MCP Test 2".
|
|
804
|
+
**Decision:** Keep the adapter rules that made it work: themes take set objects, not names; components are made from boards, never bare SVG shapes; imported SVG strokes are bound to the variant foreground token; managed shapes are named "[ds] …" and replaced on each sync; new components are placed below everything on the page. Penpot rejects negative shadow spread, so Tailwind's md/lg spread (-1px, -3px) is clamped to 0 in Penpot only.
|
|
805
|
+
**Why:** Each rule fixes a failure seen in the first run; the live read-back (generated/design/penpot.verify.json) matched the spec in light and dark.
|
|
806
|
+
**Watch out:** Penpot's md/lg shadows are slightly larger than the code's. Motion tokens (24) are not in Penpot by design. Penpot's default font is used instead of the system font stack.
|
|
807
|
+
|
|
808
|
+
### SB-0009 · 2026-11-08 · Shadow-DOM controls: what crosses the boundary and what doesn't
|
|
809
|
+
**Context:** The review-rangers review and the parity audit of Spinner, Button and Input (reports in docs/parity-audits/) found three shadow-DOM gaps, each reproduced in Chromium.
|
|
810
|
+
**Decision:** (1) Form controls handle Enter themselves and call `form.requestSubmit()`, because an input inside a shadow root has no form owner and implicit submission never fires. (2) A prop that shows an error also sets a `customError` validity, so the form blocks submission. (3) Only `aria-label` is forwarded from the host; `aria-labelledby` and `aria-describedby` are not, because ID references don't resolve across shadow roots.
|
|
811
|
+
**Why:** Each gap broke a promise in the contract while every test passed; the tests now cover all three.
|
|
812
|
+
**Watch out:** Enter submits without a submitter, so a ds-button submit's name/value is not sent on Enter (logged as Input drift).
|
|
813
|
+
|
|
814
|
+
### SB-0008 · 2026-11-08 · Design file: Penpot only for now
|
|
815
|
+
**Context:** Both adapters were proven in spikes; the owner wants to focus.
|
|
816
|
+
**Decision:** Build and sync only the Penpot adapter in v1's first phases. The Figma adapter stays designed (spec) but unbuilt.
|
|
817
|
+
**Why:** Penpot is free and open source, and its tokens can be imported from files.
|
|
818
|
+
**Watch out:** `harness.config.json` `adapters.design.tool` is `penpot`; contracts keep `realizations.design` tool-neutral.
|
|
819
|
+
|
|
820
|
+
### SB-0007 · 2026-11-08 · Component architecture for the 35 Tier 1 components
|
|
821
|
+
**Context:** shadcn/ui is the UI reference; implementation is Lit Web Components built the the reference implementation way.
|
|
822
|
+
**Decision:** Parts are separate custom elements named like shadcn's (`ds-card`, `ds-card-header`); compound state uses `@lit/context`; roving focus is one reactive controller generalized from a name-based radio-group mixin; native elements first (checkbox, switch, radio, select, range, ARIA table roles on custom elements); `ds-direction` sets `dir` and components read `:dir(rtl)`. Shared mixins and controllers are added in the wave that first needs them (hammock YAGNI).
|
|
823
|
+
**Why:** Native semantics and proven patterns give accessibility for free; shadcn names keep the API familiar.
|
|
824
|
+
**Watch out:** Native Select must mirror light-DOM options into its shadow `<select>`; Slider needs one range input per thumb.
|
|
825
|
+
|
|
826
|
+
### SB-0006 · 2026-11-08 · Button: href, xs sizes, and Spinner in the slice
|
|
827
|
+
**Context:** Open question Q4 and current shadcn Button sizes.
|
|
828
|
+
**Decision:** `href` renders a native `<a part="button">` with button styling (shadcn's asChild link pattern). Sizes add `xs` (24px) and `icon-xs`. Spinner is built in the slice and Button uses it.
|
|
829
|
+
**Why:** Links keep link semantics; sizes match the reference; no throwaway inline spinner.
|
|
830
|
+
**Watch out:** With `href`, `type`, `name` and `value` are ignored and `disabled` removes the href (links can't be disabled natively).
|
|
831
|
+
|
|
832
|
+
### SB-0005 · 2026-11-08 · Button and Input follow shadcn/ui, with three accessibility deviations
|
|
833
|
+
**Context:** UI follows shadcn/ui; process follows the contract-first standard; D-001 makes accessibility a requirement.
|
|
834
|
+
**Decision:** Button gets shadcn variants and sizes (icon-only via `size="icon"`), plus a `loading` prop. Input gets shadcn's look with label, description and error built in. Deviations: solid 3px focus ring; loading keeps focus; the Input error is announced when it appears.
|
|
835
|
+
**Why:** shadcn's ring/50 is below 3:1; the reference implementation's loading drops focus mid-action; an unannounced error is missed by screen-reader users.
|
|
836
|
+
**Watch out:** Every deviation is listed in the contract's `realizations.*.drift` so it can be revisited.
|
|
837
|
+
|
|
838
|
+
### SB-0004 · 2026-11-08 · Default theme is shadcn/ui "neutral", with three contrast fixes
|
|
839
|
+
**Context:** The default install should look like shadcn/ui and stay white-label.
|
|
840
|
+
**Decision:** brand.config generates Tailwind's neutral ramp and shadcn's theme variables. Changed from shadcn: `input` border neutral-500 (was neutral-200), `ring` neutral-500 / dark neutral-400 (was neutral-400 at 50%), light `muted` neutral-50 (was neutral-100).
|
|
841
|
+
**Why:** Check T6 found those three below WCAG 2.1 AA (1.4.11 for borders and focus, 1.4.3 for muted text).
|
|
842
|
+
**Watch out:** A team restyling to exact shadcn values will see T6 fail; that is intended.
|
|
843
|
+
|
|
844
|
+
### SB-0003 · 2026-11-08 · Components are built test-first
|
|
845
|
+
**Context:** Quality has to be proven, not asserted.
|
|
846
|
+
**Decision:** `features.testFirst = true`. Behavior specs (Playwright, axe) are written from the contract and must fail before implementation.
|
|
847
|
+
**Why:** A spec that never failed may not test anything.
|
|
848
|
+
**Watch out:** Tests are not edited to fit code; the contract changes first.
|
|
849
|
+
|
|
850
|
+
### SB-0002 · 2026-11-08 · Component creation follows the contract-first standard (generalized from a production design system)
|
|
851
|
+
**Context:** the reference implementation's contract pair, file layout and Lit patterns are a proven structure.
|
|
852
|
+
**Decision:** Contract format, file layout (`<Name>.ts`, `.scss`, generated `.styles.ts`, `.stories.ts`), `FormAssociated` and `NativeControl` mixins, behavior specs, this decision format, the simplicity debt log, and the hammock, review-rangers and playwright-worker skills. Kept from ds-portable: three token layers (component tokens only in component CSS), all-English docs, shadcn names, sm/default/lg sizes.
|
|
853
|
+
**Why:** Reuse a structure that already works, without copying any company's brand, copy or IDs.
|
|
854
|
+
**Watch out:** the reference implementation's own accessibility gaps are not inherited (see SB-0005).
|