← Search

Locked design language + buildable UI/UX spec, no AI slop
Design 🧪 Install ran in our test sandbox · Nov 11, 2026 📌 Pinned version: commit b3e5e33
Install test only, on the date shown. This does not guarantee the code is safe.
⚙ Needs: a feature, screen…

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

At a glance
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.

Version:

Quick answer

Locked design language is a free design-spec skill with rules, not an skill, that never writes production UI. Its workflow covers discovery and inputs, inspiration intake without cloning, design reading and aesthetic direction committing to one named direction from an anti-slop menu, locking the identity in DESIGN.md, and handing an agent a buildable spec, while banning AI slop by name.

⌁

Install

Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit b3e5e33

Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. 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://raw.githubusercontent.com/ulpi-io/skills/b3e5e33424cfcccdbc0468fb66f06bb56f4e2a1f/frontend-design-ui-ux/SKILL.md Pinned version: install the code at commit b3e5e33424cfcccdbc0468fb66f06bb56f4e2a1f exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 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.

🔒 Security, provenance and what this touches
🧭 What this touches
Based on the install prompt we scanned, this skill does not run commands, make third-party network calls, install packages, write files, or ask for API keys.
Install prompt analysis · 2026-10-13
🔒 Security and provenance
📌 Pinned version: commit b3e5e33 · 2026-10-13
🧪 Install ran in our test sandbox · Nov 11, 2026
👁 Observed during the install test · Nov 11, 2026 : no network contact
🔎 Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

✓

Verification certificate

Dated facts about what was checked for this listing, and how. This is not a safety certification.

Pinned version
b3e5e33 · 2026-10-13
Sandbox install test
Install ran in our test sandbox · Nov 11, 2026
Creator identity
Not verified
Fingerprint watch
Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Install prompt analysis
2026-10-13 : No commands, network calls, packages, file writes or API keys detected.

Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify

?

Questions

How do I install a skill?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill 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 skill before installing it.