Rei: Prompt Compiler & Linter
Most AI conversations follow the same script: vague prompt, wrong answer, correction, another correction, until you get what you wanted by trial and error. Rei makes you think before you send. Three fields, real-time compilation, a quality score, and a list of everything you forgot to mention. Fewer follow-ups, less time negotiating with a machine. It runs locally and has no submit button: it compiles as you type.
Task & Context
Explain to me the practices, beliefs, and life views of a craftsman shown in the Jiro Dreams of Sushi film, and how these can be applied to regular design work.
Persona
Copywriter who used to write for a think tank with strong opinions
Constraints
Condensed and actionable text, no emojis.
You are a copywriter who used to write for a think tank with strong opinions. Your task is to explain the practices, beliefs, and life views of a craftsman featured in the film Jiro Dreams of Sushi, and subsequently detail how these philosophies can be applied to regular, modern design work. Please ensure the resulting text is condensed and highly actionable, containing no emojis.
- Consider explicitly asking the AI to organize the output into distinct sections (e.g., 'Craftsman's Philosophy' and 'Design Application') to improve readability.
- Consider adding a specific length or structural requirement for the output to further guide the AI's response.
- Considering the 'think tank' background, prompting for a specific tone (e.g., intellectual, didactic, or persuasive) might refine the output.
- Designer who studied film before they studied software
- Product manager who keeps a list of features they’re proud they cut
- Researcher who watches people use things rather than asking them
- Hostage negotiator who facilitates product workshops now
- Strategist who works from evidence
- Copywriter who came from stand-up comedy
- Product manager who used to write code
- Editor with a preference for short sentences
- Bullshit-agnostic designer
- Theatre dramaturg now working in product strategy
- Strategist who reads more philosophy than business books
- Product manager who has killed more features than they’ve launched
- Researcher who came from academic ethnography
- Copywriter who used to write for a think tank with strong opinions
- Therapist who has read too many product books
- Designer who reads novels instead of design books
- Sceptical product manager
- Journalist who covers tech and is mildly disillusioned
- Strategist who keeps a private list of frameworks that didn’t work
- Critic who writes about design for a small audience and consults on the side
- Product manager who writes specs as if they were short stories
- Editor who keeps a list of words they will not use
- Designer who refuses to call them “users”
- Anthropologist embedded in a software team
- Copywriter who came from investigative journalism and never lost the habit
- Product manager who learned the trade in a failing startup
- Researcher who used to write travel journalism
- Cognitive scientist who does decision design
- Strategist who has worked agency-side and client-side and prefers neither
- Designer who has shipped enough to know what survives
- Game theorist who ended up in product management
- Curator who has started consulting for design teams
- Product manager who started as a designer and never quite let go
Copywriter who used to write for a think tank with strong opinions