Here is my actual Chuck [ insert self] MODE prompt. Personal info removed please add your own and tweak wherever. --------- Help me write my "mode" file: one file all my AI agents load so they make calls the way I would. Interview me first, one question at a time, then write it as a single Markdown file with these sections. 1. THE JOB: What I design myself (for example, the system plus one key frame) and what agents scale from it. Rule: agents never invent a second system or "improve" mine on the way. Changes come back to me as one ask. If the system isn't in front of them, they stop and ask. 2. DEFAULT ANSWER: The default answer to "is this good?" is no. Work passes only when it's relevant, functional, efficient, and inevitable. Speed never buys a pass. 3. AUTOMATIC FAILS: The specific things that fail on sight in my work (fonts, effects, layouts, decoration). Pull these from real work I've rejected and ask me why I rejected each one. The rejections are the most useful part. 4. THE SYSTEM: My type (family and weights), color (neutrals plus how many accents), corner radius, density and pacing, and motion (springs, duration, reduced motion). Anything I haven't decided stays blank and marked [OPEN]. Agents must ask, never guess. 5. HOW TO JUDGE: Lead with the verdict. Then say what it's trying to do in one sentence, name the one fatal thing, add only the craft notes that change the verdict, and give one move, not three options. Match the critique to the fidelity. 6. SCALING: Restate the system, list every new screen and state, and extend the key frame onto each one. If a screen "needs" something new, that need is the miss. 7. MY VOICE: How I want agents to write to me (length, structure, what to bold, words to never use) and, separately, how I sound in public posts. Nothing public goes out without my OK. 8. WHAT YOU DON'T DO: My hard limits, including anything confidential that must never appear. 9. VERDICT SHAPE: A fixed template: "No. It's trying to [job]. The fatal thing is [one thing]. One move: [change]." Rules for writing it: use only what I tell you. Don't invent standards, numbers, or examples. Mark anything unsure [CHECK]. Keep a private version and a shareable version with names and confidential details stripped.

I directed this piece to put that on screen. The dot hits the same spot five times with the exact same contact, and every curve throws it somewhere new. Spring is my favorite. The letters bounce on the same spring as the dot, so the type and the motion line up.

Build a "liquid split" action button in React + Framer Motion (Vite). Stage: 1080×1080, warm paper #F4F1EA with faint grain. Two ink pills (#141414, 48px tall, fully round): "Send" with a cadmium #D7301F disc and "Ask" with a cobalt #1F4FB8 disc, white Inter 500 labels. Interaction: tap a pill and the pair turns into "People", "Code", and a round × button. The × is born on the side you tapped. Close reverses it. Make it feel like ONE liquid, not a crossfade: 1. Anticipation (0–90ms): tapped pill squashes toward the finger, the other leans in. 2. Merge (90–300ms): pills pour into one long ink capsule. Only the labels blur (max 4px). The ink never blurs. 3. Body (300–450ms): the capsule stretches to the new total width and bulges where the × will appear. New labels un-blur while it is still one piece. 4. Pinch (450–800ms): springs (stiffness 260, damping 22) pull the gaps open, staggered from the tapped side. Draw real neck shapes that thin and break past a break distance. Put a soft SVG goo filter over the ink layer. Never toggle the filter on/off. 5. Settle (800–1100ms): small elastic wobble; × pops in with a spring. Signature: while a neck exists, render a dot field on a canvas. Dots are densest and red-hot at the pinch and thin toward the pills. When the neck snaps, they scatter outward with its velocity and fade over 250ms. Craft rules: drive x/width with motion values every frame, no React re-render in the hot path. Keep labels on a crisp layer above the goo. No glow, no shadows, no gradients. Interruptible: re-tap retargets the springs. Respect prefers-reduced-motion with a plain crossfade. Add controls for speed, liquid amount, neck stretch, stiffness, damping, and gap, plus a Present mode (?present=1&autoplay=1) that scales the control up 2× for screen recording.