coding-principles
Universal coding principles and best practices for maintainable software
Discover devops architecture patterns skills, compare source repositories and read the instructions for each workflow.
Universal coding principles and best practices for maintainable software
Universal patterns for using MCP (Multi-Client Protocol) servers in agentic workflows
Universal testing strategies and best practices for software projects
REST API design best practices, versioning strategies, error handling, pagination, and OpenAPI documentation. Use when designing or implementing REST APIs, HTTP endpoints, or API documentation.
This skill should be used when designing system architecture, making architectural decisions, or evaluating design patterns. It provides guidance on common patterns, ADR templates, design principles, and tradeo...
Domain type design and architectural planning for Go code. Use when planning new features, designing self-validating types, preventing primitive obsession, or when refactoring reveals need for new types. Focuse...
Per-task ralph loop pattern for implementation and debugging. One loop per task, not one loop per feature.
Skill for creating and editing Architecture Decision Records (ADRs). Use when requests involve "create ADR", "record architecture decision", or "document design decisions". Supports creating new ADRs, updating...
Use when choosing between CloudKit vs iCloud Drive, implementing reliable sync, handling offline-first patterns, or designing sync architecture - prevents common sync mistakes that cause data loss
Use when needing synchronous actor access in tests, legacy delegate callbacks, or performance-critical code. Covers MainActor.assumeIsolated, @preconcurrency protocol conformances, crash behavior, Task vs assum...
Generate professional draw.io diagrams in XML format from architectural descriptions. Use when Claude needs to create visual diagrams for (1) System architecture diagrams, (2) Microservices layouts, (3) Workflo...
Generate detailed architectural descriptions of IT systems from short prompts. Produces structured output with overview, components list, connections/integrations, and ASCII diagrams with annotated arrows. Use...
Gerencia persistencia de contexto, decisoes e learnings do projeto. Armazena e recupera informacoes entre sessoes para manter continuidade. Use quando: salvar decisoes, recuperar contexto, persistir learnings.
Motor de decisão para System Design. Use quando a pessoa usuária pedir para desenhar, decidir, revisar ou defender uma arquitetura. O foco é identificar padrões recorrentes, exigir perguntas obrigatórias, força...
Use when designing Go interfaces including interface design, duck typing, and composition patterns. Use when designing Go APIs and abstractions.
Provide patterns for implementing Role-Based Access Control and multi-tenant authorization in laneweaverTMS. Use when implementing user roles, permissions, tenant isolation, Echo authorization middleware, RLS p...
Use when implementing Go concurrency with goroutines, channels, and sync patterns. Use when writing concurrent Go code.
Concurrent agent dispatch for independent problems. Use when facing multiple independent tasks that can be worked on simultaneously. Reduces total time by parallelizing work that has no shared state.
Guidance on when and how to apply design patterns. Use when: (1) asking which pattern to use, (2) refactoring code, (3) discussing code smells, (4) need to decouple components, (5) building extensible systems.
Enforce a precise, minimal design system inspired by Linear, Notion, and Stripe. Use this skill when building dashboards, admin interfaces, or any UI that needs Jony Ive-level precision - clean, modern, minimal...
Testing patterns, fixtures, and best practices for Kubani. Use this skill when writing or running tests.
Standard code patterns and conventions used in Kubani. Reference this skill when writing new code or reviewing existing code.
Kubani architecture principles, patterns, and design decisions. Use this skill when making architectural decisions or understanding the system design.
Four-phase debugging framework with root cause tracing - understand the source before proposing fixes. Use when investigating bugs, errors, unexpected behavior, or failed tests.
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.