4,439 件 ・ 関連度順
概要と使いどころ
Use when the user asks to create a custom post type, build a portfolio, set up case studies, add team members, events, or podcast episodes, or says 'scaffold a CPT'. Creates the post type plus supporting taxonomies, an ACF field group, sample entries, and a builder-specific single template suggestion.
日本語の概要は準備中です。原文の説明を表示しています。
Breaks down complex tasks into ordered, verifiable sub-tasks with dependencies, milestones, and risks.
日本語の概要は準備中です。原文の説明を表示しています。
Cross-validate code, architecture or design decisions using a second model. Use for critical decisions, complex refactoring, security reviews.
日本語の概要は準備中です。原文の説明を表示しています。
Code exploration strategies for understanding unfamiliar codebases. Use when exploring unknown code, debugging, or analyzing architecture.
日本語の概要は準備中です。原文の説明を表示しています。
Run the repo's lint, format-check and test suite, then fix anything that fails. Use before opening a PR or when asked to "polish" or "clean up" the repo.
日本語の概要は準備中です。原文の説明を表示しています。
Fix a GitHub issue end to end -- read it, reproduce, patch, add a regression test, verify, and open a PR. Use when given an issue number or URL in this repo.
日本語の概要は準備中です。原文の説明を表示しています。
Skill for building with the Astro web framework. Helps create Astro components and pages, configure SSR adapters, set up content collections, deploy static sites, and manage project structure and CLI commands. Use when the user needs to work with Astro, mentions .astro files, asks about static site generation (SSG), islands architecture, content collections, or deploying an Astro project.
日本語の概要は準備中です。原文の説明を表示しています。
Interactive code simulation engine that spawns ghost personas to review your code before it ships. Each ghost walks through your code line-by-line from a different failure perspective: The Adversary (race conditions, double-submit, idempotency), The Enterprise Edge (business logic gaps, multi-currency, B2B tax exemptions, locale), Chaos Monkey (timeouts, partial failures, network partitions, OOM). Produces a chaos timeline, structured bug report with severity ratings, and three resolution tiers (quick fix, robust architecture, generated test suite). Use this skill whenever the user mentions code review, PR review, "find bugs", "what could go wrong", "will this break", "is this safe", "stress test", "edge cases", design review, pre-merge check, dry run, chaos test, or wants a second opinion on any code — even if they don't explicitly ask for "ghost personas" or "simulation". Also trigger when someone pastes a code snippet with any question about its correctness or safety.
日本語の概要は準備中です。原文の説明を表示しています。
Use for repo structure and symbol maps. Triggers: repo map, codebase overview, architecture map, 와꾸.
日本語の概要は準備中です。原文の説明を表示しています。
Use for module boundaries and dependencies. Triggers: circular import, coupling, barrel, re-export, validation placement, 모듈 경계, 순환 참조.
日本語の概要は準備中です。原文の説明を表示しています。
Use for project/module setup and docs. Triggers: scaffold, structure audit, architecture docs, API docs, monorepo setup, 스캐폴딩, 새 프로젝트, 새 기능, 구조 점검, 모듈 추가.
日本語の概要は準備中です。原文の説明を表示しています。
OWASP secure design review for code and architecture. Checks input validation, authentication, authorization, data protection.
日本語の概要は準備中です。原文の説明を表示しています。
Implement or modify Python, JavaScript, SCSS, templates, CLI, HTTP, logging, or tests. Use for code changes that require architecture, style, testing, and verification conventions.
日本語の概要は準備中です。原文の説明を表示しています。
Apply MCAF non-functional-requirements guidance to capture or refine explicit quality attributes such as accessibility, reliability, scalability, maintainability, performance, and compliance. Use when a feature or architecture change needs explicit quality attributes and trade-offs.
日本語の概要は準備中です。原文の説明を表示しています。
Set up or refine open-source .NET code-quality gates for CI: formatting, `.editorconfig`, SDK analyzers, third-party analyzers, coverage, mutation testing, architecture tests, and security scanning. Use when a .NET repo needs an explicit quality stack in `AGENTS.md`, docs, or pipeline YAML.
日本語の概要は準備中です。原文の説明を表示しています。
Builds Stitch-ready prompts via two paths — Path A enhances vague ideas into polished prompts, Path B merges a Design Spec JSON + user request into a structured [Context] [Layout] [Components] prompt.
日本語の概要は準備中です。原文の説明を表示しています。
Iteratively build multi-page websites using Stitch. Reads next-prompt.md (the baton), generates the next page with Stitch MCP, integrates it into the site, then updates next-prompt.md to continue the loop. Works with stitch-design-md and stitch-ui-prompt-architect for consistent multi-page output.
日本語の概要は準備中です。原文の説明を表示しています。
Generates 3 alternative Stitch prompts for A/B testing screen concepts — vary layout, visual style, or content while keeping the underlying information architecture consistent.
日本語の概要は準備中です。原文の説明を表示しています。
Converts a Stitch screen, a local HTML file, or a URL into modular Vite + React components — TypeScript, theme-mapped Tailwind, dark mode via CSS variables, and clean component architecture. Use this for Vite/React apps without App Router. For Next.js 15 App Router, use stitch-nextjs-components instead. Only the Stitch route needs an API key.
日本語の概要は準備中です。原文の説明を表示しています。
Meta-skill for creating new stitch-kit skills. Enforces naming conventions, SKILL.md structure, examples format, and the Design-First SOP. Use when adding new framework support, a new domain-specific prompt architect, or any new capability to the stitch-kit plugin.
日本語の概要は準備中です。原文の説明を表示しています。
Turn a raw product idea into build-ready docs — one doc per EPIC with locked decisions, exact API contracts, a story-by-story priority plan, and an execute.md handoff Claude can build from across sessions. Gets the clarity by interrogating the user through a roster of expert personas that grill, counter, and refuse to flatter. Use to ideate, validate, scope, architect, or plan a product, feature, startup, or app before any code is written. Invoke by persona name or acronym to summon one expert, or with no argument to run the full lifecycle end to end.
日本語の概要は準備中です。原文の説明を表示しています。
Explores codebases to find relevant files, trace execution paths, and map architecture with team communication capabilities for collaborative analysis (converted from agent)
日本語の概要は準備中です。原文の説明を表示しています。
Generates MkDocs-flavored or standard GitHub-flavored Markdown documentation from codebase analysis findings including API references, architecture guides, standalone markdown files, and change summaries (converted from agent)
日本語の概要は準備中です。原文の説明を表示しています。
Provides Mermaid diagram syntax, best practices, and styling rules for technical visualizations. Use when creating diagrams, flowcharts, sequence diagrams, class diagrams, state diagrams, ER diagrams, architecture diagrams, C4 diagrams, or any visual documentation in markdown.
日本語の概要は準備中です。原文の説明を表示しています。