@atelier-ui/create-workspace 0.4.11 → 0.4.13

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/CHANGELOG.md CHANGED
@@ -1,3 +1,17 @@
1
+ ## 0.4.13 (2026-11-19)
2
+
3
+ ### 🩹 Fixes
4
+
5
+ - **create-workspace:** component skill carries the standing rules ([5ee6fd2e](https://github.com/DominikPieper/atelier-ui/commit/5ee6fd2e))
6
+
7
+ ### ❤️ Thank You
8
+
9
+ - Dominik Pieper @DominikPieper
10
+
11
+ ## 0.4.12 (2026-11-18)
12
+
13
+ This was a version bump only for create-workspace to align it with other projects, there were no code changes.
14
+
1
15
  ## 0.4.11 (2026-11-18)
2
16
 
3
17
  ### 🚀 Features
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@atelier-ui/create-workspace",
3
- "version": "0.4.11",
3
+ "version": "0.4.13",
4
4
  "description": "Nx preset for Atelier workshop workspaces",
5
5
  "keywords": [
6
6
  "nx",
@@ -30,10 +30,22 @@ wired in `.mcp.json` and the Desktop Bridge plugin is running. If it is not, the
30
30
  and nothing else, say that behaviour has not been specified yet and ask for the node.
31
31
  2. **Write the component.** Tokens only — every colour, space and radius is a `--ui-*` custom
32
32
  property. A raw hex or a hardcoded `2.5rem` is a stylelint error here, not a style opinion.
33
+ Compose by region: a component with more than one logical region (header, body, footer;
34
+ icon, label, action) gives each region its own sub-component or the framework's slot or
35
+ projection mechanism, the way `AtlCard` does with `AtlCardHeader`/`AtlCardContent`/`AtlCardFooter`
36
+ (look it up with `docs-show`) — a flat prop bag cannot take content the design did not
37
+ foresee, and consumers then rebuild the component. Give every icon-only control a real
38
+ accessible name (`aria-label`, or the library icon's `label`) and make every interactive
39
+ control a real `<button>` or `<a>`, not a styled `<div>`/`<span>` — axe in `check:stories`
40
+ flags a missing name, but not a div that only looks clickable. Make any severity, status
41
+ or state visible without colour (an icon, a prefix word, or visually hidden text) — colour
42
+ alone fails users who cannot see it, and no check here catches that.
33
43
  3. **Write the stories, because the stories are the claims.** One story per variant value and
34
44
  per Boolean state, `args`-based; one `play` per behaviour you are asserting, with a real
35
45
  assertion. Copy the shape from `<app>/src/atl-button.stories.*`, which ships with this
36
46
  workspace for exactly that purpose.
47
+ Declare `tags: ['autodocs']` on the story meta, as `atl-button.stories.*` does — without it
48
+ Storybook renders Canvas only, with no Docs tab.
37
49
  4. **Run the checks.** `npm run check:stories`. Read the exit code, not the last line of
38
50
  output.
39
51
  5. **Close the loop against Figma** if the MCP is available: `figma_check_design_parity`,
@@ -36,10 +36,22 @@ workspace is a separate scaffold (`--figma`), not something this one can do.
36
36
  2. **Write the component.** Tokens only — every colour, space and radius is a `--ui-*`
37
37
  custom property. A raw hex or a hardcoded `2.5rem` is a stylelint error here, not a
38
38
  style opinion.
39
+ Compose by region: a component with more than one logical region (header, body, footer;
40
+ icon, label, action) gives each region its own sub-component or the framework's slot or
41
+ projection mechanism, the way `AtlCard` does with `AtlCardHeader`/`AtlCardContent`/`AtlCardFooter`
42
+ (look it up with `docs-show`) — a flat prop bag cannot take content the design did not
43
+ foresee, and consumers then rebuild the component. Give every icon-only control a real
44
+ accessible name (`aria-label`, or the library icon's `label`) and make every interactive
45
+ control a real `<button>` or `<a>`, not a styled `<div>`/`<span>` — axe in `check:stories`
46
+ flags a missing name, but not a div that only looks clickable. Make any severity, status
47
+ or state visible without colour (an icon, a prefix word, or visually hidden text) — colour
48
+ alone fails users who cannot see it, and no check here catches that.
39
49
  3. **Write the stories, because the stories are the claims.** One story per variant value
40
50
  and per Boolean state, `args`-based; one `play` per behaviour you are asserting, with a
41
51
  real assertion. Copy the shape from `<app>/src/atl-button.stories.*`, which ships with
42
52
  this workspace for exactly that purpose.
53
+ Declare `tags: ['autodocs']` on the story meta, as `atl-button.stories.*` does — without it
54
+ Storybook renders Canvas only, with no Docs tab.
43
55
  4. **Run the checks.** `npm run check:unit`, then `npm run check:stories`. Read the exit
44
56
  code, not the last line of output.
45
57