← Search

Experience First: product principle for Muse agents
Developer tools 🧪 Install ran in our test sandbox · Nov 18, 2026 📌 Pinned version: commit ccb5507
Install test only, on the date shown. This does not guarantee the code is safe.
⚙ Needs: none — this skill is a principle the agent applies…

Experience First: product principle for Muse agents

Choose user delight over implementation convenience — ship fewer polished features over more rough ones; justify every control; prototype before committing

At a glance
What
Choose user delight over implementation convenience — ship fewer polished features over more rough ones; justify every control; prototype before committing
Cost
Free
Needs
none — this skill is a principle the agent applies when product, UX, or feature-scope tradeoffs come up, not software to install
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

Quick answer

Experience First is a free Muse principle from @cursor for product, UX and feature-scope tradeoffs: choose user delight over implementation convenience, ship fewer polished features over more rough ones, justify every feature and option, and prototype in throwaway code before committing. It insists on sweating details like transitions, alignment, spacing, feedback and error states while keeping the core loop tight.

⌁

Install

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

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: none — this skill is a principle the agent applies when product, UX, or feature-scope tradeoffs come up, not software to install Install "Experience First: product principle for Muse agents" for me. It gives my agent @cursor's Experience First principle: when implementation convenience conflicts with user delight, choose delight — justify every feature, control and option; ship less but better; prototype in throwaway code before committing to production; get the details right (transitions, alignment, spacing, feedback, error states); tighten the core loop. IMPORTANT: the repo states no license — fetch from the link only, and reproduce nothing beyond the link. Repository: https://raw.githubusercontent.com/cursor/plugins/ccb5507cec1546dc88135c1139c811e6c59115ba/pstack/skills/principle-experience-first/SKILL.md Pinned version: install the code at commit ccb5507cec1546dc88135c1139c811e6c59115ba 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 "principle-experience-first". 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. nothing — it's a decision principle the agent applies on product/UX tradeoffs). 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 ccb5507 · 2026-10-13
🧪 Install ran in our test sandbox · Nov 18, 2026
👁 Observed during the install test · Nov 18, 2026 : registry.npmjs.org
🔎 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
ccb5507 · 2026-10-13
Sandbox install test
Install ran in our test sandbox · Nov 18, 2026 · Observed during the install test: registry.npmjs.org
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.