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,673–18,696 of 70,054 skills
- Project Guidelines ExampleProject-specific skill template covering architecture, patterns, testing, and deployment guidance.Votes: 0GitHub stars: 2
- Frontend PatternsFrontend development patterns for React, Next.js, state management, performance optimization, and UI best practices.Votes: 0GitHub stars: 2
- Coding StandardsBaseline cross-project coding conventions for naming, readability, immutability, and code-quality review. Use detailed frontend or backend skills for framework-specific patterns.Votes: 0GitHub stars: 2
- Quick Gate JsRun the optional KWIK-E-GATE JS/TS adapter or interpret its gate-result/v1 diagnostics. Use for JavaScript/TypeScript tool checks; the core owns completion receipts.Votes: 0GitHub stars: 5
- Quick Gate JsRun the optional KWIK-E-GATE JS/TS adapter or interpret its gate-result/v1 diagnostics. Use for JavaScript/TypeScript project checks; the core owns completion receipts.Votes: 0GitHub stars: 5
- Write Developer DocumentationHow to write developer documentation that a developer can read once and act on. Load it BEFORE writing or rewriting any documentation for people who install, configure, integrate, maintain or contribute to software, and for AI coding agents that follow written rules. Covers READMEs, quickstarts, installation and upgrade guides, settings and CLI references, troubleshooting pages, architecture and design documents, contributor guides, rule documents that agents follow, changelogs and release no...Votes: 0GitHub stars: 11
- Write A GuideHouse style for guides, the documentation that tells a reader what something is, how it works, how to use it and how to change it. Load it BEFORE writing a guide, even when the request never says "guide": judge by what the document is for, not by the word "document". Covers internal docs for a team (dashboards, pipelines, scripts, tools, processes), product help for users, READMEs and handover docs, wherever they will live (a wiki, a README, a help page, a docs site). Trigger phrases: "docume...Votes: 0GitHub stars: 11
- Adopt Coast StandardsInstall or upgrade Coast Standards (engineering rules for AI-built software, plus the checks that enforce them) in the current project. Use when asked to adopt, install, set up or upgrade Coast Standards, or to add coding-standard checks and git hooks to a repository. Fetches a published release; the installer copies the rules and checks into the project.Votes: 0GitHub stars: 11
- StoryFile tracker stories for review threads a human already approved — search for an existing one first, create at most one per entry, and report each id and URL back. Places records only: never rewrites the approved text, never edits the worktree, never posts. Use when the orchestrator starts a story pass.Votes: 0GitHub stars: 7
- ReviewAnswer a pull request's review threads end to end with a human deciding in the orchestrator's overlay — read the threads and propose options, make the changes they pick, then post the replies. Use when the orchestrator starts a review session, or when somebody asks you to work a PR's review feedback with the overlay driving.Votes: 0GitHub stars: 7
- OrchHow to reach the orchestrator you are running inside — ask the human a blocking question, start or end another session, list the sessions and where they run, or start one of the workspace's declared processes. Use whenever you need a decision from the person watching, want a second session to work in parallel, or need to know what else is running before touching a branch or a worktree.Votes: 0GitHub stars: 7
- Handle ReviewWork through a pull request's review threads in a pane — judge each one, apply what is right, ask about the rest, draft replies and post only on an explicit go. Use when somebody asks you to resolve, handle or answer the review feedback on a PR.Votes: 0GitHub stars: 7
- GreenGet a PR green. Rebase it on its base branch, fix the easy red, ask about the rest, amend into the commit that owns the change, force-push, and watch CI until it passes. Use when a PR is red or has fallen behind, and never for review threads, which are somebody's words rather than a failing check.Votes: 0GitHub stars: 7
- Fix PrGet a pull request green. Take its base branch in, fix the red checks, amend, push, and watch until the checks settle. Mechanical only: never comments, never resolves a thread, never merges the PR itself. Use when somebody asks you to fix, rebase or unbreak a PR's CI, or when the orchestrator hands you a fix run.Votes: 0GitHub stars: 7
- Domain Consistency ReviewRead-only product & domain consistency review for orchd — reconstruct the domain model from the implementation, then check whether the domain logic is internally coherent. Finds contradictions, unclear state ownership, impossible states, duplicated business rules, and rules enforced in one place but bypassed in another — especially across the SPA / daemon / persistence / GitHub / background-poller boundaries. Produces inferred domain rules plus evidence-backed inconsistencies and modifies no ...Votes: 0GitHub stars: 7
- Architecture Health CheckRead-only architecture health check for orchd — find where many individually reasonable changes have gradually degraded the architecture (responsibility accumulation, workflow fragmentation, conditional sprawl, boundary violations, unclear state ownership, incremental duplication, over-stretched abstractions). Produces a prioritized, evidence-backed report and modifies no code. Use for a periodic review, or after a subsystem has grown a lot. Optionally pass a path, subsystem, or git range to ...Votes: 0GitHub stars: 7
- Ui Ux Pro MaxUI/UX design intelligence for web, mobile, and desktop. This skill should be used when designing, building, reviewing, or fixing interfaces, including pages, components, design systems, accessibility, interaction, responsive layout, typography, color, charts, and stack-specific UI implementation. Searchable local data: 79 searchable styles (50 active), 192 product palettes and reasoning profiles, 74 font pairings, 119 UX guidelines, 105 icons, 17 GSAP presets, 25 chart types, and 22 stacks.Votes: 0GitHub stars: 3
- DebugDiagnose a Phosphor session that errors, hangs, or returns an empty reply — read the main-process debug log, pi's session JSONL, and the provider's own transcript. Use when a session "isn't working", a turn fails with a confusing message, pi crashes, or a provider (Claude CLI, Bedrock) misbehaves.Votes: 0GitHub stars: 10
- StopLeave the review loop for this worktree. Commits and file changes stop being gated. Nothing is reverted.Votes: 0GitHub stars: 2
- StatusShow the review loop state for this worktree — status, phase, baseline, approvals, failure counters and stored reports.Votes: 0GitHub stars: 2
- ResumeContinue an already-armed adversarial-review-loop plan in a new session (or adjust the model or plan in this one), without losing the original baseline or any approvals already recorded. Runs to the end of the plan unless --until N sets a pause target.Votes: 0GitHub stars: 2
- ReportPrint a stored review report in full, including every finding and the raw reviewer output.Votes: 0GitHub stars: 2
- PauseMove the review loop's pause target. With no argument the phase in flight is finished and committed as usual, then the turn ends instead of continuing into the next phase.Votes: 0GitHub stars: 2
- ImplementImplement an agreed plan with an enforced adversarial review loop. Every phase commit is gated on an external review that must pass before the commit proceeds.Votes: 0GitHub stars: 2