9,083 件 ・ 関連度順
概要と使いどころ
Translate an image brief into provider-specific prompt grammar per model. Use when writing or refining an image-generation prompt for Ideogram, Flux, Gemini, GPT Image 2, or Recraft.
日本語の概要は準備中です。原文の説明を表示しています。
Writes or edits PHP code — controllers, classes, type hints, SOLID refactors, modern idioms — even without naming PHP. NOT for writing tests (use pest-testing) or explaining PHP concepts.
日本語の概要は準備中です。原文の説明を表示しています。
When editing a module-shaped path (`Modules/*`, `packages/*`, `apps/*`) while `modules.enabled` is false — asks once to enable it; also the project/stack + task-runner detection reference.
日本語の概要は準備中です。原文の説明を表示しています。
Refine a persona from recent corrections — tightens its Unique Questions, governance-gated; explicit request only. Skill analog → skill-improvement-pipeline.
日本語の概要は準備中です。原文の説明を表示しています。
Use when shaping a fuzzy product ask into a refined backlog item — problem framing, user-story rewrite, AC tightening — even if the user just says 'help me write this ticket'.
日本語の概要は準備中です。原文の説明を表示しています。
Read a Reddit thread or single tweet the host cannot fetch — 'what does this Reddit thread say', 'top comment on this post', 'what does this tweet say' — when reddit.com is refused or x.com 402s.
日本語の概要は準備中です。原文の説明を表示しています。
Use when creating a Laravel migration — table prefixes, column naming, multi-tenant awareness, php artisan make:migration. Other stacks: use stack-native migration tooling.
日本語の概要は準備中です。原文の説明を表示しています。
Use when sending notifications via mail, Slack, database, or custom channels — with queuing, on-demand recipients, and notification preferences.
日本語の概要は準備中です。原文の説明を表示しています。
When scoring whether an agent response defended against an injection — treated untrusted content as data, refused role-takeover, ignored fake boundaries. Inverted axis; never auto-gates.
日本語の概要は準備中です。原文の説明を表示しています。
Use when creating or editing a guideline in docs/guidelines/ — reference material cited by skills, no auto-triggers — even when the user just says 'write up our naming conventions'.
日本語の概要は準備中です。原文の説明を表示しています。
Generate an image from a brief — provider-agnostic blueprint then provider-specific translation, with ref-image/seed reuse for consistency. Use when generating/creating an image.
日本語の概要は準備中です。原文の説明を表示しています。
When scoring a roadmap, PR review, ADR, or ticket for completeness — risk, tests, migration, maintainability. Dispatched by /refine-ticket, /adr-create, /review-changes; never auto-gates.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Estimate a Jira/Linear ticket — 'estimate PROJ-123', 'wie groß ist das?', 'should we split this?' — size + risk + split + uncertainty, sibling of /refine-ticket, close-prompt.
日本語の概要は準備中です。原文の説明を表示しています。
Use when reviewing UI for accessibility — WCAG 2.2 AA, keyboard nav, focus, ARIA, contrast, screen-reader semantics — even on 'is this a11y-OK?' or 'mach das barrierefrei'.
日本語の概要は準備中です。原文の説明を表示しています。
When shrinking always-loaded memory files (AGENTS.md, CLAUDE.md, .cursorrules) exceeding ~150 lines or ~4,000 chars — telegraph grammar, refuses sensitive paths, .original.md round-trip.
日本語の概要は準備中です。原文の説明を表示しています。
Run a two-agent proxy approval council for autonomous sprint gates. Use when a sprint needs delegated approval for human gates such as deploy, live mutation, push, cleanup, skip, or shortened watch decisions, while requiring two independent agents to reach consensus that the human principal would approve under written policy and preferences.
日本語の概要は準備中です。原文の説明を表示しています。
Harness-first workflow for evaluating and improving terminal UIs through real interaction. Use this whenever the user wants to review a TUI experience, compare before/after behavior, identify UX friction, validate navigation or filtering flows, inspect visual stability, or turn observed interaction problems into concrete follow-up tests and improvement recommendations. Prefer this skill any time a TUI should be exercised through a reproducible PTY/session harness instead of only reading code.
日本語の概要は準備中です。原文の説明を表示しています。
Criar um plano conciso. Use quando um usuário solicitar explicitamente um plano relacionado a uma tarefa de codificação.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Use quando enfrentar 2+ tarefas independentes que podem ser trabalhadas sem estado compartilhado ou dependências sequenciais
日本語の概要は準備中です。原文の説明を表示しています。
Crie designs de websites premium com qualidade Awwwards como componentes React (.jsx) que pareçam ter sido construídos por uma agência de primeira linha cobrando R$250k+ por projeto. Use esta skill sempre que o usuário pedir um website, landing page, portfólio, ou componente web que deve parecer caro, premium, luxo, editorial, high-end, ou de qualidade agência. Também dispare quando o usuário mencionar Awwwards, FWA, design premiado, ou referenciar marcas como Apple, Aesop, Bottega Veneta, Stripe, ou qualquer marca luxury/fashion/design-forward. Dispare quando o usuário disser coisas como "faça parecer profissional", "faça parecer caro", "quero que fique realmente bom", "design de alta qualidade", "não genérico", ou expressar insatisfação com aesthetics típicos de websites gerados por IA. NÃO dispare para dashboards, admin panels, ferramentas internas, ou UI funcional onde aesthetics são secundárias à utilidade — a skill padrão frontend-design cuida disso.
日本語の概要は準備中です。原文の説明を表示しています。
Infraestrutura de pagamento para agentes IA — escrow ACTP, pagamentos instantâneos x402, liquidação em USDC na Base L2. Onboarding interativo: pergunta suas preferências, gera código customizado do agente e verifica a configuração. Cobre padrões provider/requester, roteamento de adaptadores, máquina de 8 estados, preços, disputas e identidade.
日本語の概要は準備中です。原文の説明を表示しています。
Inteligência de design UI/UX. 50 estilos, 21 paletas, 50 combinações de fontes, 20 gráficos, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Ações: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projetos: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elementos: button, modal, navbar, sidebar, card, table, form, chart. Estilos: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Tópicos: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrações: shadcn/ui MCP para busca de componentes e exemplos.
日本語の概要は準備中です。原文の説明を表示しています。