code-philosophy
Internal logic and data flow philosophy (The 5 Laws of Elegant Defense). Understand deeply to ensure code guides data naturally and prevents errors.
Discover databases architecture patterns skills, compare source repositories and read the instructions for each workflow.
Internal logic and data flow philosophy (The 5 Laws of Elegant Defense). Understand deeply to ensure code guides data naturally and prevents errors.
Competence in data analytics and machine learning, enabling developers to build data-driven features and integrate AI/ML capabilities.
Communicating the intended behavior and context of code through clear documentation and comments, and sharing knowledge with the team.
The practice of restructuring and simplifying code continuously – reducing complexity, improving design, and keeping codebases clean.
Working effectively with others in coding projects – including code reviews, clear communication, and contributing to shared or open-source codebases.
Leveraging AI coding assistants and tools to boost development productivity, while maintaining oversight to ensure quality results.
Writing clean, understandable, and self-documenting code that is easy to review and maintain over time.
Incorporating security at every step of software development – writing code that defends against vulnerabilities and protects user data.
Use when designing or architecting Elixir/Phoenix applications, creating comprehensive project documentation, planning OTP supervision trees, defining domain models with Ash Framework, structuring multi-app pro...
Use when writing async/await code, enabling strict concurrency, fixing Sendable errors, migrating from completion handlers, managing shared state with actors, or using Task/TaskGroup for concurrency.
Reference for Splitrail's core data types. Use when working with ConversationMessage, Stats, DailyStats, or other type definitions.
Performance optimization guidelines for Splitrail. Use when optimizing parsing, reducing memory usage, or improving throughput.
Common logging patterns and practices. This skill is designed to be included in composite skills via the 'includes' feature.
Foundation for error handling patterns. This is a base skill designed to be extended by language-specific error handling skills.
Common testing patterns and practices. This skill is designed to be included in composite skills via the 'includes' feature.
A comprehensive skill for Rust development that combines error handling, testing, and logging patterns. Demonstrates the 'includes' composition feature by merging content from multiple standalone skills.
Rust-specific error handling patterns, building on the base error handling skill. Demonstrates the 'extends' composition feature.
Build consistent design systems with tokens, components, and theming. Use when creating component libraries, implementing design tokens, building theme systems, or ensuring design consistency. Triggers on desig...
Universal execution engine using scientific method to achieve ideal state. USE WHEN complex tasks, multi-step work, "run the algorithm", "use the algorithm", OR any non-trivial request that benefits from struct...
Implement Event-Driven Architecture (EDA) in Spring Boot using ApplicationEvent, @EventListener, and Kafka. Use for building loosely-coupled microservices with domain events, transactional event listeners, and...
Testing Spring application events (ApplicationEvent) with @EventListener and ApplicationEventPublisher. Test event publishing, listening, and async event handling in Spring Boot applications. Use when validatin...
Implement REST API design standards and best practices for Spring Boot projects. Use when creating or reviewing REST endpoints, DTOs, error handling, pagination, security headers, HATEOAS and architecture patte...
Implement persistence layers with Spring Data JPA. Use when creating repositories, configuring entity relationships, writing queries (derived and @Query), setting up pagination, database auditing, transactions,...
Implement distributed transactions using the Saga Pattern in Spring Boot microservices. Use when building microservices requiring transaction management across multiple services, handling compensating transacti...
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.