最近新增
刚加入收藏的新技能，抢先试用。
lib-publish-ready
osdlc
Audit one library package for a first public release. Produces a readiness report (every quality-bar row with evidence and a verdict: pass, gap, blocker, n/a or owner), the evidence for the name, worthwhile, stable, home and API gates, an inventory of the public API, the first public version, a sanitized CHANGELOG draft, owner questions with a recommendation each, and a fix list whose items are tagged safe or needs-decision. Reads the package; never writes inside it. Use it before publishing a library to a public registry such as crates.io or npm, or to re-audit after fixes.
explore-codebase
osdlc
Systematic method for understanding an unfamiliar codebase: getting oriented in a new repo, locating where something is implemented, tracing how a feature or request flows end to end, and building an accurate mental model before answering questions or making changes. Use whenever you're dropped into a repo or the user asks things like "how does X work here", "where is Y handled", "how is this project structured", "help me understand this codebase", "onboard me to this code", "find where Z is implemented", or "explore this repo and write up notes" — or before editing code you haven't read yet. Can optionally save the resulting map as a markdown file, a linked Obsidian-style vault, or a self-contained HTML page carrying diagrams of the structure it found.
explain
osdlc
Explain one thing as a parley document with no questions: the subject as typed blocks with numbered nodes anchored to the exact text, a walkthrough the reader comments on. Domains are notes beside this skill (sql today). Then hand it to parley. Use it when the reader needs to understand something, not decide something.
discuss
osdlc
Propose one solution as a parley document that ends in a decision: the problem, the solution as typed blocks, and a question with a recommendation for every trade-off the reviewer must ratify, so the page can be approved or sent back. Domains are notes beside this skill (sql and ui). Then hand it to parley. Use it when the reader must decide.
decision-make
osdlc
Make one decision in the open: state the question and its forcing drivers, research the facts and the prior art it rests on, write the options with consequences, choose with criteria written first, and record what would reopen it. Use it whenever a choice will constrain later work.
comment-review
osdlc
"Review the comments in a diff or a subtree and minimize them against the expression ladder: a fact belongs first in the identifier, then in the signature and types, then in the declaration's doc annotation, and only when none of those can carry it does it earn an inline comment. Deletes comments that restate the code, moves facts down the ladder, tightens what survives to one short literal statement, strips volatile project state, and replaces duplicated prose with a reference to one canonical home. Invoke for \"review the comments\", \"too many comments\", \"comment cleanup\", or as the comment pass on a branch before review."
collaborate
osdlc
Co-edit a markdown document the user has open and is typing in. Read the document, find @agent markers, do the work each one asks for, then present every proposed change in chat and get approval before writing anything. Use when the user points at a markdown file containing @agent markers, asks you to fill in or answer parts of a doc you are both working on, or says to collaborate on / work through a document together. Exists to keep writes from clobbering content the user is editing live.
code-review
osdlc
"Review a change for correctness bugs and report concrete findings with a fix for each. The rubric other reviewing skills embed: what to read, what to look for, what to skip, and how to write a finding."
nx-import
jumbleknot
Import, merge, or combine repositories into an Nx workspace using nx import. USE WHEN the user asks to adopt Nx across repos, move projects into a monorepo, or bring code/history from another repository.
link-workspace-packages
jumbleknot
'Link workspace packages in monorepos (npm, yarn, pnpm, bun). USE WHEN: (1) you just created or generated new packages and need to wire up their dependencies, (2) user imports from a sibling package and needs to add it as a dependency, (3) you get resolution errors for workspace packages (@org/*) like "cannot find module", "failed to resolve import", "TS2307", or "cannot resolve". DO NOT patch around with tsconfig paths or manual package.json edits - use the package manager''s workspace commands to fix actual linking.'
template-update
mirunamu00
Change a Pigment design system that is already published — fix a rule, change tokens, add or change a component — as a new internal version that is re-applied to the four base apps, evaluated, approved and published with a public changelog entry. Use when the user asks to fix, update, improve or extend an existing system. For a brand-new system, use template-intake.
template-intake
mirunamu00
Turn a reference website into a tested Pigment design system template — capture, analysis, design prompt authoring, demo generation on the four base apps, evaluation, iteration and (after user approval) publishing. Use when the user submits a site they like, asks to add a template, or asks to iterate on a template candidate. To change a system that is already published, use template-update.
stacks-events
stacksjs
Use when working with the event system in a Stacks application - dispatching events, listening for events, model events, wildcard listeners, the event emitter, or event-driven architecture. Covers @stacksjs/events, app/Events.ts, app/Listener.ts, and app/Listeners/.
stacks-design-soft
stacksjs
Use when a Stacks UI should feel high-end, "expensive", soft, and premium - designing a landing page, hero, marketing section, pricing, or portfolio that needs generous whitespace, premium fonts, soft diffused shadows, and spring-like motion. Composes with stacks-design-taste as an aesthetic preset built on stx + ts-css + composables.
stacks-dashboard
stacksjs
Use when building or customizing the Stacks admin dashboard, including dashboard pages, model management views, analytics widgets, commerce dashboards, content management, settings panels, deployment monitoring, job/queue management, or the 414 built-in dashboard components. Covers the dashboard system at storage/framework/defaults/.
stacks-commerce
stacksjs
Use when building e-commerce features in Stacks - the commerce namespace with 15 sub-modules (products, carts, orders, customers, coupons, payments, gift cards, auctions, shipping, tax, waitlists, restaurant, devices, receipts, errors), 20+ commerce models, checkout and redemption logic, or the commerce configuration. Covers @stacksjs/commerce.
capability-review
osdlc
Review existing Capability entities for accuracy against the code they anchor: do the locations still realize the Statement, do kind, audience and state match the shared rubric, do parent_key and related still resolve, does the body describe what the code does. Runs sdlc capability coverage and sdlc capability graph read-only, dispatches one read-only sub-agent per capability, and prints a report. With --fix it also corrects frontmatter through sdlc capability update and stamps last_reviewed; with --rewrite it also rewrites drifted body sections; both open a PR. Invoke after a mapping run, after a refactor that moved packages, or when the System page's capability view looks wrong. Usage: /sdlc:capability-review <dir C-NNNN all> [--fix] [--rewrite] [--auto].
pr-stats
osdlc
Summarize a pull request or branch diff beyond GitHub's +/-: lines added and removed by code, comments, blank and prose; a change-category breakdown (added, deleted, renamed, tests, docs, generated, formatting-only, comment-only, logic); dependency and exported-API changes; and the cyclomatic-complexity movers. Use before or after opening a PR, in review, or when asked to "summarize this change", "how big is this PR", "what did this branch actually change", or "add stats to the PR". Optionally writes the table into the PR body. Runs from a bundled script with plain Node, git and gh; needs no other plugin.
pr-review
osdlc
Shell out to a headless external agent — codex by default, claude on request — for a code review of the current branch against the upstream default branch: potential errors, cleanup areas, duplication, and opportunities to better use or grow the project's own library set.
fygo-browser-cdp
Russ534
"Drive fygo-browser for real desktop browser tasks."
cross-platform-context-sync
Russ534
Use when one user talks via multiple channels.
excalidraw
Russ534
"Hand-drawn Excalidraw JSON diagrams (arch, flow, seq)."
ascii-art
Russ534
"ASCII art: pyfiglet, cowsay, boxes, image-to-ascii."
merge-reconciler
Russ534
"Neutral third-party resolution of agent merge conflicts."