Point at taste
Links, screenshots and recordings beat adjectives. Then give the feeling one word.
The way Caleb Peterson builds games and products with Claude (MiniRush, Action Order, YardCheck, PitchAside), packaged as skills your AI follows and a library of design resources it can search.
Taken from ~900 of Caleb's own prompts across 17 shipped projects. No theory, just what worked.
Links, screenshots and recordings beat adjectives. Then give the feeling one word.
New product? A detailed PRD and milestones first, then build M1, M2, M3.
One slice at a time, each one something you can open and use.
Never judge from the code. Open it on the screens your users have: phone, laptop, in-app browser, a game pad.
What you saw, where, on what, and what you wanted. Hold the AI to a senior bar. Ask for options, then pick.
Small releases, real users, their feedback in the next prompt. Park what can wait, out loud.
Paste these into Claude Code, then restart. The skills kick in on their own when you ask for things.
/plugin marketplace add https://learn.calbridgedigitallabs.xyz/marketplace.json/plugin install almighty-prompter@almighty-prompterAdd this server URL in your app's MCP or connector settings to search the resources and skills library.
https://learn.calbridgedigitallabs.xyz/mcpYour AI searches a curated library of inspiration and assets, and pulls extra skills only when a task needs them.