Conventions

Rules every agent and person follows on every task.

Voice and copy

Never use em dashes in user-facing writing. Use commas or periods.
Nothing that sounds AI-generated. No “delve”, no “elevate”, no breathless marketing filler.
Match each site’s existing voice, sentence length, and person (we/I) when editing client content.
Titles are specific, never generic (“Canvas Embellishment Basics”, not “Video One”).

Secrets live in environment variables and (once adopted) Infisical. Never in code, docs, commits, logs, or chat output.
Known env vars by name: EDITOR_PASSWORD, GITHUB_TOKEN, VERCEL_TOKEN, UMAMI_USERNAME, UMAMI_PASSWORD, EDIT_MODEL, INBOX_URL, SOCIAL_URL, MONEY_URL, TASKS_URL. Porter secrets: PORTER_GH_PAT, VERCEL_TOKEN, UMAMI_USERNAME, UMAMI_PASSWORD.
Never print a token or password, even partially, when debugging.

The console is Vercel-inspired: shadcn/ui, Geist fonts, light and dark mode, data tables over cards for anything enumerable.
Client site edits reuse the site’s own class names and structure. Never invent classes, never write inline styles into ported sites.
Media is never fake. No stock URLs, no placeholder embeds of unrelated content. Reuse the site’s own assets or leave a styled empty container and say what media is needed.

Verify against production before reporting anything as live. Fetch the page, check the API, screenshot the UI.
Finished work ends with the final live link.
Prefer boring reliability over cleverness in anything that touches client production sites.
When the AI creates repeating content on a page, it registers a collection so the content becomes editable. Rickrolls taught us this.
Every ported or newly built site gets Umami tracking before it is called done. See the tracking playbook.

Read the relevant playbook fully before starting. They encode gotchas that cost hours the first time.
Do not widen scope. If a task reveals adjacent problems, report them, do not fix them silently.
All prompts that generate client-facing copy must include the voice rules above.