Locked design language + buildable UI/UX spec, no AI slop
A DESIGN-SPEC skill that never writes production UI — commit to one bold aesthetic, ban AI slop by name, lock the identity in DESIGN.md, and hand a delegated agent a buildable spec
- What
- A DESIGN-SPEC skill that never writes production UI — commit to one bold aesthetic, ban AI slop by name, lock the identity in DESIGN.md, and hand a delegated agent a buildable spec
- Cost
- Free
- Needs
- a feature, screen, or design problem to specify (plus optional inspiration URLs) — this skill produces a design spec under .ulpi/design/, never production UI code
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Selected by Skill Harbor — short listing (the repo states no license, so no content is reproduced): @ulpi-io's frontend-design-ui-ux skill — a DESIGN-SPEC skill with non-negotiable rules, not an implementation skill. The workflow: discovery and inputs (target users, goal, context — ask once for reference URLs), optional inspiration intake (visit links with the browse skill, extract design DNA, synthesize — never clone one), design read and aesthetic direction (commit to ONE named direction from the anti-slop menu and pass the counterfactual default test), derive and LOCK the design language (palette in OKLCH, type roles, one spacing/radius/motion scale, the Signature, the voice — written to .ulpi/design/DESIGN.md, re-read every session), model flows and states (primary journey plus loading/empty/error/edge cases into .ulpi/design/<feature>.md), specify components and interaction rules (variants, props, states, responsive, accessibility), run the Design Pre-Flight gate (identity lock, anti-slop, state coverage, scored self-critique — fix anything ticked off), and finish with a build handoff (target engineering agent + acceptance criteria: "implement exactly this spec, do NOT redesign"). Everything is written under .ulpi/design/. Honest caveats: produces specs, never production UI — hand the build to a delegated engineering agent; inspiration-link visiting needs the browse skill (degrades gracefully without it); license not stated by the source repo — short listing with a link only, nothing copied. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: a feature, screen, or design problem to specify (plus optional inspiration URLs) — this skill produces a design spec under .ulpi/design/, never production UI code Install "Locked design language + buildable UI/UX spec, no AI slop" for me. It gives my agent @ulpi-io's frontend-design-ui-ux DESIGN-SPEC skill: the non-negotiable rules, discovery and inspiration intake, committing to one bold aesthetic direction with the anti-slop menu, deriving and locking the design language in DESIGN.md, modeling flows and states, specifying components with accessibility, running the Design Pre-Flight gate, and handing a delegated agent the build brief. IMPORTANT: the repo states no license — fetch from the link only, and reproduce nothing beyond the link. Repository: https://github.com/ulpi-io/skills/blob/main/frontend-design-ui-ux/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. 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 "frontend-design-ui-ux". 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. describe the feature or design problem; this skill never writes UI — hand its spec to an engineering agent to build). 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.