「context」の検索結果

Creates a dedicated story file with all the context the agent will need to implement it later. Use when the user says "create the next story" or "create story [story identifier]"

日本語の概要は準備中です。原文の説明を表示しています。

Adapt designs to work across different screen sizes, devices, contexts, or platforms. Implements breakpoints, fluid layouts, and touch targets. Use when the user mentions responsive design, mobile layouts, breakpoints, viewport adaptation, or cross-device compatibility.

日本語の概要は準備中です。原文の説明を表示しています。

Run the speckit implementation phase chunk-by-chunk in clean-context subagents, then review, then produce a final report. Picks up from an existing tasks.md.

日本語の概要は準備中です。原文の説明を表示しています。

Run a session retrospective that surfaces context-management gaps and routes them to approved follow-up actions.

日本語の概要は準備中です。原文の説明を表示しています。

React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.

日本語の概要は準備中です。原文の説明を表示しています。

Read the project's knowledge record before answering from memory or from the files. Use before answering about the project's state, a number, a date, a decision, a source, a deadline or what was agreed - even a casual 'what's the situation with X' or 'is that quote still current'; before changing a recorded value; and whenever the opener or a grounding line names entries. After finding relevant IDs, prefer kpop context to read them with their declared dependencies and checks. Uses pull for concise readings or when the checked reader is unavailable, affects for changed inputs, and search when no ID is known. A missing id is not absence. Not for showing the record's page (the hub skill). Requests come in any language.

日本語の概要は準備中です。原文の説明を表示しています。

Verify that the current Git branch, upstream state, and dirty working tree match the user's intended task before staging, committing, pushing, or continuing work from another session. Use this to detect stale branch reuse, leftover dirty files from previous sessions, unrelated commits on the current branch, cases where work should be split into a new branch or worktree, and post-publish cleanup decisions after push, PR creation, or PR merge.

日本語の概要は準備中です。原文の説明を表示しています。

Use when shaping brand voice — voice attributes, tone-by-context matrix, consistency review. Triggers on 'define our voice', 'why does our copy sound different on every surface'.

日本語の概要は準備中です。原文の説明を表示しています。

Use BEFORE any verbose CLI run, large file read, doc conversion, or near-context handoff — decision tree keyed by intent citing the canonical token-saving asset.

日本語の概要は準備中です。原文の説明を表示しています。

Use when looking for project-specific documentation. Knows which docs exist in agents/reference/docs/ and agents/settings/contexts/ and maps work areas to relevant docs.

日本語の概要は準備中です。原文の説明を表示しています。

Use when asking for a review or creating a PR — self-review first, frame the right context, test plan included — even when the user just says 'open a PR' or 'ready to merge'.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a repo has its own generators, scripts or turbo tasks and an agent reaches for a generic skill instead — derive a Playbook context (ADR-244) from the real config, graded by the tree.

日本語の概要は準備中です。原文の説明を表示しています。

Use when working with MCP (Model Context Protocol) servers — their tools, capabilities, and best practices for effective agent workflows.

日本語の概要は準備中です。原文の説明を表示しています。

Before stating any specific fact about an LLM provider's product — models, pricing, limits, context windows, SDK/API — for OpenAI, Gemini, Claude & others, verify against official docs, not memory.

日本語の概要は準備中です。原文の説明を表示しています。

When co-authoring a PRD, design doc, RFC, decision doc, or technical spec — 3-stage flow (context → section-by-section → reader-test) — even if the user just says 'help me write this spec'.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user invokes a slash command like /create-pr, /commit, /fix-ci, or pastes command file content — routes to the right command with context inference and GitHub API patterns.

日本語の概要は準備中です。原文の説明を表示しています。

Use when capturing an architectural decision — file naming, next ADR number, Status / Context / Decision / Consequences, index regen; fires even without saying 'ADR'.

日本語の概要は準備中です。原文の説明を表示しています。

Use when verifying cross-references between skills, rules, commands, guidelines, and context documents are not broken after edits, renames, or deletions.

日本語の概要は準備中です。原文の説明を表示しています。

Coordination guidance for the narrow case of multiple desktop-backed agents active concurrently in the same desktop-backed coordination context. Use ONLY when two or more desktop peers are running at the same time; normal CLI agents and single desktop peers should ignore this skill. Read this BEFORE concurrent desktop-to-desktop handoffs to keep sender labels unique, identity routing cooperative, and material handoffs proven.

日本語の概要は準備中です。原文の説明を表示しています。

Planeje e roteirize trabalho de Domain-Driven Design desde modelagem estratégica até implementação tática e padrões de arquitetura orientada a eventos.

日本語の概要は準備中です。原文の説明を表示しています。

Padrões abrangentes para criar, manter e gerenciar Registros de Decisões de Arquitetura (ADRs) que capturam o contexto e a lógica por trás de decisões técnicas significativas.

日本語の概要は準備中です。原文の説明を表示しています。

Guia completo para criar diagramas de software usando sintaxe Mermaid. Use quando usuários precisarem criar, visualizar ou documentar software por meio de diagramas, incluindo diagramas de classe (modelagem de domínio, design orientado a objetos), diagramas de sequência (fluxos de aplicação, interações de API, execução de código), fluxogramas (processos, algoritmos, jornadas do usuário), diagramas de relacionamento de entidades (esquemas de banco de dados), diagramas de arquitetura C4 (contexto do sistema, containers, componentes), diagramas de estado, git graphs, gráficos de pizza, gráficos de Gantt ou qualquer outro tipo de diagrama. Acionadores incluem solicitações para "diagram", "visualize", "model", "map out", "show the flow" ou ao explicar arquitetura de sistema, design de banco de dados, estrutura de código ou fluxos de usuário/aplicação.

日本語の概要は準備中です。原文の説明を表示しています。

Traduza nós do Figma em código pronto para produção com fidelidade visual 1:1 usando o workflow MCP do Figma (contexto de design, screenshots, assets e tradução de convenções de projeto). Ative quando o usuário fornecer URLs do Figma ou IDs de nó, ou solicitar implementar designs ou componentes que devem corresponder às especificações do Figma. Requer uma conexão funcional com servidor MCP do Figma.

日本語の概要は準備中です。原文の説明を表示しています。

Use o servidor Figma MCP para buscar contexto de design, screenshots, variáveis e assets do Figma, além de traduzir nós do Figma em código de produção. Ative quando uma tarefa envolver URLs do Figma, IDs de nós, implementação design-to-code ou configuração e troubleshooting do Figma MCP.

日本語の概要は準備中です。原文の説明を表示しています。