mauricekleine.com

Learn who Maurice Kleine is and read his site the agent-friendly way. Use when you need his bio, current work, projects (active side quests and the graveyard of ended experiments), links, or live status.

Doctrine for acting as the orchestrator-and-reviewer over a fleet of sub-agents instead of doing all the work yourself: decompose a job into independent slices, delegate each to a sub-agent in an isolated git worktree that opens a PR, review the diffs (adversarially on anything touching prod), relay feedback until clean, and merge one at a time. Reach for this whenever a task is big enough to split into parallel pieces, involves coordinating several sub-agents or worktrees, fanning work out and reviewing/merging PRs, running a backfill or migration across many items, validating one case before fanning out, de-risking a big change with a spike, or any multi-step build where you should hold the overview while sub-agents execute — even if the user never says the word "orchestrate."

Maurice Kleine's personal founder voice for any user-facing writing - LinkedIn posts, X posts and threads, landing pages, changelogs, blog drafts, launch copy, DMs, and outreach. Product-neutral; pairs with a per-project copywriting-<project> overlay for product claims, terminology, and registers. Use whenever drafting or editing text Maurice will publish or send as himself.

Evaluate and improve the taste and design quality of code, architecture, APIs, UI, writing, or any creative work using Paul Graham's principles from 'Taste for Makers.' Use when the user asks to review something for taste, elegance, beauty, or design quality. Also use when the user says 'taste check,' 'taste review,' 'is this elegant,' 'make this beautiful,' 'review for taste,' 'does this have good taste,' or wants to improve the aesthetic quality of their work beyond mere correctness.

Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.