dzhng/skills is a JavaScript project with 630 stars.
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
AI skills for building software factories. My personal library of
domain-agnostic agent skills, reused across every project. Small, composable,
and hackable — works with any harness that supports skills: Claude Code, Codex,
opencode, Cursor, duet, and
70+ others.
npx skills add dzhng/skills
Add --list to pick individual skills, or copy any skills/<category>/<name>/
folder into your harness's skills directory (e.g. .claude/skills/).
Why
Software is moving from tasks to factories: agents that pursue a goal
autonomously until the output can be trusted. The hard part isn't breaking the
goal into tasks — it's breaking it into independently verifiable pieces, and
knowing where the pieces even are.
These skills run that loop. Treat the unknown as fog of war: map the
terrain, carve it into territories that build and verify in isolation, and
recursively re-slice whatever hides more map. And re-planning doesn't stop when
planning ends — the spec is a living document, updated and re-sliced
mid-implementation whenever the work teaches the agent that the plan is stale.
Every piece must prove itself — architecture review, code review, and visual
review against a baseline — before the loop moves on. Each iteration gets less
wrong, until the goal is done.
Proof: one unattended Codex run pursuing a single goal for 1d 16h on top
of these skills, slicing and iterating until done.
How to use
Plan. Ask your agent to /write-spec the goal. It interviews you,
researches the unknowns, and materializes a spec under specs/<feature>/ —
a slice graph where every slice is independently verifiable.
Build. Kick off the loop:
/goal /implement-spec specs/<feature>
Add whatever framing fits: on the xyz branch, or using /codex as the implementer while you stay the parent orchestrator and reviewer.
The rest fires on its own. The spec tells the loop when to call the
other skills — a /review pass at the end of every slice,
/screenshot-critique and /compare-screenshots on anything
visual, /close-spec when the last slice lands — and to update and
re-slice the plan whenever implementation proves it stale. Every skill is
also independently useful: invoke any of them manually whenever you want.
Skills
Engineering — slice, build, verify, repeat
Skill
What it does
explore-unknowns
Walk the user through mapping a task's unknowns quadrant by quadrant — known knowns first, then interviews, reactable artifacts, and blindspot passes — ending with a complete four-quadrant map.
write-spec
Break a large feature into independently verifiable, human-reviewable slices with API seams and playable checkpoints.
implement-spec
Build an existing spec to completion, one reviewable pass at a time, delegating independent slices in parallel.
implement-spec-with-codex
Run implement-spec with Codex writing the code — you orchestrate, integrate, and review every pass.
close-spec
Archive a shipped spec and rewrite it from a build plan into a durable rationale record that points back at the code.
refactor-clean
Refactor by moving ownership to one clean concept instead of layering compatibility sediment beside the problem.
write-tests
Write tests one tracer bullet at a time that pin real behavior — not implementation details, config values, or lucky samples.
audit-performance
Find hot paths that amplify or repeat without progress, rank them by real failure risk, and prefer the smallest bounded fix that preserves healing.
write-docs
Write docs as a glossary of principles and pointers, never a mirror of the code that will rot.
code-review
Audit a diff for stale names, dead references, needless complexity, and comments that narrate instead of explain — ending on a clean/not-clean verdict.
audit-choices
Audit the choices an implementer made, not its diff — a pure, never-blocking audit whose ledger discloses the architecture and decisions made on the user's behalf, reviewed instead of the code.
eli5
Explain a spec or change in plain language without losing precision — the ELI5 register other skills borrow for standalone, walked-scenario explanations.
review
Closeout a finished change as one pass — refactor-clean, then code-review, then write-docs — sequenced into a single verdict.
codex
Use the local Codex CLI as an independent second agent for review and (on explicit ask) delegated implementation.
claude
Use Claude Code (claude -p) as an independent second agent for consultation and (on explicit ask) delegated implementation.
marketing-pages
Rulebook for writing, updating, and auditing marketing pages by page class — campaign landers stay noindexed and unlinked with one CTA; everything else earns its sitemap entry, crawl-rail link, and canonical copy source.
Visual review — never accept visuals on vibes
Skill
What it does
compare-screenshots
Judge which image is less wrong against a target you establish — telemetry to locate divergence, not a baseline match. Ships a reusable diff script.
screenshot-critique
Use an unprimed subagent as a second set of eyes on visual work before accepting it; mandatory before declaring a reported visual bug fixed.
preview-shots
Open a curated set of image shots in one macOS Preview window for the user to eyeball.
Authoring — keep the skills themselves sharp
Skill
What it does
write-skills
Create or revise agent skills: triggers, leading words, progressive disclosure, and the failure modes to prune.
eval-skills
Eval a skill against golden cases — blind runs in fresh subagents, a separate judge, and gap-driven edits.
Graphics
Skill
What it does
renderer
Build, debug, or review WebGPU renderer work — three.js/TSL scene layers, node materials, WGSL passes, depth semantics, and browser-verified visuals.
The most recent commit recorded on dzhng/skills was 2 days ago, based on the GitHub push timestamp. The repository has 42 forks — one of the better signals of community interest.
How many stars does dzhng/skills have?
dzhng/skills has 630 GitHub stars — refresh the page for the live number, or check github.com/dzhng/skills. TopGit mirrors GitHub's count but does not claim minute-by-minute accuracy.
Is dzhng/skills open source?
Yes — dzhng/skills ships under the MIT license, which makes its source code freely readable (and, depending on license terms, forkable and reusable). Source: github.com/dzhng/skills.
What is dzhng/skills?
dzhng/skills (dzhng/skills) is a JavaScript project tracked by TopGit. The repository has 630 GitHub stars at the time of our last sync.
Where do I read more about dzhng/skills?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/dzhng/skills is the definitive source.
Read full README in the tab above.
Is skills worth your time?
ChatGPT, Claude and Perplexity can all read this page. Ask one of them what it makes of skills.
/skills
