5,804 件 ・ 関連度順
概要と使いどころ
Session-start orientation for this team harness. Load first, before any work. Explains the operating contract, when each skill triggers, and how installed companion plugins supply agent-craft capabilities while this harness supplies the team contract. Trigger at the start of every session and whenever unsure which skill applies.
日本語の概要は準備中です。原文の説明を表示しています。
Cloud guardrails for any vendor workload — Google Cloud (GCP, Vertex AI, GKE), AWS (IAM, EKS, Bedrock), Azure (Entra ID, Policy, AKS), Alibaba Cloud (RAM, mainland/international residency). Enforces identity least-privilege, mechanical policy, data boundaries, residency, cost caps, network egress and observability, with official-source validation before any claim. Trigger on any cloud infrastructure design, review, Terraform plan, or LLM/agent deployment; the-architect routes here.
日本語の概要は準備中です。原文の説明を表示しています。
Validate agent output against declared domain rules and ground truth before trusting it downstream. Trigger after any agent produces output that will be used in a decision, stored persistently, or passed to another agent.
日本語の概要は準備中です。原文の説明を表示しています。
Ship an already-committed Git branch through GitHub: verify branch/worktree intent, push, create or mark a pull request ready for review, optionally wait for CI, optionally address review comments automatically, and merge with explicit safety gates. Use when a solo developer repeatedly asks to publish committed work, register a ready PR, handle PR feedback, and complete merge.
日本語の概要は準備中です。原文の説明を表示しています。
BEFORE writing/changing tests, mocks, or test-only methods on production classes — mocking-the-mock, production pollution, overfit assertions; for order, `test-driven-development` wins.
日本語の概要は準備中です。原文の説明を表示しています。
Implementing a feature, fixing a bug, refactoring — failing test first, then the code. For a WRONG test, `testing-anti-patterns` wins.
日本語の概要は準備中です。原文の説明を表示しています。
Writes Symfony PHP — DI container, bundles, Doctrine, Messenger, Security voters, console commands. For Laravel / Eloquent / Artisan use `laravel`. For framework-free PHP use `php-coder`.
日本語の概要は準備中です。原文の説明を表示しています。
Use when PHPStan, Rector, or ECS output appears — "phpstan says mixed", type errors, "fix code style", "run rector" — even when Eloquent/Laravel/model code is also mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
Use when creating or rewriting a README for a reusable package or library. Focus on installability, minimal usage example, compatibility, and developer onboarding.
日本語の概要は準備中です。原文の説明を表示しています。
Use for deep Laravel project analysis: boot flow, request lifecycle, container usage, Eloquent/data flow, async systems, and Laravel-specific failure patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Writes Laravel PHP — Eloquent, Artisan controllers, FormRequests, jobs, events, policies, providers. For Symfony / Doctrine use `symfony-workflow`. For framework-free PHP use `php-coder`.
日本語の概要は準備中です。原文の説明を表示しています。
Use when upgrading dependencies — 'update framework X', 'bump runtime version', or 'upgrade packages'. Covers changelog review, breaking-change detection, and verification. Stack-agnostic.
日本語の概要は準備中です。原文の説明を表示しています。
Use when implementing, debugging, refactoring, or reviewing code — enforces the think → analyze → verify → execute workflow — even when the user just says 'implement X' without naming it.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the feature is implementation-complete and the next step is 'ship it' — verifies, cleans up, routes to merge/PR/park/discard; never destroys work without explicit confirmation.
日本語の概要は準備中です。原文の説明を表示しています。
Combine independent work from two or more selected agents into one decision-ready research report, design, or proposal. Preserve useful complementary findings, develop stronger combined options, and present material alternatives only when they exist. Use when multiple perspectives should improve the product without forcing consensus or staging disagreement.
日本語の概要は準備中です。原文の説明を表示しています。
Projete esquemas de banco de dados robustos e escaláveis para SQL e NoSQL. Fornece diretrizes de normalização, estratégias de indexação, padrões de migração, design de restrições e otimização de desempenho. Garante integridade de dados, desempenho de consultas e modelos de dados mantíveis.
日本語の概要は準備中です。原文の説明を表示しています。
Development skill from everything-claude-code
日本語の概要は準備中です。原文の説明を表示しています。
Migre prompts e código de Claude Sonnet 4.0, Sonnet 4.5 ou Opus 4.1 para Opus 4.5. Use quando o usuário quiser atualizar sua base de código, prompts ou chamadas de API para usar Opus 4.5. Lida com atualizações de string de modelo e ajustes de prompt para diferenças comportamentais conhecidas de Opus 4.5. NÃO migra Haiku 4.5.
日本語の概要は準備中です。原文の説明を表示しています。
Esta habilidade deve ser usada quando o usuário pede para "criar um slash command", "adicionar um comando", "escrever um comando personalizado", "definir argumentos de comando", "usar frontmatter de comando", "organizar comandos", "criar comando com referências de arquivo", "comando interativo", "usar AskUserQuestion em comando", ou precisa de orientação sobre estrutura de slash command, campos de frontmatter YAML, argumentos dinâmicos, execução bash em comandos, padrões de interação com usuário, ou melhores práticas de desenvolvimento de comando para Claude Code.
日本語の概要は準備中です。原文の説明を表示しています。
Revisão profissional de código com geração automática de CHANGELOG, integrado com Codex AI
日本語の概要は準備中です。原文の説明を表示しています。
Analisa seu histórico recente de chats do Claude Code para identificar padrões de codificação, lacunas no desenvolvimento e áreas para melhoria, seleciona recursos de aprendizagem relevantes do HackerNews e envia automaticamente um relatório de crescimento personalizado para suas DMs do Slack.
日本語の概要は準備中です。原文の説明を表示しています。
Development skill from everything-claude-code
日本語の概要は準備中です。原文の説明を表示しています。
Regras obrigatórias de habilidades, convenções e comportamento para desenvolvimento Avalonia UI com o toolkit Zafiro.
日本語の概要は準備中です。原文の説明を表示しています。
Use quando o Codex está construindo ou iterando em um jogo web (HTML/JS) e precisa de um loop confiável de desenvolvimento + teste: implementar pequenas mudanças, executar um script de teste baseado em Playwright com rajadas curtas de input e pausas intencionais, inspecionar screenshots/texto e revisar erros de console com render_game_to_text.
日本語の概要は準備中です。原文の説明を表示しています。