GITHUB AGENT SKILLS / 技能收录

给你的 AI 助手
装上专业技能

我们从 GitHub 持续收录、审核并分类优质的 Agent Skills,按职业与使用场景整理,复制一行命令即可安装到 Claude Code、Cursor 等智能体。

01 /

按职业浏览 Agent Skills

为不同岗位挑选的高频技能

全部职业
02 /

按使用场景浏览 Agent Skills

从你要完成的任务出发

全部场景
03 /

按创作者浏览 Agent Skills

按 GitHub Stars 排序的优秀创作者

全部创作者

全部 Skills 482556

bendusz
bendusz/bstack

reflect

Spawn three parallel review subagents over the active transcript, surface learnings, and route each to a concrete edit on an existing skill. Use when the user says reflect.

★ 3
bendusz
bendusz/bstack

principle-type-system-discipline

Apply when designing types, reviewing a function signature, or writing code in any statically-typed language. Make illegal states unrepresentable, brand semantic primitives, parse external data at boundaries, refuse to lie to the compiler, exhaust variants, derive from authoritative schemas.

★ 3
bendusz
bendusz/bstack

principle-test-behavior-not-implementation

Apply when you write, change, or keep a test. Call the code as its users do and assert the exact result they see. Rewrite or delete a test that would pass if every imported function returned undefined.

★ 3
bendusz
bendusz/bstack

principle-subtract-before-you-add

Apply when sequencing an addition, refactor, or rewrite. Remove dead code, redundant validators, and stub references first, then build on the simpler base.

★ 3
bendusz
bendusz/bstack

principle-sequence-verifiable-units

Apply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs. Break work into small units that each end in a verifiable state, check each before the next, and order delivery so the sequence proves itself to a reviewer.

★ 3
bendusz
bendusz/bstack

principle-separate-before-serializing-shared-state

Apply when concurrent actors might write to the same file, branch, key, or state object. Eliminate the sharing first; serialize structurally only when one shared writer is a real invariant.

★ 3
bendusz
bendusz/bstack

principle-redesign-from-first-principles

Apply when integrating a new requirement into an existing design.

★ 3
bendusz
bendusz/bstack

principle-prove-it-works

Apply after completing a task, before declaring done. Verify against the real artifact (run the feature, read the actual value, inspect the diff), not a proxy, self-report, or 'it compiles.'

★ 3
bendusz
bendusz/bstack

principle-outcome-oriented-execution

Apply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; don't preserve smooth intermediate states with throwaway compatibility code.

★ 3
bendusz
bendusz/bstack

principle-never-block-on-the-human

Apply when tempted to ask 'should I do X?' on reversible work.

★ 3
bendusz
bendusz/bstack

principle-model-the-domain

Apply when writing stateful logic, or when code branches a lot or repeats a shape assumption across files.

★ 3
bendusz
bendusz/bstack

principle-minimize-reader-load

Apply when reviewing or shaping code that's hard to trace. Count layers between question and answer, and hidden state in the reader's head; collapse one-caller wrappers and shrink mutable scope.

★ 3
bendusz
bendusz/bstack

principle-migrate-callers-then-delete-legacy-apis

Apply when introducing a new internal API while old callers still exist. Migrate callers and delete the old API in the same wave instead of preserving compatibility layers.

★ 3
bendusz
bendusz/bstack

principle-make-operations-idempotent

Apply when designing commands, lifecycle steps, or processing loops that run amid crashes, restarts, and retries. Converge to the same end state regardless of partial prior runs.

★ 3
bendusz
bendusz/bstack

principle-laziness-protocol

Apply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward deletion and the smallest change that solves the problem.

★ 3
bendusz
bendusz/bstack

principle-guard-the-context-window

Apply when context is filling up: large outputs, long files, repeated reads, fan-out planning. Route bulk to subagents; keep summaries in the main thread, not raw payloads.

★ 3
bendusz
bendusz/bstack

principle-foundational-thinking

Apply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what concurrent actors share. Get the data structures right so downstream code becomes obvious.

★ 3
bendusz
bendusz/bstack

principle-fix-root-causes

Apply when debugging. Trace each symptom to its root cause and fix it there; reproduce first, ask why until you reach it, resist nil-check guards that silence crashes.

★ 3