Architecture Patterns

from "obra/superpowers"

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree...

from "obra/superpowers"

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before...

from "obra/superpowers"

Use when you have a spec or requirements for a multi-step task, before touching code

from "affaan-m/everything-claude-code"

Python testing strategies using pytest, TDD methodology, fixtures, mocking, parametrization, and coverage requirements.

from "affaan-m/everything-claude-code"

NestJS architecture patterns for modules, controllers, providers, DTO validation, guards, interceptors, config, and production-grade TypeScript backends.

from "affaan-m/everything-claude-code"

Design, implement, and refactor Ports & Adapters systems with clear domain boundaries, dependency inversion, and testable use-case orchestration across TypeScript, Java, Kotlin, and Go...

from "affaan-m/everything-claude-code"

Idiomatic C# and .NET patterns, conventions, dependency injection, async/await, and best practices for building robust, maintainable .NET applications.

from "affaan-m/everything-claude-code"

Clean Architecture patterns for Android and Kotlin Multiplatform projects — module structure, dependency rules, UseCases, Repositories, and data layer patterns.

from "affaan-m/everything-claude-code"

适用于Android和Kotlin多平台项目的Clean Architecture模式——模块结构、依赖规则、用例、仓库以及数据层模式。

from "affaan-m/everything-claude-code"

HIPAA-specific entrypoint for healthcare privacy and security work. Use when a task is explicitly framed around HIPAA, PHI handling, covered entities, BAAs, breach posture, or US healthcare...

from "affaan-m/everything-claude-code"

Create CodeTour .tour files — persona-targeted, step-by-step walkthroughs with real file and line anchors. Use for onboarding tours, architecture walkthroughs, PR tours, RCA tours, and...

from "affaan-m/everything-claude-code"

设计、实现并重构端口与适配器系统，具有清晰的领域边界、依赖反转以及跨 TypeScript、Java、Kotlin 和 Go 服务的可测试用例编排。

from "affaan-m/everything-claude-code"

在Claude Code会话期间，将做出的架构决策捕获为结构化的架构决策记录（ADR）。自动检测决策时刻，记录上下文、考虑的替代方案和理由。维护一个ADR日志，以便未来的开发人员理解代码库为何以当前方式构建。

from "affaan-m/everything-claude-code"

Go-specific design patterns and best practices including functional options, small interfaces, dependency injection, concurrency patterns, error handling, and package organization. Use when...

from "bytedance/deer-flow"

-

from "addyosmani/agent-skills"

Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as...

from "addyosmani/agent-skills"

Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to...

from "addyosmani/agent-skills"

Optimizes application performance. Use when performance requirements exist, when you suspect performance regressions, or when Core Web Vitals or load times need improvement. Use when...

from "addyosmani/agent-skills"

Extracts what the user actually wants instead of what they think they should want. Achieves this through one-question-at-a-time interview until 95% confidence about the underlying intent....

from "github/awesome-copilot"

Update an existing implementation plan file with new or update requirements to provide new features, refactoring existing code or upgrading packages, design, architecture or infrastructure.

from "github/awesome-copilot"

Create a new implementation plan file for new features, refactoring existing code or upgrading packages, design, architecture or infrastructure.

from "github/awesome-copilot"

Prompt for creating Product Requirements Documents PRDs for new features, based on an Epic.

from "github/awesome-copilot"

Prompt for creating an Epic Product Requirements Document PRD for a new epic. This PRD will be used as input for generating a technical architecture specification.

from "github/awesome-copilot"

Prompt for creating the high-level technical architecture for an Epic, based on a Product Requirements Document.