Updated 2mo ago
by jsmastery-pro
skills
Agentic Development skills behind the JS Mastery workflow
1.5k GitHub stars (1,490)
+112 in 16 days
| Period | New stars |
|---|---|
| Oct 1 | +3 |
| Oct 2 | +7 |
| Oct 3 | +9 |
| Oct 4 | +8 |
| Oct 5 | +3 |
| Oct 6 | +11 |
| Oct 7 | +7 |
| Oct 8 | +16 |
| Oct 9 | +9 |
| Oct 10 | +2 |
| Oct 11 | +2 |
| Oct 12 | +1 |
| Oct 13 | +6 |
| Oct 14 | +8 |
| Oct 15 | +12 |
| Oct 16 | +8 |
- 9 skills (9 skills found in its SKILL.md files)
- 296 forks (296 forks)
- 2mo ago last update (Last updated 2mo ago)
Install
Skills CLI
npx skills add jsmastery-pro/skills
Asks which skills and agents to install. Just one: npx skills add jsmastery-pro/skills --skill architect — add -g for every project.
Claude Code
git clone https://github.com/jsmastery-pro/skillscp -r "skills/skills/architect" ~/.claude/skills/
Copies the architect skill into ~/.claude/skills/ for every project (use .claude/skills/ for one project). Repeat for the other skills listed below.
Plugin
/plugin marketplace add jsmastery-pro/skills
Run inside Claude Code if the repository ships a plugin marketplace, then pick plugins from /plugin.
Skills can run code on your machine — read the SKILL.md first.
What it does
In the author's own words, from each skill's SKILL.md.
-
architect
Run /architect when choosing between approaches, designing a feature or page, picking a tech stack, or when /develop says a decision is owed, anytime a load bearing technical decision is unmade. Asks deep questions, recommends an answer, and writes a build spec to docs/specs/. Owns all spec files.
skills/architect/SKILL.md on GitHub (opens in a new tab) -
audit
Run /audit on a greenfield project, an existing codebase with missing docs, or one area (/audit src/auth) to bootstrap the project's AI context, the AGENTS.md files every later skill reads. Writes tool agnostic AGENTS.md plus thin CLAUDE.md pointers, adding only what is missing; never overwrites curated content.
skills/audit/SKILL.md on GitHub (opens in a new tab) -
check
Confirm a change before merge. `/check verify` drives the real app to prove behavior against the spec (every acceptance criterion met, every surface built). `/check review` runs a senior code review on a fresh model, one that did not write the code. Verify after /develop, review before a PR. Writes to docs/reviews/, never edits code.
skills/check/SKILL.md on GitHub (opens in a new tab) -
debug
Run /debug to find and fix a bug's root cause: a test failing for an unclear reason, /check verify finding a failure, or behavior being wrong. Runs a reproduce, localize, hypothesize, test, fix, verify loop, makes the minimal fix, and hands a regression test to /test. No features, no extra refactors.
skills/debug/SKILL.md on GitHub (opens in a new tab) -
develop
Run /develop to build a feature, UI or backend, from an approved design, a page, component, API, service, or data slice. If something load bearing is undecided and no spec records it, it stops and routes you to /architect; otherwise it reads the spec plus AGENTS.md, builds, and advances the scope.
skills/develop/SKILL.md on GitHub (opens in a new tab) -
document
Run /document `pr` | `changelog` | `release-note` | `postmortem` (or let it ask) to write the human facing prose about a change. Drafts from the real commits and diff, writing to the right place. Does not write code, tests, or specs.
skills/document/SKILL.md on GitHub (opens in a new tab) -
scope
Run /scope to turn a product idea into a living, coarse scope in docs/scope/ and keep it current: plan a new product, plan the next slice, enroll one named feature, or run with no argument to reconcile after shipping and queue what is next. Seeds WHAT to build; /architect designs, /develop builds.
skills/scope/SKILL.md on GitHub (opens in a new tab) -
sync
Run /sync as the last step after a change is complete, around merge, to keep durable knowledge current. Updates root and nested AGENTS.md, reconciles the scope from repo evidence, and flags specs the change made stale. Surgical edits only: it adds lines, and rewrites single lines it owns. Never a whole section, never curated prose.
skills/sync/SKILL.md on GitHub (opens in a new tab) -
test
Run /test to write a test suite for code you just built or changed, after implementing a feature, route, or fix. Targets uncommitted changes automatically, reads test preferences.json for your framework (asks and saves it if absent), and picks the right strategy per file: happy path, edge cases, error states, accessibility.
skills/test/SKILL.md on GitHub (opens in a new tab)
No skill matches that filter.
Review before you install
A skill is a set of instructions and scripts your agent will follow, and it can run code on your machine. Read the SKILL.md and any scripts first — this listing is not a security review.