All authors
Claude Skills by alleneubank
github.com/alleneubank42 skills0 installs0 views
- CoordinatorUse when coordinating agent lanes across hosts or workspaces, starting or resuming a campaign from a tee-up agreement, preparing unattended work, rotating coordinators, or planning a workspace's backlog by theme. Bounded attended implementation needs no coordinator.Votes: 0GitHub stars: 2
- Dissolve DocsUse when the user calls a docs cleanup, a campaign has shipped, or the repo has accumulated narrative, planning, status, handoff, or loop docs whose authoritative content belongs in the standing docs (VISION, BRIEF, SPEC, README).Votes: 0GitHub stars: 2
- DoneUse when claiming a change done, asking for acceptance or a merge, inviting someone to try a build (a bug bash, dogfood run, or visual or design review), requesting a specialist review, or landing reviewed work.Votes: 0GitHub stars: 2
- E2eUse when running or repairing a scripted end-to-end test suite.Votes: 0GitHub stars: 2
- EvalUse when evaluating whether an instruction or workflow change helps agents complete real work, using recorded sessions or bounded comparative tasks.Votes: 0GitHub stars: 2
- Git Rebase SyncUse when syncing a feature branch onto the latest origin base branch via git rebase.Votes: 0GitHub stars: 2
- Git Worktree TidyUse when fetching and pruning a worktree-based repository, removing stale local branches, worktrees, or stashes, or bringing its important branches up to date.Votes: 0GitHub stars: 2
- HandoffUse when preserving enough task context for another agent or future session to continue without the current conversationVotes: 0GitHub stars: 2
- Host TidyUse when a dev host is overloaded, out of memory, or hitting fork/resource limits and stale localnets, orphaned dev daemons, or leftover containers need to be found and cleared safelyVotes: 0GitHub stars: 2
- Live OpsUse when operating on live systems - cutovers, migrations, production config changes, or incident triageVotes: 0GitHub stars: 2
- OnboardUse when preparing a repository for agent work, or when work stalls because a repository does not say how to run or try its product, what a change must demonstrate, which paths are high-risk, or what its brand, design system, and other customer-facing basics are.Votes: 0GitHub stars: 2
- PapercutsUse when you worked around friction in your own tools or environment during a task (a misleading or failing command, missing setup, a dead-end tool call, an unhelpful error, a stale doc), or when asked to triage papercuts.Votes: 0GitHub stars: 2
- Rewrite HistoryUse when the user asks to rebuild a feature branch into a clean, reviewable git historyVotes: 0GitHub stars: 2
- SitrepUse when the user asks for a sitrep, a status report, or "where are we" — on the current campaign or task, on what all agent sessions are doing, or as a written status update for an outside audienceVotes: 0GitHub stars: 2
- Tee UpUse when the user asks to refine or review a draft prompt before it runs; the draft is reviewed, not executed.Votes: 0GitHub stars: 2
- TiltUse when working with Tilt or a Tilt-driven dev environment - starting it, Tiltfile errors, resource status, or logs.Votes: 0GitHub stars: 2
- Writing PlansUse when the user requests an implementation plan, or unresolved dependencies make a brief execution plan useful before work.Votes: 0GitHub stars: 2
- Writing SkillsUse when creating or editing a skill and you need it to be discoverable, concise, and native to the target harnessVotes: 0GitHub stars: 2
- Agent OperabilityUse when designing or changing a CLI, API, control plane, or automation surface that an agent must inspect, operate, and verify safely.Votes: 0GitHub stars: 2
- Atlas Best PracticesUse when working with atlas.hcl, Atlas CLI commands, schema HCL/SQL files, or migration planning and reviews.Votes: 0GitHub stars: 2
- Brief Best PracticesUse when a surface needs a durable quality agreement or the user requests a BRIEF.md; ordinary drafts and repeated edits do not automatically need one.Votes: 0GitHub stars: 2
- Canton Network ReposUse when working with Canton Network participants, DAML smart contracts, Splice applications, or debugging LF version and package ID issues.Votes: 0GitHub stars: 2
- Code LawUse when writing or changing code in any language. Not for prose, docs-only, or config-only changes.Votes: 0GitHub stars: 2
- Fnox CliUse when reading, writing, or piping secrets with fnox — authoring fnox.toml, resolving a secret that comes back empty, diagnosing the caching daemon, or running a program with secrets in its environment.Votes: 0GitHub stars: 2
- GhUse when invoking the GitHub CLI for repository inspection, issues, opening or stacking pull requests (dependent PRs), attachments, release assets, projects, or API access.Votes: 0GitHub stars: 2
- Git Best PracticesUse when creating commits, managing branches, opening PRs, or rewriting history. Not for non-git implementation tasks or repo-specific release policy decisions.Votes: 0GitHub stars: 2
- Go Best PracticesUse when reading or writing Go files (.go, go.mod).Votes: 0GitHub stars: 2
- Nix Best PracticesUse when working with Nix flakes, overlays, shell.nix, or flake.nix files.Votes: 0GitHub stars: 2
- Op CliUse when reading, writing, or piping secrets with the 1Password CLI (op) — resolving op:// references, choosing an account, finding an item, or handling an op auth failure.Votes: 0GitHub stars: 2
- Orbstack Best PracticesUse when working with OrbStack Linux VMs, Docker on macOS, orbctl commands, or orb machine lifecycle.Votes: 0GitHub stars: 2
- Platform ToolingUse when working with Electrobun desktop apps, physical iOS devices through pymobiledevice3, or AXe automation of iOS Simulator.Votes: 0GitHub stars: 2
- Playwright Best PracticesUse when writing or modifying Playwright tests (.spec.ts, .test.ts with @playwright/test imports).Votes: 0GitHub stars: 2
- PlaywriterUse when driving a person's real Chrome through the playwriter CLI — opening sessions, running `-e`/`-f` scripts, downloading files, or reading sites they are signed in to.Votes: 0GitHub stars: 2
- Python Best PracticesUse when reading or writing Python files (.py, pyproject.toml, requirements.txt).Votes: 0GitHub stars: 2
- React Best PracticesUse when reading or writing React components (.tsx, .jsx files with React imports).Votes: 0GitHub stars: 2
- Rust Best PracticesUse when reading or writing Rust files (.rs, Cargo.toml).Votes: 0GitHub stars: 2
- Spec Best PracticesUse when creating, reviewing, updating, interviewing for, completing, or finding gaps in SPEC.md files.Votes: 0GitHub stars: 2
- Tamagui Best PracticesUse when working with Tamagui projects (tamagui.config.ts, @tamagui imports).Votes: 0GitHub stars: 2
- Testing Best PracticesUse when choosing a verifier, running a feature on its closest-to-live surface, capturing UI evidence, deciding whether a check becomes a permanent test, diagnosing an unreliable test, or designing nontrivial regression coverage; routine execution of an established check needs no extra workflow.Votes: 0GitHub stars: 2
- Typescript Best PracticesUse when reading or writing TypeScript or JavaScript files (.ts, .tsx, .js, tsconfig.json).Votes: 0GitHub stars: 2
- Web FetchUse when fetching documentation, articles, or reference pages from HTTP or HTTPS URLs as clean Markdown.Votes: 0GitHub stars: 2
- Zig Best PracticesUse when reading or writing Zig files (.zig, build.zig, build.zig.zon).Votes: 0GitHub stars: 2