All categories
Documentation
Docs, README files, API references, tutorials, specs, and changelogs
- 16,089
- 671
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 documentation skills
Showing 6,265–6,288 of 16,089 skills
- Amuro Skill安室透（少年推理漫）认知与表达框架（压缩蒸馏）：三重身份张力、波本梗、服务生伪装 触发：名侦探柯南 等。虚构；禁止犯罪教唆Votes: 0GitHub stars: 9
- Akagi Skill赤木刚宪（少年漫）认知与表达框架（压缩蒸馏）：队长脊梁、篮板信仰、大猩猩梗自嘲 触发：灌篮高手 等。虚构Votes: 0GitHub stars: 9
- Kotlin Coding StandardsConventions for clean, idiomatic, safe Kotlin. Use when writing or reviewing Kotlin code.Votes: 0GitHub stars: 10
- ReleaseRelease a new version: bump version, update docs, commit, push, and tagVotes: 0GitHub stars: 8
- Write EvidenceWrite a content string to a target path inside the `.garura/` folder whitelist. Enforces whitelist compliance at the write boundary. Used by the scriber agent.Votes: 0GitHub stars: 3
- Infer Mvp Recommendation From CodeInfer the MVP recommendation from scan-index.json during /codify by reverse-engineering what the shipped codebase ALREADY treats as v1 — primary use cases evidenced by release history, entry points, churn, and README — plus deferred capabilities evidenced by thin/scaffold-only code. Output is Markdown with YAML frontmatter. Used exclusively by product-keeper in the /codify play.Votes: 0GitHub stars: 3
- Infer Market Brief From CodeProduce a low-fidelity market-brief.md stub from codebase signals (README, manifests, ADRs, git tags, deploy config) during /codify. Owned by product-keeper. Confidence defaults to low; real market data is never inferable from code.Votes: 0GitHub stars: 3
- Draft Implementation PlanCreate a plan.yaml artifact — execution order of features as vertical slices with scope items, exit gates, and scenario gatesVotes: 0GitHub stars: 3
- Author Build PlanDraft /implement's build plan for ONE epic — the working spine of the build. Reads the epic's box (the epic record, its functionalities' ICE, the slice's six lenses, the captured repo context + test harness) and breaks the epic into PIECES — stories, tasks, tests, docs — with explicit dependency edges forming a DAG, test-first (every epic acceptance criterion covered by a test piece authored from the spec, never from the implementation). Every piece carries a grounding citation into the box (...Votes: 0GitHub stars: 3
- Analyze PrAnalyze branch and generate context-aware quality checklistVotes: 0GitHub stars: 3
- Aggregate Codify ProposalsWalk the inference-output directory under STM, read every proposal artifact each infer-*-from-code skill produced, and compose the master proposals.yaml index classified by the two-level learning taxonomy (learning_category + sub_category). This is the artifact that /garura:enrich consumes. Used exclusively by the /codify play.Votes: 0GitHub stars: 3
- ImplementBuild one ready epic to done — every spec passing — strictly inside the epic''s box. Breaks the epic into a test-first plan (stories, tasks, tests, docs as a DAG), publishes that plan to the epic''s tracked issue and keeps it current as the working spine, builds with spec separation (the implementer never sees tests or evals), and accepts done only from adversarial steelman verification. Opens the work; never closes it — the close belongs after /validate. Also the FIX ROUND: when /validate st...Votes: 0GitHub stars: 3
- MinimalProduce test data that is deterministic, isolated per test, and states its intent in the test that uses it.Votes: 0GitHub stars: 2
- MinimalSpend analysis where it pays — heavily on decisions that are expensive to reverse, barely at all on the ones you can undo next sprint.Votes: 0GitHub stars: 2
- VerboseEvery value has exactly one owner. Assigning or passing a non-`Copy` value moves ownership; the source binding becomes invalid, and the compiler enforces this at compile time with zero runtime cost.Votes: 0GitHub stars: 2
- MinimalMove, borrow, or clone deliberately, and satisfy the borrow checker by fixing the design it is complaining about — not by scattering `.clone()`.Votes: 0GitHub stars: 2
- VerboseA requirement earns the name only if someone could write a check that fails. Everything else is a preference wearing a requirement's clothes, and it will be settled in code review by whoever argues longest.Votes: 0GitHub stars: 2
- Verbose```promql rate(http_requests_total[5m])Votes: 0GitHub stars: 2
- VerboseAlmost all bad documentation is well-intentioned writing in which two or more purposes have been welded into one page. The reader arrives with one need and is served three, so the page fails all three. The Diátaxis framework names the split along two axes: is the reader *learning* or *working*, and does the content serve *practice* or *understanding*?Votes: 0GitHub stars: 2
- MinimalSeparate the four kinds of documentation, generate everything that can rot, and delete the pages nobody reads.Votes: 0GitHub stars: 2
- Prometheus Query Patternsrate(http_requests_total[5m])Votes: 0GitHub stars: 2
- Documentation Best PracticesAlmost all bad documentation is well-intentioned writing in which two or moreVotes: 0GitHub stars: 2
- Writing RevisionRevise text for clarity, scannability, and direct action by busy readers.Votes: 0GitHub stars: 4
- StandaloneStrip references the reader cannot see from prose and code comments.Votes: 0GitHub stars: 4