v1.0.0 to v1.0.0

9 added, 10 removed. Audit A to A.

---

name: lazy-developer

- description: Use for implementing, refactoring, packaging, UI/UX, responsive, animation, design system, or 3D/Three.js/WebGL work.

+ description: Use for implementing, refactoring, packaging, UI/UX, responsive design, animation, design system, 3D/Three.js/WebGL, SEO, and shipping work.

metadata:

version: "1.0.0"

---

# Lazy Developer

- **RESEARCH → UNDERSTAND → PLAN → ACT → OBSERVE → VERIFY → SHIP.** Native systems remain active.

+ RESEARCH → UNDERSTAND → PLAN → ACT → OBSERVE → VERIFY → SHIP. Native systems remain active.

## Core

- Inspect scope, stack, files. For current/external facts, **RESEARCH** first. Define acceptance and the **smallest complete repo-native** change. Never invent APIs, behavior, assets, evidence, or tests; ask only **blocking questions**. Reuse code; trace **source → validation → sink**.

+ Inspect scope, stack, routes, assets, source. RESEARCH current/external facts first. Define the smallest complete repo-native change. Ask blocking questions only. Trace source → validation → sink. Never invent APIs, assets, tests.

- ## UI / UX

- Use LazyDev Personal Pro UI: visual anchor, hierarchy, type, spacing, color roles, components, states, **responsive** behavior, accessibility, motion, and performance. Compile/search the **design system** before UI code; extract patterns, not copies. Reject **anti-patterns**: card soup, pill-everything, gradients/glass, icon piles, fake controls/data, filler, oversized heroes, invented content, guessed assets. For factual/current/history/date-sensitive copy, RESEARCH first and **verify** dates, names, and statistics. Use verified image assets or inline SVG/CSS; never guessed URLs. Prove narrow/medium/wide, overflow, long text, touch, reduced motion, and asset loading.

+ ## UI/UX + Taste

+ Use the built-in design system before code: visual anchor, hierarchy, type, spacing, color roles, components, states, responsive behavior, accessibility, motion, performance. Research references; extract patterns. Reject anti-patterns: card soup, pill-everything, AI gradients, stacked glass, icon piles, fake controls/data, filler, oversized heroes, repeated templates. Verify assets, states, narrow/medium/wide, long text, touch, keyboard, reduced motion, overflow.

## 3D-viz mode

- Prefer CSS/SVG/canvas; use Three.js/WebGL when useful; verify **mobile performance**.

+ For 3D/Three.js/WebGL, RESEARCH a concrete example and current API/version before writing. Trace camera, assets, materials, interaction, lifecycle, draw calls, geometry, DPR, disposal, mobile performance. Verify loading/error/reduced-motion; never invent APIs/assets.

- ## Model-agnostic scaffold

- Non-trivial work: inspect evidence → short plan → one change → observe → targeted **proof** → repair observed failures. When uncertain, read the source of truth and use small evidence-producing steps.

+ ## SEO

+ For SEO, RESEARCH current guidance; inspect rendered HTML. Verify title/meta, canonical, crawlable links, indexability, structured data, sitemap/robots, JS content, image semantics, accessibility, performance. Never keyword-stuff or fabricate claims/markup.

## Verification

- Run the smallest meaningful proof and stop; **skipped ≠ passed**. **Anti-yap:** 75% less prose; preserve exact paths, commands, URLs, versions, errors, negation, and ordering.

+ Run the smallest proof and stop. skipped ≠ passed. UI/3D/SEO requires domain checks or explicit blocked/unavailable status. Anti-yap (~75% less prose): preserve exact paths, commands, URLs, versions, errors, negation, ordering.