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
- 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.
Selected by Skill Harbor — short listing (the repo states no license, so no content is reproduced): @cursor's Experience First principle for when product, UX, or feature-scope tradeoffs come up — choose user delight over implementation convenience, ship fewer polished features over more rough ones, justify every feature and option, prototype in throwaway code before committing, and sweat the details (transitions, alignment, spacing, feedback, error states) while keeping the core loop tight. The "user" is whoever consumes the work — end user, the colleague importing your library, or the engineer maintaining the code next. Honest caveats: a principle, not tooling — nothing to install, nothing to run; the frontmatter sets disable-model-invocation so it guides decisions rather than auto-triggering; 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: 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://github.com/cursor/plugins/blob/main/pstack/skills/principle-experience-first/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 "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.
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.