Documentation

Docs, README files, API references, tutorials, specs, and changelogs

skills in category: 15,624
pages available: 651

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 documentation skills

Showing 3,769–3,792 of 15,624 skills

AuditAPerforms a systematic, multi-category audit of the ELPS codebase.documentationgobashVotes: 0GitHub stars: 36
SurfaceAHow a downstream app consumes the shared @kolu/surface stack (@kolu/surface · surface-app · surface-nix-host · surface-mcp) — declaring a typed reactive surface, serving it, consuming it (SolidJS hooks or a CLI), and mirroring a remote surface over ssh. Grounded in the real consumers: kolu, pulam-web, drishti, odu, and the TUIs. Load when wiring a surface server/client/mirror, or reaching for getHostSession / a link / the `.use()` hooks. CHANGING the framework is gated separately — `.claude/r...documentationgoreactVotes: 0GitHub stars: 959
PuCProvision and drive a `pu` box — an Incus container used as a clean Linux host for CI, builds, and evidence capture. Use when you need to run something on a fresh remote box instead of the user's machine: `nix run` a build, run CI against a real host, capture screenshots/video off-machine, or reproduce on a pristine environment. Covers create/connect/scp/destroy, running remote commands, copying artifacts back, and the no-egress failure mode. Triggers on "pu box", "spin up a box", "run this o...documentationgitapiVotes: 0GitHub stars: 959
Perfection ReviewAAdversarial "perfection" review — hold a change to an *ideal* bar, not just a correct one, assuming eternal time, unlimited energy, and no ship pressure. Use when the user asks to review "for perfection", to make a defect "impossible to express", or to hunt where a defect "relocates" across review rounds. Grounds every claim in the diff, fans out adversarial verifiers via Workflow, and reports residual surfaces with a structural fix for each. ONLY invoke when the user explicitly asks for a pe...documentationgoexpressVotes: 0GitHub stars: 959
Nix PlaywrightAUse this when adding Nix-based local runs for an existing Playwright e2e suite. Provides a self-contained `tests/shell.nix` that uses `nixpkgs-latest` for `playwright-driver.browsers`, plus a justfile entry — works on NixOS where `npx playwright install --with-deps` cannot.documentationshellnodeVotes: 0GitHub stars: 959
Nix JustfileAConventions for writing justfile recipes in Nix-based projects.documentationgoshellVotes: 0GitHub stars: 959
Skills DirectorySkills Directory Look up any of 103,619 scanned skills — grade, score, and every finding. Free.Check a skill
Nix HaskellAUse this when working on a Haskell project with Nix. Covers haskell-flake setup, adding/overriding dependencies, package settings, and devShell configuration.documentationgoshellVotes: 0GitHub stars: 959
Nix Chrome Devtools McpAchrome-devtools-mcp launcher — a single bash script that resolves Playwright's bundled Chrome-for-Testing and Node.js directly through Nix. See repo README for usage, override mechanisms, and version compatibility.documentationshellbashVotes: 0GitHub stars: 959
HickeyAEvaluate code (especially LLM-generated) for structural simplicity using Rich Hickey's "Simple Made Easy" framework. Use this skill whenever reviewing a PR, diff, or code snippet for accidental complexity — particularly when the code was generated by an AI coding assistant and line-by-line review isn't feasible. Also use when the user asks about complecting, simplicity vs. easiness, structural coupling, or concept deduplication. Trigger on phrases like "is this simple", "does this complect", ...documentationgoshellVotes: 0GitHub stars: 959
Forge PrAWrite engaging PR titles and descriptions for any forge (GitHub today; Bitbucket planned). Use when creating or updating PRs. Leads with narrative paragraphs and reaches for lists, tables, and diagrams when content is genuinely structured.documentationgoshellVotes: 0GitHub stars: 959
Fact CheckAAudit code for correctness and rigor — logic errors, silent error swallowing, wishful thinking, and unjustified fallbacks. This is not a style review; it's a logic review. Use when you want a focused correctness audit separate from the full code-police pass.documentationgogitVotes: 0GitHub stars: 959
Dpella McpAReference for the dpella/mcp Haskell library — types, handler shape, transports, and the conventions Emanote uses. Load this before adding MCP resources/tools/subscriptions so you don't re-discover the API by WebFetch.documentationgitapiVotes: 0GitHub stars: 959
CiAReference for the `odu` runner — how to invoke a full pipeline, a single recipe, or a platform-pinned node, and how to attach to a live run, from a project whose CI odu runs. Trigger when the user asks to "run CI", "run the pipeline", "re-run a check", to run named lanes or recipes (e.g. "run fmt and nix", "just the e2e lane", bare selectors like `fmt`/`nix`/`e2e`), or names a recipe by `<recipe>@<platform>`. This skill — not a repo's local `just ci` / `just <recipe>` — is how an odu-run requ...documentationgoshellVotes: 0GitHub stars: 959
BeAModern, interactive alternative to `/do` — clarify intent up front, then take a task end-to-end with a serial AI review gauntlet (lens debate (lowy ⇄ hickey) → codex debate → simplify → code-police, each editing the branch in turn) → CI → evidence. ONLY invoke when the user explicitly types `/be` or `$be`; never auto-select from a natural-language request.documentationtypescriptrustVotes: 0GitHub stars: 959
Be ReviewARun /be's review gauntlet SERIALLY — /lens-debate (lowy ⇄ hickey), then /codex-debate, then /simplify, then code-police, each editing and committing on the live branch in turn. Use from /be §4, or when the user asks to "run the review gauntlet". Requires Claude Code's Skill tool.documentationrustgoVotes: 0GitHub stars: 959
Update UpstreamABump the manifold3d pin, add FFI + safe wrappers for new upstream C API functions, bump versions, open a PRdocumentationgogitVotes: 0GitHub stars: 20
ReviewARun a deep code review across the manifold-csg cratesdocumentationpythonrustVotes: 0GitHub stars: 20
PublishBPublish crates to crates.io with pre-flight checksdocumentationpythongoVotes: 0GitHub stars: 20
Swiftui View RefactorARefactor and review SwiftUI view files for consistent structure, dependency injection, and Observation usage. Use when asked to clean up a SwiftUI view’s layout/ordering, handle view models safely (non-optional when possible), or standardize how dependencies and @Observable state are initialized and passed.documentationswiftexpressVotes: 0GitHub stars: 334
Swift Concurrency ExpertASwift Concurrency review and remediation for Swift 6.2+. Use when asked to review Swift Concurrency usage, improve concurrency compliance, or fix Swift concurrency compiler errors in a feature or file.documentationswiftVotes: 0GitHub stars: 334
Releasing SoftwareAUse when preparing a release, tagging a version, or when user says "release", "tag", "ship it", "push to production" - ensures all release artifacts are verified before tagging to avoid the retag-four-times failure patterndocumentationrustgoVotes: 0GitHub stars: 334
App Store ChangelogACreate user-facing App Store release notes by collecting and summarizing all user-impacting changes since the last git tag (or a specified ref). Use when asked to generate a comprehensive release changelog, App Store "What's New" text, or release notes based on git history or tags.documentationgogitVotes: 0GitHub stars: 334
Grill With DocsAGrilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when the user wants to stress-test a plan against the project's language and documented decisions. Run BEFORE /claude-setup:build on non-trivial features in repos that have (or should have) a CONTEXT.md.documentationdocumentationVotes: 0GitHub stars: 31
Grill With DocsAGrilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when the user wants to stress-test a plan against the project's language and documented decisions. Run BEFORE /build on non-trivial features in repos that have (or should have) a CONTEXT.md.documentationdocumentationVotes: 0GitHub stars: 31