architecture-patterns

System and API design guidance covering component boundaries, data flow, integration patterns, and scalability considerations.

代码质量与审查1.8klibrary/methodologies/cc10x/skills/architecture-patterns/SKILL.md

Install

Send this to Claude Code, Codex or Cursor. The agent checks the Skill for safety first and installs it only after you confirm.

读取 https://funcoding.ai/skills/a5c-ai/babysitter/architecture-patterns/install.md ，按里面的步骤帮我安装这个 Skill。

SKILL.md

Single responsibility boundaries
Interface contracts and type safety
Dependency injection patterns
Module cohesion and coupling analysis

Data Flow

Request/response patterns
Event-driven architecture
State management strategies
Data transformation pipelines

Integration Patterns

API design (REST, GraphQL, RPC)
Message queuing and async processing
Service boundaries and communication
Error propagation across boundaries

Scalability

Horizontal vs vertical scaling considerations
Caching strategies
Database design and query optimization
Load balancing and distribution

Decision Checkpoints

Architectural decisions require user approval when:

Introducing new service boundaries
Changing data flow patterns
Adding new external dependencies
Modifying public API contracts

When to Use

During PLAN workflow architecture phases
During BUILD when architectural choices arise
When reviewing system design in REVIEW workflow

Agents Used

planner (architecture planning)
component-builder (architecture implementation)
code-reviewer (architecture review)

Similar Skills

claude-api

anthropics/skills180k

claude-api

Reference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).

Code quality & review

ponytail-review

DietrichGebert/ponytail158k

ponytail-review

Quality review of a change: is the logic right, is it safe, does it hold under real load, is risky code tested, is it fast enough, and is every line needed. Reads the connected code, not only the diff. Each finding is explained in plain English. Use for "review this", "code review", "review the last commit", "review my PR", "is this over-engineered", /ponytail-review.

Code quality & review

code-review-and-quality

addyosmani/agent-skills103k

code-review-and-quality

Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch. Use when asked to review a diff or a pull request, even when the diff is pasted inline.

Code quality & review

documentation-and-adrs

addyosmani/agent-skills103k

documentation-and-adrs

Records decisions and documentation. Use when you need to document an architecture decision (ADR) or the reasoning behind a design choice, when changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.

Code quality & review

code-simplification

addyosmani/agent-skills103k

code-simplification

Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.

Code quality & review

understand

Egonex-AI/Understand-Anything86k

understand

Analyze a codebase to produce an interactive knowledge graph for understanding architecture, components, and relationships

Code quality & review