ui-add-popup
Skill0 starsChanged 6 months agoMITView on GitHub
Add the built-in RobloxUI popup prefab and immediately generate preview artifacts. Use when the user wants to run /ui-add-popup from a Bloxkit repo or project.
In this repository29 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- add-placeSkill
- adopt-projectSkill
- buildSkill
- doctorSkill
- fix-myselfSkill
- new-featureSkill
- new-gameSkill
- new-placeSkill
- persistence-proofSkill
- run-testsSkill
- runtimeSkill
- serveSkill
- setup-new-gameSkill
- setupSkill
- testSkill
- travel-proofSkill
- ui-add-daily-rewardsSkill
- ui-add-hudSkill
- ui-add-inventorySkill
- ui-add-leaderboardSkill
- ui-add-quest-logSkill
- ui-add-settingsSkill
- ui-add-shopSkill
- ui-add-upgrade-menuSkill
- ui-previewSkill
- uiSkill
- upgrade-projectSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use the shared Bloxkit workflow runner instead of rebuilding this flow manually.
- Very specific: line 13
Run node toolkit-v2/scripts/command-runner.mjs /ui-add-popup [--theme simulator] [--prompt "confirm purchase"] with any user arguments …
- Distinctive: line 14
Do not substitute lower-level scripts unless you are debugging the shared workflow.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/ui-add-popup
Use the shared Bloxkit workflow runner instead of rebuilding this flow manually.
Workflow:
- Confirm you are in the current Bloxkit project root.
- Run
node toolkit-v2/scripts/command-runner.mjs /ui-add-popup [--theme simulator] [--prompt "confirm purchase"]with any user arguments filled in. - Do not substitute lower-level scripts unless you are debugging the shared workflow.
- Return the command summary, changed artifacts, and any remaining manual Studio or MCP steps.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.