ClaudSkillsEngineering › Page 24

Claude Engineering Skills (Page 24 of 163)

Code review, refactoring, testing, DevOps, CI/CD, databases, cloud platforms, and full-stack development skills for Claude Code.

9,773 skills · updated 2026-05-03 · showing 1381–1440 of 9,773 by quality score

Comprehensive frontend architecture analyzer that identifies technology stacks, build tools, and architectural patterns.
Score 70/100
Analyze and visualize software architecture patterns, dependencies, and module boundaries for migration planning
Score 70/100
Evaluates codebase architecture for patterns, anti-patterns, coupling, cohesion, scalability, and technical debt.
Score 70/100
Comprehensive project consistency review across code, documentation, diagrams, and configuration
Score 70/100
Architecture audit and analysis specialist for Modular Monoliths. **ALWAYS use when reviewing codebase architecture, evaluating bounded contexts, assessing shared kernel size,…
Score 70/100
Architecture-aware project initialization combining online research with archetype selection.
Score 70/100
Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.
Score 70/100
プロジェクトで使用しているアーキテクチャの実装ベストプラクティスを調査し、 docs/best-practices.md にドキュメント化する。技術スタックを自動検出し、 スタック別のベストプラクティス(コード例・アンチパターン)を出力する。 「ベストプラクティスをまとめて」「実装パターンを調べて」「コーディングガイドを作成」…
Score 70/100
Orchestrates parallel specialized agents for major architectural decisions. Spawns perspective agents (Schema-Sage, Repo-Maven, Event-Oracle, etc.), collects findings to shared…
Score 70/100
Create and manage Architecture Decision Records (ADRs) for documenting important architectural decisions, tradeoffs, and rationale.
Score 70/100
Comprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions.
Score 70/100
Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation.
Score 70/100
Guides the selection and documentation of architectural decisions using ADR patterns.
Score 70/100
When the user needs to design or evaluate system architecture — service boundaries, data models, API contracts, infrastructure topology, database selection, or dependency…
Score 70/100
PRDと機能設計書に基づいてアーキテクチャ設計書を作成するスキル。docs/prd.md と docs/functional-design.md…
Score 70/100
Conducts comprehensive architecture design reviews including system design validation, architecture pattern assessment, quality attributes evaluation, technology stack review, and…
Score 70/100
Use when designing new high-level system architecture, reviewing existing designs, or making architectural decisions.
Score 70/100
Create professional, dark-themed architecture diagrams as standalone HTML files with SVG graphics. Use when the user asks for system architecture diagrams, infrastructure…
Score 70/100
Architecture Diagram Creator - Auto-activating skill for Visual Content. Triggers on: architecture diagram creator, architecture diagram creator Part of the Visual Content skill…
Score 70/100
Create professional architecture diagrams using D2, Draw.io, Mermaid, and OCI official icons for enterprise-grade visualizations
Score 70/100
Guide users through discovering and defining system architecture through structured conversation. Triggers on "I want to build", "design a system", "architect", "planning a new…
Score 70/100
Systematic completeness audit of Architecture Documentation using 188-item viewpoint-based checklist, severity-classified gap detection, technical debt indicators, and…
Score 70/100
Architecture Doc Creator - Auto-activating skill for Technical Documentation. Triggers on: architecture doc creator, architecture doc creator Part of the Technical Documentation…
Score 70/100
Architecture Doc Creator - Auto-activating skill for Technical Documentation. Triggers on: architecture doc creator, architecture doc creator Part of the Technical Documentation…
Score 70/100
Create and maintain architecture documentation with Mermaid diagrams. Use when writing technical documentation, system diagrams, or updating the implementation plan.
Score 70/100
Create comprehensive technical documentation for code systems including data flow diagrams, architecture overviews, algorithm documentation, cheat sheets, and multi-file…
Score 70/100
Document system architecture and technical design decisions for effective team communication and ...
Score 70/100
Manage architecture changes with impact analysis, ADR generation, and migration planning. Use when relevant to the task.
Score 70/100
Track architectural decisions and detect drift from ADRs (Architecture Decision Records). Calculate alignment score (0.00-1.00) showing code-to-design conformance.
Score 70/100
Convert raw project structure into clear architectural understanding — module boundaries, data flows, service relationships, and architectural patterns.
Score 70/100
Analyze, review, and plan architecture alternatives through a structured interview. Use when the user needs tradeoffs surfaced before implementation or a Linear decision note…
Score 70/100
Detect clean architecture layer violations and check dependency rule violations. Verify dependency direction of events→facades→services→repository.
Score 70/100
Create or revise repository `ARCHITECTURE.md` files as short, stable architecture codemaps. Use when an agent needs to author or edit `ARCHITECTURE.md`, restructure an…
Score 70/100
Build comprehensive ARCHITECTURE.md files following matklad's canonical guidelines — bird's-eye views, ASCII/Mermaid diagrams, codemaps, invariants, and layer boundaries.
Score 70/100
Client-server architecture for web/mobile apps with centralized services and API design.
Score 70/100
Apply CQRS and Event Sourcing for read/write separation and audit trails. Use when auditability is critical.
Score 70/100
Apply event-driven async messaging to decouple producers and consumers. Use for real-time processing.
Score 70/100
Functional Core, Imperative Shell: isolate deterministic logic from side effects for testability.
Score 70/100
Hexagonal (Ports and Adapters) architecture isolating domain logic from infrastructure.
Score 70/100
Layered (n-tier) architecture with enforced layer boundaries and separation of concerns.
Score 70/100
Microkernel architecture with a minimal core and plugin-based extensibility for platforms.
Score 70/100
Apply microservices for independent deployment and per-service scaling. Use when bounded contexts are clear.
Score 70/100
Design pipes-and-filters for sequential data transformations. Use when data flows through processing stages.
Score 70/100
Apply serverless FaaS patterns for event-driven workloads with minimal infrastructure. Use when cost scales with usage.
Score 70/100
Design coarse-grained service architecture for deployment independence without microservices complexity and overhead.
Score 70/100
Apply data-grid architecture for high-traffic stateful workloads with in-memory processing and linear scalability.
Score 70/100
Recommend architecture patterns (monolith, microservices, serverless, modular monolith) based on scale, team size, and constraints.
Score 70/100
Master proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design to build maintainable, testable, and scalable systems.
Score 70/100
Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design.
Score 70/100
Core architectural principles for StepLeague - modular design, system thinking, future-proofing, and maintenance reduction.
Score 70/100
Core architecture principles (SSOT, DRY, Anti-Spaghetti) for maintainable code design. Use when planning features, implementing code, or reviewing architecture to prevent…
Score 70/100
Creates an upfront system architecture proposal before implementation begins. Defines bounded contexts, layer strategy, system-wide patterns, and quality attributes — the…
Score 70/100
Quick reference for Portfolio Buddy 2 project structure. Use when: adding new features, modifying existing components, understanding data flow, or onboarding to the codebase.
Score 70/100
Meta-skill for maintaining and evolving Alex's cognitive architecture through deliberate documentation and pattern extraction.
Score 70/100
Expert in Gravito architecture and clean code. Trigger this for refactoring, design pattern implementation, or architectural audits.
Score 70/100
Assess architecture decisions, ADR compliance, coupling analysis, and design principles
Score 70/100
Use when making architectural decisions, planning features, designing new components, reviewing PRs, or validating that proposed changes align with Clean Architecture principles.
Score 70/100
System architecture patterns including monolith, microservices, event-driven, and serverless, with C4 modeling, scalability strategies, and technology selection criteria.
Score 70/100
Automated SRP validation using multi-dimensional detection. Use when reviewing code for SRP compliance, checking "is this doing too much", validating architectural boundaries,…
Score 70/100
Comprehensive system architecture design and implementation workflow that orchestrates expert analysis, technical decision-making, and architectural pattern selection using the…
Score 70/100
Search all 9,773 Engineering skills →