Prompts we have actually used
Every record is one markdown file: the prompt verbatim, the model and effort it ran at, and what it produced. Captured at generation time, not reconstructed afterwards — so the result line can be trusted.
Motion craft standard — reference, not prompt
# Motion notes — the standard this asset should hit Written for whoever refines RAIL STORE. These are the things that separate a correct implementation from one that feels expensive. Everything here is a judgement call, so disagree where you have a better argu
→ Handed alongside motion work. The house timing bands and the cheap/expensive lists are what models actually absorb.
Paired front + profile product views (matched set)
The reference image shows a garment hanging on a hanger, photographed from the front. Show the EXACT SAME garment — identical colour, identical fabric, identical hanger, identical wall, identical lighting, identical cast-shadow direction and camera height — bu
→ Third pass on a 10-product set. Pass 1 drifted to three-quarter; pass 2 over-corrected to thin slivers; this one reads correctly.
Refinement work order for a strong model
# Work order — RAIL STORE: assessment + premiere-quality refinement pass Adopt the perspective of a senior design engineer and creative director while working through this. The brief is deliberately blunt about what is wrong; please be equally blunt back in yo
→ Produced a genuinely sharp critique that found six real defects, then fixed them. Cost: one clean run.
Programmatic typeface with Yoruba diacritic coverage
You are a type designer working programmatically. Work in your current working directory. If you find you cannot write files for any reason, stop and report that rather than attempting any workaround. --- ## Where we are `vale-v2/` in this directory is your pr
→ Closrd the accented/diacritic gap on the custom face, including the mandatory Yoruba dot-below set and its tone-marked combinations.
Re-time a finished film and replace one sequence
You are revising a finished motion graphic. Work in your current working directory. If you find you cannot write files for any reason, stop and report that rather than attempting any workaround. --- THEN the task: REVISE the finished 15-second Nazadi teaser in
→ Extended 15s to 21s by re-timing rather than stretching, with the ball pit replaced by a slow physical assembly.
Deep synthesis: patterns, gaps and openings
I need you to do deep synthesis analysis. Read the file at /home/ubuntu/oracle_research/fmist-research-raw.md for the raw data. Then produce a strategic analysis document. Read that file now, then produce the following: Output a structured document with these
→ Strategic analysis of FMIST used for a partnership approach. The forced five-pattern structure is what made it usable.
Client-feedback rebuild with a locked palette
You are the heavy design and implementation model for the Ukoni rebuild (Nigerian restaurant, Asaba, Delta State). Brand name is ONLY "Ukoni — On Point Food, Asaba"; never say "Ukoni African Grill". You are fixing a real client review: D O said the current bui
→ Rebuilt to a "warm grill-house" direction; moved the client off the rejected moody build. Palette proved across hero, menu and footer.
Branded logo exploration sheet (flat vector, one ink)
Create a rigorous flat-vector logo exploration sheet for DR. ADAEZE OREH, a Nigerian physician, public-health leader, health-policy executive and universal-healthcare advocate. Evolve the supplied existing AO monogram rather than discarding its recognition. Co
→ Three construction-sheet concepts; "Civic Bridge" selected by the client. The negation list is the reusable part.
Codex build prompt
# Codex Build Prompt Read the vision and architecture docs first. Implement: - Route-safe page scaffolds - Typed project ingestion - Reusable layout and portfolio primitives - Preview-ready detail pages - Cloudflare-friendly build conventions Do not assume bac
→ Carried over from menashi-design/docs/prompts. Model and outcome unrecorded — verify before reuse.
Codex component implementation
# Codex Component Implementation Prompt When refining a component: - Keep the component boundary stable unless the data contract is wrong - Preserve reduced-motion behavior - Favor content-driven rendering over hardcoded strings - Use Tailwind and existing tok
→ Carried over from menashi-design/docs/prompts. Model and outcome unrecorded — verify before reuse.
Codex system prompt
# Codex System Prompt Implement production-ready structure for Menashi Design while preserving the repo architecture, typed content model, and route stability. Prefer composable primitives and avoid destructive refactors that would break Antigravity-owned UI l
→ Carried over from menashi-design/docs/prompts. Model and outcome unrecorded — verify before reuse.
Component generation (Antigravity)
# Antigravity Component Generation When generating UI directions: - Treat `src/components/layout`, `src/components/hero`, `src/components/portfolio`, and `src/components/marketing` as the main extension points - Prefer replacing placeholder internals over chan
→ Carried over from menashi-design/docs/prompts. Model and outcome unrecorded — verify before reuse.
Opus UX critic
# Opus UX Critic Review proposed Menashi Design UI work for: - Brand fidelity - Clarity of hierarchy - Conversion and inquiry path strength - Preview discoverability - Mobile restraint - Whether motion improves comprehension Reject work that feels template-dri
→ Carried over from menashi-design/docs/prompts. Model and outcome unrecorded — verify before reuse.
UI direction (Antigravity)
# Antigravity UI Direction Design the interface for `design.menashiconsulting.com` as the creative showcase arm of Menashi. ## Requirements - Preserve the existing Next.js route and component structure - Use the content model in `src/content/projects/` - Home
→ Carried over from menashi-design/docs/prompts. Model and outcome unrecorded — verify before reuse.
Nothing matches that.