How to make Claude better.
A living document I'll read at the start of every Claude session. Edit anything, add anything, and Claude inherits it. Stored locally in your browser; export as JSON when you want to back it up.
★Right now
What I'm working on at this minute. Use it as a handoff to the next device / partner / Claude session. Click Stamp to prepend a timestamp.
00TL;DR
The single page Claude should read first. Keep it under 200 words. Below: the longer index.
01Active projects
What I'm building right now. Drop in URLs + one-liner status so Claude can pick up mid-thread.
?raw=1[§ion=ID] for Claude WebFetch, "Right now" scratchpad, per-section last-edit pills, session-starter prompt builder, offline service worker
- empire-food-catering.pages.dev — real client · awaiting $650 quote signoff
- inkredibletattoosupply.com — real client · live, monthly retainer
- rave-productions.pages.dev — bento services grid recently rebuilt
Add new ones here when they start. Strike them out when they ship.02Inspirations
Sites Claude can WebFetch + analyze before starting visual work. URLs only — Claude does the analysis.
03Style rules
Hard "always / never" rules. Claude should treat these as immutable for the brand.
04Code patterns I want
When Claude writes code for me, default to these shapes.
@theme tokens (not v3 config)
- Motion (formerly Framer Motion) for React animation, not raw GSAP
- GSAP + ScrollTrigger only for scroll-pinned scrub timelines
- Lenis desktop-only (smoothTouch:false, gate on matchMedia("(pointer:fine)"))
- Supabase for backend with VITE_SUPABASE_URL/ANON_KEY env vars
Component patterns:
- Glass primitive for surfaces (backdrop-filter blur)
- Drawer for inline editing (Esc closes, lock body scroll)
- Field for inline-editable text (saves on blur)
- Kicker for section labels (uppercase, tracking-[0.32em])
- StatusPill for state indicators
- KineticNumber for count-up rAF animations
- Empty states: invitation, not "no data"
Naming:
- React components PascalCase, files PascalCase
- CSS uses --color-ink for text (4 shades), --color-pane for surfaces
- Section accents: cyan strategy, amber content, magenta clients, lime missions, lavender inspiration05Mistakes you've made
Claude — don't repeat these. Add new ones as they happen.
Chen & Associates vs Chen <span>&</span> Associates. Always do a full grep after rename, not just pattern match.
- Renamed cards but never created new CF projects — left dead links pointing to heartlands-cards.pages.dev etc. Either rename underlying site OR keep card pointing to existing project.
- Deployed without verification — wrong scroll positions in tests led me to declare chapters 2/3 broken when they actually worked.
- Translate(-50%,-50%) baked into spin keyframes shifted rings off-center. Cleanup unused keyframes after deleting components.
- Framer motion's transform on motion.div clobbers inline style.transform — wrap motion.div inside positioning div, not the other way around.
- Used trademark-conflicting names without IPOS check — FORGE Fitness incident. Always check Singapore IPOS before fictional brand naming.
- Forgot user said "real client" when nuking sites in trademark cleanup. Verify list of real-vs-demo clients before destructive ops.
- Lenis wheelMultiplier > 1.0 + short duration = stuttery scroll. User reported "1% to 10% jumps" on ASTRA. wheelMultiplier:1.15 + duration:0.85 + ease-out cubic amplified each wheel tick into a chunky ramp. Default for cinematic sites: {duration:1.2, easing:t=>Math.min(1,1.001-Math.pow(2,-10*t)), wheelMultiplier:1.0, lerp:0.1, smoothWheel:true, smoothTouch:false}. Don't multiply wheel input unless the user explicitly says scroll feels slow.
- Visual bugs invisible to DOM/state checks. Two real bugs (ASTRA rail tooltip occluding stat content, Handbook toolbar background too transparent) only surfaced when I took screenshots and looked. Lesson: after any UI change, take screenshots at multiple scroll positions on desktop AND mobile. Don't rely solely on opacity/state assertions.06Workflow preferences
How I want Claude to actually behave during work.
codex for design forks (architecture, "this vs that").
- Use agency-craft + distinctive-frontend for premium agency builds.
- Use scroll-story for cinematic landing pages.
Build/deploy:
- Always deploy to Cloudflare Pages on completion.
- Hand back the .pages.dev URL as part of "done".
- For React SPAs, include _redirects: /* /index.html 200.
Communication:
- Singapore English: dollar amounts in SGD, addresses in SG style.
- Don't use emojis in writing unless I do first.
- When listing trade-offs, use a table.
- Keep summary "what shipped" at top, "what's pending" at bottom.Session starter
Type what you want to work on — the prompt below auto-fills with the handbook URL + your "Right now" scratchpad as live context. Paste into a new Claude session.
Tip: each section above has a copy raw link button — gives Claude a URL like ?raw=1§ion=rules for ~80% lighter context when only one section is relevant.