2,955 件 ・ 関連度順
概要と使いどころ
Check proposed stack, data flows, cloud choices, and delivery controls against declared enterprise policies, compliance frameworks, and security controls. Trigger at R2/R3 risk classification, before locking architecture decisions, or when the operating profile names a governance pointer.
日本語の概要は準備中です。原文の説明を表示しています。
Sync reusable frontend decisions into persistent project documentation after UI work. Use when frontend changes introduce or modify component APIs, variants, design-system tokens, styling conventions, layout behavior, accessibility rules, interaction patterns, responsive behavior, or agent operating instructions; when the user asks to reflect decisions in components.md, design system docs, AGENTS.md, CLAUDE.md, GEMINI.md, or similar project memory files; or before finalizing frontend work where future consistency depends on decisions made during implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when orchestrating implementer/judge subagents — form gate + nine modes (do-and-judge ±two-stage, steps/parallel/worktrees, competitively, debate, live-app-judge, adversarial-council).
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants a security-maturity scorecard / posture assessment of a module — category ratings with evidence, not a vulnerability hunt. Also on 'wie sicher ist dieses Modul aufgestellt?'
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing, generating, or improving Pest tests for Laravel — clear intent, good coverage, maintainable structure, and alignment with project testing 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 generating or editing a Word .docx — create, fill a template, or edit body XML via a consumer library; round-trip validated. Triggers on 'generate a docx', 'fill this Word template'.
日本語の概要は準備中です。原文の説明を表示しています。
Generate brand assets — banners, social cards, CIP elements — with brand-token injection + provider routing. Use when generating a banner / social image / branded asset.
日本語の概要は準備中です。原文の説明を表示しています。
Use this Canvas-owned clean-room skill to guide collaborative writing for documentation, proposals, technical specs, decision records, PRDs, RFCs, operating guides, and structured memos. Trigger when the user wants help drafting, organizing, refining, reviewing, or testing a document before sharing it.
日本語の概要は準備中です。原文の説明を表示しています。
Load this skill whenever you are filing, reviewing, or generating accessibility bug reports — whether from automated tool output, manual testing, user reports, or testing with disabled people. The purpose of this skill is to make accessibility findings easier to report accurately, connect them to real people and tasks, and let developers reproduce, understand, and fix them without unnecessary back-and-forth. Absolutely always describe the barrier and its task impact before citing a WCAG criterion. Under no circumstances guess a disability diagnosis, treat automated tool output as a conformance conclusion, or expose secrets/personal data in a report.
日本語の概要は準備中です。原文の説明を表示しています。
[Documentation] Use when (re)generating the DERIVED technical spec view over code + tests, or reporting canonical §8 TC/test-code drift. A GENERATOR — it projects code + tests into a regenerable per-component view and NEVER authors business content. Modes generate|audit|sync. Per-mode procedure lives in references/{author,sync}.md.
日本語の概要は準備中です。原文の説明を表示しています。
[Git] Use when generating developer KPI, performance, contribution value, story point, man-day, or code-quality reports from local git commit history.
日本語の概要は準備中です。原文の説明を表示しています。
[Planning] Use when calibrating estimates from actual code, diff, PR scope, and developer time.
日本語の概要は準備中です。原文の説明を表示しています。
[Testing] Use when generating, updating, or maintaining E2E tests from recordings, specs, or code changes.
日本語の概要は準備中です。原文の説明を表示しています。
Use when generating or editing draw.io/diagrams.net architecture diagrams via MCP or native XML.
日本語の概要は準備中です。原文の説明を表示しています。
Use when initializing or migrating an AI agent harness in a repository.
日本語の概要は準備中です。原文の説明を表示しています。
Use when generating or updating a project README.md or CHANGELOG.md.
日本語の概要は準備中です。原文の説明を表示しています。
Use when generating, documenting, or updating architecture diagrams, flowcharts, sequence, ER, class, or state diagrams using Mermaid in docs/architecture/.
日本語の概要は準備中です。原文の説明を表示しています。
Use when generating a single dense technical architecture, reference poster, or system diagram image for a software project. Produces a source-grounded bitmap diagram with topology, primitives, ingest/process flow, core logic, state scopes, tiers/modules, surfaces, runtime cards, and strict semantic color rules.
日本語の概要は準備中です。原文の説明を表示しています。
Cursor Cloud Agentにタスクを委託するよう依頼された際に発動。エージェント作成、SSEストリーム監視（stream）、実行キャンセル（cancel）、ステータスポーリング（フォールバック）、Pull Request状態確認、Linear紐付け、レビュー・フォローアップを行う。
Use when integrating an app with local AI models through Ollama — connection checks, model listing/selection, local-only mode, cloud-fallback consent, visible run states, and recovering from Ollama errors.
日本語の概要は準備中です。原文の説明を表示しています。
Project-level visual direction skill for WeChat Official Account articles. Use when planning, improving, diversifying, generating, or reviewing cover images and body illustrations for公众号文章, especially when Codex image generation should be used without being constrained by repetitive preset-based illustration skills.
日本語の概要は準備中です。原文の説明を表示しています。
Research-grounded typography for any text-bearing surface — web, PDF, email, documents. GENERATIVE: apply correct line length, font sizing, contrast, dark mode, mobile, and Japanese rules from the start when building any UI, page, layout, or document. REVIEW: audit existing CSS/HTML/templates for typography violations. Use this skill whenever you are writing CSS that touches font-size, line-height, max-width, color, or font-family. Use it when building any frontend component, page, or layout — even if the user doesn't mention typography. Use it when reviewing any rendered output for readability. Use it when generating PDFs, emails, or any formatted document. If text will be read by a human, this skill applies.
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing, moving, reviewing, or auditing documentation in the deepseek-harness repo — choosing hierarchy and detail, separating tutorials from references, checking tutorial progression, trimming doc slop, responding to a verify-doc-budgets failure, or requests like "improve the docs", "audit the docs", "where should this be documented", or "this doc is too long".
日本語の概要は準備中です。原文の説明を表示しています。