byteforge-loki-logging
Configure Grafana Loki logging using byteforge-loki-logging library for Python/Flask applications. Use when setting up Loki logging, configuring centralized logging, or adding structured JSON logging to any Python project.
flask-docker-deployment
Set up Docker deployment for Flask applications with Gunicorn, automated versioning, and container registry publishing. Use when dockerizing a Flask app, containerizing for production, or setting up CI/CD with Docker.
flask-smorest-api
Set up Flask REST API with flask-smorest, OpenAPI docs, blueprint architecture, and dataclass models. Use when creating a new Flask API server, building REST endpoints, or setting up a production API.
mcp-docker-deployment
Set up Docker deployment for Python MCP servers (FastMCP or low-level mcp.server.Server SDK) with streamable-http transport (preferred) or legacy SSE, automated versioning, and container registry publishing. Use when dockerizing an MCP server, containerizing for remote access, deploying an MCP server behind nginx, or setting up a production MCP server with Docker. Covers Dockerfile, build scripts, docker-compose, and nginx reverse proxy.
mcp-server-nginx-gatekeeper
Use this skill when the user asks to "add a new MCP server behind nginx", "wire an MCP into the mcp.<domain> vhost", "expose an MCP container with gatekeeper auth", or otherwise needs to put a Streamable-HTTP MCP server (FastMCP or low-level SDK) behind nginx with ByteForge Gatekeeper auth (`auth_request /auth`). Emits a shared `conf.d/snippets/mcp-location.conf` (proxy/auth/streaming headers all in one place) and either a single new `location /mcp-<name>` block (brownfield) or the full umbrella vhost from scratch (greenfield). Includes the `.well-known` OAuth-discovery bypass that forces MCP clients like Claude Code to fall back to bearer-token auth, the `/mcp-<name>` → `/mcp` rewrite trio that makes path-prefix routing survive Streamable-HTTP's absolute upstream endpoint, and the buffering/timeout settings that keep streaming connections alive.
postgres-setup
Set up PostgreSQL database with standardized schema.sql pattern. Use when starting a new project that needs PostgreSQL, setting up database schema, or creating setup scripts for postgres.
python-lib-setup
Set up Python project for PyPI publishing or private GitHub distribution with pyproject.toml, src layout, and optional build scripts. Use when creating a new Python package, setting up for PyPI distribution, initializing a Python library project, or setting up a private library distributed via GitHub.
python-project-scaffold
Scaffold a multi-repo Python workspace with models library, core library, Flask backend, and optional sub-projects. Creates directory structure and root CLAUDE.md describing each sub-project and which skills to use next. Use when starting a new Python project, setting up a multi-repo workspace, or scaffolding a project skeleton.
kurrentdb
Provides KurrentDB (EventStoreDB) client code for event sourcing and CQRS. Generates correct package names, connection strings, and API patterns for Python, Node.js, .NET, F#, Go, Java, Rust. Triggers on "kurrentdb", "eventstore", "event sourcing", "append events", "read stream", "subscription", "aggregate", "CQRS".
cc-track-tools
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.
repo-clipboard
Snapshot the current directory into pseudo-XML for LLM context. Use when you need to share a repo (or a sub-tree) with Codex/LLMs, especially for code review/debugging, generating an agent-friendly “repo snapshot”, or piping context into tools like `llm` (see skill $llm-cli). Supports `.gitignore`-aware file discovery, common ignore patterns, extension filtering, regex include/exclude, optional file-list printing, line-range snippets, and writes `/tmp/repo_clipboard.{stdout,stderr}` for reuse.
claude-five-prompting-guide
Guidelines for prompting and building context for Claude 5 generation models (Sonnet 5, Opus 5, Fable 5), based on Anthropic's official guidance from July 2026. Use this skill whenever the user asks how to prompt Claude 5 models, wants to write or review a system prompt, CLAUDE.md, skill, or agent harness targeting these models, mentions "unhobbling", "unknowns", "blind spot pass", "context engineering", or asks why an agentic task came back wrong despite detailed instructions. Also use it when auditing existing prompts or rules for over-constraint, or when migrating prompts written for Claude 4-era models. When invoked with file path arguments, audit those files against the guide (prefer delegating the audit to a read-only sub-agent and returning only findings).
log-binnacle
>
claudify
Esta skill debe usarse cuando el usuario pide "documenta el modulo", "claudify", "generate module docs", "actualiza el CLAUDE.md de este modulo", "onboarding del modulo", "necesito un CLAUDE.md para X", o quiere crear/actualizar un CLAUDE.md a nivel de modulo. Corre como fork en background — no roba contexto a la sesion principal y devuelve solo un resumen de una linea. Genera documentacion token-efficient con referencias LSP-optimizadas (`file::Symbol`) enfocada en informacion no-obvia que ahorra al agente tener que inferirla del codigo.
end-session
Skill de invocacion manual exclusiva, ejecutada por el usuario via /end-session; el modelo nunca debe autoinvocarla. Cierra formalmente una sesion de trabajo: commitea los cambios de logica de negocio y genera un documento de contexto autocontenido para reconstruccion futura de la sesion.
remember
Esta skill debe usarse cuando el usuario pide "recuerda que", "guarda
rulify
Esta skill debe usarse cuando el usuario pide "aligerar el CLAUDE.md", "dividir el CLAUDE.md", "extraer reglas a .claude/rules", "rulify", "claudemd splitter", "convertir secciones del CLAUDE.md en rules bajo demanda", o menciona que su CLAUDE.md crecio demasiado, supera las 200 lineas, o quiere migrar a carga contextual con globs. Divide un CLAUDE.md monolitico en archivos `.claude/rules/*.md` cargados bajo demanda via frontmatter `paths`, fusionando con reglas existentes y dejando el CLAUDE.md base con solo informacion que aplica a todo el proyecto.
stabilize
>
document-endpoints
Esta skill debe usarse cuando el usuario pide "documenta los endpoints", "documenta la API", "documentar las rutas", "document the endpoints", "document the API", "necesito la doc de los endpoints para el frontend", o cuando menciona documentar endpoints HTTP para consumo desde el frontend. Tambien activar cuando el usuario menciona pasar endpoints al frontend, compartir contratos HTTP, o preparar documentacion de rutas REST. No usar para WebSockets ni socket.io (usar document-sockets en su lugar).
document-sockets
Esta skill debe usarse cuando el usuario pide "documenta los sockets", "documenta los eventos", "documentar websockets", "document the sockets", "document socket events", "necesito la doc de los sockets para el frontend", o cuando menciona documentar eventos de socket.io para consumo desde el frontend. Tambien activar cuando el usuario menciona pasar eventos al frontend, compartir contratos de sockets, o preparar documentacion de eventos en tiempo real. No usar para endpoints HTTP REST (usar document-endpoints en su lugar).
domain-restructure
Use this skill when the user asks to "restructure by domain", "group by feature", "apply screaming architecture", "reorganize the architecture", "move everything into modules per domain", "domain-driven folder structure", "my project is organized by layers and I want it by features", or mentions that their code is layer-first (controllers/, services/, models/ at the top) and wants the structure to scream the business. Also use it with the ultracode trigger for architectural restructuring. It runs a PURE STRUCTURAL refactor (zero functional change): it discovers domains via strategic DDD, classifies them core/supporting/generic, moves files into modules/<domain>/<layer>, and rewrites imports — all inside a dedicated worktree, closing with a single green commit. It is NOT for tactical modeling (entities, aggregates, events) — it only reorganizes where files live.
claude-code-agent-creator
Crea archivos markdown de sub-agentes de Claude Code (con YAML frontmatter y system prompt) listos para colocar en ~/.claude/agents/, .claude/agents/ o agents/ de un plugin. Usa esta skill proactivamente cuando el usuario diga "crea un agente", "create an agent", "necesito un sub-agente que...", "scaffold an agent", "haz un auditor", "make a code reviewer agent", "agente que revise", "agente que audite", "agente que investigue", o cuando describa funcionalidad especializada que conviene aislar en un sub-agente (ej. "necesito algo que revise PRs", "quiero un agente que analice seguridad"). Cubre seleccion de tools con principio de menor privilegio, tuning de description para auto-invocacion, eleccion de arquetipo (auditor / researcher / implementer / orchestrator), calibracion de modelo + effort segun la carga de razonamiento de la tarea (mas mecanico = modelo mas ligero y menos effort) e incluye un sistema de scoring de confianza 0-100 con umbral >=80 para agentes tipo auditor.
lib-advisor
>-
plan-constraints
>-
workflow-creator
Designs, writes, or audits dynamic workflows for Claude Code — the JavaScript orchestration scripts the Workflow tool runs to fan many subagents across one large job (triggered by 'ultracode' or by asking to "use a workflow"). Use this skill proactively whenever the user says "create a workflow", "write a dynamic workflow", "orchestrate subagents", "fan out agents", "parallelize this with agents", "codebase-wide audit", "massive bug hunt", "ultracode workflow", "port this from X to Y", "migrate the whole repo", or describes work a single pass can't hold (repo-wide audits, large migrations, language ports, verified multi-source research). Also use it to audit or review an existing workflow script — "audit this workflow", "review my orchestration script", "is this workflow correct", "improve this workflow" — checking data-flow shape, per-role thinking load, and runtime safety. For authoring a single isolated sub-agent that reports back once, this is not the skill. Reach for this even when the user only hints at coordinating many agents or scaling a job beyond one context window.
branching
>
commit
>
conflict-resolver
>
squash-suggester
>
split-component
Esta skill debe usarse cuando el usuario pide "dividir componente", "separar componente", "split component", "extraer componentes", "componente muy grande", "refactorizar componente grande", "break down component", "este archivo tiene muchas responsabilidades", o menciona que un archivo React tiene demasiado codigo, demasiado estado, o demasiada logica mezclada con UI. Analiza un componente React y lo divide en piezas mas manejables siguiendo el patron smart/dumb components.
refactor
>
smell-scan
>
close-design
>
create-specification
Create a new, closed and self-contained specification file optimized for Generative AI consumption and cold execution via the /goal command. Scaffolds the managed Design Gaps section that the close-design loop consumes. Use when the user wants to write a new spec, draft a specification, capture requirements, or plan a substantial change as a cold-executable spec.
implement-spec
>
update-specification
Update an existing specification file optimized for Generative AI consumption, based on new requirements or code changes. Also the living-document maintainer for the spec-kit closure loop: folds accepted Design Gaps into the spec body and removes resolved entries from the managed section. Use when the spec drifted from the code, requirements changed, the implementation diverged, or the user says to sync, revise, or update the spec.
binnacle
>
resume-from-binnacle
>
task-planning
>
retrofit-testing
Esta skill debe usarse cuando el usuario pide "agrega tests a esto", "retrofit tests", "cubre este modulo con tests", "configura testing para X", "este codigo no tiene tests", "escribe tests para el paquete de pagos", "sube la cobertura aqui", "add tests to this", "cover this code with tests", o menciona poner codigo existente y no testeado bajo pruebas. Usala incluso si nunca dice la palabra "retrofit": cualquier peticion de poner codigo de produccion existente bajo tests debe activarla. Corre un pipeline autonomo de 6 fases (medir testabilidad, romper dependencias con seams, scaffolding de utilidades de test compartidas, escribir characterization + behavior tests, auditar calidad, y reconciliar el build completo como gate de mergeabilidad) aislado en un worktree dedicado, y devuelve el worktree para revisar y mergear solo si es realmente mergeable. No la uses para TDD test-first de codigo nuevo, ni para depurar un solo test que falla.
typescript-migration
Esta skill debe usarse cuando el usuario pide "migra este proyecto a TypeScript", "convierte de JS a TS", "agrega TypeScript a este proyecto", "migrate to TypeScript", "add types to this codebase", "quiero tipado estatico en este proyecto", o menciona querer convertir un proyecto JavaScript existente a TypeScript de forma incremental. Ejecuta un pipeline autonomo de 5 fases (auditar proyecto, instalar tooling y renombrar archivos, extraer tipos compartidos, tipar chunks en paralelo, consolidar con strict progresivo y gate de build final) aislado en un worktree dedicado. No la uses para proyectos nuevos iniciados directamente en TypeScript ni para agregar tipos a un solo archivo.
browser-automation
Playwright MCPを使用したブラウザ自動化。ページ操作、スクリーンショット、フォーム入力のパターン集
cl-coding-style
Common Lispのコーディング規約を適用。Lispコード作成・レビュー時に使用
cl-mallet-linter
malletリンターのルールと設定を適用。コードレビュー・品質チェック時に使用
cl-asdf-system
ASDFシステム定義のベストプラクティス。.asdファイル作成・編集時に使用
cl-macro-design
マクロ設計のベストプラクティスを適用。マクロ作成・レビュー時に使用
wayland-automation
Wayland環境でのGUI自動化。スクリーンショット取得、テキスト入力、クリップボード操作のパターン集
cl-condition-system
condition/restartパターンを適用。エラーハンドリング実装時に使用
refactor-claude-md
CLAUDE.mdをベストプラクティスに基づいてリファクタリング
cl-clos-patterns
CLOS設計パターンを適用。クラス設計・メソッド実装時に使用
Page 1414 of 1712 · 85563 results
