nelsonwerd
- 6 skills
- 0 followers
- 4 days ago last updated
- ▌ Art Direction · nelsonwerd bundleCommit to ONE governing art direction for anything visual — app, website, game, dashboard, poster, brand, data-viz, deck, email, motion piece — via a disciplined diagnose → candidates → independent panel → COMMIT → govern process, and produce one durable ART_DIRECTION.md: a short constitutional brief (a world-with-physics idea + a membership test, a named material, palette-as-law, one depth model, type roles, an emphasis budget over a quiet baseline, quantified restraint, one earned climactic moment, provenance) that pre-answers every later visual decision — then govern execution with fidelity critics who are never allowed to add. It states its honest bounds: it guarantees a governed, coherent direction, not a beautiful one — taste stays human-gated, market appeal out of scope. ALWAYS invoke when the user says any of "art direction", "design direction", "visual identity", "design language", "make it cohesive", "commit to a style", "it looks tacky/generic/AI-generated", "redesign the look", or "style guide / a
- ▌ Audit And Fix · nelsonwerd bundleAudit an existing codebase, then autonomously implement the fixes it judges worth making against your next goal — composing deep-dive → triage → prompt-pack → build-loop to turn "here's what's wrong" into verified, receipted local commits + an honest ledger. ALWAYS invoke when the user says any of "audit this repo and fix what you find", "audit and edit", "deep dive then fix the bugs", "implement the audit's recommendations", "plan and execute these fixes", or "autopilot this repo but skip the ideation". It composes those skills, never reimplementing them. Honest bounds: a receipt records what ran, it never proves correctness; the deep-dive→triage→pack half is proven, the build-loop seam is not; local commits only, never push/merge/tag/publish. Do NOT use to audit with no intent to change (deep-dive), for a change you already know you want (prompt-pack + build-loop), for a new idea with no codebase (autopilot), or for feature work — it fixes what the audit found, nothing more.
- ▌ Prompt Pack · nelsonwerd bundleAuthor and execute "prompt packs" — a big job broken into a sequence of self-contained, independently-shippable prompts, each run in its own fresh chat so a single change never dies to a context/token limit. Also writes paste-ready handoff briefings to resume a dying chat or relay work to another tool (e.g. Codex). ALWAYS invoke when the user says any of "make a prompt pack", "turn this into prompts", "break this into phases", "prompts I can run in separate chats", "I'm running out of tokens/context", "write me a handoff", "a prompt I can paste into a new chat", "this is too big for one chat", "build plan I can hand off", or "execute Pxx / phase X from the pack". Also invoke proactively when a requested change is too large or too risky to finish safely in one session and should be decomposed into ordered, verifiable steps.
- ▌ Build Loop · nelsonwerd bundleDrive a build to actually-works, near-finish-line craft by looping build → see → exercise → check → critique → rebuild over the agent's existing tools (bash build/test, headless screenshot + vision, Playwright, axe/Lighthouse) until acceptance criteria pass or an explicit stop-condition fires — no infinite thrash. ALWAYS invoke when the user says any of "tighten this build", "iterate until it passes", "self-verify the UI", "make it actually work, not just compile", "loop until the core flows pass", or "drive this to near-finish-line". Also invoke proactively after a scaffold or feature lands and before handing a draft to a human. Composition-first over existing tools, not a new program; it states its own honest bounds — objective craft only, taste self-graded, ~80% ceiling, market validation out of scope. Do NOT use to decide WHAT to build (that's ideate) or whether a design/strategy is sound (deep-dive).
- ▌ Deep Dive · nelsonwerd bundleRigorous multi-agent deep-dive analysis for complex investigative tasks — auditing codebases, evaluating strategies or systems, validating designs, doing open-ended research. Deploys 4–6 specialist agents in parallel across distinct lanes, then synthesis, then adversarial red-team review, then optional patching — producing structured markdown research files plus a plain-English executive briefing with honest 1–10 confidence ratings. ALWAYS invoke when the user says any of "deep dive", "thorough audit", "rigorous analysis", "comprehensive review", "audit this codebase", "analyze the strategy", "evaluate this design", "review this thoroughly", or "research deep dive". Also invoke proactively for any open-ended investigative task involving a codebase, strategy, system design, or research question that warrants 30+ minutes of structured analysis — even when the user doesn't use these exact phrases.
- ▌ Ideate · nelsonwerd bundleTake a fuzzy idea (or an existing thing you want to improve) through a disciplined funnel — explore → pressure-test → converge — and produce one living CONCEPT_BRIEF.md: a locked concept + phased roadmap. Acts as a blunt, honest co-founder (permission to overrule you), forces a success metric and a kill criterion before any roadmap, and hands off cleanly to the prompt-pack skill for building. ALWAYS invoke when the user says any of "help me figure out what to build", "I have an idea for…", "is this idea any good", "pressure-test this idea", "should I build / should I rebuild X", "evaluate whether my app/idea is worth building", "where are we really at", "is this idea or app worth pursuing", "iron out / scope / spec this concept", or "turn my idea into a plan/roadmap". Also invoke proactively when someone is reasoning about WHAT to build or WHETHER an idea is worth it — before any code or prompt pack exists.