All categories
Development
Programming, frameworks, implementation, frontend, backend, and app development
- 70,054
- 2,919
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 browserBrowse development skills
Showing 18,817–18,840 of 70,054 skills
- PairAgentic pair programming — drive a change together with a human partner in the loop, narrating intent and pausing at decision points. Use when the user wants to work side-by-side rather than hand off a whole task. Calibrated by three dials (role, detail, autonomy) and an always-on challenge mandate.Votes: 0GitHub stars: 2
- KnowledgeUse when work surfaces something epistemic worth keeping — "we're assuming / proceeding as if X", "we decided X over Y", "open question worth outliving this session", "we're bound by X", "evidence for/against X", "testable hypothesis", or a stable concept worth naming — and when settling, relating, or surveying such records. Routes capture, settle, and survey intent to the correct `doctrine knowledge` verb.Votes: 0GitHub stars: 2
- InquisitionUse only when the user explicitly requests an "inquisition" (e.g. "seek out heresy", "begin an inquisition", "inquisition on X") to hunt adversarially for deviations from doctrine, design, plan, conventions, or acceptance criteria. Do NOT use for routine "review X" or ordinary code review.Votes: 0GitHub stars: 2
- HarvestUse at the end of any coherent unit — a phase, task, review close, or slice wrap — to sweep what the unit produced, learned, and left open into their durable sinks, and to maintain the Harvest section of the governing slice's notes.Votes: 0GitHub stars: 2
- HandoverUse when handing work to a fresh context — first bring the durable harvest current, then emit a continuation at one of two weights — a printed continuation prompt (light) or a handover.md context packet (full). Use whenever a fresh agent would more efficiently continue.Votes: 0GitHub stars: 2
- FeedbackUse when receiving feedback on your work — review findings, user corrections, audit results, external reviewer notes — to triage by authority, adjudicate each point on evidence, integrate without regressions, and close the loop with the source. Evidence flips positions; assertions don't.Votes: 0GitHub stars: 2
- ExecuteUse to implement one planned, approved phase of a slice — once its design and plan exist and its runtime phase sheet is ready. Move the phase to in_progress, build it TDD red/green/refactor, keep notes current, end green, and surface blockers early.Votes: 0GitHub stars: 2
- ElicitUse when running a value-elicitation session — surfacing and asking the next worthwhile pairwise value questions, reviewing suspect anchors, or calibrating value evidence with a human via `doctrine compare elicit`.Votes: 0GitHub stars: 2
- DreamingUnified memory corpus maintenance — covers both reactive (change-triggered) and proactive (periodic/idle-time improvement) paths. One skill, two entries.Votes: 0GitHub stars: 2
- DispatchUse to drive a slice's phases to completion through confined subprocess workers in isolated worktrees — you orchestrate and are the sole writer, the workers execute. Workers spawn via `/dispatch-spawn`, one path for every harness. You drive the landing yourself — import, commit, record, verify, conclude, reap; `doctrine dispatch next` prescribes only for a fork bound at creation, which this path does not mint. Default serial (one worker per phase); parallelize file-disjoint phases. Conflicts ...Votes: 0GitHub stars: 2
- Dispatch SpawnThe one spawn path for `/dispatch` — `scripts/spawn-confined.sh <harness>` forks the worker's worktree, wraps it in a kernel-level jail, and runs the harness headless inside it. Every harness takes this path; there is no in-session arm and no unconfined fallback. The worker cannot commit — it hands back an uncommitted working tree and the orchestrator imports it. Reached from the `/dispatch` router; do not invoke directly.Votes: 0GitHub stars: 2
- DesignUse when a slice needs architectural shaping before implementation — decision triage, critical analysis of tradeoffs and solutions, and section-by-section validation of design.md until the decisions lock. Routed to from /route once a slice exists.Votes: 0GitHub stars: 2
- ConsultUse the moment you hit an unanticipated obstacle, a decision with competing tradeoffs, or emergent complexity mid-task — before adapting planned scope, adding a dependency, taking a shortcut, or making any impactful concession on your own.Votes: 0GitHub stars: 2
- Code ReviewUse whenever reviewing code for quality and correctness — a diff, PR, module, or subsystem — producing verified, severity-ranked findings on the RV ledger. Not for comprehension tours (walkthrough) or doctrine-conformance hunts (inquisition, user-invoked only).Votes: 0GitHub stars: 2
- CloseUse to formally close a slice once its phases are complete, audited, and reconciled — confirm the rollup, verify spec-coherence, harvest durable findings, reconcile lifecycle status, and land a clean final commit. Routed to from /reconcile.Votes: 0GitHub stars: 2
- Capsule DriverUse to drive a slice's phases to completion through in-session capsule subagents in the MAIN worktree — you are the super-orchestrator seat, spawning capsule-orchestrators that each charter ~3 phases and spawn their own planners and workers. No worktrees, no dispatch, no confinement. Use when you want a whole slice implemented under a tight context budget without handing the tree to confined workers. Not for confined or parallel-worktree execution — that is /dispatch.Votes: 0GitHub stars: 2
- CanonUse before making architectural or workflow choices, when correctness depends on project governance, or when entering an unfamiliar subsystem — to load the project's authoritative rules before you act on assumptions.Votes: 0GitHub stars: 2
- BacklogUse when the user wants to create, survey, triage, tag, or transition a doctrine backlog item (issue / improvement / chore / risk / idea) — `doctrine backlog` is the CLI surface; use this skill to drive the correct verb for the intent.Votes: 0GitHub stars: 2
- AuditUse after a slice's phases are implemented, when the task is now evidence, conformance, and reconciliation against the design — disposition every finding on a reconciliation review ledger (the RV kind) before closure.Votes: 0GitHub stars: 2
- Redline TourOpen the current diff as a Redline review round in VS Code with a numbered walkthrough attached, then listen for the review.Votes: 0GitHub stars: 3
- Redline ConnectAttach this session to the reviewer's Redline submits. Invoke after request_review, when VS Code says "No agent is connected", or when the user asks to pick up a review.Votes: 0GitHub stars: 3
- Redline AnnotateOpen the current diff as a Redline review round in VS Code with the notes you already wrote, then listen for the review.Votes: 0GitHub stars: 3
- ReleaseCut a redline release from this checkout: bump, build, test, commit, then push the tag that makes the Release workflow publish npm, marketplace, and GitHub release, after one confirmation.Votes: 0GitHub stars: 3
- Local InstallInstall the redline extension and Claude Code plugin from this checkout. Defaults to VS Code Insiders, default profile.Votes: 0GitHub stars: 3