Skip to main content
jsmastery-pro
GitHub creator profile

jsmastery-pro

Repository-level view of 25 collected skills across 5 GitHub repositories.

skills collected
25
repositories
5
updated
Aug 15, 2026
repository explorer

Repositories and representative skills

develop
software-developers

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…

Jul 29, 2026
architect
software-developers

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…

Jul 28, 2026
scope
software-developers

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…

Jul 28, 2026
sync
software-developers

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…

Jul 28, 2026
audit
software-developers

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…

Jul 28, 2026
check
software-quality-assurance-analysts-and-testers

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…

Jul 28, 2026
test
software-quality-assurance-analysts-and-testers

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…

Jul 28, 2026
debug
software-developers

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…

Jul 28, 2026
Showing 8 of 9 collected skills.
architect
software-developers

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…

Jul 9, 2026
audit
software-developers

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…

Jul 9, 2026
check
software-quality-assurance-analysts-and-testers

Run /check before merge to confirm a change is sound. Two modes: `/check verify` drives the real app and proves behavior against the spec (every acceptance criterion met, every specced surface built); `/check review` runs a senior code review on a different…

Jul 9, 2026
develop
software-developers

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 ADR records it, it stops and routes you to /architect; otherwise it reads the ADR plus…

Jul 9, 2026
scope
project-management-specialists

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…

Jul 9, 2026
sync
software-developers

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 ADRs the change made stale. Surgical, additive edits only.

Jul 9, 2026
test
software-quality-assurance-analysts-and-testers

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…

Jul 9, 2026
document
software-developers

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 ADRs.

Jul 9, 2026
Showing 8 of 9 collected skills.
Showing 5 of 5 repositories
All repositories loaded