golang-dependency-management
Dependency management strategies for Golang projects — go.mod management, installing/upgrading packages, Minimal Version Selection, vulnerability scanning, outdated dependency tracking, binary size analysis, Dependabot/Renovate setup, conflict resolution, and go.work workspaces. Use when adding, removing, or upgrading Go dependencies, auditing vulnerabilities, resolving version conflicts, or setting up automated dependency updates.
golang-design-patterns
Idiomatic Golang design patterns — functional options, constructors, error flow and cascading, resource management and lifecycle, graceful shutdown, resilience, architecture, dependency injection, data handling, streaming, and more. Apply when explicitly choosing between architectural patterns, implementing functional options, designing constructor APIs, setting up graceful shutdown, applying resilience patterns, or asking which idiomatic Go pattern fits a specific problem.
golang-documentation
Comprehensive documentation guide for Golang projects, covering godoc comments, README, CONTRIBUTING, CHANGELOG, Go Playground, Example tests, API docs, and llms.txt. Use when writing or reviewing doc comments, documentation, adding code examples, setting up doc sites, or discussing documentation best practices. Triggers for both libraries and applications/CLIs.
golang-error-handling
Idiomatic Golang error handling — creation, wrapping with %w, errors.Is/As, errors.Join, custom error types, sentinel errors, panic/recover, the single handling rule, structured logging with slog, HTTP request logging middleware, and samber/oops for production errors. Built to make logs usable at scale with log aggregation 3rd-party tools. Apply when creating, wrapping, inspecting, or logging errors in Go code. For samber/oops specifics → See `samber/cc-skills-golang@golang-samber-oops` skill; for slog handler ecosystem → See `samber/cc-skills-golang@golang-samber-slog` skill.
golang-grpc
Provides gRPC usage guidelines, protobuf organization, and production-ready patterns for Golang microservices. Use when implementing, reviewing, or debugging gRPC servers/clients, writing proto files, setting up interceptors, handling gRPC errors with status codes, configuring TLS/mTLS, testing with bufconn, or working with streaming RPCs.
golang-lint
Linting best practices and golangci-lint configuration for Golang projects — running linters, configuring .golangci.yml, suppressing warnings with nolint directives, interpreting lint output, and selecting linters. Use when configuring golangci-lint, asking about lint warnings or nolint suppressions, setting up code quality tooling, or choosing linters. Also use when the user mentions golangci-lint, go vet, staticcheck, or revive.
golang-modernize
Modernize Golang code to use recent language features, standard library improvements, and idiomatic patterns. Trigger proactively when writing or reviewing Go code and old-style patterns are detected, or when encountering a deprecation warning. Also use when the user explicitly asks for modernization, a Go version upgrade, or a CI/tooling refresh.
golang-naming
Go (Golang) naming conventions — covers packages, constructors, structs, interfaces, constants, enums, errors, booleans, receivers, getters/setters, functional options, acronyms, test functions, and subtest names. Use this skill when writing new Go code, reviewing or refactoring, choosing between naming alternatives (New vs NewTypeName, isConnected vs connected, ErrNotFound vs NotFoundError, StatusReady vs StatusUnknown at iota 0), debating Go package names (utils/helpers anti-patterns), or asking about Go naming best practices. Also trigger when the user mentions MixedCaps vs snake_case, ALL_CAPS constants, Get-prefix on getters, or error string casing. Do NOT use for general Go implementation questions that don't involve naming decisions.
golang-observability
Golang everyday observability — the always-on signals in production. Covers structured logging with slog, Prometheus metrics, OpenTelemetry distributed tracing, continuous profiling with pprof/Pyroscope, server-side RUM event tracking, alerting, and Grafana dashboards. Apply when instrumenting Go services for production monitoring, setting up metrics or alerting, adding OpenTelemetry tracing, correlating logs with traces, migrating legacy loggers (zap/logrus/zerolog) to slog, adding observability to new features, or implementing GDPR/CCPA-compliant tracking with Customer Data Platforms (CDP). Not for temporary deep-dive performance investigation (→ See `samber/cc-skills-golang@golang-benchmark` and `samber/cc-skills-golang@golang-performance` skills).
golang-performance
Golang performance optimization patterns and methodology - if X bottleneck, then apply Y. Covers allocation reduction, CPU efficiency, memory layout, GC tuning, pooling, caching, and hot-path optimization. Use when profiling or benchmarks have identified a bottleneck and you need the right optimization pattern to fix it. Also use when performing performance code review to suggest improvements or benchmarks that could help identify quick performance gains. Not for measurement methodology (→ See `samber/cc-skills-golang@golang-benchmark` skill) or debugging workflow (→ See `samber/cc-skills-golang@golang-troubleshooting` skill).
golang-popular-libraries
Recommends production-ready Golang libraries and frameworks. Apply when the user explicitly asks for library suggestions, wants to compare alternatives, needs to choose a library for a specific task, or when a new dependency is being added to the project.
golang-project-layout
Provides a guide for setting up Golang project layouts and workspaces. Use when starting a new Go project, organizing an existing codebase, setting up a monorepo with multiple packages, creating CLI tools with multiple main packages, deciding between cmd/internal/pkg directory conventions, or discussing package restructuring, package splits, or module splits.
golang-safety
Defensive Golang coding to prevent panics, silent data corruption, and subtle runtime bugs. Use when encountering nil panics, append aliasing, map concurrent access, float comparison pitfalls, or zero-value design questions. Also use when reviewing code for nil-safety, numeric conversion overflow, resource lifecycle issues (defer in loops), or defensive copying of slices and maps.
golang-samber-do
Dependency injection in Golang using samber/do — service containers, lifecycle management, scopes, health checks, graceful shutdown, and module organization. Apply when using or adopting samber/do, when the codebase imports github.com/samber/do or github.com/samber/do/v2, or when refactoring manual constructor injection into a DI container.
golang-samber-hot
In-memory caching in Golang using samber/hot — eviction algorithms (LRU, LFU, TinyLFU, W-TinyLFU, S3FIFO, ARC, TwoQueue, SIEVE, FIFO), TTL, cache loaders, sharding, stale-while-revalidate, missing key caching, and Prometheus metrics. Apply when using or adopting samber/hot, when the codebase imports github.com/samber/hot, or when the project repeatedly loads the same medium-to-low cardinality resources at high frequency and needs to reduce latency or backend pressure.
golang-samber-lo
Functional programming helpers for Golang using samber/lo — 500+ type-safe generic functions for slices, maps, channels, strings, math, tuples, and concurrency (Map, Filter, Reduce, GroupBy, Chunk, Flatten, Find, Uniq, etc.). Core immutable package (lo), concurrent variants (lo/parallel aka lop), in-place mutations (lo/mutable aka lom), lazy iterators (lo/it aka loi for Go 1.23+), and experimental SIMD (lo/exp/simd). Apply when using or adopting samber/lo, when the codebase imports github.com/samber/lo, or when implementing functional-style data transformations in Go. Not for streaming pipelines (→ See `samber/cc-skills-golang@golang-samber-ro` skill).
golang-samber-mo
Monadic types for Golang using samber/mo — Option, Result, Either, Future, IO, Task, and State types for type-safe nullable values, error handling, and functional composition with pipeline sub-packages. Apply when using or adopting samber/mo, when the codebase imports `github.com/samber/mo`, or when considering functional programming patterns as a safety design for Golang.
golang-samber-oops
Structured error handling in Golang with samber/oops — error builders, stack traces, error codes, error context, error wrapping, error attributes, user-facing vs developer messages, panic recovery, and logger integration. Apply when using or adopting samber/oops, or when the codebase already imports github.com/samber/oops.
golang-samber-ro
Reactive streams and event-driven programming in Golang using samber/ro — ReactiveX implementation with 150+ type-safe operators, cold/hot observables, 5 subject types (Publish, Behavior, Replay, Async, Unicast), declarative pipelines via Pipe, 40+ plugins (HTTP, cron, fsnotify, JSON, logging), automatic backpressure, error propagation, and Go context integration. Apply when using or adopting samber/ro, when the codebase imports github.com/samber/ro, or when building asynchronous event-driven pipelines, real-time data processing, streams, or reactive architectures in Go. Not for finite slice transforms (→ See `samber/cc-skills-golang@golang-samber-lo` skill).
golang-samber-slog
Structured logging extensions for Golang using samber/slog-**** packages — multi-handler pipelines (slog-multi), log sampling (slog-sampling), attribute formatting (slog-formatter), HTTP middleware (slog-fiber, slog-gin, slog-chi, slog-echo), and backend routing (slog-datadog, slog-sentry, slog-loki, slog-syslog, slog-logstash, slog-graylog...). Apply when using or adopting slog, or when the codebase already imports any github.com/samber/slog-* package.
context7-documentation-fetcher
Automatically fetches up-to-date library documentation from Context7 when code generation, setup instructions, or API documentation is needed
document
Markdown 文档编写规范，包括目录结构、README 内容规范、版本记录和代码示例规范
async-python-patterns
Master Python asyncio, concurrent programming, and async/await patterns for high-performance applications. Use when building async APIs, concurrent systems, or I/O-bound applications requiring non-blocking operations.
git-commit
Git 提交规范和分支 management 最佳实践，包括 Conventional Commits 格式和分支命名约定
cpp-dev
现代 C++ (C++17/20) 编码规则和最佳实践，包括 STL、智能指针、RAII 和性能优化
gitflow
Gitflow 工作流规则，包括分支策略、版本控制、PR 规则和发布流程
python-dev
Python 编码规则和最佳实践，包括 PEP 8 风格、类型注解、虚拟环境、测试和文档规范
riper-5
RIPER-5 严格模式协议，包含研究、创新、规划、执行、审查五个阶段的代码开发工作流
skill-creator
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
typescript-dev
TypeScript 编码规则和最佳实践，包括类型系统、严格模式、泛型和工具类型使用
code-reviewer
Comprehensive code review skill for TypeScript, JavaScript, Python, Swift, Kotlin, Go. Includes automated code analysis, best practice checking, security scanning, and review checklist generation. Use when reviewing pull requests, providing code feedback, identifying issues, or ensuring code quality standards.
twilight-zone-writer
Génère une nouvelle complète style Twilight Zone (8000-15000 mots) EN FRANÇAIS inspirée par un sujet scientifique/technologique. Utilise ce Skill pour créer une fiction autonome avec twist inattendu, exploration philosophique de la condition humaine, et conclusion réflexive dans l'esprit authentique de Rod Serling. Référence obligatoire: twilight_zone_episodes.json.
dialogue
Crée le dialogue intérieur et la réflexion profonde pour l'Acte V d'un épisode NEW TEMPS X. Utilise ce Skill quand tu dois créer une réflexion intime, un dialogue intérieur, ou une méditation sur les implications profondes du sujet scientifique traité dans l'épisode.
fiction-writer
Écrit un court segment fictionnel immersif pour l'Acte IV d'un épisode NEW TEMPS X. Utilise ce Skill quand tu dois créer une scène fictionnelle qui illustre les implications d'un sujet scientifique, faire ressentir plutôt qu'expliquer, ou créer une résonance émotionnelle à travers la fiction.
narrative-conductor
Définit l'arc narratif complet et valide la cohérence narrative pour les épisodes NEW TEMPS X. Utilise ce Skill quand tu dois créer ou valider un arc narratif structuré en 7 actes, ou vérifier qu'un épisode respecte la structure narrative obligatoire et l'esprit Temps X.
narrative-validator
Valide la cohérence narrative complète d'un épisode NEW TEMPS X, y compris la validation des liens web. Utilise ce Skill quand tu dois vérifier qu'un épisode respecte la structure en 7 actes, valider la qualité narrative, vérifier que tous les liens sont accessibles et pertinents, rejeter les contenus de type "blog post" ou "Wikipedia", ou garantir l'esprit Temps X.
science-editor
Explique les concepts scientifiques de manière claire et accessible pour les Actes I, II et III d'un épisode NEW TEMPS X. Utilise ce Skill quand tu dois expliquer des concepts scientifiques, créer une introduction intrigante, décrypter un mécanisme scientifique, ou poser des questions ouvertes sur un sujet scientifique.
audience
Crée la question ouverte finale et transmet la réflexion au public pour l'Acte VII d'un épisode NEW TEMPS X. Utilise ce Skill quand tu dois créer une conclusion qui ouvre une réflexion, poser une question profonde non résolue, ou transmettre une interrogation au public de manière subtile et engageante.
archivist
Connecte les prédictions et visions du passé aux réalités présentes pour l'Acte VI d'un épisode NEW TEMPS X. Utilise ce Skill quand tu dois créer un pont temporel entre les années 1980 (Temps X original) et aujourd'hui, évoquer la mémoire collective, ou réfléchir sur l'écart entre prédictions passées et réalité présente.
fto-analyst
Autonomous Freedom to Operate analysis agent. Identifies blocking patents, assesses infringement risk, and recommends mitigation strategies for product commercialization.
patent-examiner
Autonomous patent examination agent. Simulates USPTO examination by analyzing applications for compliance with 35 U.S.C. §§ 101, 102, 103, 112 and identifying potential office action issues.
prior-art-hunter
Autonomous prior art search and analysis agent. Searches multiple databases, analyzes references, creates claim charts, and assesses patentability impact.
claims-engineer
Autonomous claims drafting and optimization agent. Drafts, analyzes, and refines patent claims to maximize protection while ensuring validity.
patent-drafter
Autonomous patent application drafting agent. Drafts complete patent applications including claims, specification, and abstract from invention descriptions.
remotion-best-practices
Best practices for Remotion - Video creation in React
start-session
Use when user says "let's get started", "where are we", or at beginning of a session. Reads project context from CLAUDE.md, checks git status and recent commits, and provides orientation for the session. Works across all repo types (code, research, mixed).
write-article
Write newsletter articles for The Hybrid Builder (chatwithgpt.substack.com) with intelligent cross-referencing of the full article archive. Includes sitemap-based article cache with theme indexing, reference suggestions, session transcript export, and cover image generation. Use when asked to write a blog post, article, or newsletter about a collaboration or technical topic.
wrap-up-session
Use when user says "let's wrap up", "close shop", "done for today", or wants to end a session. Handles session wrap-up including git operations, documentation updates, roadmap updates, and preparing for next session. Works across all repo types.
microsim-vis-network
Create an educational MicroSim using the vis-network JavaScript library. Each MicroSim is a directory located in the /docs/sims folder. It has a main.html file that can be referenced with an iframe. The main.html file imports the main JavaScript code to run the educational MicroSim.
vibe-coder-sdlc
This skill should be used when users want professional SDLC practices with automated git workflows, intelligent code review, and project management without rigid processes. Orchestrates specialized agents for feature development, branch management, language-specific code review, and GitHub integration. Ideal for developers who want to stay in flow while maintaining code quality.
Page 1358 of 1713 · 85646 results
