@fugood/bricks-ctor 2.25.0-beta.12 → 2.25.0-beta.13

package/skills/bricks-ux/references/ux-critique.md

@@ -0,0 +1,256 @@
+# UX Critique
+
+Verification proves the flow *runs*. UX critique proves the flow is *usable*. Both are required before declaring done; neither substitutes for the other.
+
+UX critique runs in parallel with visual-design critique (`bricks-design/design-critique.md`). A Canvas can fail one and pass the other; both block ship.
+
+This file is tiered. The same UX problem (e.g., closure missing) is **CRITICAL** on a payment kiosk and **MEDIUM** on a museum signage loop. Critique fails ship when CRITICAL or HIGH items go unaddressed in their applicable tiers.
+
+## How to run the pass
+
+1. **Open the journey.** Walk every interaction step-by-step using `user-journey.md` as the spine.
+2. **For each Canvas / Brick group, classify by deployment risk** (table below). The classification determines which tier of checks apply.
+3. **Run the checks in the applicable tier(s).** CRITICAL items always run; HIGH applies broadly; MEDIUM and LOW depend on classification.
+4. **Fix every CRITICAL miss and every HIGH miss.** Surface MEDIUM and LOW misses in the trade-off note if not addressed.
+5. **Re-verify after fixes.** Don't accumulate fix debt.
+
+## Risk classification by deployment shape
+
+| Deployment shape | Risk profile | Tier weighting |
+|---|---|---|
+| Payment / identity capture / safety-critical | CRITICAL-dense — every transact discipline must pass | CRITICAL + HIGH + MEDIUM all apply |
+| Self-service interactive (ordering, check-in, configuration) | HIGH-dense — journey completeness, idle reset, recovery paths | CRITICAL + HIGH apply; MEDIUM where relevant |
+| Monitoring / dashboard / control room | HIGH-dense — alarm hierarchy, stale-data trust, calm/detect/demand | CRITICAL + HIGH apply for alarm states |
+| Browse / wayfinding / menu board | MEDIUM-dense — legibility, comparison clarity, sparse states | HIGH legibility, MEDIUM elsewhere |
+| Glanceable signage / dwell / ambient loop | LOW-dense — main checks are legibility and rhythm | HIGH legibility, LOW elsewhere |
+
+## CRITICAL — blocks ship
+
+Failure on any of these is sufficient grounds to declare the work mid-iteration.
+
+### CR-1. The user-journey spine is whole
+
+Every interaction must have all seven steps present (or deliberately compressed; see `user-journey.md` § "When the seven steps compress"). Most-common holes:
+
+- **Immediate feedback missing** (step 3). User taps, nothing visible, taps again.
+- **In-flight visibility missing** (step 4). Action triggered, screen frozen, user re-triggers.
+- **Recovery as dead-end** (step 6). Error Canvas with no path forward.
+- **Closure ambiguous or missing** (step 7). Success state transient or unclear.
+
+**Must Have:** every interaction has a designed and verified affordance, instruction, feedback, in-flight state, continuation, recovery, closure — or deliberate documented collapse.
+**Anti-Pattern:** journey skipping any step on the assumption "it's fast enough not to need".
+
+### CR-2. Transact has its intensification
+
+For payment / identity / safety-critical flows, the seven steps must be tightened (`user-journey.md` § "When the seven steps intensify"):
+
+- Confirmation step before commit.
+- In-flight visibility non-skippable.
+- Recovery categorised (declined / network / cancelled / timeout).
+- Closure with weight and hold time.
+
+**Must Have:** transact closure holds ≥ 5 seconds, success unmistakable, peripheral state visible.
+**Anti-Pattern:** "Process payment in one tap" with no confirmation; closure that auto-advances in < 2s.
+
+### CR-3. Monitoring has demand discipline
+
+For dashboards / monitor screens with alarm capability:
+
+- Calm / detect / demand are three distinct designed states.
+- Demand state stands out unambiguously; not a slight colour change.
+- Multiple concurrent demand states have priority ordering already designed.
+- Stale-data is visibly declared per source.
+- Color is never the only encoding of severity.
+
+**Must Have:** alarm-state preview captured and reviewed; squint-test passes (alarm visible from peripheral vision); monochrome preview still distinguishes severity tiers.
+**Anti-Pattern:** alarm styled identically to detect-state; "stale" indicator at 8pt in corner; severity by colour alone.
+
+### CR-4. Accessibility floors met for the audience
+
+The seven accessibility disciplines (`accessibility.md`) apply at deployment-relative floors. CRITICAL when the audience includes:
+
+- Reduced-vision users (contrast, scale, color-not-only).
+- Reduced-motor users (touch targets, no precise gestures, no time-pressure auto-cancels).
+- Sensitive-to-motion users (reduced-motion path available).
+- Multilingual audience (strings via Data; type scale accommodates longest translation).
+
+**Must Have:** contrast verified under deployment-actual lighting; touch targets verified with real-finger / real-hardware testing; severity / status encoded by shape + color + label.
+**Anti-Pattern:** WCAG-compliance-on-desktop-monitor as the audit (deployment is sunlit signage at 4m); time-pressure UI on a venue that includes slow / hesitant users.
+
+### CR-5. Idle reset is clean
+
+For self-service interactive deployments:
+
+- Idle timeout exists and is calibrated to the use pattern.
+- Idle reset clears flow state — no half-built order persists; no name on screen; no half-confirmed action.
+- Reset returns to a designed idle / attractor state, not to "whatever Canvas was loaded".
+
+**Must Have:** verified idle reset behaviour via Automation or live test; verified that no leaked state persists to next session.
+**Anti-Pattern:** idle = last interact Canvas; idle that requires operator to manually reset.
+
+## HIGH — must fix before launch
+
+### H-1. Affordance is unambiguous
+
+Every pressable Brick declares "press me" visually — contrast, weight, motion, or icon. Affordance vocabulary is consistent across the deployment.
+
+**Must Have:** pressable tiles visually distinct from non-pressable; squint test confirms which Bricks are interactive.
+**Anti-Pattern:** identical-looking tiles where some are pressable and some aren't; pressable Bricks with no visual distinction from background.
+
+### H-2. Press feedback at registration
+
+Every `on_press` produces a visible state change at the moment of registration — scale, opacity, color, or new Brick entry via Standby Transition. Not a fade-in.
+
+**Must Have:** Brick under press visibly responds within 100ms (effectively snap, not fade).
+**Anti-Pattern:** press registers, no visible change; press relies on Canvas-change-only feedback (user perceives lag).
+
+### H-3. Flow states designed, not skipped
+
+Idle / loading / empty / error / boot / maintenance (as applicable to the deployment) are designed states, each with verified preview.
+
+**Must Have:** every applicable state's preview captured and reviewed; failure modes per state checked against `flow-states.md`.
+**Anti-Pattern:** "empty state is fine, the list is always populated" without testing the empty case; error state in 8pt corner text; boot = loading spinner.
+
+### H-4. Hero continuity across journey Canvases
+
+For multi-Canvas flows, hero Bricks share ids across Canvases — chrome (logo, progress indicator, time, back action) carries via Truth #3 auto-tween.
+
+**Must Have:** primary chrome elements identifiable in the same screen positions across the flow's Canvases.
+**Anti-Pattern:** every Canvas remounts its full Brick set; user loses spatial mental model between steps.
+
+### H-5. Error recovery has a path
+
+Every error state offers retry, alternate method, abandon, or help — never a dead-end. Different error categories get distinguishable recovery treatments.
+
+**Must Have:** each error path verified end-to-end via Automation or live test.
+**Anti-Pattern:** "Error. Please try again." with no retry mechanism; generic recovery for all error types.
+
+### H-6. Stale-data trust
+
+For monitoring / live-data screens, every dynamic source has a visibly declared staleness state or a visible "last update" relative-time indicator.
+
+**Must Have:** staleness visible in peripheral vision; stale value distinguishable from current value.
+**Anti-Pattern:** dynamic value with no age indication; "last update" in 8pt absolute timestamp.
+
+### H-7. Predictable navigation
+
+Navigation affordances (back, next, home) sit consistently across Canvases. Idle returns to the same idle Canvas every time.
+
+**Must Have:** back / next affordance positions verified across Canvases; idle reset produces identical idle Canvas every time.
+**Anti-Pattern:** back button at top-left on Canvas 2, bottom-right on Canvas 3; idle rotates such that the "anchor" element moves.
+
+## MEDIUM — impacts polish; prioritize by user impact
+
+### M-1. Instruction matches user mental model
+
+Action instructions ("Scan your code", "Tap to start", "Pay now") match the user's likely understanding; jargon avoided; language locale-matched.
+
+**Must Have:** wording reviewed for the actual audience; jargon removed.
+**Anti-Pattern:** "Initiate authentication sequence" on a public kiosk; English-only instruction on a multilingual venue.
+
+### M-2. Continuation is non-surprising
+
+The Canvas the user lands on after an action matches their expectation. Big jumps in journey context happen only with explicit transition.
+
+**Must Have:** continuation Canvas reviewed for context preservation; hero continuity in place.
+**Anti-Pattern:** success on Canvas A jumps to Canvas D mid-flow; user loses context.
+
+### M-3. Closure proportional to stakes
+
+Success closure hold time and visual weight match the action's stakes. Routine completions get brief acknowledgement; transact completions get held visible.
+
+**Must Have:** closure hold time tuned to action stakes; auto-advance only after enough time for the user to read.
+**Anti-Pattern:** 1.5s closure for a transact flow; 8s closure for a "saved to favorites" toast.
+
+### M-4. Density rhythm in browse / dwell
+
+For browse / dwell deployments, content rotation has variation in density / framing / colour rhythm across Canvases or slides. Three identical-rhythm Canvases in a row is a tell. (Cross-reference: `bricks-design/design-critique.md` density-rhythm collapse.)
+
+**Must Have:** rhythm variation across the sequence; no three identical-archetype Canvases in a row.
+**Anti-Pattern:** ten Canvases that all read as "headline + bullet list".
+
+### M-5. Audio cues calibrated (when hardware allows)
+
+If the deployment uses audio, volume / timing / time-of-day awareness is intentional.
+
+**Must Have:** audio volume / scheduling reviewed; success / alarm cues distinguishable from ambient.
+**Anti-Pattern:** constant-volume cues regardless of time; audio-only confirmation (no visual pair).
+
+### M-6. Reduced-motion path available (if relevant)
+
+For deployments in clinical / safety / motion-sensitive contexts, a reduced-motion path exists.
+
+**Must Have:** `reduceMotion` Data flag wired where applicable; verified reduced-motion preview.
+**Anti-Pattern:** continuous-motion design with no reduction path for a clinical deployment.
+
+## LOW — context-dependent
+
+### L-1. Polish on idle / attractor presence
+
+For deployments where idle dominates: idle is *inviting*, not just *running*.
+
+**Must Have for high-traffic public deployments:** attractor sequence engages from peripheral vision.
+**Anti-Pattern:** logo-only idle on a deployment whose purpose is to invite interaction.
+
+### L-2. Maintenance state designed
+
+If the deployment has scheduled downtime, a maintenance Canvas exists and distinguishes itself from error.
+
+**Must Have for deployments with maintenance windows:** maintenance Canvas with return path.
+**Anti-Pattern:** maintenance = black screen.
+
+### L-3. Empty-state composition
+
+Empty states explain the absence and suggest what populates.
+
+**Must Have:** empty state designed rather than collapsed-whitespace.
+**Anti-Pattern:** "—" or blank where content would be.
+
+## Tier-by-tier checklist (running order)
+
+Use this when running the pass:
+
+**CRITICAL (always run):**
+
+- [ ] User-journey spine whole (CR-1)
+- [ ] Transact intensified if applicable (CR-2)
+- [ ] Monitoring demand discipline if applicable (CR-3)
+- [ ] Accessibility floors met (CR-4)
+- [ ] Idle reset clean if applicable (CR-5)
+
+**HIGH (always run except for glance / dwell loops):**
+
+- [ ] Affordance unambiguous (H-1)
+- [ ] Press feedback at registration (H-2)
+- [ ] Flow states designed (H-3)
+- [ ] Hero continuity across Canvases (H-4)
+- [ ] Error recovery has a path (H-5)
+- [ ] Stale-data trust if applicable (H-6)
+- [ ] Predictable navigation (H-7)
+
+**MEDIUM (run for interact / transact / browse):**
+
+- [ ] Instruction matches mental model (M-1)
+- [ ] Continuation non-surprising (M-2)
+- [ ] Closure proportional (M-3)
+- [ ] Density rhythm (M-4)
+- [ ] Audio cues calibrated (M-5)
+- [ ] Reduced-motion path (M-6)
+
+**LOW (run for public-facing / high-dwell):**
+
+- [ ] Idle / attractor polish (L-1)
+- [ ] Maintenance state (L-2)
+- [ ] Empty-state composition (L-3)
+
+## Definition of UX done
+
+A flow is UX-done when:
+
+1. The CRITICAL tier passes — zero unaddressed CRITICAL items.
+2. The HIGH tier passes — zero unaddressed HIGH items (or surfaced as accepted trade-off with rationale).
+3. Applicable MEDIUM / LOW items either pass or are surfaced.
+4. Every state (golden path + error categories + idle + empty if relevant) has been verified via preview screenshot or Automation, and reviewed.
+5. Accessibility floors are met at the deployment-relative threshold, not at a desktop default.
+
+If any item is unmet, the work is mid-iteration. Say so explicitly to the user; offer a precise list of what remains.

package/tools/pull.ts

@@ -1,8 +1,31 @@
-import { readFile, writeFile } from 'node:fs/promises'
+import { readdir, readFile, unlink, writeFile } from 'node:fs/promises'
+import { existsSync } from 'node:fs'
+import { join, relative } from 'node:path'
 import { format } from 'oxfmt'
 import { sh } from './_shell'
 import { buildCommitArgs } from './_git-author'
 
+// Directories whose .ts contents are entirely owned by the generator.
+// Anything under these dirs not present in the freshly pulled file list is an orphan.
+const ownedTsDirs = ['subspaces', 'automation-tests']
+
+async function walkTsFiles(dir: string, baseDir: string): Promise<string[]> {
+  if (!existsSync(dir)) return []
+  const result: string[] = []
+  const entries = await readdir(dir, { withFileTypes: true })
+  await Promise.all(
+    entries.map(async (entry) => {
+      const full = join(dir, entry.name)
+      if (entry.isDirectory()) {
+        result.push(...(await walkTsFiles(full, baseDir)))
+      } else if (entry.isFile() && entry.name.endsWith('.ts')) {
+        result.push(relative(baseDir, full))
+      }
+    }),
+  )
+  return result
+}
+
 const cwd = process.cwd()
 const args = process.argv.slice(2)
 const force = args.includes('--force') || args.includes('-f')
@@ -89,6 +112,23 @@ const oxfmtConfig = await readFile(`${cwd}/.oxfmtrc.json`, 'utf8')
     printWidth: 100,
   }))
 
+const expectedFiles = new Set(files.map((file: { name: string }) => file.name))
+
+// Remove orphan .ts files under generator-owned directories before writing.
+// File paths are produced by buildApplicationFiles and use forward slashes,
+// so normalise the walked paths the same way for comparison.
+const orphans: string[] = []
+await Promise.all(
+  ownedTsDirs.map(async (dir) => {
+    const existing = await walkTsFiles(join(cwd, dir), cwd)
+    for (const file of existing) {
+      const normalized = file.split(/[\\/]/).join('/')
+      if (!expectedFiles.has(normalized)) orphans.push(normalized)
+    }
+  }),
+)
+await Promise.all(orphans.map((name) => unlink(`${cwd}/${name}`)))
+
 await Promise.all(
   files.map(async (file: { name: string; input: string; formatable?: boolean }) => {
     let content = file.input
@@ -118,5 +158,5 @@ if (isGitRepo) {
 }
 
 console.log(
-  `${isModule ? 'Module' : 'App'} project pulled: ${files.length} files${force ? ' (force)' : ''}`,
+  `${isModule ? 'Module' : 'App'} project pulled: ${files.length} files${orphans.length ? `, removed ${orphans.length} orphan .ts file${orphans.length === 1 ? '' : 's'}` : ''}${force ? ' (force)' : ''}`,
 )

package/types/automation.ts

@@ -203,6 +203,7 @@ export type LocalSyncMode = 'main-only' | 'minor-only'
 export interface AutomationTest {
   __typename: 'AutomationTest'
   id: string
+  alias?: string
   title: string
   hideShortRef?: boolean
   timeout: number

package/types/data-calc.ts

@@ -2,6 +2,7 @@
 export interface DataCalculation {
   __typename: string
   id: string
+  alias?: string
   title?: string
   description?: string
   hideShortRef?: boolean

package/skills/bricks-design/LICENSE.txt

@@ -1,180 +0,0 @@
-                                 Apache License
-                           Version 2.0, January 2004
-                        http://www.apache.org/licenses/
-
-   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
-   1. Definitions.
-
-      "License" shall mean the terms and conditions for use, reproduction,
-      and distribution as defined by Sections 1 through 9 of this document.
-
-      "Licensor" shall mean the copyright owner or entity authorized by
-      the copyright owner that is granting the License.
-
-      "Legal Entity" shall mean the union of the acting entity and all
-      other entities that control, are controlled by, or are under common
-      control with that entity. For the purposes of this definition,
-      "control" means (i) the power, direct or indirect, to cause the
-      direction or management of such entity, whether by contract or
-      otherwise, or (ii) ownership of fifty percent (50%) or more of the
-      outstanding shares, or (iii) beneficial ownership of such entity.
-
-      "You" (or "Your") shall mean an individual or Legal Entity
-      exercising permissions granted by this License.
-
-      "Source" form shall mean the preferred form for making modifications,
-      including but not limited to software source code, documentation
-      source, and configuration files.
-
-      "Object" form shall mean any form resulting from mechanical
-      transformation or translation of a Source form, including but
-      not limited to compiled object code, generated documentation,
-      and conversions to other media types.
-
-      "Work" shall mean the work of authorship, whether in Source or
-      Object form, made available under the License, as indicated by a
-      copyright notice that is included in or attached to the work
-      (an example is provided in the Appendix below).
-
-      "Derivative Works" shall mean any work, whether in Source or Object
-      form, that is based on (or derived from) the Work and for which the
-      editorial revisions, annotations, elaborations, or other modifications
-      represent, as a whole, an original work of authorship. For the purposes
-      of this License, Derivative Works shall not include works that remain
-      separable from, or merely link (or bind by name) to the interfaces of,
-      the Work and Derivative Works thereof.
-
-      "Contribution" shall mean any work of authorship, including
-      the original version of the Work and any modifications or additions
-      to that Work or Derivative Works thereof, that is intentionally
-      submitted to Licensor for inclusion in the Work by the copyright owner
-      or by an individual or Legal Entity authorized to submit on behalf of
-      the copyright owner. For the purposes of this definition, "submitted"
-      means any form of electronic, verbal, or written communication sent
-      to the Licensor or its representatives, including but not limited to
-      communication on electronic mailing lists, source code control systems,
-      and issue tracking systems that are managed by, or on behalf of, the
-      Licensor for the purpose of discussing and improving the Work, but
-      excluding communication that is conspicuously marked or otherwise
-      designated in writing by the copyright owner as "Not a Contribution."
-
-      "Contributor" shall mean Licensor and any individual or Legal Entity
-      on behalf of whom a Contribution has been received by Licensor and
-      subsequently incorporated within the Work.
-
-   2. Grant of Copyright License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      copyright license to reproduce, prepare Derivative Works of,
-      publicly display, publicly perform, sublicense, and distribute the
-      Work and such Derivative Works in Source or Object form.
-
-   3. Grant of Patent License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      (except as stated in this section) patent license to make, have made,
-      use, offer to sell, sell, import, and otherwise transfer the Work,
-      where such license applies only to those patent claims licensable
-      by such Contributor that are necessarily infringed by their
-      Contribution(s) alone or by combination of their Contribution(s)
-      with the Work to which such Contribution(s) was submitted. If You
-      institute patent litigation against any entity (including a
-      cross-claim or counterclaim in a lawsuit) alleging that the Work
-      or a Contribution incorporated within the Work constitutes direct
-      or contributory patent infringement, then any patent licenses
-      granted to You under this License for that Work shall terminate
-      as of the date such litigation is filed.
-
-   4. Redistribution. You may reproduce and distribute copies of the
-      Work or Derivative Works thereof in any medium, with or without
-      modifications, and in Source or Object form, provided that You
-      meet the following conditions:
-
-      (a) You must give any other recipients of the Work or
-          Derivative Works a copy of this License; and
-
-      (b) You must cause any modified files to carry prominent notices
-          stating that You changed the files; and
-
-      (c) You must retain, in the Source form of any Derivative Works
-          that You distribute, all copyright, patent, trademark, and
-          attribution notices from the Source form of the Work,
-          excluding those notices that do not pertain to any part of
-          the Derivative Works; and
-
-      (d) If the Work includes a "NOTICE" text file as part of its
-          distribution, then any Derivative Works that You distribute must
-          include a readable copy of the attribution notices contained
-          within such NOTICE file, excluding those notices that do not
-          pertain to any part of the Derivative Works, in at least one
-          of the following places: within a NOTICE text file distributed
-          as part of the Derivative Works; within the Source form or
-          documentation, if provided along with the Derivative Works; or,
-          within a display generated by the Derivative Works, if and
-          wherever such third-party notices normally appear. The contents
-          of the NOTICE file are for informational purposes only and
-          do not modify the License. You may add Your own attribution
-          notices within Derivative Works that You distribute, alongside
-          or as an addendum to the NOTICE text from the Work, provided
-          that such additional attribution notices cannot be construed
-          as modifying the License.
-
-      You may add Your own copyright statement to Your modifications and
-      may provide additional or different license terms and conditions
-      for use, reproduction, or distribution of Your modifications, or
-      for any such Derivative Works as a whole, provided Your use,
-      reproduction, and distribution of the Work otherwise complies with
-      the conditions stated in this License.
-
-   5. Submission of Contributions. Unless You explicitly state otherwise,
-      any Contribution intentionally submitted for inclusion in the Work
-      by You to the Licensor shall be under the terms and conditions of
-      this License, without any additional terms or conditions.
-      Notwithstanding the above, nothing herein shall supersede or modify
-      the terms of any separate license agreement you may have executed
-      with Licensor regarding such Contributions.
-
-   6. Trademarks. This License does not grant permission to use the trade
-      names, trademarks, service marks, or product names of the Licensor,
-      except as required for reasonable and customary use in describing the
-      origin of the Work and reproducing the content of the NOTICE file.
-
-   7. Disclaimer of Warranty. Unless required by applicable law or
-      agreed to in writing, Licensor provides the Work (and each
-      Contributor provides its Contributions) on an "AS IS" BASIS,
-      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-      implied, including, without limitation, any warranties or conditions
-      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
-      PARTICULAR PURPOSE. You are solely responsible for determining the
-      appropriateness of using or redistributing the Work and assume any
-      risks associated with Your exercise of permissions under this License.
-
-   8. Limitation of Liability. In no event and under no legal theory,
-      whether in tort (including negligence), contract, or otherwise,
-      unless required by applicable law (such as deliberate and grossly
-      negligent acts) or agreed to in writing, shall any Contributor be
-      liable to You for damages, including any direct, indirect, special,
-      incidental, or consequential damages of any character arising as a
-      result of this License or out of the use or inability to use the
-      Work (including but not limited to damages for loss of goodwill,
-      work stoppage, computer failure or malfunction, or any and all
-      other commercial damages or losses), even if such Contributor
-      has been advised of the possibility of such damages.
-
-   9. Accepting Warranty or Additional Liability. While redistributing
-      the Work or Derivative Works thereof, You may choose to offer,
-      and charge a fee for, acceptance of support, warranty, indemnity,
-      or other liability obligations and/or rights consistent with this
-      License. However, in accepting such obligations, You may act only
-      on Your own behalf and on Your sole responsibility, not on behalf
-      of any other Contributor, and only if You agree to indemnify,
-      defend, and hold each Contributor harmless for any liability
-      incurred by, or claims asserted against, such Contributor by reason
-      of your accepting any such warranty or additional liability.
-
-   END OF TERMS AND CONDITIONS
-
-   This skill is a derivative work based on:
-   https://github.com/anthropics/skills/blob/main/skills/frontend-design/SKILL.md
-   Copyright Anthropic, PBC. Licensed under the Apache License, Version 2.0.