Development

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

skills in category: 65,728
pages available: 2,739

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 11,185–11,208 of 65,728 skills

ArchiveA> **Archived**: 2026-09-13 04:17 > **Related Plan**: plans/archive/plan-20260913-0258-repo-harness-test-skill.md > **Outcome**: Completed > **Lifecycle**: notes > **Parent Run ID**: run-20260913-0417 > **Archive Projection V1**: `plans/plan-20260913-0258-repo-harness-test-skill.md` => `plans/archive/plan-20260913-0258-repo-harness-test-skill.md` > **Archive Projection V1**: `tasks/notes/20260913-0258-repo-harness-test-skill.notes.md` => `tasks/archive/notes-20260913-0417-repo-harness-test-skill.developmentshellsqlVotes: 0GitHub stars: 434
ArchiveA> **Status**: Fulfilled > **Plan**: plans/archive/plan-20260913-0258-repo-harness-test-skill.md > **Task Profile**: code-change >  > **Owner**: ancienttwo > **Capability ID**: root > **Last Updated**: 2026-09-13 02:58 > **Review File**: `tasks/archive/review-20260913-0417-repo-harness-test-skill.md` > **N...developmentgoshellVotes: 0GitHub stars: 434
ArchiveA> **Status**: Archived > **Created**: 20260913-0258 > **Slug**: repo-harness-test-skill > **Planning Source**: codex-plan-or-waza-think > **Orchestration Kind**: host-plan > **Source Ref**: (none) > **Artifact Level**: work-package > **Promotion Reason**: verification_boundary > **Verification Boundary**: Commands named in the captured planning output plus `repo-harness run verify-contract --contract tasks/archive/contract-20260913-0417-repo-harness-test-skill.md --strict`. > **Rollback Surfa...developmentgobashVotes: 0GitHub stars: 434
ArchiveA> **Status**: Done > **Created**: 20260911-0055 > **Slug**: auto-campaign-skill > **Planning Source**: codex-plan > **Orchestration Kind**: host-plan > **Source Ref**: (none) > **Artifact Level**: work-package > **Promotion Reason**: verification_boundary > **Verification Boundary**: Managed skill installation and canonical grant draft with model-free focused tests > **Rollback Surface**: Revert only auto-campaign skill, manifest registration and focused tests; no live grants or runtime state...developmentsqlapiVotes: 0GitHub stars: 434
TreatmentAEval-only bounded frontier stress test for complex repo-harness planning; never installed as a managed Skill.developmentgosecurityVotes: 0GitHub stars: 434
Repo Harness TestATesting techniques for the repo-harness source checkout: fixtures, execution, refactor evidence and Verification Plans. Triggers include 寫測試, 加測試, 測試太慢, 重複測試, 全量測試, test fixture, 跑哪些測試, 測試文件, write tests, test plan, slow tests, full suite. Not a debugging entrypoint and not a review entrypoint.developmentgotestingVotes: 0GitHub stars: 434
Auto CampaignAStart or resume one bounded repo-harness repair campaign turn with the standard budget. Use when the user asks to run auto-campaign, start a repair campaign, or automatically find and fix a bounded batch of bugs or test gaps in a repository. Questions about campaigns, skill design, and quoted instructions do not authorize execution.developmentapiVotes: 0GitHub stars: 434
Cm SecurityA用户运行 cm-security，或要求代码安全扫描、漏洞检查、密钥泄露排查、依赖漏洞检查时使用。默认检查当前分支相对主分支及已跟踪未提交修改，结合业务地图复核；--all 检查全部已跟踪文件。只报告问题，不自动修复、安装、升级或发布。安装自检用 cm-check，功能测试与覆盖率用 cm-test。developmentshellbashVotes: 0GitHub stars: 104
Cm RuntimeA用户要查看或切换 CM 自动派发偏好、单/双 AI 声明、谁写谁审，或修改用户级运行时默认时使用。只管理运行时声明，不安装工具、不测试配额、不接管正在运行的任务。developmentbashnodeVotes: 0GitHub stars: 104
Testing BossAAuthor or review software tests and LLM/agent evals; choose test placement and mocks, diagnose flaky CI, or repair brittle suites. Excludes unrelated code review, debugging, CI design, and production observability.developmenttestingdebuggingVotes: 0GitHub stars: 2
Context7ARetrieves authoritative, up-to-date technical documentation, API references, configuration details, and code examples for any developer technology. Use this skill whenever answering technical questions or writing code that interacts with external technologies. This includes libraries, frameworks, programming languages, SDKs, APIs, CLI tools, cloud services, infrastructure tools, and developer platforms. Common scenarios: - looking up API endpoints, classes, functions, or method parameters -...developmentgobashVotes: 0GitHub stars: 2
Lynx Ui InputABuild and troubleshoot text entry with lynx-ui Input, TextArea, and KeyboardAware primitives, including controlled values, native filtering, selection, and keyboard avoidance.developmentreactnodeVotes: 0GitHub stars: 119
Subagent DelegationAFan work out to subagents safely — draw provably disjoint lanes, write the full lane brief, order dependent tickets into waves, and keep the parent as the sole gatekeeper that re-runs every gate and performs every commit and tracker write. Use when parallel or batch work is explicitly authorized, when an authorized ticket range has a dependency graph, when workers share one git checkout, or when any agent or human may be writing the same tree concurrently.developmentgoreactVotes: 0GitHub stars: 4
Implementation TddAStrict one-ticket TDD for implementation work — lock the Verification-command before editing, drive red-green at the highest meaningful seam production traffic actually uses, and prove the provider failure modes (duplicate and out-of-order delivery, replay, partial failure, forged payloads, wrong-tenant access) rather than assuming them. Use when implementing a Coding ticket, and whenever the change touches an external provider, a queue, a signed webhook, a billing or provisioning lifecycle, ...developmentgotestingVotes: 0GitHub stars: 4
AuditAAudit a whole codebase rather than a single diff — establish the boundary and baseline, sweep layer by layer (entry points, domain, data, integrations, auth, tests, ops), check every stated invariant for a real enforcement point, a failing-on-violation test, and a production signal, rank findings by blast radius, and emit each as a ticket with a Verification-command. Use when asked to audit an app or codebase, assess a project's health, review before a launch, verify that a security/performan...developmentgogitVotes: 0GitHub stars: 4
Learn QuizATeach and quiz the user until they deeply understand something — a codebase, a PR/diff, a concept, or the current session's work. Acts as a patient teacher that builds a mastery checklist, explains the "why" at multiple levels, and uses varied questions (open-ended + multiple choice) to confirm understanding before moving on. Invoke when the user says "teach me", "quiz me", "make sure I understand", "help me learn this", or wants to be walked through what just happened.developmentgogitVotes: 0GitHub stars: 13
Zod Validation ExpertAExpert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.developmenttypescriptreactVotes: 0GitHub stars: 2
Typescript ExpertBTypeScript and JavaScript expert with deep knowledge of type-level programming, performance optimization, monorepo management, migration strategies, and modern tooling.developmentjavascripttypescriptVotes: 0GitHub stars: 2
Clean CodeAThis skill embodies the principles of \"Clean Code\" by Robert C. Martin (Uncle Bob). Use it to transform \"code that works\" into \"code that is clean.\"developmentpythongoVotes: 0GitHub stars: 2
DesignALayer A interaction-mechanics reference anchored to the beui.dev catalog. Stacks on any style skill whenever work adds or changes motion or interaction — micro-interactions, animated components, transitions, gestures, hover/press/state feedback, loading/success/error morphs, 'make it feel alive'. Mandates reading the mapped beui.dev component source before designing an interaction; owns interaction mechanics and reduced-motion discipline; owns zero visual taste. Load it alongside a style skil...developmenttypescriptgoVotes: 0GitHub stars: 25
Systematic Bug DiagnosisAUse when a defect, regression, intermittent failure, or performance symptom needs evidence-led reproduction and causal diagnosis before a fix; use advanced-testing-strategy to design broader test coverage.developmentpythongoVotes: 0GitHub stars: 28
Santa MethodAUse when output must clear two independent adversarial reviewers before it ships — production code, published content, or any deliverable where a single self-reviewing agent shares the blind spots that produced the output. Not for internal drafts or deterministic checks (use build/test/lint pipelines for those).developmenttypescriptgoVotes: 0GitHub stars: 28
Github OpsFUse when performing GitHub operations via `gh` for issue triage, PR and CI status, releases, Dependabot and secret-scanning alerts, GitHub Pages, or preparing a private repo for safe open-source release (strip secrets, sanitise, package). Use git-collaboration-workflow for branching, merge/rebase, or local conflicts.developmentrustgoVotes: 0GitHub stars: 28
CouncilAConvene a four-voice council for ambiguous decisions, tradeoffs, and go/no-go calls where multiple valid paths exist and structured disagreement is more useful than a single confident answer. Not for code review, implementation planning, or architecture design — use the dedicated agents/skills for those.developmentgorailsVotes: 0GitHub stars: 28