3,617 件 ・ 関連度順
概要と使いどころ
Analyze a codebase for high-leverage architectural improvements and explain evidence, tradeoffs, and next steps. Use explicitly for architecture audits or deep-module refactoring opportunities.
日本語の概要は準備中です。原文の説明を表示しています。
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
日本語の概要は準備中です。原文の説明を表示しています。
Plans architecture migrations with compatibility, data safety, rollout and recovery; does not execute them.
日本語の概要は準備中です。原文の説明を表示しています。
Records one architecture decision with alternatives, consequences and status; does not design the whole system.
日本語の概要は準備中です。原文の説明を表示しています。
Audits implemented architecture boundaries, dependencies and ownership; not target design or plan review.
日本語の概要は準備中です。原文の説明を表示しています。
Creates evidence-backed current or target architecture diagrams; not UI design.
日本語の概要は準備中です。原文の説明を表示しています。
Documents current architecture from implementation evidence; does not propose a target or audit fitness.
日本語の概要は準備中です。原文の説明を表示しています。
Defines measurable architecture drivers and constraints before system design; edits architecture docs only.
日本語の概要は準備中です。原文の説明を表示しています。
Structure Spring Boot 3+ projects with feature packaging and clean layering. Use when structuring Spring Boot 3 projects, defining layers, or applying architecture patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Structure React Native projects with feature-first organization and separation of concerns. Use when structuring a React Native project or applying clean architecture patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Structure Python backends with explicit dependency direction, ports/adapters, and runtime boundaries. Use when shaping project layout, clean architecture, service boundaries, dependency injection, report rendering boundaries, or transport separation in Python.
日本語の概要は準備中です。原文の説明を表示しています。
Enforce inward dependency flow, pure domain layers, and DTO-to-entity mapping in Flutter DDD architecture. Use when structuring layers or boundaries; defer navigation-only routing and feature implementation such as notifications.
日本語の概要は準備中です。原文の説明を表示しています。
Organize Flutter apps with modular feature-based clean architecture. Use when creating features under lib/features/ with domain, data, and presentation layers. Do not use for test-only, BlocBuilder, navigation, or spinner requests.
日本語の概要は準備中です。原文の説明を表示しています。
Apply Clean Architecture layering, modularization, and Unidirectional Data Flow in Android projects. Use when setting up project structure, placing code in layers, configuring feature/core modules, or implementing UDF patterns; defer Compose state and ViewModel/StateFlow implementation to their specific skills.
日本語の概要は準備中です。原文の説明を表示しています。
Audit structural debt, logic leakage, and monolithic components across Web, Mobile, and Backend codebases. Use when reviewing architecture, assessing tech debt, detecting logic in wrong layers, or identifying God classes.
日本語の概要は準備中です。原文の説明を表示しています。
Draws architecture diagrams as editable draw.io files with a fixed house style, C4 levels, evidence-tagged shapes, and optional multi-view identity checks. Use when producing a system context, container, component, deployment, data flow, sequence, state, or ERD, or redrawing an ASCII or Mermaid one.
日本語の概要は準備中です。原文の説明を表示しています。
Unified team skill for architecture optimization. Uses team-worker agent architecture with role directories for domain logic. Coordinator orchestrates pipeline, workers are team-worker agents. Triggers on "team arch-opt".
日本語の概要は準備中です。原文の説明を表示しています。
Designs modular high-level architectures from functional requirements and produces design documents for each module. Use when designing a new system, creating architecture documentation, or producing module-level design specs with integration contracts and test specifications.
日本語の概要は準備中です。原文の説明を表示しています。
Router-First Architecture
日本語の概要は準備中です。原文の説明を表示しています。
OPC Architecture Understanding
日本語の概要は準備中です。原文の説明を表示しています。
Meta-skill for internal codebase exploration at varying depths (quick/deep/architecture)
日本語の概要は準備中です。原文の説明を表示しています。
Generate comprehensive technical documentation including API docs (OpenAPI/Swagger), code documentation (TypeDoc/Sphinx), documentation sites (Docusaurus/MkDocs), Architecture Decision Records (ADRs), and diagrams (Mermaid/PlantUML). Use when documenting APIs, libraries, systems architecture, or building developer-facing documentation sites.
日本語の概要は準備中です。原文の説明を表示しています。
Design comprehensive security architectures using defense-in-depth, zero trust principles, threat modeling (STRIDE, PASTA), and control frameworks (NIST CSF, CIS Controls, ISO 27001). Use when designing security for new systems, auditing existing architectures, or establishing security governance programs.
日本語の概要は準備中です。原文の説明を表示しています。
Create branded architecture, architecture delta, IT current-state, flowchart, sequence, state machine, ER/data model, timeline, swimlane, quadrant, radar/spider, polar chart (polar/radial lollipop), loop/flywheel, nested, tree, org chart, layer stack, exploded axonometric, axonometric plan, Venn, pyramid/funnel, treemap and marimekko, heatmap, bar and dumbbell, waterfall, line (slopegraph, ridgeline, streamgraph, bump), Gantt and scatter charts (bubble, beeswarm), high-level, process, medallion, data flow, DP integration, DP security matrix, Sankey, fishbone, Wardley map, kanban, user journey, deployment, dependency graph, UML class, story map, or database schema diagrams as HTML/SVG/PNG, with .drawio, Mermaid, and .excalidraw import, plus lifecycle phase maps, block decomposition trees, and onboarding guidance.
日本語の概要は準備中です。原文の説明を表示しています。