cc-thingz

In the author's own words, from each skill's SKILL.md — showing the first 27 of 189 files.

• brainstorming-ideas

  Brainstorm ideas and stress-test draft plans before coding. Use when brainstorming, exploring approaches, designing a feature/API/flow, grilling or debating a bounded plan, challenging assumptions, or resolving design-blocking terminology. NOT for implementation task breakdown. NOT for generic technology comparisons or best-practice research; use researching-web. NOT for docs updates; use documen…

  src/skills/brainstorming-ideas/SKILL.md on GitHub (opens in a new tab)

• browser-automation

  Browser automation for rendered UI exploration, validation, screenshots, recordings, and end-to-end flows. Use when a task needs an actual browser or rendered DOM: inspect UI state, click/fill forms, debug frontend behavior, capture evidence, verify a feature, or run/generate browser tests. NOT for API checks or pure logic tests where curl, unit tests, or JSDOM is cheaper.

  src/skills/browser-automation/SKILL.md on GitHub (opens in a new tab)

• cleanup-git

  Remove merged local branches and stale git worktrees. Use when the user says "cleanup branches", "prune worktrees", "tidy git", "remove merged branches", "delete merged branches", "gone branches", or wants to clean local git state. NOT for creating commits, creating worktrees, or configuring git hooks.

  src/skills/cleanup-git/SKILL.md on GitHub (opens in a new tab)

• committing-code

  Create normal git commits with logical grouping. Use when committing, saving changes, creating commits, or grouping work into commits. NOT for amending, rebasing, force-pushing, or rewriting history.

  src/skills/committing-code/SKILL.md on GitHub (opens in a new tab)

• configuring-git-hygiene

  Configure safe git workflow hygiene: pre-commit/pre-push hooks, Gitleaks secret scanning, .gitignore rules, local git config, and guardrails. Use when setting up git hooks, gitleaks/git leaks, staged pre-commit checks, pre-push validation, core.hooksPath, .gitignore, or git config best practices. NOT for creating commits (use committing-code), cleaning branches/worktrees (use cleanup-git), or cre…

  src/skills/configuring-git-hygiene/SKILL.md on GitHub (opens in a new tab)

• documenting-code

  Write, rewrite, or update project docs from implementation facts - README front pages, user guides, configuration references, architecture docs, evaluations, agent instructions, and code comments. Use when docs are stale after a change, or when a doc set must become clear, visual, and consistent with the code. NOT for release preparation or release notes (use releasing-code), external library doc…

  src/skills/documenting-code/SKILL.md on GitHub (opens in a new tab)

• evolving-config

  Audit and improve AI coding-agent configuration. Use when reviewing or changing Claude Code, Pi, Codex, Copilot, Cursor, Grok, skill, agent, hook, MCP, permission, package, or generated-export setup. Default is review-only; fixes require explicit user approval or --fix. NOT for score-only instruction review or prompt lint; use reviewing-instructions. NOT for application config, git hygiene, code…

  src/skills/evolving-config/SKILL.md on GitHub (opens in a new tab)

• fixing-code

  Fix code defects with a reproducible feedback loop, root-cause diagnosis, minimal patch, regression test, and clean verification. Use when debugging, diagnosing, or resolving lint/test/build failures. NOT for test-suite cleanup without a production bug (use improving-tests), or code review findings without fixes (use reviewing-code).

  src/skills/fixing-code/SKILL.md on GitHub (opens in a new tab)

• improving-tests

  Improve test design, speed, and coverage with behavior-focused tests, useful seams, characterization tests, TDD, and test refactoring. Use when improving tests, optimizing slow suites, adding coverage, refactoring brittle tests, removing test waste, or working test-first. NOT for fixing production bugs (use fixing-code), or reviewing non-test code quality (use reviewing-code).

  src/skills/improving-tests/SKILL.md on GitHub (opens in a new tab)

• installation-doctor

  Diagnose 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.

  src/skills/installation-doctor/SKILL.md on GitHub (opens in a new tab)

• looking-up-docs

  Find exact, version-correct library/API/framework docs through one lookup workflow. Use when the user says "look up docs", "how to use", "API for", "syntax for", "examples of", "show me the docs", mentions "ctx7"/"Context7", passes a `/org/project` library ID, or needs API signatures, config keys, syntax, examples, or versioned docs. NOT for comparisons, current-state or release-behavior question…

  src/skills/looking-up-docs/SKILL.md on GitHub (opens in a new tab)

• operating-infra

  Author, inspect, troubleshoot, review, and apply (after explicit confirmation) infrastructure across IaC, Kubernetes, cloud resources, containers, CI/CD, and Linux hosts. Use when changing Terraform/OpenTofu, Kubernetes, Helm, Kustomize, Dockerfiles, GitHub Actions workflow/job/permissions semantics, AWS, GCP, Cloud Run, BigQuery, IAM, logs, instances, or service health, or when the user says "de…

  src/skills/operating-infra/SKILL.md on GitHub (opens in a new tab)

• releasing-code

  Prepare, 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.

  src/skills/releasing-code/SKILL.md on GitHub (opens in a new tab)

• researching-web

  Web research via platform web tools. Use for technical comparisons, current-state and release-behavior questions, recent facts, ecosystem news, best practices, standards, or questions needing grounded web evidence. NOT for exact API syntax, config keys, or code examples — use looking-up-docs for those. NOT for repo-specific questions — search local files first.

  src/skills/researching-web/SKILL.md on GitHub (opens in a new tab)

• reviewing-code

  Use when reviewing changed code, PRs, diffs, or specific files. Finds evidence-backed defects in security, correctness, tests, reliability, performance, maintainability, and docs. Supports quick, standard, deep, team, and external-review modes, plus a simplify mode for over-engineering and "what can we delete" reviews. NOT for repo-wide architecture review, general codebase exploration, fixing is…

  src/skills/reviewing-code/SKILL.md on GitHub (opens in a new tab)

• reviewing-instructions

  "Use when asked to lint, audit, review, or score AI-facing instruction files such as SKILL.md, AGENT.md, AGENTS.md, CLAUDE.md, platform body.md files, prompt files, rules, policies, and agent-facing references. NOT for plugin manifests, application code review, harness configuration review, ordinary docs, tests, or generated build output. "

  src/skills/reviewing-instructions/SKILL.md on GitHub (opens in a new tab)

• spec-flow

  Use when planning, executing, checkpointing, finishing, or inspecting lightweight spec-driven work. Runs one task at a time using `.spec/` markdown files and the bundled `specctl` helper. NOT for broad product discovery beyond a short requirement interview. NOT for generic implementation planning that does not read or write `.spec/` files.

  src/skills/spec-flow/SKILL.md on GitHub (opens in a new tab)

• using-git-worktrees

  Creates and removes isolated git worktrees for parallel development. Use when starting feature work needing isolation, working on multiple branches simultaneously, or removing one specific worktree and its branch after its PR merges. NOT for simple branch switching, sweeping multiple stale worktrees or merged branches at once (use cleanup-git), or git hook/config setup (use configuring-git-hygien…

  src/skills/using-git-worktrees/SKILL.md on GitHub (opens in a new tab)

• writing-csharp

  Idiomatic C# /.NET development. Use when writing C# code, changing `.csproj` or `.sln`, or working on ASP.NET Core apps, libraries, CLIs, workers, and xUnit/NUnit/MSTest suites. Emphasizes nullable references, async/await, boundary validation, focused `dotnet` feedback, and minimal dependencies. NOT for Go, Python, TypeScript, shell scripts, or infra-only work.

  src/skills/writing-csharp/SKILL.md on GitHub (opens in a new tab)

• writing-go

  Idiomatic Go development. Use when writing Go code, designing APIs, reviewing Go implementations, or changing Go tests. Follow the module's target Go version. Prefer stdlib, concrete types, explicit errors, goroutine ownership, fast feedback, and behavior tests. NOT for Python, Rust, TypeScript, shell scripts, or infra-only work.

  src/skills/writing-go/SKILL.md on GitHub (opens in a new tab)

• writing-java-kotlin

  Idiomatic modern Java and Kotlin JVM development. Use when writing `.java`, `.kt`, or `.kts` code; changing Gradle or Maven builds; or working on Spring, Micronaut, Quarkus, Ktor, Android JVM modules, JUnit, Mockito, Kotest, ktlint, detekt, or JVM CLI/services. Emphasizes JDK toolchains, null-safety, fast focused Gradle/Maven feedback, deterministic formatting, and minimal dependencies. NOT for J…

  src/skills/writing-java-kotlin/SKILL.md on GitHub (opens in a new tab)

• writing-python

  Idiomatic Python 3.12+ development. Use when writing Python code, CLI tools, scripts, or services. Emphasizes stdlib, type hints, fast pytest feedback, uv/ruff/pyright toolchain, optional project-adopted ty, and minimal dependencies. NOT for Go, Rust, TypeScript, or shell-only tasks.

  src/skills/writing-python/SKILL.md on GitHub (opens in a new tab)

• writing-rust

  Idiomatic Rust development. Use when writing Rust code, Cargo crates/workspaces, Rust tests, or rustfmt/clippy/cargo workflows. Emphasizes ownership, Result errors, small APIs, stdlib-first dependencies, fast cargo feedback, and behavior tests. NOT for Go, Python, TypeScript, shell scripts, or infra-only work.

  src/skills/writing-rust/SKILL.md on GitHub (opens in a new tab)

• writing-shell

  Idiomatic shell development for POSIX sh, Bash, Zsh, Fish, hooks, CI shell steps, and scriptable CLI glue. Use when writing or changing `.sh`, `.bash`, `.zsh`, `.fish`, `.bats`, shell functions, shell pipelines, CI `run:` shell bodies, or command-runner recipes. Emphasizes portability, quoting, safe filesystem/process handling, non-TUI CLI tools, ShellCheck, shfmt, Bats, and ShellSpec. NOT for Py…

  src/skills/writing-shell/SKILL.md on GitHub (opens in a new tab)

• writing-skills

  Create, split, slim, or rewrite repository skills. Use when adding a new `src/skills/<name>/` skill, editing a skill description, frontmatter, references, overlays, or plugin placement, or tightening routing between neighboring skills. NOT for score-only instruction review; use reviewing-instructions. NOT for broad agent/package config audits; use evolving-config. NOT for ordinary docs; use docum…

  src/skills/writing-skills/SKILL.md on GitHub (opens in a new tab)

• writing-typescript

  Idiomatic TypeScript development. Use when writing TypeScript code, Node.js services, React apps, or TypeScript design advice. Emphasizes strict typing, boundary validation, composition, fast feedback, behavior tests, and project-configured tooling. NOT for Go, Python, Rust, plain HTML/CSS/JS, or server-rendered templates (use writing-web).

  src/skills/writing-typescript/SKILL.md on GitHub (opens in a new tab)

• writing-web

  Simple web development with HTML, CSS, JS, and HTMX. Use when working with .html, .css, or .htmx files, web templates, stylesheets, or vanilla JS scripts. NOT for React/Vue/Angular (use writing-typescript) or Node.js backends.

  src/skills/writing-web/SKILL.md on GitHub (opens in a new tab)

No skill matches that filter.

Similar skills

• skillsby wondelai Wondel.ai Agent Skills — Business, Marketing, UX & Coding Frameworks from Bestselling Books. 50 skills + 12 guided journeys for Claude Code… 2.4k stars · 30 skills
• ponytailby DietrichGebert Makes your AI agent think like the laziest senior dev in the room. The best code is the code you never wrote. 164k stars · 6 skills
• marketingskillsby coreyhaines31 Marketing skills for Claude Code and AI agents. CRO, copywriting, SEO, analytics, and growth engineering. 54.9k stars · 30 skills
• autoharnessby tigerless-labs Autoharness — a self-learning skill layer for Claude Code — distills skills from your real sessions, updates them as you work, and prunes t… 11.1k stars · 1 skill
• superpowers-zhby jnMetaCode 🦸 AI 编程超能力 · 中文增强版 — superpowers（250k+ ⭐）完整汉化 + 4 个中国原创 skills，让 Claude Code / Copilot CLI / Hermes Agent / Cursor / Windsurf / Kiro / Gemi… 8.3k stars · 20 skills
• gentle-aiby Gentleman-Programming Gentle-AI configures the AI coding agents you already use: Claude Code, Cursor, OpenCode, Codex, Pi, and more. Choose persistent memory, Or… 7.8k stars · 20 skills