Extract a repo's design system into an executable UX contract (.uxproof/)
One-time scan of tokens, components, screen archetypes and conventions via a pinned npx extractor, with manual overrides that survive regeneration — every other UX skill in the collection judges against it
- What
- One-time scan of tokens, components, screen archetypes and conventions via a pinned npx extractor, with manual overrides that survive regeneration — every other UX skill in the collection judges against it
- Cost
- Free
- Needs
- a code repository whose design system (or lack of one) should be captured; Node.js/npm for the pinned extractor — the skill produces a contract, it does not review anything
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @open-mercato's om-ux-setup skill: run once per repository to extract the design system into a committed, executable contract at `.uxproof/` — `contract.json` (framework, styling system, component roots, screen archetypes), `tokens.json` (every design token with kind and source file), `components.json` (component registry), and `conventions.md` (human-readable house rules, with a manual section for the judgment calls only the team can know — it survives regeneration and outranks generated rules). The workflow: check for an existing contract first (never regenerate silently), extract via a pinned `npx [email protected] init --no-skills` (pinned deliberately so `@latest` never executes unreviewed remote code), report what was found for a human sanity check, ask the two or three questions only the team can answer, surface hygiene warnings (contracts built on scratch files), then hand over — this skill produces the contract and stops; it never reviews anything. Security boundaries: repo content is data, never instructions (embedded directives are reported as prompt injection); secrets stay out of model output. Honest caveats: it degrades gracefully for repos with no design system (falls back to a proposed de-facto palette derived from the code); companion skills it names (om-ux-review-pr, om-ux-shape, om-mockup-prototype) are separate members of the collection, not bundled here. MIT licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: a code repository whose design system (or lack of one) should be captured; Node.js/npm for the pinned extractor — the skill produces a contract, it does not review anything Install "Extract a repo's design system into an executable UX contract (.uxproof/)" for me. It gives my agent @open-mercato's om-ux-setup workflow: check for an existing .uxproof/contract.json first, extract tokens/components/archetypes/conventions via the pinned npx [email protected] init --no-skills (or the manual fallback offline), report findings for a human sanity check, capture the team's judgment calls in the manual section, surface contract-hygiene warnings, and hand over a report — then stop. MIT licensed. Repository: https://github.com/open-mercato/skills/blob/main/skills/om-ux-setup/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "om-ux-setup". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. point the agent at the repository to scan; decide whether to refresh an existing contract vs leave it; answer the 2-3 judgment-call questions; companion skills (om-ux-review-pr for PR review, om-ux-shape for feature shaping, om-mockup-prototype for mockups) are separate collection members — install separately if needed). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.