Claude Skills by thedixitjain

Comprehensive project architecture blueprint generator that analyzes codebases to create detailed architectural documentation. Automatically detects technology stacks and architectural patterns, generates visual diagrams, documents implementation patterns, and provides extensible blueprints for maintaining architectural consistency and guiding new development.

Comprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions.

Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes.

Capture architectural decisions made during Claude Code sessions as structured ADRs. Auto-detects decision moments, records context, alternatives considered, and rationale. Maintains an ADR log so future developers understand why the codebase is shaped the way it is.

Creates an Architecture Decision Record (ADR) documenting a significant technical decision, its context, alternatives considered, and consequences. Every major technical choice should have an ADR.

Generates a Mermaid architecture diagram showing high-level component relationships. Use when visualizing how plugins or modules fit together.

'Create architecture diagram creator operations. Auto-activating skill for Visual Content. Triggers on: architecture diagram creator, architecture diagram creator Part of the Visual Content skill category. Use when working with architecture diagram creator functionality. Trigger with phrases like \"architecture diagram creator\", \"architecture creator\", \"architecture\". '

Dark-themed SVG architecture/cloud/infra diagrams as HTML.

'Create architecture doc creator operations. Auto-activating skill for Technical Documentation. Triggers on: architecture doc creator, architecture doc creator Part of the Technical Documentation skill category. Use when working with architecture doc creator functionality. Trigger with phrases like \"architecture doc creator\", \"architecture creator\", \"architecture\". '

Applies CQRS and Event Sourcing for read/write separation and audit trails. Use when designing systems with complex domain logic or full state-change history.

Models a business in its own language. Use when the domain has real business rules to capture.

Applies event-driven async messaging to decouple producers and consumers. Use when designing real-time or multi-subscriber systems needing loose coupling.

Applies Functional Core, Imperative Shell to isolate logic from side effects. Use when business logic is entangled with I/O or unit tests are slow and brittle.

Applies hexagonal architecture isolating domain from infrastructure. Use when designing systems where testability and port/adapter separation are priorities.

Applies layered n-tier architecture with enforced boundaries. Use when designing moderate systems needing clear presentation, domain, and persistence layers.

Applies microkernel architecture with minimal core and plugin extensibility. Use when building platforms where third parties extend core functionality.

Applies microservices for independent deployment and per-service scaling. Use when teams need autonomous release cycles with distinct capability scaling needs.

Applies modular monolith with enforced internal boundaries. Use when teams want service-level autonomy without distributed system overhead.

Applies coarse-grained service architecture for deployment independence. Use when independent deployment is needed but shared databases rule out microservices.

Applies data-grid architecture for high-traffic stateful workloads. Use when a single database cannot scale and in-memory partitioning is needed.

Selects and routes to the right architecture paradigm. Use when choosing patterns for a new system or comparing trade-offs before making architecture decisions.

Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use this skill when designing clean architecture for a new microservice, when refactoring a monolith to use bounded contexts, when implementing hexagonal or onion architecture patterns, or when debugging dependency cycles between application layers.

Master proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design to build maintainable, testable, and scalable systems.

Assesses architecture decisions, ADR compliance, and coupling. Use when evaluating design changes or validating structural decisions before merging.

Validates completeness and consistency of the project architecture against all GDDs. Builds a traceability matrix mapping every GDD technical requirement to ADRs, identifies coverage gaps, detects cross-ADR conflicts, verifies engine compatibility consistency across all decisions, and produces a PASS/CONCERNS/FAIL verdict. The architecture equivalent of /design-review.

System architecture patterns including monolith, microservices, event-driven, and serverless, with C4 modeling, scalability strategies, and technology selection criteria. Use when designing system architectures, evaluating patterns, or planning scalability.

Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.

Downloads, exports, and inspects existing Arize traces and spans to understand what an LLM app is doing or debug runtime issues. Covers exporting traces by ID, spans by ID, sessions by ID, and root-cause investigation using the ax CLI. Use when the user wants to look at existing trace data, see what their LLM app is doing, export traces, download spans, investigate errors, or analyze behavior regressions.

Ask which skill or flow fits your situation. A router over the skills in this repo.

Use when positioning an ASPLOS submission against three communities' literatures at once — covering the architecture, OS/systems, and PL/compiler lanes plus accelerator and prior-ASPLOS lines, handling own-work and arXiv material under the 2027 double-blind rules, and meeting the full-name/DOI citation format.

Use when deciding whether a project belongs at ASPLOS or at a single-community venue — applying the cross-layer deletion test, matching against ASPLOS's architecture/PL/OS intersection identity, routing to ISCA/MICRO/HPCA, PLDI/POPL, SOSP/OSDI/EuroSys, SC, or MLSys instead, and choosing between the April and September deadlines.

Build, review, refactor, or architect ASP.NET Core web applications using current official guidance for .NET web development. Use when working on Blazor Web Apps, Razor Pages, MVC, Minimal APIs, controller-based Web APIs, SignalR, gRPC, middleware, dependency injection, configuration, authentication, authorization, testing, performance, deployment, or ASP.NET Core upgrades.

'Diagnose and fix AssemblyAI common errors and exceptions. Use when encountering AssemblyAI errors, debugging failed transcriptions, or troubleshooting streaming and LeMUR issues. Trigger with phrases like \"assemblyai error\", \"fix assemblyai\", \"assemblyai not working\", \"debug assemblyai\", \"transcription failed\". '

'Collect AssemblyAI debug evidence for support tickets and troubleshooting. Use when encountering persistent issues, preparing support tickets, or collecting diagnostic information for AssemblyAI problems. Trigger with phrases like \"assemblyai debug\", \"assemblyai support bundle\", \"collect assemblyai logs\", \"assemblyai diagnostic\". '

'Optimize AssemblyAI API performance with caching, parallel processing, and model selection. Use when experiencing slow transcriptions, implementing caching strategies, or optimizing throughput for batch transcription workloads. Trigger with phrases like \"assemblyai performance\", \"optimize assemblyai\", \"assemblyai latency\", \"assemblyai caching\", \"assemblyai slow\", \"assemblyai batch\". '

'Implement AssemblyAI reference architecture with best-practice project layout. Use when designing new AssemblyAI transcription services, reviewing project structure, or building production-grade speech-to-text applications. Trigger with phrases like \"assemblyai architecture\", \"assemblyai best practices\", \"assemblyai project structure\", \"how to organize assemblyai\", \"assemblyai design\". '

'Apply production-ready AssemblyAI SDK patterns for TypeScript and Python. Use when implementing AssemblyAI integrations, refactoring SDK usage, or establishing team coding standards for transcription workflows. Trigger with phrases like \"assemblyai SDK patterns\", \"assemblyai best practices\", \"assemblyai code patterns\", \"idiomatic assemblyai\". '

'Analyze, plan, and execute AssemblyAI SDK upgrades with breaking change detection. Use when upgrading the assemblyai npm package, migrating from the old SDK, or switching between speech models (Best, Nano, Universal). Trigger with phrases like \"upgrade assemblyai\", \"assemblyai migration\", \"assemblyai breaking changes\", \"update assemblyai SDK\". '

AST-based code search and refactoring via ast-grep MCP

Build content-focused websites with Astro — zero JS by default, islands architecture, multi-framework components, and Markdown/MDX support.

Core Python library for astronomy and astrophysics workflows that need Astropy APIs, including units/quantities, coordinates, FITS I/O, tables, time systems, WCS, and cosmology. Use when implementing or debugging astronomical data analysis code with Astropy.

Master Python asyncio, concurrent programming, and async/await patterns for high-performance applications. Use when building async APIs, concurrent systems, or I/O-bound applications requiring non-blocking operations.

Comprehensive guidance for implementing asynchronous Python applications using asyncio, concurrent programming patterns, and async/await for building high-performance, non-blocking systems.

Maintain per-repo and cross-repo changelogs — append structured entries after agent work. Use when asked to \"log this change\", \"update changelog\", \"what changed\", \"change history\".

'Collect Attio integration diagnostic evidence -- API health, scopes, object schema, and rate limit status -- for debugging or support tickets. Trigger: \"attio debug\", \"attio support bundle\", \"attio diagnostic\", \"collect attio logs\", \"attio not working debug\". '

'Optimize Attio API performance -- caching, batch queries, pagination strategies, connection pooling, and latency reduction. Trigger: \"attio performance\", \"optimize attio\", \"attio slow\", \"attio latency\", \"attio caching\", \"attio batch requests\". '

'Production reference architecture for Attio CRM integrations -- layered project structure, sync patterns, webhook processing, and multi-environment setup. Trigger: \"attio architecture\", \"attio best practices\", \"attio project structure\", \"how to organize attio\", \"attio integration design\". '

'Migrate between Attio API versions, handle breaking changes in the v1-to-v2 transition, and plan for future deprecations. Trigger: \"upgrade attio\", \"attio migration\", \"attio v1 to v2\", \"attio breaking changes\", \"attio API version\", \"attio deprecation\". '

Use when targeting Automatica or deciding whether a systems-and-control manuscript fits this venue. Encodes the journal's fit, the methodological-breadth-with-guarantees bar, theory rigor, the Automatica-vs-TAC routing, house style, official-submission re-check, and desk-reject heuristics.

| How Cavekit's autonomous execution loop works — state machine, stop hook, completion sentinel, lock, budgets, iteration cap. Read this skill any time you are about to run /ck:make, debug a stuck session, or write a new command that needs the loop. Trigger phrases: \"how does the loop work\", \"stop hook\", \"autonomous\", \"completion sentinel\", \"why is the session looping\".