Discover Testing & security skills, compare source repositories and read the instructions for each workflow.
Analyzes CI/CD pipelines to identify common antipatterns (like slow feedback loops or sequential steps) and recommends best practice patterns (like build images, parallelization, and build-once-deploy-anywhere)...
Provides paths to cc-track utility scripts for validation, task completion, and git operations. Use when a cc-track command needs to run a script.
Go testing conventions and patterns. Use when writing tests, discussing coverage, or editing _test.go files. Triggers: test organization, black-box testing, table-driven tests, HTTP mocking, coverage criteria,...
Core Go development patterns and idioms. Use for package design, code organization, configuration patterns, interface definitions, or when editing .go files. Triggers: package structure, dependency hierarchy, i...
Describe when this skill should be invoked. Include: - Trigger keywords (e.g., authentication, API design) - File patterns (e.g., when editing *.go files) - Use cases (e.g., implementing login flows)
ImageMagick integration patterns for Go. Use when processing images, rendering documents, or integrating ImageMagick commands. Triggers: image processing, document rendering, magick command, image conversion, P...
Container and infrastructure patterns for Go applications. Use when working with Dockerfiles, external binaries, or deployment configuration. Triggers: containerization, external binary integration, dependency...
Describe when this skill should be invoked. Include trigger keywords, file patterns, and explicit use cases. The more specific, the better Claude can determine when to load this skill.
Go library development patterns. Use when designing library APIs, implementing extensibility, or working on packages in pkg/ directories. Triggers: format extensibility, provider separation, capability composit...
HTTP API development patterns for Go. Use when creating endpoints, handlers, middleware, or error responses. Triggers: API design, HTTP handlers, error handling, functional options, option merging, response for...
Enforces security rules for AAW sessions. Activated automatically when handling sensitive operations, external connections, package installations, or file access to protected paths.
Enforces AAW standard operating procedures. Use this when working on any code changes that need to be auditable. Ensures proper workflow: plan -> implement -> test -> evidence.
Implement CQRS (Command Query Responsibility Segregation) pattern for Electron services. Use when creating service methods, separating read/write operations, or implementing reactive data streams with Observabl...
Advanced patterns for Hono-based Electron IPC including CQRS, Zod validation, error handling, and reactive data with RxJS. Use when implementing complex IPC patterns or needing guidance on architecture decision...
Implement reactive state management with Jotai atoms in Electron renderer. Use when creating atoms, implementing real-time updates via IPC, or setting up hybrid stream + HTTP fallback patterns. Covers event sub...
Set up Hono-based type-safe IPC architecture for Electron applications. Use when implementing IPC communication, creating routes between main and renderer processes, or migrating from traditional ipcRenderer to...
Implement type-safe IPC communication in Electron using Hono RPC. Use when creating API routes between main and renderer processes, setting up typed clients, or implementing request/response IPC patterns. Provi...
Design system architecture, create technical specifications, and make architectural decisions
Create videos for demos and marketing
Create beautiful, production-ready interfaces using Gemini with design system constraints
Comprehensive web research with synthesis and actionable insights
Identify and fix security vulnerabilities in code and infrastructure
Manage database operations, migrations, RLS policies, and performance optimization
Rapidly build and launch micro-SaaS applications with best practices, monetization, and deployment
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.