All authors
Claude Skills by damusix
github.com/damusix16 skills0 installs27 views
- Atomic VerifyEvidence-before-claim gate. Auto-triggers when Claude is about to claim "done", "fixed", "passing", "complete", "ready to merge", "looks good", "should work", "should pass", "green", or any synonym. Iron rule: no completion claim without a fresh verification command run in this turn. Dispatches `atomic-reviewer` on code the main agent wrote itself, outside a loop command. Explicit invocation: /atomic-verify.Votes: 0GitHub stars: 96
- Atomic Cli ContribConventions for editing the atomic CLI and command artifacts in this repo. Auto-fires on phrases like "add a CLI subcommand", "wire a new flag", "prompt the user", "add a doctor check", "add a doctor repair", "edit cmd/atomic/main.go", "extend claudeinstall", "add an internal package", "use huh", "add a command", "create a new verb", "add a partial", "render templates", "edit a command", "edit commands/", "create a new command", "edit an agent", "edit agents/", or "add an agent". Contributor-...Votes: 0GitHub stars: 96
- Atomic Release CiDiagnose and fix broken release-please CI in this repo. Auto-fires on "release-please CI is failing", "release branch is out of date", "release branch is stale", "release PR is red", "release-please broke", "fix the release CI", "release branch CI failing", "version branch is behind", "release PR changelog is wrong", "release PR missing work". Contributor-only — never bundled, never installed.Votes: 0GitHub stars: 96
- TemplatesFires when creating or editing docs under {{BUCKET}}/ — new topic files, router subtrees, or edits to existing entries. Use when the user asks to add a note, doc, or topic to {{BUCKET}}, or references a file inside it.Votes: 0GitHub stars: 96
- Atomic BusPeer messaging between concurrent Claude Code sessions over named rooms. Fires when the user wants this session to talk to another running session: "join the bus", "connect to the bus", "join room <name>", "message the backend session", "tell the other session to ...", "delegate this to the frontend session", "hand this off to another session", "coordinate with the other agent", "who else is on the bus", "what rooms are open", "watch the room", "halt the room", "stop the agents". Also fires w...Votes: 0GitHub stars: 96
- Atomic Git DisciplineCompressed commit message and PR body generator. Cuts noise from both while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious; PR bodies state only what the diff can't show, ~120 words max. Use when user says "write a commit", "commit message", "generate commit", "open a PR", "PR description", or invokes /atomic-git-discipline. Auto-triggers when staging changes or authoring a pull request.Votes: 0GitHub stars: 96
- Atomic Visual OptionsPlanning-phase visual comparison aid. Renders 2-4 side-by-side variants per decision dimension as a single throwaway, self-contained HTML file and captures the user's pick as typed terminal codes (e.g. "A2 B3"). Auto-fires on phrases like "show me a few options", "mock up some variants", "let me see this side by side", "visual options for", "compare these layouts", "show layout options", "wireframe some choices". Also invoked by /atomic-plan just-in-time when a design question is genuinely vi...Votes: 0GitHub stars: 96
- Atomic WikiConversational wiki and capture-bucket routing. Fires when the user wants a place, space, or folder for notes, research, tickets, raw dumps, or knowledge capture — checks the <wikis> block in ~/.claude/CLAUDE.md; if the cwd is under a registered realm, creates the folder as a bucket via `atomic wiki bucket add` rather than a bare mkdir. Also fires on "add a bucket", "set up a karpathy wiki", "karpathy realm", "set up a wiki for my projects", "add this to my wiki", "wiki this", "what does my w...Votes: 0GitHub stars: 96
- Atomic WritingOne voice for every file the repo ships: README, docs/guides/, docs/reference/, docs/spec/, docs/design/, docs/research/, docs/wiki/, CLAUDE.md, and the prompt artifacts under commands/, agents/, skills/, rules/, and output-styles/. Clear, direct, technical, and visual wherever the content has a shape. No marketing language, no AI-tell phrases, no em dashes in prose, no throat-clearing. The voice is constant; length is set by what the surface has to carry. Prefer a diagram, table, or tree ove...Votes: 0GitHub stars: 96
- Atomic DebugHypothesis-driven debugging skill. Use when a bug, test failure, crash, or unexpected behavior is reported. Auto-trigger on error pastes or "broken/doesn't work/failing" language. Explicit invocation: /atomic-debug. Output: symptom statement → hypothesis table → cheapest test first → root cause. No symptom-patching. Boundary with atomic-tdd: this skill owns diagnosing an unknown root cause. Once the cause is known and you are writing the fix, that is atomic-tdd's job (failing test first, then...Votes: 0GitHub stars: 96
- Atomic DocumentationDiff-driven documentation surface classifier. Given a diff (staged, branch, or range), reads the project's indexed ## Documentation surfaces table from CLAUDE instructions, matches the diff against it, and emits a structured list of proposed edits. Two modes: maintenance (commit flow — stale/incomplete only, never suggests new pages) and authoring (/documentation explicit — full discovery, gap detection, content generation). Auto-fires on "doc this change", "what surfaces does this touch", "d...Votes: 0GitHub stars: 96
- Atomic ReviewCompressed code review comments. Cuts noise from PR feedback while preserving the actionable signal. Each comment is one line: location, problem, fix. Use when user says "review this PR", "code review", "review the diff", or invokes /atomic-review. Auto-triggers when reviewing pull requests.Votes: 0GitHub stars: 96
- Atomic TddTest-first discipline. Auto-triggers on "let's implement X", "add feature Y", "fix bug Z", "write a test for", "implement", "build out", and similar pre-code-change phrases. Iron rule: failing test exists before production code. Skip only for pure docs/config changes with an explicit "skipped because:" note. Explicit invocation: /atomic-tdd. Boundary with atomic-debug: this skill owns writing or changing code — new behavior, or a fix whose root cause is already understood. Diagnosing why some...Votes: 0GitHub stars: 96
- SolidjsSolidJS framework development skill for building reactive web applications with fine-grained reactivity. Use when working with SolidJS projects including: (1) Creating components with signals, stores, and effects, (2) Implementing reactive state management, (3) Using control flow components (Show, For, Switch/Match), (4) Setting up routing with Solid Router, (5) Building full-stack apps with SolidStart, (6) Data fetching with createResource, (7) Context API for shared state, (8) SSR/SSG confi...Votes: 0GitHub stars: 19
- Memory ManagementThis skill should be used when saving memories, searching for past context, remembering decisions, forgetting memories, or managing the memory store. Trigger phrases include "remember this", "save a memory", "what did we decide about", "search memories", "forget this", "list tags", "rescan architecture". Guides effective use of ai-memory MCP tools (save_memory, search_memories, list_tags, delete_memory, rescan_project_architecture) and slash commands (/remember, /forget).Votes: 0GitHub stars: 19
- Ralph LoopUse when the user asks to "write a ralph prompt", "build something with ralph", "create a ralph loop", "set up ralph", "initialize ralph", "start a new ralph project", "run ralph", "configure ralph", "instantiate a ralph loop", or describes a feature, task, or project they want to build autonomously. The primary workflow is an interactive prompt-writing guide that helps users craft high-quality task prompts through structured clarification. Also covers setup, initialization, and execution.Votes: 0GitHub stars: 19