Prompts that work

Everything in Modus is driven by what you type, which makes prompting a skill worth ten minutes. The pattern behind every recipe here: one intent per message, with the constraint that matters said out loud. Vague in, vague out.

Chats (ideation)

"A launchpad for music NFTs. Assume I know web3 but not the music industry; poke holes in the distribution side."

Tell the partner where your blind spot is and it aims its research there instead of lecturing you on what you know.

"Compare this against how Sound.xyz and Catalog actually work today."

Naming real competitors triggers real lookups, not from-memory takes.

PRD

"Refine Scope: v1 is a single artist, manual payouts, no mobile. Cut everything that doesn't serve the first drop."

The refine flow is at its best with hard exclusions. "Make it better" gives the model nothing to push against.

Design

"Warm, editorial, generous whitespace. Closer to a magazine than a dashboard. One accent color, used only on actions."

Adjectives plus one concrete rule beats a paragraph of vibes. The rule ("accent only on actions") is checkable, so the compliance pass can hold pages to it.

Code

"The tip button: make it full-width on mobile only."

One change, one constraint, then check the preview. Ten small turns beat one ten-part turn: each gets its own checkpoint, so any one of them is trivially reversible.

(with the inspector) "This element: align it with the card above."

Select the element first and "this" means exactly one thing.

Deploy

"Why did the last deploy fail?"

The deploy chat reads the actual deploy state (status, provider, error), so ask it before you go log-diving.

Docs

"Rewrite the README for someone deciding whether to clone this, not someone who already has."

Docs prompts work best when you name the reader.

Token Launcher

"Just pick defaults and take me to the summary."

After you've chosen a preset, this skips the remaining questions and jumps to final approval: the fastest honest path through the interview.