Development

Programming, frameworks, implementation, frontend, backend, and app development

skills in category: 66,392
pages available: 2,767

Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.

Open in full browser

Browse development skills

Showing 14,089–14,112 of 66,392 skills

Web TestsAWrites Vitest unit tests for a plan's dashboard logic.developmenttestingVotes: 0GitHub stars: 2
Web ImplAImplements dashboard changes from a plan: TypeScript, Vite, no framework.developmenttypescriptVotes: 0GitHub stars: 2
TriageAPulls open GitHub issues into TODO.md as backlog entries, and audits the two lists against each other.developmentrustgoVotes: 0GitHub stars: 2
SpecAInteractive spec interviewer that guides you through defining requirements before planning. Produces a spec.md that feeds into /plan-work.developmentgobashVotes: 0GitHub stars: 2
Review WorkACorrectness review of a plan's implementation and test changes against the plan, the protocol contract and Muster's hard rules.developmentVotes: 0GitHub stars: 2
RetroAReviews a finished /orchestrate run and proposes the smallest change to the pipeline docs that would have prevented what went wrong — or says nothing needs changing. --audit reviews the pipeline docs themselves: size, retirement candidates, dead references, review-cycle trend.developmentpythongoVotes: 0GitHub stars: 2
Skills DirectorySkills Directory Look up any of 103,619 scanned skills — grade, score, and every finding. Free.Check a skill
Plan WorkAInteractive planning agent for building implementation plans. Produces plans with a precise protocol contract and UI specs for parallel daemon/web execution.developmenttypescriptgoVotes: 0GitHub stars: 2
OrchestrateARuns the full multi-agent implementation pipeline for an approved plan. Spawns subagents for E2E authoring, implementation, testing, and review.developmentpythongoVotes: 0GitHub stars: 2
LandASquash-merges an approved plan branch to main with a conventional subject that closes its issues, then deletes the branch.developmentgobashVotes: 0GitHub stars: 2
Interface ProbeARuns a controlled probe against the real pinned Claude Code binary to answer a wire-format question (hook payloads, status-line JSON, CLI behaviour), using the isolated rig in test/rig/. Findings land as fact records in docs/facts/.developmentrustgoVotes: 0GitHub stars: 2
E2e SpecsAAuthors or validates Playwright E2E tests for a plan (Claude Code faked via synthesized payloads).developmentVotes: 0GitHub stars: 2
Doc ReconcileAReconciles the feature specs and protocol document with what the code actually does. Use for doc upkeep after a change that skipped the pipeline.developmentVotes: 0GitHub stars: 2
Dev LoopABuilds and runs musterd locally against the real data dir for manual testing. Covers where the dashboard URL and tokens live and how to stop cleanly.developmentgobashVotes: 0GitHub stars: 2
DecideASettles a product/design decision by an honest two-agent debate (advocates talk directly, a fresh judge breaks a tie). Used by /orchestrate for [orchestrator:decision] review issues; also usable standalone for a question with exactly two options.developmentbashVotes: 0GitHub stars: 2
Daemon TestsAWrites Go unit tests for a plan's daemon implementation.developmentgotestingVotes: 0GitHub stars: 2
Daemon ImplAImplements Go daemon changes from a plan: ingest, state machine, storage, tmux/PTY, HTTP/WS.developmentgoVotes: 0GitHub stars: 2
Claude Code UpgradeADrives the Claude Code version ritual: runs make canary against the installed binary, then records a green run as a verified version and commits it. Routes a red run to the red ritual instead of improvising a fix.developmentgobashVotes: 0GitHub stars: 2
MjAConfigure Mjolnir (mj) for the user or drive its coding sessions from localhost. Use for requests to configure mj profiles, targets, review, delegation, or interface preferences; to start and steer sessions; or to diagnose the daemon.developmentgitapiVotes: 0GitHub stars: 87
gerillassAUse the Gerillass Sass mixin library — loading it, the mixin catalogue, and the argument forms that are easy to get wrong. Use when writing SCSS in a project that has gerillass installed.developmentgorubyVotes: 0GitHub stars: 171
Sass TestAWrite or debug sass-true unit tests for Gerillass mixins and utility functions. Use when adding test coverage, when a spec fails, or when the user asks to test a mixin.developmentgobashVotes: 0GitHub stars: 171
ReleaseACut and publish a Gerillass release — version bump, changelog, tag, GitHub release, npm publish, and post-publish verification. Use when the user asks to release, publish, ship a version, or push a fix out to npm.developmentgorubyVotes: 0GitHub stars: 171
New MixinAScaffold a new Gerillass mixin or utility function with the project's conventions, wire it into the folder index, describe it in meta/, and test it. Use when adding a new mixin, helper function, list or map to the library.developmentgoshellVotes: 0GitHub stars: 171
Commit And PrAWrite a Gerillass commit message and a pull request title and description to the house standard. Use whenever committing, and whenever a branch is pushed and handed over for a pull request.developmentgoshellVotes: 0GitHub stars: 171
Audit LibraryASweep every mixin and function in Gerillass and report where it misbehaves — silent failures, unhelpful errors, questionable output, and gaps in test coverage. Use when asked to audit or comprehensively test the library, before a release, or after a change that touches many mixins.developmentgobashVotes: 0GitHub stars: 171