Claude skills and agent skills

dzhngSkill

audit-agents

dzhng/jevgrep/.agents/skills/audit-agents/SKILL.md

Audit or rewrite AGENTS.md so it holds only lasting principles. Run it only when the user asks for it by name; never invoke it on your own.

dzhngSkill

audit-choices

dzhng/jevgrep/.agents/skills/audit-choices/SKILL.md

Audit the choices an implementing agent made, not its diff — a pure decision audit that traces the session's history into a choices ledger, changes no code, and never blocks an unsupervised run. Working code still embeds architecture the user never chose; surface it because future work inherits it. Use when the user wants to review the decisions the AI made on their behalf, before merging or committing AI-implemented work, when integrating a delegated subagent's pass, or when a fix "works" but might be a point fix.

dzhngSkill

audit-performance

dzhng/jevgrep/.agents/skills/audit-performance/SKILL.md

Audit and prioritize performance work through bounded-work and forward-progress checks. Use when asked to find performance issues, investigate freezes/500s/OOMs, review retries or polling for no-progress loops, rank a performance backlog, or implement the next simple performance fixes.

dzhngSkill

audit-tests

dzhng/jevgrep/.agents/skills/audit-tests/SKILL.md

Audit whether tests earn their maintenance cost and which suite owns each contract. Use when pruning redundant tests, investigating implementation coupling or test-only production hooks, reviewing the value of proposed coverage, or auditing an entire subsystem. Use write-tests to implement the resulting test changes.

dzhngSkill

auto-research

dzhng/jevgrep/.agents/skills/auto-research/SKILL.md

Run fast, progressive experiments to map tunable parameters and their effects. Use when optimizing code, prompts, configurations, or other artifacts against a goal or benchmark, or when a long research run needs a planned hypothesis queue, focused trials, and durable findings.

dzhngSkill

claude

dzhng/jevgrep/.agents/skills/claude/SKILL.md

Use Claude Code as an independent `claude -p` subagent when the user explicitly asks for Claude, wants a second-agent opinion from Claude, or asks to delegate a well-scoped task to Claude. Supports selecting `--model` and thinking/effort level with defaults of the current `opus` alias and `high`.

Often used withcompare-screenshots·eval-skills·write-skills

dzhngSkill

close-spec

dzhng/jevgrep/.agents/skills/close-spec/SKILL.md

When a spec under specs/<feature>/ is done shipping (a write-spec build, or any planned task that produced a spec), archive it to specs/done/ and rewrite it from a build-plan into a durable rationale — the why, the principles, the invariants — pointing back to the real code for the how. Use when implementation has landed and the plan no longer matches what shipped, or the user says a feature/spec is finished. Pairs with [write-spec](../write-spec/SKILL.md) (the plan this closes) and [review](../review/SKILL.md) (run before closing).

dzhngSkill

code-review

dzhng/jevgrep/.agents/skills/code-review/SKILL.md

Review changed code for naming, stale references, unnecessary complexity, and comment quality. Use after completing implementation work, before committing, or when the user asks to review or audit code.

Often used withadd-new-model

dzhngSkill

codex

dzhng/jevgrep/.agents/skills/codex/SKILL.md

Use the local Codex CLI as an independent second agent. Two branches — (1) proactively run `codex review` for a second opinion after completing a substantive change, before presenting it as done or committing; (2) delegate a well-defined implementation task via `codex exec`, ONLY when the user explicitly asks for Codex to do it. Also covers how to prompt Codex.

Often used withcompare-screenshots·ios-sync·minecraft-modpack-server

dzhngSkill

compare-screenshots

dzhng/jevgrep/.agents/skills/compare-screenshots/SKILL.md

Compare screenshots against the intended design, distinguishing approved references from historical baselines. Use for iterative implementation matching, before/after visual review, objective image telemetry, or checking a lone capture for flat, empty, or badly framed content.

dzhngSkill

design-with-images

dzhng/jevgrep/.agents/skills/design-with-images/SKILL.md

Explore UI and visual design with image generation, then iterate the real implementation against the user-selected concept. Use when brainstorming visual directions, offering mockup variants, or implementing an approved generated design; do not stop at the mockups or the first code approximation.

dzhngSkill

eli5

dzhng/jevgrep/.agents/skills/eli5/SKILL.md

Explain a technical spec or proposed change in plain language: what problem it solves, how the solution works, and every schema change.

Often used withcompare-screenshots

dzhngSkill

eval-skills

dzhng/jevgrep/.agents/skills/eval-skills/SKILL.md

Eval and improve a skill against golden cases — run the target skill blind in a fresh, context-free subagent on each example input, grade the artifact against the expected outcome, and let the gaps drive the edits. Use when the user wants to test/eval/improve/harden a skill, says "this skill keeps producing X / keeps missing Y", or hands a skill plus example input→expected-output pairs. Pairs with [write-skills](../write-skills/SKILL.md) (the authoring principles every fix obeys).

Often used withcompare-screenshots·write-skills

dzhngSkill

explore-unknowns

dzhng/jevgrep/.agents/skills/explore-unknowns/SKILL.md

Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the codebase or domain is unfamiliar, the user will "know it when they see it", a reference implementation must be understood before porting, mid-build deviations from the plan need capturing, or a finished change needs buy-in or verified understanding before merge. Pairs with [write-spec](../write-spec/SKILL.md) — walk the quadrants to burn off fog before slicing, and feed the finished map into the spec.

dzhngSkill

handoff-spec

dzhng/jevgrep/.agents/skills/handoff-spec/SKILL.md

Hand a spec that is mid-implementation to another machine or another agent.

dzhngSkill

implement-spec

dzhng/jevgrep/.agents/skills/implement-spec/SKILL.md

Implement an existing spec through committed passes. Use for long or multi-pass specs that need maintenance checkpoints to periodically clean code, handoffs, priorities, and plan bloat before drift accumulates.

dzhngSkill

implement-spec-with-codex

dzhng/jevgrep/.agents/skills/implement-spec-with-codex/SKILL.md

Run [implement-spec](../implement-spec/SKILL.md) with Codex doing the implementation passes while you orchestrate, integrate, and review. Use when the user asks to implement a spec with Codex, or to run implement-spec with Codex as the implementer.

dzhngSkill

jevgrep

dzhng/jevgrep/.agents/skills/jevgrep/SKILL.md

Use for questions about how, why, or where behavior works in a repository, including questions that name a function or setting. Start behavioral discovery with jg before broad text searches or git history. When delegating repository discovery, instruct the subagent to start with jg. Jevgrep returns relevant files and source excerpts. For exact symbol definitions, string matches, or filenames, use grep or file search instead.

No other project uses it yet

dzhngSkill

launch-video

dzhng/jevgrep/.agents/skills/launch-video/SKILL.md

Make a showreel-grade motion-graphics launch video, with music, that introduces a CLI, library, or product from its repo. Use when asked for a launch, promo, sizzle, or showreel video, an animated intro for a project, or a video to post on X/social.

dzhngSkill

marketing-pages

dzhng/jevgrep/.agents/skills/marketing-pages/SKILL.md

Best-practice rulebook for a marketing site's pages, organized by page class — campaign landers, product pages, programmatic SEO trees, editorial. Use when writing or updating a landing/marketing page, wiring a campaign lander to an attribution identifier, changing site-wide nav/footer links, touching sitemap/robots/agent-readable surfaces, or auditing a public site's indexing, reachability, and conversion setup.