struts-to-jsf-migration
Apache Struts 1.xからJakarta Faces (JSF) 4.0へのマイグレーションを支援。仕様駆動アプローチ(Spec-Driven Migration)により、リバースエンジニアリング、タスク分解、詳細設計、コード生成、結合テスト、E2Eテストの7段...
Discover documentation architecture patterns skills, compare source repositories and read the instructions for each workflow.
Apache Struts 1.xからJakarta Faces (JSF) 4.0へのマイグレーションを支援。仕様駆動アプローチ(Spec-Driven Migration)により、リバースエンジニアリング、タスク分解、詳細設計、コード生成、結合テスト、E2Eテストの7段...
Replaces the process of defining the system's overall picture (SSOT) and dynamically maintaining alignment between codebase reality and design maps. Typical use cases: (1) Defining initial system boundaries and...
Replaces the "information organization" task of improving readability and consistency of architecture diagrams while maintaining accuracy. Typical use cases: (1) Optimizing cognitive load by minimizing crossing...
Replaces the task of identifying information gaps needed for decision-making and proposing strategic approaches to resolve bottlenecks. Typical use cases: (1) Analyzing trade-offs and 4 Big Risks among multiple...
Replaces the process of visualizing approved ADRs into concrete diagrams and sequence charts while ensuring architectural integrity. Typical use cases: (1) Decomposing approved ADRs into specific diagramming ta...
Replaces the work of drafting determined architectural hypotheses into logical and detailed ADR documents following standard formats. Typical use cases: (1) Recording the background, reasoning, and impact of de...
Replaces the entire process of formulating implementation plans and integrating results based on detailed specifications through Test-Driven Development (TDD). Typical use cases: (1) Decomposing detailed specif...
Replaces the work of drafting and refining Design Docs, which serve as the Implementation SSOT, by integrating various design outcomes. Typical use cases: (1) Creating comprehensive Design Doc drafts based on t...
Decomposes approved ADRs/Design Docs into a dependency graph of Artifacts and Tasks using backward chaining. Generates a robust roadmap where every task is logically connected to existing assets.
Replaces the entire process of translating high-level designs (Architecture/Design Docs) into detailed technical specifications (Specs) that developers can implement immediately. Typical use cases: (1) Decompos...
Replaces the entire process of formulating Architecture Decision Records (ADRs) based on the OODA loop. Typical use cases: (1) Defining the specific scope and components of the system to be implemented next, (2...
Replaces the DDD-based modeling work of translating business knowledge into structures that can be reflected in code and architecture. Typical use cases: (1) Defining bounded contexts and creating relationship...
Replaces the task of strictly verifying whether proposals or deliverables conceptually align with the project's Single Source of Truth (SSOT). Typical use cases: (1) Confirming new design proposals do not viola...
Replaces the diagramming task of visualizing the "big picture" and "external boundaries" of the system based on the C4 model (Level 1). Typical use cases: (1) MECE identification of actors and external systems...
Replaces the entire design process for architectural decision-making and overall structural design for new features or major changes. Typical use cases: (1) Formulating and evaluating multi-perspective approach...
Layered Composition Architecture patterns. Use when designing system boundaries, state flow, lifecycle management, configuration, or module structure. Includes Infrastructure pattern for shared dependencies and...
Creates complete DDD entity with factory method, domain events, value objects, and EF configuration
Scaffolds complete CQRS command or query with handler, validator, and DTO following Merge project patterns
API 설계, SSE 스트리밍, 에러 처리 등 백엔드 개발 가이드
프론트엔드 개발 시 준수해야 할 아키텍처, 컨벤션, 워크플로우 가이드
AI-powered systematic codebase analysis. Combines mechanical structure extraction with Claude's semantic understanding to produce documentation that captures not just WHAT code does, but WHY it exists and HOW i...
新機能やコード変更時にアーキテクチャの妥当性を検証する。 簡易DDD構成、レイヤー分離、依存方向の正しさをチェック。
从技术架构层面确保系统代码符合架构要求,实现健壮性、扩展性、并发支撑性、伸缩性等目标。
Systematic process for implementing minimal, intelligent bug fixes in any language (Implementation Only).
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.