All authors
Claude Skills by alexei-led
github.com/alexei-led140 skills0 installs159 views
- Writing SkillsCreate or reshape a skill so it loads at the right time, gives the model the result and the finish line, and ships intact to every target. The same rules apply to agent bodies and other AI-facing instruction files; the reviewing-instructions skill scores against them. Done when the skill meets the shape and writing rules below, the rendered Claude skill still holds the base body and its reference links, and the relevant build/test/lint checks pass on what you changed, or you name each check t...Votes: 0GitHub stars: 36
- Writing TypescriptFollow the repository's TypeScript version, tsconfig, package manager, framework, and test runner. In a monorepo, work from the nearest `package.json` and `tsconfig.json` and name the package you chose.Votes: 0GitHub stars: 36
- Writing WebFollow the existing template language, asset pipeline, and conventions. Add a dependency, build step, or framework only when the project already uses it or the user approves; requests that need a SPA framework belong to writing-typescript.Votes: 0GitHub stars: 36
- Brainstorming IdeasBrainstorm ideas and stress-test draft plans before coding. Use whenVotes: 0GitHub stars: 36
- Browser Automation'Browser automation for rendered UI exploration, validation, screenshots,Votes: 0GitHub stars: 36
- Cleanup GitRemove merged local branches and stale git worktrees. Use when the userVotes: 0GitHub stars: 36
- Committing CodeCreate normal git commits with logical grouping. Use when committing,Votes: 0GitHub stars: 36
- Configuring Git Hygiene'Configure safe git workflow hygiene: pre-commit/pre-push hooks, GitleaksVotes: 0GitHub stars: 36
- Documenting CodeWrite, rewrite, or update project docs from implementation facts - READMEVotes: 0GitHub stars: 36
- Evolving ConfigAudit AI coding-agent configuration and report prioritized, evidence-backed findings with the smallest fix for each. Local files come first; official docs and changelogs settle syntax, feature availability, and deprecation. Do not recommend a change on the strength of an uncited blog. For installed cc-thingz resource or version diagnostics, use installation-doctor first and continue here for broader review or authorized changes.Votes: 0GitHub stars: 36
- Fixing CodeFix code defects with a reproducible feedback loop, root-cause diagnosis,Votes: 0GitHub stars: 36
- Improving TestsImprove test design, speed, and coverage with behavior-focused tests,Votes: 0GitHub stars: 36
- Looking Up DocsFind exact, version-correct library/API/framework docs through one lookupVotes: 0GitHub stars: 36
- Operating InfraAuthor, inspect, troubleshoot, review, and apply (after explicitVotes: 0GitHub stars: 36
- Researching WebWeb research via platform web tools. Use for technical comparisons, current-stateVotes: 0GitHub stars: 36
- Reviewing CodeProduce findings, not edits, for the requested diff, PR, changed files, or file list. Read `references/severity-rubric.md` before scoring or reporting: it owns the dimensions, severity, confidence, and score rules. Load a language reference only when a finding needs language or framework semantics; do not read every reference merely because that language is in scope: - C#: `references/csharp.md` - Go: `references/go.md` - Java/Kotlin: `references/java-kotlin.md` - Python: `references/python.m...Votes: 0GitHub stars: 36
- Reviewing InstructionsScore AI-facing instruction files and report findings an author can act on. The target style: outcome and done criteria up front, each rule stated once, hard constraints explicit, nothing the model already knows, portable across agent targets. The writing-skills skill teaches the same style to authors. Done when every in-scope file has a score, a cited reason per dimension, caps applied, and a confidence level, and every finding quotes or locates its evidence.Votes: 0GitHub stars: 36
- Spec FlowUse when planning, executing, checkpointing, finishing, or inspectingVotes: 0GitHub stars: 36
- Using Git WorktreesA worktree gives parallel work its own folder and branch while the main worktree stays clean on the integration branch. Each project gets one sibling root, `<project>.worktrees/`, with one directory per branch named by its slug (`/` → `-`, so `feature/auth` → `feature-auth`). Remove the worktree and branch after the PR merges. A plain branch switch with no parallel work needs no worktree: check `git status --short`, then `git switch <branch>`. Trivial solo one-liners may also stay in the main...Votes: 0GitHub stars: 36
- Writing CsharpIdiomatic C# /.NET development. Use when writing C# code, changing `.csproj`Votes: 0GitHub stars: 36
- Writing GoIdiomatic Go development. Use when writing Go code, designing APIs, reviewingVotes: 0GitHub stars: 36
- Writing Java KotlinIdiomatic modern Java and Kotlin JVM development. Use when writing `.java`,Votes: 0GitHub stars: 36
- Writing PythonIdiomatic Python 3.12+ development. Use when writing Python code, CLIVotes: 0GitHub stars: 36
- Writing RustIdiomatic Rust development. Use when writing Rust code, Cargo crates/workspaces,Votes: 0GitHub stars: 36
- Writing ShellIdiomatic shell development for POSIX sh, Bash, Zsh, Fish, hooks, CIVotes: 0GitHub stars: 36
- Writing SkillsCreate or reshape a skill so it loads at the right time, gives the model the result and the finish line, and ships intact to every target. The same rules apply to agent bodies and other AI-facing instruction files; the reviewing-instructions skill scores against them. Done when the skill meets the shape and writing rules below, the rendered Claude skill still holds the base body and its reference links, and the relevant build/test/lint checks pass on what you changed, or you name each check t...Votes: 0GitHub stars: 36
- Writing TypescriptIdiomatic TypeScript development. Use when writing TypeScript code, Node.jsVotes: 0GitHub stars: 36
- Writing WebSimple web development with HTML, CSS, JS, and HTMX. Use when workingVotes: 0GitHub stars: 36
- Installation DoctorInspect installed resources without a repository checkout. The helper compares files against its bundled release catalog; it does not execute hooks or modify installations.Votes: 0GitHub stars: 36
- Installation DoctorInspect installed resources without a repository checkout. The helper compares files against its bundled release catalog; it does not execute hooks or modify installations.Votes: 0GitHub stars: 36
- Installation DoctorInspect installed resources without a repository checkout. The helper compares files against its bundled release catalog; it does not execute hooks or modify installations.Votes: 0GitHub stars: 36
- Installation DoctorDiagnose cc-thingz plugin installations with the bundled read-only doctor. Use for missing installed skills, helpers, or hook files, stale package versions, duplicate packages, or migration from old cc-thingz packages. NOT for broad agent configuration audits or config edits; use evolving-config.Votes: 0GitHub stars: 36
- Releasing CodePrepare a release, route its publication, write its notes, or repair notes on a published release. Read [notes.md](references/notes.md) when writing or checking release content. Follow the project's own release instructions where they are more specific.Votes: 0GitHub stars: 36
- Releasing CodePrepare a release, route its publication, write its notes, or repair notes on a published release. Read [notes.md](references/notes.md) when writing or checking release content. Follow the project's own release instructions where they are more specific.Votes: 0GitHub stars: 36
- Releasing CodePrepare a release, route its publication, write its notes, or repair notes on a published release. Read [notes.md](references/notes.md) when writing or checking release content. Follow the project's own release instructions where they are more specific.Votes: 0GitHub stars: 36
- Releasing CodePrepare, publish, or repair a software release and write its release notes. Use for cutting a versioned release or editing release notes. NOT for updating an installed package, publishing articles, or discussing a release; for general documentation use documenting-code.Votes: 0GitHub stars: 36
- Writing StyleProduce text that a reader understands in one pass, with the fewest words that preserve its meaning. Explicit user and project requirements override these defaults. Apply the style in the reader's language, not just English. Done when the text states the concrete point, contains no redundant material, and preserves necessary context, risks, and uncertainty. Return the text itself unless the user asks for an explanation or review.Votes: 0GitHub stars: 36
- Writing StyleProduce text that a reader understands in one pass, with the fewest words that preserve its meaning. Explicit user and project requirements override these defaults. Apply the style in the reader's language, not just English. Done when the text states the concrete point, contains no redundant material, and preserves necessary context, risks, and uncertainty. Return the text itself unless the user asks for an explanation or review.Votes: 0GitHub stars: 36
- Writing StyleProduce text that a reader understands in one pass, with the fewest words that preserve its meaning. Explicit user and project requirements override these defaults. Apply the style in the reader's language, not just English. Done when the text states the concrete point, contains no redundant material, and preserves necessary context, risks, and uncertainty. Return the text itself unless the user asks for an explanation or review.Votes: 0GitHub stars: 36
- Writing StyleWrite or edit commit messages, PR/MR descriptions, issues, review comments, and technical discussions. Use for concise, clear engineering communication grounded in facts, without filler or boilerplate. NOT for creating commits (committing-code), project docs (documenting-code), release notes (releasing-code), or AI instructions (writing-skills).Votes: 0GitHub stars: 36