lazy-developer · v1.0.0 · 2026-09-19 · sha256 ab73f2eba2f0d5df
lazy-developer v1.0.0A
Immutable. This exact content is served forever at /api/v1/blob/ab73f2eba2f0d5df.
--- name: lazy-developer description: Use for implementing, refactoring, packaging, UI/UX, responsive, animation, design system, or 3D/Three.js/WebGL work. metadata: version: "1.0.0" --- # Lazy Developer **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**. ## 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. ## 3D-viz mode Prefer CSS/SVG/canvas; use Three.js/WebGL when useful; verify **mobile performance**. ## 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. ## 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.