governing-logic-placement

What problem does it solve?

This Skill provides a structured decision framework to determine the optimal placement of business logic, ensuring data integrity and maintainability by deciding whether logic belongs in the database layer or the application layer.

Core Features & Use Cases

• Decision Matrix: A clear table guiding placement decisions for various logic types (e.g., constraints, RLS, workflows).
• Database Layer Guidance: Detailed explanations and examples for using CHECK constraints, Foreign Keys, RLS, EXCLUDE constraints, partial unique indexes, and deferrable constraints.
• Application Layer Guidance: Explanations for placing workflow orchestration, dynamic business rules, and complex calculations.
• Hybrid Patterns: Best practices for audit trails and updated-at timestamps.
• Use Case: When designing a new feature that requires enforcing a business rule, use this Skill to decide if the rule should be a database constraint or an application-level validation.

Quick Start

Use the governing-logic-placement skill to decide where to implement a new business rule that ensures a user cannot have more than 5 active API keys.