7,443 件 ・ 人気順
概要と使いどころ
Design multi-agent architectures for complex tasks. Use when single-agent context limits are exceeded, when tasks decompose naturally into subtasks, or when specializing agents improves quality.
日本語の概要は準備中です。原文の説明を表示しています。
Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
日本語の概要は準備中です。原文の説明を表示しています。
Use when Code implementation and refactoring, architecturing or designing systems, process and workflow improvements, error handling and validation. Provide tehniquest to avoid over-engineering and apply iterative improvements.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "plan team structure", "determine hiring needs", "design org chart", "calculate compensation", "plan equity allocation", or requests organizational design and headcount planning for a startup.
日本語の概要は準備中です。原文の説明を表示しています。
Create interface designs, wireframes, and design systems. Masters user research, accessibility standards, and modern design tools. Specializes in design tokens, component libraries, and inclusive design. Use PROACTIVELY for design systems, user flows, or interface optimization.
日本語の概要は準備中です。原文の説明を表示しています。
Build scalable design systems with Tailwind CSS, design tokens, component libraries, and responsive patterns. Use when creating component libraries, implementing design systems, or standardizing UI patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Rigorous visual validation expert specializing in UI testing, design system compliance, and accessibility verification. Masters screenshot analysis, visual regression testing, and component validation. Use PROACTIVELY to verify UI modifications have achieved their intended goals through comprehensive visual analysis.
日本語の概要は準備中です。原文の説明を表示しています。
Generate and maintain OpenAPI 3.1 specifications from code, design-first specs, and validation patterns. Use when creating API documentation, generating SDKs, or ensuring API contract compliance.
日本語の概要は準備中です。原文の説明を表示しています。
Design effective KPI dashboards with metrics selection, visualization best practices, and real-time monitoring patterns. Use when building business dashboards, selecting metrics, or designing data visualization layouts.
日本語の概要は準備中です。原文の説明を表示しています。
Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.
日本語の概要は準備中です。原文の説明を表示しています。
Design monorepo structure, build systems, and dependency boundaries using Nx, Turborepo, Bazel, or Lerna. Use when setting up a monorepo, optimizing builds, or scaling development workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Write idiomatic Elixir code with OTP patterns, supervision trees, and Phoenix LiveView. Masters concurrency, fault tolerance, and distributed systems. Use PROACTIVELY for Elixir refactoring, OTP design, or complex BEAM optimizations.
日本語の概要は準備中です。原文の説明を表示しています。
Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling, designing APIs, or improving application reliability.
日本語の概要は準備中です。原文の説明を表示しています。
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
日本語の概要は準備中です。原文の説明を表示しています。
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Creates comprehensive technical documentation from existing codebases. Analyzes architecture, design patterns, and implementation details to produce long-form technical manuals and ebooks. Use PROACTIVELY for system documentation, architecture guides, or technical deep-dives.
日本語の概要は準備中です。原文の説明を表示しています。
Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use when architecting complex backend systems or refactoring existing applications for better maintainability.
日本語の概要は準備中です。原文の説明を表示しています。
Master software architect specializing in modern architecture patterns, clean architecture, microservices, event-driven systems, and DDD. Reviews system designs and code changes for architectural integrity, scalability, and maintainability. Use PROACTIVELY for architectural decisions.
日本語の概要は準備中です。原文の説明を表示しています。
Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing API design standards.
日本語の概要は準備中です。原文の説明を表示しています。
设计哲学顾问，从20种风格中推荐3个方向并生成视觉Demo和AI提示词。当用户提到"设计风格"、"设计方向"、"配色方案"、"视觉风格"、"设计评审"、"推荐风格"时使用。
日本語の概要は準備中です。原文の説明を表示しています。
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Half-hour television comedy craft (半小时情景喜剧/笑点力学/困境机器/多机位单机位格式) — merged from Evan S. Smith's Writing Television Sitcoms (premise-driven comedy in three levels, nine predicaments, six character mixes, setup/punchline mechanics, toppers, running gags, ten comedic nuances, format rules), Neil Landau's sitcom seven-step formula and comedy-room models, Richard Blum's act-length and set-count parameters, Phoebe Waller-Bridge's Fleabag scripts (direct address as a season-long device, six-episode skeleton), Pamela Douglas on dramedy, Kam Miller on complementary comic traits, and Jesse Armstrong on jokes carrying tragedy. Use when writing or fixing a sitcom episode or spec, raising joke density per page, designing a comic predicament that generates stories, choosing between multi-camera and single-camera format and page counts, structuring cold open/acts/tag, writing a half-hour pilot, running a comedy punch-up, or making a drama funny without shifting genre.
日本語の概要は準備中です。原文の説明を表示しています。
Character creation, protagonist/antagonist design and dramatic conflict for scripts (人物/对手/冲突) — merged from Lajos Egri (three-dimensional character, orchestration, unity of opposites, pivotal character, rising vs static vs jumping conflict, transition), William Indick's Psychology for Screenwriters (Freud, Erikson, Jung archetypes, Campbell/Murdock hero journeys, Adler, Rollo May), Robert McKee (characterization vs true character, dimensions, gap, antagonism principle), Neill Hicks (character invocation, self-concept, cognitive dissonance, five conflict focuses, Maslow), Lisa Cron (desire vs misbelief), and Lu Jun (人物要活八要, 对手要强, 给对手一把刀, 最强的对手是自己, 不许请祥云). Use when building a protagonist, an antagonist or a cast, when a character feels flat or acts out of character, when conflict stalls or jumps, when a villain is too weak, when designing an arc or motive, or when diagnosing melodrama.
日本語の概要は準備中です。原文の説明を表示しています。