What problem does it solve? Designing resource architecture in the Go CMS backend is error-prone: mixing tree resources with high-volume LibraryItem collections, leaking PostgreSQL partition details into domain code, or allowing route collisions can cause serious data and scalability problems. This Skill encodes the architectural invariants and design rules for the CMS resource model. ## Core Features & Use Cases - Resource Model Guidance: Enforces separation of resource identity, tree placement, and physical storage, including the Library vs LibraryItem distinction. - Routing and URL Patterns: Defines a small URL-pattern DSL, route namespace collision checks, and bounded validation that never loads entire collections into memory. - Storage and Lifecycle Rules: Keeps PostgreSQL partitioning behind repository adapters and defines move, soft-delete, permission, and pagination invariants. - Use Case: When adding a new resource type or modifying Library behavior, follow this Skill to validate type immutability, route uniqueness, and adapter boundaries before writing code. ## Quick Start Ask the AI to review or design a change to the Go CMS resource model, such as adding a LibraryItem move operation, using the go-cms-resources guidelines.
