ui-pack-create
Use when making a new UI design system pack - from an existing project's source code, or without source from a website URL, SNS post link (reel, video), screenshot, image or video - or when syncing or editing an existing pack. Not for applying a pack to a project - that is the ui-pack skill. Triggers - "turn this project's UI into a pack", "make a pack", "make a pack from this site", "UI pack from this link", "pack from screenshots", "inspired pack", "sync the pack", "edit the pack", "/ui-pack-create".
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Badge for your README
Markdown
[](/listings/greeun--ui-pack-create)HTML
<a href="/listings/greeun--ui-pack-create"><img src="/api/listings/greeun--ui-pack-create/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
git clone https://github.com/greeun/ui-pack-create.git ln -s "$(pwd)/ui-pack-create" ~/.claude/skills/ui-pack-create
Install `ui-pack` the same way, linked as `~/.claude/skills/ui-pack`.
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
SKILL.md · Manifest · 61 lines
- ---
- name: ui-pack-create
- description: Use when making a new UI design system pack - from an existing project's source code, or without source from a website URL, SNS post link (reel, video), screenshot, image or video - or when syncing or editing an existing pack. Not for applying a pack to a project - that is the ui-pack skill. Triggers - "turn this project's UI into a pack", "make a pack", "make a pack from this site", "UI pack from this link", "pack from screenshots", "inspired pack", "sync the pack", "edit the pack", "/ui-pack-create".
- ---
- # ui-pack-create
- This skill makes and edits UI packs. Applying a pack to another project is the job of the `ui-pack` skill.
- A UI pack is a folder that holds one screen design: color, type and spacing tokens, fonts, components, motion, the design guide, the gallery page and the tests that check them. Packs live in the pack store. The shared files that packs depend on live in the `ui-pack` skill.
- `UI_PACK_HOME` is the pack store. It defaults to `~/.axt/vault/ui-pack` when the environment variable is not set.
- | Location | Contents |
- | --- | --- |
- | `$UI_PACK_HOME/packs/<pack>/` | A pack. New packs are made here too. The pack index is `$UI_PACK_HOME/packs/index.html` |
- | `~/.claude/skills/ui-pack/references/pack-format.md` | The reference for the pack format. An existing pack in the pack store is the best worked example when there is one |
- | `~/.claude/skills/ui-pack/catalog.json` | The component catalog (the standard list of components). Each pack records a status per component in `components` of its `pack.json` |
- | `~/.claude/skills/ui-pack/scripts/` | `install.py` (install), `build-view.py` (pack viewer), `gallery-check.mjs` (gallery comparison), `compare.py` (before/after comparison of an application) |
- | `~/.claude/skills/ui-pack/viewer/` | The Next.js template that builds the pack viewer. The `next` version in `viewer/package.json` is the reference version for the empty test project |
- | `~/.claude/skills/ui-pack-create/scripts/` | Tools used only when making packs: `site-collect.mjs`, `site-fidelity.mjs`, `origin-check.mjs`, `shot-compare.py`, `image-colors.py`, `cdp.mjs`, `source-changes.py` |
- ## Actions
- | Request | Condition | Document to follow |
- | --- | --- | --- |
- | "Turn this project's UI into a pack", `/ui-pack-create extract <pack>` | The source code of the source project is available | [extract.md](extract.md) |
- | "Make a pack from this site / link / screenshot", `/ui-pack-create from <URL or file>` | There is no source code (website URL, SNS post link, screenshot, image, video) | [from-site.md](from-site.md) |
- | "Sync the pack", `/ui-pack-create sync <pack>` | The source of a pack extracted from source code has changed | "Sync" below |
- | "Edit the pack" (change values, components or the design guide) | An existing pack is being edited | "Editing a pack" below |
- When you receive both source code and a URL, the source code is the reference ([extract.md](extract.md)). Use the URL only to check the rendered screens.
- ## Common rules
- - Packs are made and edited in the pack store. If the pack store (`$UI_PACK_HOME`) is a git repository, work in a worktree or branch of that repository and commit there. Other projects see the pack only after the branch is merged; ask the user when to merge. If the pack store is not a git repository, edit in place and say so in the report.
- - While you work in a worktree of the pack store, the pack folder is the worktree's `packs/<pack>`. Pass that folder wherever a command below takes `<pack>` (a new pack and an edited pack exist only in the worktree until the merge).
- - The skill files (`~/.claude/skills/ui-pack/`, `~/.claude/skills/ui-pack-create/`) are edited in their own repositories, not in the pack store. If an installed skill folder is a link into a repository's working tree, do not edit files through the link; work in a worktree or branch of that repository.
- - After making or editing a pack, rebuild the pack viewer with `python3 ~/.claude/skills/ui-pack/scripts/build-view.py <pack>` and commit it together with the pack.
- - When you add a component definition to `catalog.json`, also record that component as `absent` in the `pack.json` of every other pack and rebuild the pack viewers of those packs.
- - The design quality review (an anti-slop review skill) is done only in this skill, when the pack is made. It is not done when a pack is applied.
- ## Editing a pack
- 1. Decide the value and the scope first. One token is used by several components (for example `--radius-pill` is shared by buttons, tags and count badges), so find every use with `grep`. If the request points at only some of them, ask the user how far the change should go.
- 2. For a pack that has a source repository (`source.repo` in `pack.json`), the source project is the reference. If the change should also land in the source, change the source first and bring it in with "Sync". If the change stays in the pack only, change the pack and record it in `changes` of `pack.json` as a "pack-only change" (so that the next sync does not revert it to the source value).
- 3. In the pack (in the worktree when the pack store is a git repository), change the value and every place that records it: `tokens/globals.css`, the components, the matching section of `guide/ui-direction.md`, the `tests/` that check the value, and `version` and `changes` in `pack.json`.
- 4. Verify: steps 1 and 2 of section 3 in [extract.md](extract.md) (install into an empty project, `tsc`, lint, `vitest`), `gallery-check.mjs` against `/design` of the test project, and look at the gallery captures yourself. Then rebuild the pack viewer with `build-view.py`.
- 5. Projects that already installed this pack are not updated automatically. After the change is merged (or saved in place), run `install.py` again in that project (it does not overwrite files that were edited after the install).
- To try an edited pack before the merge, give `install.py` the pack folder in the worktree (`<worktree>/packs/<pack>`) as the pack path.
- ## Sync
- Only for packs extracted from source code. A pack that has `origin` in `pack.json` (a pack made without source) has no source repository and is not synced.
- 1. Run `python3 ~/.claude/skills/ui-pack-create/scripts/source-changes.py <pack>` to see which files changed and which files were added in the source.
- 2. For each changed file, carry the diff into the pack, file by file. Do not carry over the source's business vocabulary or the source app's configuration values. Do not overwrite pack files with the source (that erases the pack-only wiring edits).
- 3. For each added file, decide whether to include it with the classification in [extract.md](extract.md).
- 4. Update `source.commit`, `version`, `sources` and `components` in `pack.json`.
- 5. Run the pack tests and `gallery-check.mjs`, and rebuild the pack viewer.
README.md · README · 65 lines
- # ui-pack-create
- A Claude Code skill that makes and edits UI design system packs.
- A UI pack is a folder that holds one screen design: color, type and spacing tokens, fonts, components, motion, a design guide, a gallery page and the tests that check them. This skill makes a pack in one of two ways:
- - **From source code** (`extract.md`): classify the shared UI code of an existing project, copy what is not tied to the business, and wire the app-specific values into one configuration file.
- - **Without source code** (`from-site.md`): from a website URL, an SNS post link, screenshots, images or video. Values are measured, the design guide is written, and the components are written from scratch. Nothing is copied from the original's code.
- It also syncs a pack with its source project and edits existing packs. Applying a pack to a project is the job of the companion skill.
- ## Companion skill (required)
- This skill depends on [ui-pack](https://github.com/greeun/ui-pack). `ui-pack` provides the pack format reference, the component catalog, the installer, the pack viewer builder and the gallery check that the documents here call. Install both.
- ## Install
- ```bash
- git clone https://github.com/greeun/ui-pack-create.git
- ln -s "$(pwd)/ui-pack-create" ~/.claude/skills/ui-pack-create
- ```
- Install `ui-pack` the same way, linked as `~/.claude/skills/ui-pack`.
- ## Where packs live
- Packs are kept in a pack store, not inside the skills:
- - default: `~/.axt/vault/ui-pack/packs/<pack>/`
- - override: set the environment variable `UI_PACK_HOME`; packs are then in `$UI_PACK_HOME/packs/<pack>/`
- If the pack store is a git repository, the skill works in a worktree or branch of it and asks before merging.
- ## Requirements
- - Node 22 or later
- - Python 3 with Pillow (`pip install pillow`)
- - pnpm (for the empty Next.js test project)
- - Google Chrome (the scripts start it headless; the path is the macOS default and is set at the top of `scripts/cdp.mjs`)
- - `ffmpeg` and `yt-dlp` for video and SNS post input
- ## Scripts
- | Script | What it does |
- | --- | --- |
- | `scripts/site-collect.mjs` | Collects computed styles and screenshots of up to three pages (read-only). Refuses blocked services, paths disallowed by `robots.txt` and pages behind a login (exit code 3) |
- | `scripts/site-fidelity.mjs` | Compares the values that repeat in the collected pages with the pack gallery, per style family |
- | `scripts/origin-check.mjs` | Checks the origin record in `pack.json`; for an inspired pack, that no source name, proprietary font or brand color remains |
- | `scripts/shot-compare.py` | Compares a source image with a capture of a screen redrawn from pack components |
- | `scripts/image-colors.py` | Measures colors in regions of an image |
- | `scripts/source-changes.py` | Lists source files that changed since the pack was extracted |
- | `scripts/cdp.mjs` | Shared Chrome DevTools Protocol helpers used by the three `.mjs` scripts |
- ## Responsible use
- - **Respect collection rules.** `site-collect.mjs` does not collect from services that forbid automated collection, from paths that `robots.txt` disallows, or from pages behind a login. There is no option to skip these checks, and the skill does not use other tools to get around a refusal. It asks you for screenshots instead.
- - **Other people's designs become inspired packs only.** Unless you state that the original is yours or that you have permission, the skill makes an inspired pack: no product names, logos, illustrations or screen copy; brand colors shifted by 30° or more of hue angle; proprietary fonts replaced by open-license fonts. Only structure (spacing, radius, type scale, layout, how components are composed) is carried over as reference.
- - **No copied assets.** Fonts and icons come from open-license sources at their official distribution, never from the original site.
- - **Logins are yours to do.** The skill never asks for a password and does not use browser cookies to pass a login wall.
- You are responsible for having the right to use any material you give the skill.
- ## License
- Licensed under the [Apache License, Version 2.0](LICENSE).
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.