Issue
One job, one worklog.
Put the PR, preview, screenshots, checks, decisions, and blockers on the issue.
Howard onboarding
Repo access gets you into the work. Linear tells you what matters. UAT is where we prove it.
Linear
Issue
Put the PR, preview, screenshots, checks, decisions, and blockers on the issue.
Project
PowerAdvice launch work is in LONG, under the current launch, content, redirects, and analytics projects.
Ask
If your agent needs a maintainer action, tag @Keith with the exact command, error, and next decision.
Your first tickets
Environments
Setup, lint, tests, docs, UI work, optional anonymous local Convex.
Hosted CMS, UAT data, UAT MCP, PR confidence before staging.
Production-like checks after UAT. Use only when the ticket says staging.
No production deploys, secrets, Cloudflare, or Convex dashboard work.
Three ways to work
Best for UI PRs against real UAT data. Uses public browser env, not secret keys.
npm run dev
Best for cold start and PR confidence. Run check:external before opening a PR.
npm run contributor:setup
MCP setup
Project work
Read assigned tickets, post worklogs, tag Keith, and keep blocker status out in the open.
Coordination
Use the workstream or DM context for quick handoffs, then move decisions back to Linear.
CMS
Open CMS, click MCP setup, choose UAT or Staging, then copy OAuth config or generate a personal token.
https://cms-mcp-uat.poweradvice.com/mcp
https://cms-mcp-staging.poweradvice.com/mcp
What good looks like
Branch from origin/uat, include the Linear ID, open the PR into uat.
Use the PR preview for unmerged UI work. Do not use staging as a preview substitute.
Hermes/Codex, DeepSeek, and Claude Code are fine. The output is PR plus Linear proof.
No raw Clerk secrets, Convex deploy keys, Cloudflare tokens, or production authority.