[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72CGMP7FKG49MS7M2VTD52W":3,"skill-same:01M72CGMP7FKG49MS7M2VTD52W":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M72CGMP7FKG49MS7M2VTD52W","ui-kit",null,"Use project UI prototypes, shared components and artboard conventions for desktop, mobile, tablet and print.","1aGh\u002Fmaude","1aGh","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F17166964?v=4","01M72CAQDBB0YG724KFT7WEYRF","Michal Dovrtel","01M72CAQDXC32AWQRZYNJXXDC4",3,"MIT","https:\u002F\u002Fgithub.com\u002F1aGh\u002Fmaude\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign\u002Fskills\u002Fui-kit\u002FSKILL.md",[],[],"2026-11-10 18:39:20",false,"---\nname: ui-kit\ndescription: \"Use project UI prototypes, shared components and artboard conventions for desktop, mobile, tablet and print.\"\n---\n\n# UI kit — pointer skill\n\nFollow [host conventions](..\u002F..\u002FHARNESS.md) for Claude Code or Codex.\n\nThis skill is a **thin pointer**. The actual UI-kit content lives under the project's design root, defined in `\u003Crepo>\u002F.design\u002Fconfig.json`:\n\n```\n\u003CdesignRoot>\u002Fui\u002F\n  ├── project\u002F\n  │   ├── \u003CProjectName> Studio.tsx       # multi-artboard desktop canvas (composer)\n  │   ├── \u003CProjectName> Mobile.tsx       # multi-artboard mobile canvas (composer)\n  │   ├── \u003COther Canvas>.tsx             # additional canvas projects\n  │   ├── components\u002F*.tsx               # shared desktop components\n  │   └── components\u002Fmobile\u002F*.tsx        # shared mobile components\n  ├── chats\u002F                             # iteration transcripts per surface (if migrated from Claude Design)\n  └── README.md                          # canvas catalog\n```\n\nPer-canvas TSX files import frame primitives (`DesignCanvas`, `DCSection`, `DCArtboard`, `DCPostIt`) from `@maude\u002Fcanvas-lib` — a virtual specifier the dev-server resolves to its bundled canvas-lib at `apps\u002Fstudio\u002Fcanvas-lib.tsx` (single source, ships with the dev-server install per DDR-025). `\u002Fdesign:handoff` AST-inlines the used exports on emit so the registry-item drop is self-contained (no `@maude\u002Fcanvas-lib` reference survives in the consumer drop).\n\nThis skill is non-user-invocable. Auto-loads when Claude is doing UI work. The user-facing entry point is the `design` orchestrator skill.\n\n## Canon: canvas-first, multi-artboard\n\nEvery project canvas under `\u003CdesignRoot>\u002Fui\u002Fproject\u002F` follows the same shape:\n\n1. **`DesignCanvas`** wrapper — panable \u002F zoomable infinite-canvas pattern.\n2. **`DCSection`** blocks — labeled groups of related screens.\n3. **`DCArtboard`** instances — individual screens, each wrapped in the project's app shell where applicable.\n\nStandalone single-page HTML wrappers (one screen, no canvas) are an anti-pattern and should be migrated when found. New screens always go into an existing canvas as a new `DCArtboard`, or a new canvas via `\u002Fdesign:new` (made by the app's own create, so it matches the one ⌘N makes: \"Untitled canvas\", the default design system, or the one its folder uses).\n\n## Artboard kinds (feature-1-artboard-kinds-foundation · S7.20)\n\nEvery `DCArtboard` declares what it IS via a `kind` prop: `digital` (the designer word is **Fixed size**: screens, apps, social pictures at exact pixels) | `web` (**Web page**) | `print` (**Print**) | `video` (**Video**). The size picker (F over empty canvas) groups them by what you are making: **App · Web page · Social · Print · Video**; App and Social both make a Fixed size artboard. Read [Artboards of a kind](..\u002Fdesign\u002F_guide-28-artboards.md) for the presets, the exact `\u003CDCArtboard>` each one writes, and the order to add them in; never guess a size or write `paper: \"custom\"`. An artboard with no `kind` still resolves to `digital`, or to `video` when its subtree contains a `\u003CVideoComp>` (the structural fallback for canvases written before the prop existed), but anything you add now carries its kind.\n\n**Which kind to generate:**\n\n- **Fixed size** (`kind=\"digital\" fixed`, written by the App and Social presets) — app screens, dashboards, mobile UI, and fixed-size social pictures (a post, a story, a cover). A picked preset always writes the kind, so write it too; App screens are flow-first, Social compositions are absolute-first.\n- **Print** (`kind=\"print\" print={{ paper, orientation }}`) — a page meant to be physically printed or exported as a print-ready PDF (business cards, posters, brochures). The px size is trim + 2 × bleed, so it comes from the paper (the table in the guide), with bleed, trim and safe-margin guides and DPI-aware export on top.\n- **Web page** (`kind=\"web\"`) — a responsive web flow authored **flow-first**: flex\u002Fgrid (or plain block flow) layout, height hugs content (`fixed` omitted), and in-artboard responsiveness rides `@container`\u002F`cqw`\u002F`cqh` (the artboard body is already a `container-type: inline-size` root) — never `vw`\u002F`vh`\u002F`@media` width queries (the existing artboard-isolation ban still applies). Absolute positioning is reserved for a deliberate, commented overlay (badge, floating CTA), not the default layout mechanism. One artboard per breakpoint (Desktop 1440 · Laptop 1280 · Tablet 834 · Mobile 390); the artboard menu's \"Duplicate at another width\" makes a structural copy, not a linked variant. Full generation contract: `\u002Fdesign:new`'s Web brief cue; full edit contract: `\u002Fdesign:edit`'s Web-artboard-awareness step (both feature-3-web-artboards).\n- **Video** (`kind=\"video\"`) — an artboard hosting a `\u003CVideoComp>` composition (see the `video-comp` skill), written by the Video presets (Reels 9:16 · Landscape 16:9 · Square 1:1).\n\n**Changing the kind of a finished artboard is not a prop edit.** The person's \"Change kind\" makes a scaled copy beside the original and says what moved; it never quietly rewrites the artboard. To get another size or kind, add a new artboard of that preset and fill it. Switching a Fixed size artboard to a Web page, or the reverse, changes chrome and editing rules only; it never converts the content's layout (flow to absolute is a different, deliberate operation).\n\n**Generic layout guides.** Any artboard, regardless of kind, can carry a `guides` prop (`guides={{ columns: {count, gutter, margin}, rows: {...}, grid: {size} }}`, Figma vocabulary) — columns\u002Frows render as violet bands, grid as red hairlines. Visibility is per viewer, never part of the versioned canvas (print guides are under Menu › View › Advanced ▸ Print guides) — don't expect a `guides` prop change alone to show anything until the viewer has guides toggled on.\n\n## How the orchestrator uses this skill\n\nWhen `design` is asked to start work on a known surface:\n\n1. Lists canvas files in `\u003CdesignRoot>\u002Fui\u002Fproject\u002F` and matches by name.\n2. Resolves component file (e.g. `\u003CdesignRoot>\u002Fui\u002Fproject\u002Fcomponents\u002F\u003CSurface>.jsx`) if the canvas references one.\n3. Reads any matching iteration transcript in `\u003CdesignRoot>\u002Fui\u002Fchats\u002F` — that's the source of truth for what the user actually wanted.\n4. Loads tokens from `\u003CdesignRoot>\u002F\u003CtokensCssRel>`.\n5. Hands the union as the aesthetic + layout brief to `frontend-design` (for new canvases) or applies inline edits (for `\u002Fdesign:edit \"\u003Cfeedback>\"`).\n\nFor unknown surfaces, the orchestrator skips component-mapping but still loads tokens + finds one similar reference canvas to learn the project's idioms.\n\n## What you must never do\n\n- **Never bypass the canvas pattern.** New screens go inside `DesignCanvas` artboards, not as new top-level HTML pages.\n- **Never edit the migrated `chats\u002F` transcripts** — they're historical record.\n- **Never assume desktop and mobile share components** — each platform has its own subdir under `components\u002F`.\n\n## Cross-links\n\n- Canvas catalog: `\u003CdesignRoot>\u002Fui\u002FREADME.md` (if present)\n- Per-repo config: `.design\u002Fconfig.json`\n- Sibling skill: `design-system` (tokens, type, color)\n- Sibling skill: `design` (orchestrator)\n","# UI kit — pointer skill\n\nFollow [host conventions](..\u002F..\u002FHARNESS.md) for Claude Code or Codex.\n\nThis skill is a **thin pointer**. The actual UI-kit content lives under the project's design root, defined in `\u003Crepo>\u002F.design\u002Fconfig.json`:\n\n```\n\u003CdesignRoot>\u002Fui\u002F\n  ├── project\u002F\n  │   ├── \u003CProjectName> Studio.tsx       # multi-artboard desktop canvas (composer)\n  │   ├── \u003CProjectName> Mobile.tsx       # multi-artboard mobile canvas (composer)\n  │   ├── \u003COther Canvas>.tsx             # additional canvas projects\n  │   ├── components\u002F*.tsx               # shared desktop components\n  │   └── components\u002Fmobile\u002F*.tsx        # shared mobile components\n  ├── chats\u002F                             # iteration transcripts per surface (if migrated from Claude Design)\n  └── README.md                          # canvas catalog\n```\n\nPer-canvas TSX files import frame primitives (`DesignCanvas`, `DCSection`, `DCArtboard`, `DCPostIt`) from `@maude\u002Fcanvas-lib` — a virtual specifier the dev-server resolves to its bundled canvas-lib at `apps\u002Fstudio\u002Fcanvas-lib.tsx` (single source, ships with the dev-server install per DDR-025). `\u002Fdesign:handoff` AST-inlines the used exports on emit so the registry-item drop is self-contained (no `@maude\u002Fcanvas-lib` reference survives in the consumer drop).\n\nThis skill is non-user-invocable. Auto-loads when Claude is doing UI work. The user-facing entry point is the `design` orchestrator skill.\n\n## Canon: canvas-first, multi-artboard\n\nEvery project canvas under `\u003CdesignRoot>\u002Fui\u002Fproject\u002F` follows the same shape:\n\n1. **`DesignCanvas`** wrapper — panable \u002F zoomable infinite-canvas pattern.\n2. **`DCSection`** blocks — labeled groups of related screens.\n3. **`DCArtboard`** instances — individual screens, each wrapped in the project's app shell where applicable.\n\nStandalone single-page HTML wrappers (one screen, no canvas) are an anti-pattern and should be migrated when found. New screens always go into an existing canvas as a new `DCArtboard`, or a new canvas via `\u002Fdesign:new` (made by the app's own create, so it matches the one ⌘N makes: \"Untitled canvas\", the default design system, or the one its folder uses).\n\n## Artboard kinds (feature-1-artboard-kinds-foundation · S7.20)\n\nEvery `DCArtboard` declares what it IS via a `kind` prop: `digital` (the designer word is **Fixed size**: screens, apps, social pictures at exact pixels) | `web` (**Web page**) | `print` (**Print**) | `video` (**Video**). The size picker (F over empty canvas) groups them by what you are making: **App · Web page · Social · Print · Video**; App and Social both make a Fixed size artboard. Read [Artboards of a kind](..\u002Fdesign\u002F_guide-28-artboards.md) for the presets, the exact `\u003CDCArtboard>` each one writes, and the order to add them in; never guess a size or write `paper: \"custom\"`. An artboard with no `kind` still resolves to `digital`, or to `video` when its subtree contains a `\u003CVideoComp>` (the structural fallback for canvases written before the prop existed), but anything you add now carries its kind.\n\n**Which kind to generate:**\n\n- **Fixed size** (`kind=\"digital\" fixed`, written by the App and Social presets) — app screens, dashboards, mobile UI, and fixed-size social pictures (a post, a story, a cover). A picked preset always writes the kind, so write it too; App screens are flow-first, Social compositions are absolute-first.\n- **Print** (`kind=\"print\" print={{ paper, orientation }}`) — a page meant to be physically printed or exported as a print-ready PDF (business cards, posters, brochures). The px size is trim + 2 × bleed, so it comes from the paper (the table in the guide), with bleed, trim and safe-margin guides and DPI-aware export on top.\n- **Web page** (`kind=\"web\"`) — a responsive web flow authored **flow-first**: flex\u002Fgrid (or plain block flow) layout, height hugs content (`fixed` omitted), and in-artboard responsiveness rides `@container`\u002F`cqw`\u002F`cqh` (the artboard body is already a `container-type: inline-size` root) — never `vw`\u002F`vh`\u002F`@media` width queries (the existing artboard-isolation ban still applies). Absolute positioning is reserved for a deliberate, commented overlay (badge, floating CTA), not the default layout mechanism. One artboard per breakpoint (Desktop 1440 · Laptop 1280 · Tablet 834 · Mobile 390); the artboard menu's \"Duplicate at another width\" makes a structural copy, not a linked variant. Full generation contract: `\u002Fdesign:new`'s Web brief cue; full edit contract: `\u002Fdesign:edit`'s Web-artboard-awareness step (both feature-3-web-artboards).\n- **Video** (`kind=\"video\"`) — an artboard hosting a `\u003CVideoComp>` composition (see the `video-comp` skill), written by the Video presets (Reels 9:16 · Landscape 16:9 · Square 1:1).\n\n**Changing the kind of a finished artboard is not a prop edit.** The person's \"Change kind\" makes a scaled copy beside the original and says what moved; it never quietly rewrites the artboard. To get another size or kind, add a new artboard of that preset and fill it. Switching a Fixed size artboard to a Web page, or the reverse, changes chrome and editing rules only; it never converts the content's layout (flow to absolute is a different, deliberate operation).\n\n**Generic layout guides.** Any artboard, regardless of kind, can carry a `guides` prop (`guides={{ columns: {count, gutter, margin}, rows: {...}, grid: {size} }}`, Figma vocabulary) — columns\u002Frows render as violet bands, grid as red hairlines. Visibility is per viewer, never part of the versioned canvas (print guides are under Menu › View › Advanced ▸ Print guides) — don't expect a `guides` prop change alone to show anything until the viewer has guides toggled on.\n\n## How the orchestrator uses this skill\n\nWhen `design` is asked to start work on a known surface:\n\n1. Lists canvas files in `\u003CdesignRoot>\u002Fui\u002Fproject\u002F` and matches by name.\n2. Resolves component file (e.g. `\u003CdesignRoot>\u002Fui\u002Fproject\u002Fcomponents\u002F\u003CSurface>.jsx`) if the canvas references one.\n3. Reads any matching iteration transcript in `\u003CdesignRoot>\u002Fui\u002Fchats\u002F` — that's the source of truth for what the user actually wanted.\n4. Loads tokens from `\u003CdesignRoot>\u002F\u003CtokensCssRel>`.\n5. Hands the union as the aesthetic + layout brief to `frontend-design` (for new canvases) or applies inline edits (for `\u002Fdesign:edit \"\u003Cfeedback>\"`).\n\nFor unknown surfaces, the orchestrator skips component-mapping but still loads tokens + finds one similar reference canvas to learn the project's idioms.\n\n## What you must never do\n\n- **Never bypass the canvas pattern.** New screens go inside `DesignCanvas` artboards, not as new top-level HTML pages.\n- **Never edit the migrated `chats\u002F` transcripts** — they're historical record.\n- **Never assume desktop and mobile share components** — each platform has its own subdir under `components\u002F`.\n\n## Cross-links\n\n- Canvas catalog: `\u003CdesignRoot>\u002Fui\u002FREADME.md` (if present)\n- Per-repo config: `.design\u002Fconfig.json`\n- Sibling skill: `design-system` (tokens, type, color)\n- Sibling skill: `design` (orchestrator)\n",{"name":5,"description":7},"main","cfde9d2b169e4b418a5c5efb35297cc575dc764c","plugins\u002Fdesign\u002Fskills\u002Fui-kit",0,"https:\u002F\u002Fgithub.com\u002F1aGh\u002Fmaude","https:\u002F\u002Fmaude.sh","https:\u002F\u002Fgithub.com\u002F1aGh","www.iagh.cz","2026-11-13 20:38:15",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add 1aGh\u002Fmaude --skill ui-kit",{"tool":39,"command":40},"bunx","bunx skills add 1aGh\u002Fmaude --skill ui-kit",{"tool":42,"command":43},"pnpm","pnpm dlx skills add 1aGh\u002Fmaude --skill ui-kit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F1aGh\u002Fmaude\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign\u002Fskills\u002Fui-kit\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M72CJCVNC5JB3M36ES649CTY","workflow-state","Read and update workflow state when planning, executing, completing, pausing or resuming project work.","https:\u002F\u002Fgithub.com\u002F1aGh\u002Fmaude\u002Fblob\u002Fmain\u002Fplugins\u002Fflow\u002Fskills\u002Fworkflow-state\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M72CJAJBZT2RHE97ND8EFTA3","ui-rules","UI hard-stop rules and audit method: WCAG 2.1 AA accessibility, responsive layout and motion.","https:\u002F\u002Fgithub.com\u002F1aGh\u002Fmaude\u002Fblob\u002Fmain\u002Fplugins\u002Fflow\u002Fskills\u002Fui-rules\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M72CJ857314HCC8A99T4K0D2","testing-rules","Apply test quality rules during implementation and review: meaningful assertions, isolation and coverage.","https:\u002F\u002Fgithub.com\u002F1aGh\u002Fmaude\u002Fblob\u002Fmain\u002Fplugins\u002Fflow\u002Fskills\u002Ftesting-rules\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M72CJ6N80HW2WRS8BV4QSS4V","security-rules","Apply application and AI security checks to code reviews, implementation and threat-driven validation.","https:\u002F\u002Fgithub.com\u002F1aGh\u002Fmaude\u002Fblob\u002Fmain\u002Fplugins\u002Fflow\u002Fskills\u002Fsecurity-rules\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M72CJ4C41Q4E1WDTFMKYFX3Q","scenario","Author or run cross-platform UI scenarios with selectors, screenshots, platform coverage and result reports.","https:\u002F\u002Fgithub.com\u002F1aGh\u002Fmaude\u002Fblob\u002Fmain\u002Fplugins\u002Fflow\u002Fskills\u002Fscenario\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M72CJ1QYX752BM7G12250YJR","question-protocol","Batch necessary questions from workflow participants, collect user answers and route them to the requester.","https:\u002F\u002Fgithub.com\u002F1aGh\u002Fmaude\u002Fblob\u002Fmain\u002Fplugins\u002Fflow\u002Fskills\u002Fquestion-protocol\u002FSKILL.md",[],[]]