Claude Skills

Setup the Ralph autonomous AI coding loop - ships features while you sleep

Creates complete Claude Code plugin packages with manifests, agents, skills, hooks, and marketplaces following official schema. Use when creating new plugins, building marketplaces, or packaging skills for distribution.

Connect Claude to any app. Send emails, create issues, post messages, update databases - take real actions across Gmail, Slack, GitHub, Notion, and 1000+ services.

Create and optimize CLAUDE.md memory files or .claude/rules/ modular rules for Claude Code projects. Comprehensive guidance on file hierarchy, content structure, path-scoped rules, best practices, and anti-patterns. Use when working with CLAUDE.md files, .claude/rules directories, setting up new projects, or improving Claude Code's context awareness.

Scaffolds a new Claude Code plugin with proper structure. Use when creating a new plugin package with skills and manifests.

Creates Claude Code rule files for .claude/rules/. Writes conventions and shared guidelines that auto-inject into context. Use for path-specific coding conventions or shared project guidelines. NOT for constitution/laws (use <law> in CLAUDE.md instead).

Creates Claude Code hooks for static analysis and code quality. Provides pre-built linting, formatting, and type-checking hooks. Use when setting up project quality gates, enforcing code standards, or adding pre-commit style checks.

Use when creating new skills, modifying existing skills, or improving skill quality. Use when user says "create a skill", "write a skill", "add capability". Use when a repeated pattern should become reusable.

Use when creating CLAUDE.md, improving existing CLAUDE.md, or setting up project configuration. Use when user says "create CLAUDE.md", "setup project", "add laws", "configure agent".

Use when setting up or migrating Claude Code agent system for a project. Use when user says "setup agent", "migrate agent system", "configure claude code", "add agent system".

Deep codebase exploration. Triggers: research, explore, investigate, understand, deep dive, current state.

This skill should be used when the user asks to "generate documentation", "validate docs", "check doc coverage", "find missing docs", "create code-map", "sync documentation", "update docs", or needs guidance on documentation generation and validation for any repository type. Triggers: doc, documentation, code-map, doc coverage, validate docs.

Distribution and packaging patterns including shell completions, man pages, cross-compilation, and release automation. Use when preparing CLI tools for distribution.

Git troubleshooting techniques including recovering lost commits, fixing merge conflicts, resolving detached HEAD, and diagnosing repository issues. Use when user encounters git errors or needs to recover from mistakes.

Updates the .claude-plugin/marketplace.json file when plugins are added, modified, or removed. Use when creating or updating plugin entries in the marketplace catalog.

Documents architecture WITHOUT implementation. Creates ADR and component docs with status: provisioned. MUST use this skill when user wants to DESIGN or PLAN without implementing: - "provision X", "provision a component", "provision new service" - "design the architecture for X", "design a component" - "plan X", "plan a new service", "plan the architecture" - "document X architecture", "architect X" - "envision X", "sketch X architecture" DO NOT use this skill if prompt contains: - "pattern", "patterns" → route to c3-ref - "ref", "refs" → route to c3-ref - "convention", "standard" → route to c3-ref Key indicator: User wants documentation/design output, NOT code changes. Requires .c3/ to exist. Creates ADR with status: provisioned. For implementation requests, route to c3-alter.

Advanced concurrency patterns with goroutines, channels, context, and synchronization primitives. Use when working with concurrent Go code, implementing parallel processing, or debugging race conditions.

Modern Go patterns, idioms, and best practices from Go 1.18+. Use when user needs guidance on idiomatic Go code, design patterns, or modern Go features like generics and workspaces.