AI coding rules

Complete the current task with the minimum sufficient change.
## Before editing
- Read the relevant code, tests, and configuration directly. Do not work from search snippets or guesses.
- If the requirement is ambiguous or the premise is unverified, resolve that before building on it.

Cut taglines, helper text and secondary labels. If a screen needs them to make sense, fix the layout.

Read this guide and review my project's CLAUDE.md, AGENTS.md, skills, and saved prompts. Find three kinds of problems: lines that push you to think more, like 'think carefully' or 'take a deep breath'; rules and prompts that hand out tasks one step at a time or don't define what done looks like; and rules that make you stop for confirmation when you don't need to.
For each issue, quote the original instruction, explain its impact, and suggest the smallest change needed. List a…

Read this guide and review my project’s AGENTS.md and Skills. Identify overly broad skill triggers, documents you’re required to read for every task, redundant checks, conflicting instructions, and rules that make you stop for confirmation before the task is complete.
For each issue, quote the original instruction, explain its potential impact, and suggest the smallest change needed. List any proposals involving safety, permission boundaries, or reduced verification separately…

Then review my Claude Code setup against it: my user and project settings, the subagents in ~/.claude/agents and .claude/agents, CLAUDE.md, and the MCP servers I have connected. Find three kinds of problems:
1. A default effort that doesn't fit the work. Use the guide's ladder: low for mechanical edits, medium for well-scoped daily work, high when medium stalls, and xhigh or max only for work where a gain was measured. Flag a default of xhigh or max, or a level I picked for Op…

Set up my Claude Code to match this tree:
1. For the three subagents, reuse fitting ones from ~/.claude/agents and .claude/agents, and propose new ones only for missing roles. Set each to model: opus and effort: medium. Leave any subagent that already sets a different model alone, and list it.
2. Set the main session's default effort to high with effortLevel in ~/.claude/settings.json.

Set up a subagent that only builds progress dashboards:
1. Create dashboard-builder in ~/.claude/agents: model: opus, effort: medium, memory: user. Preload the design skills I have installed (for example impeccable). It can only read and write the .dashboard/ folder and its own memory.
2. The first time, it asks me what style I like: dark or light, dense or airy, and one accent color. It saves my answer to memory…

Use imagegen to reimagine this page, then implement it.

Before you ship a vibe-coded site, have Opus 5.5 send out 5 subagents to check these 20 things, then fix them all in one pass:
Consistent design
- Write a DESIGN.md first, and make every color, font size, spacing and corner radius follow it
- Keep the palette restrained and the type hierarchy clear

Before you ship a vibe-coded site, have Opus 5.5 send out 4 subagents to check these 20 things that slow it down, then fix them all in one pass:
Images and fonts
- Convert every image to WebP or AVIF, sized to how big it actually shows on the page
- Serve big images from Supabase Storage through next/image at the right size. On the Pro plan,…