Menu
SkillsMP has collected 17 skills from jezweb/dotjez. Open a skill to review its source and details.
Showing 17 of 17 collected skills.
Use when planning, to think past the immediate request and find the bigger product hiding inside it, what the users and the business will need that nobody's asked for yet. Produces a north-star vision, not a task list. The expansive counterpart to the…
How to plan and approach a non-trivial build or feature with an agent, before writing phases or code. Covers the Phase-0-refactor catch, thinking in contracts, discovering the data structure from real instances before designing it, writing the proof of done…
Use for an occasional step-back, weekly, at a milestone, or after a big push, NOT every session. A reflection for both the agent and the human: what got done, the patterns worth noticing, what was learned that should change how the work is done, and what to…
Use before calling any visual or rendered output done, a UI, a layout, a generated image, a rendered document, a chart. Render the real thing and look at the actual result (playwright or Chrome screenshot, computer-use, or the project's own render/export…
Use when you want a lightweight, claimable task board that lives in the repo as markdown, for parallel multi-agent work or your own backlog, where a card is a file and the folder it sits in is its status. Covers the folder-board layout, claiming and…
Use after any non-trivial build, before commit or deploy. Convene two or more frontier models from different families and providers to review the change for Critical/High/Medium/Low findings; fix cross-validated Criticals before commit and Highs before…
Use when deciding how to arrange agents for a piece of work: one agent or several, which pattern (single loop, pipeline, routing, parallel, orchestrator-workers, evaluator loop, triage funnel), how to match roles to model temperaments, how to bound a…
Use when setting up an ongoing agent dedicated to a role rather than a one-off task, a webmaster, researcher, bookkeeper, support triager. Covers shaping the persona and its lane, populating a specialist with real reference (not a generic shell), running it…
Use when writing or revising any prompt, a system prompt, an agent brief, an extraction or classification prompt, a sub-agent contract, or when a prompt-driven feature underperforms. Covers the three parts a prompt needs (goal, contract, knowledge), worked…
Use before shipping anything agents or newcomers will read cold: a README, a CLAUDE.md or workspace brief, a skill, a playbook, a template repo, onboarding docs, a production prompt or sub-agent contract. Two moves: audit every claim (derived / checkable /…
Use when prompting an image-generation model: a hero image, icon set, product shot, illustration, OG image, scene, or any generated visual. Covers concrete specifics over quality adjectives, specifying the world not just the subject, describing presence not…
Use when asking a model to read, extract from, measure, count, or make judgements about images: technical drawings and plans, photos, scans, documents, screenshots. Covers what vision models do reliably (locate, read, judge) vs unreliably (measure, count…
Use before relying on any fast-moving fact you might "know" from training, a model ID or its capabilities, an AI or HTTP API shape, a library or framework version (Vite, Astro, React, an SDK), a Cloudflare binding or wrangler config, or an MCP standard. Also…
Use when a role has substantial repeated work one session can't finish (enriching hundreds of records, grinding a backlog, sweeping a large catalogue) AND the work keeps teaching you how to do it better. Covers the tick shape, the separate state files,…
Use when about to delegate a discrete task to a sub-agent, deciding whether to spawn one at all, how much to specify it, and how to keep its work from bloating the main thread. The one-off-task layer below run-a-role-agent. Triggers, "delegate this", "spawn a…
Use before committing to a plan or brief, to stress-test it, surface the unstated assumptions, the unknowns, the scope that will change, and the user/business needs the brief doesn't mention. The adversarial counterpart to imagine, and the planning-time…
Use whenever you're about to state or write a factual claim, a client or product fact, a KB entry, a number, a date, a piece of history, an answer presented as true. Don't write it from memory; verify it against an authoritative source and cite it, or leave…