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,793–18,816 of 70,054 skills
- Pr CleanupAudit and resolve open or stale GitHub pull requests across an explicit repository or organization scope. Use when asked to clean up PRs, merge all work that remains valid, revive or complete unfinished work against current main, close superseded PRs, or run that workflow on a schedule. Enforces a live census, current-head readiness gates, safe parallel ownership, branch retention, post-merge verification, and a final zero-open census.Votes: 0GitHub stars: 3
- Plan KbCreate or evolve a durable Markdown plan inside a hraness/wordcell vault. Use when a user asks for an implementation plan, proposal, RFC, migration plan, execution audit, phased checklist, or an update to an existing plan's decisions, progress, review findings, verification evidence, or final result.Votes: 0GitHub stars: 3
- Percolate ReadingReview saved web captures or maintained quote notes in this repository's Markdown knowledge base, turn selected sources into evidence-backed reading digests or complete reading notes, and project only explicitly published notes into the personal website. Use when triaging captured sources, percolating something read, preserving reviewed quotations, publishing a reading note, checking the reading inbox, or regenerating the public Reading collection and Atom feed.Votes: 0GitHub stars: 3
- First Principles ThinkingUse first-principles thinking as a tool for any question, design problem, strategy, decision, or explanation where the user wants to reason from fundamentals instead of analogy, convention, or inherited assumptions.Votes: 0GitHub stars: 3
- Direct VerifyVerify an existing Direct composition, including strict activation, deterministic settlement, semantic scenario behavior, coverage truthfulness, cleanup, and exclusion from production output. Use when asked to test, audit, validate, review, or report the proof boundary of a Direct workbench or frontend verification run.Votes: 0GitHub stars: 3
- Direct SetupAdd or revise a Direct deterministic development composition around product-owned ports, strict JSON worlds, scenarios, coverage claims, probes, and separate production-safe entries. Use when asked to adopt Direct, build a deterministic UI workbench, replace slow frontend dependencies with fixtures, or repair a Direct setup that leaks into production.Votes: 0GitHub stars: 3
- Decision MatrixStructure a choice between concrete options: elicit the real criteria and their weights, score each option honestly, run a sensitivity check on the weights, and separate what the numbers say from what the gut says. Use when choosing between 2–6 named alternatives (jobs, tools, vendors, apartments, strategies).Votes: 0GitHub stars: 3
- Assumption AuditExtract every assumption hidden in a claim, plan, or belief, classify each by load-bearingness and testability, and identify which single assumption would collapse the whole structure if false. Use when a plan feels solid but untested, or before committing to a decision built on unexamined premises.Votes: 0GitHub stars: 3
- WorktreeUse when work needs isolation from the current workspace — when /execute (mode=solo) or the /dispatch funnel must run a phase on its own branch without touching the main working tree. Detects existing isolation, creates a fork via `doctrine worktree fork` (the sole creation+provision+bind verb; coordination tier excluded), runs the commit-before-spawn / branch-point / baseline guards, and hands back the fork branch.Votes: 0GitHub stars: 2
- WalkthroughGuided walkthrough of code, a diff/PR, architecture, tests, or docs — build the reader's mental model, explain the choices made and their tradeoffs, and critically evaluate the artifact. Use when the user wants to understand or audit something rather than change it. Adapts to expert vs learner; companion to the pair skill.Votes: 0GitHub stars: 2
- Spec TechUse when authoring or revising the technical specification — the how of a capability, downstream of the product spec and upstream of per-slice design. Use to record durable architecture and mechanism, not a single change's design.Votes: 0GitHub stars: 2
- Spec ProductUse when authoring, revising, normalising, or reviewing a doctrine product specification/PRD - the durable product intent, requirements, success measures, behaviours, and verification basis for an evergreen capability. use before creating or scoping slices that descend from shared product intent. use when a request asks for product requirements, functional requirements, non-functional requirements, product scope, acceptance gates, out-of-scope boundaries, success measures, or agent-readable p...Votes: 0GitHub stars: 2
- Spec Coverage AssessmentUse when a named subsystem, capability, or code surface needs governance coverage assessed before authoring a spec — deciding what is already governed by an existing PRD / tech spec / ADR, what is dark, and where new spec boundaries should fall by product altitude and C4 level. Use before creating or scoping a product or technical spec for an unfamiliar or partially-governed surface. Use when a request asks to "assess coverage", "find governance gaps", "what's already specified", "where shoul...Votes: 0GitHub stars: 2
- SliceUse when code-changing intent has emerged and there is no governing slice yet — to scope the change into a slice (scope document + metadata) before any design or implementation. Routed to from /route.Votes: 0GitHub stars: 2
- RouteUse at the very start of ANY substantive work in a Doctrine repo — before inspecting files, running commands, or writing code. The mandatory gate that chooses the governing skill. Skip it only when the user has explicitly told you to.Votes: 0GitHub stars: 2
- RigourUse when operating at the edge of your capacity — high complexity, deep uncertainty, unfamiliar territory, expensive context — and being confidently wrong would be costly. A conduct posture layered onto whatever skill governs the stage; it changes how you work, not which work you do.Votes: 0GitHub stars: 2
- Reviewing MemoryStructured audit for stability gates — before releases, migrations, large refactors, or when agent confusion is detected. Use to prune, correct, and re-anchor the memory corpus before it drifts past useful.Votes: 0GitHub stars: 2
- Retrieve MemoryUse before making non-trivial assumptions — before touching a subsystem you have not this session, before running or changing a command pipeline, when code and docs conflict, when asked "what is the right way here?", when debugging a recurring failure, or when about to answer with "probably/usually/likely".Votes: 0GitHub stars: 2
- ResearchUse when a slice is scoped but not yet designed — run the pre-design research round and persist its evidence artefact — or when a consuming skill's staleness advisory reports drift. Produces a cited, verification-legended research.md that design and plan load-bear instead of recall.Votes: 0GitHub stars: 2
- Record MemoryUse when you discover or confirm a durable fact, constraint, invariant, convention, sharp edge, footgun, or reusable workflow that a future agent would otherwise rediscover — capture it before it is lost to conversation context. Triggers at phase/slice wrap-up too.Votes: 0GitHub stars: 2
- ReconcileUse after /audit resolved the RV ledger and wrote the reconciliation brief — you are the sole explicit writer of reconciled truth. Consume the RV + brief, write changes through two surfaces (direct edit for per-slice artefacts, REV for governance/spec), and hand off a resolved outcome to /close. Routed to from /audit.Votes: 0GitHub stars: 2
- PreflightUse after routing has chosen this path, when the next step is bounded up-front research to understand a substantive task, surface unknowns and tensions, and assess readiness — without drifting into implementation or open-ended exploration.Votes: 0GitHub stars: 2
- PlanUse when a slice's design is locked and it needs an executable phase plan — refine each phase's objective and entry/exit/verification criteria, author plan.toml + plan.md, and materialise the runtime phase sheets. Routed to from /design.Votes: 0GitHub stars: 2
- Phase PlanUse just before executing a specific phase — expand its authored plan entry (objective + EN/EX/VT) into the disposable runtime phase sheet with a concrete task breakdown, assumptions, and verification steps. Routed to from /plan or /execute.Votes: 0GitHub stars: 2