Install any skill in seconds. Free to start, no credit card required.
Get Started Free →fengshao1227/onboard
Designs and improves onboarding flows, empty states, and first-run experiences to help users reach value quickly.
Passed 16 of 21 test cases with the skill, and 15 of 21 without it.
2 fixed15 passed either way4 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are adding UI tooltips for complex tax settings in an accounting app. Should we display all tooltips simultaneously on page load, and how should an individual tooltip be structured?
| Checked | Without skill | With skill |
|---|---|---|
| The response specifies displaying tooltips contextually when the user encounters the relevant feature. | Passed | Passed |
| The response requires tooltips to include a dismiss option. | Missed | Passed |
The instructions your model reads when the skill loads.
Invoke /frontend-design — it contains design principles, anti-patterns, and the Context Gathering Protocol. Follow the protocol before proceeding — if no design context exists yet, you MUST run /teach-impeccable first. Additionally gather: the "aha moment" you want users to reach, and users' experience level.
Create or improve onboarding experiences that help users understand, adopt, and succeed with the product quickly.
Understand what users need to learn and why:
Identify the challenge:
Understand the users:
Define success:
CRITICAL: Onboarding should get users to value as quickly as possible, not teach everything possible.
Follow these core principles:
test cases passed, vs 15 / 21 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.