All authors
Claude Skills by robsonkades
github.com/robsonkades305 skills0 installs424 views
- Service Data OwnershipDefine and verify data authority and access contracts when services, jobs or integrations share writers, read private tables, or bypass supported interfaces. Inventory readers and writers, choose supported access paths, enforce credentials and grants, and expire temporary exceptions. Use after identifying a service boundary; does not decide service extraction, implement sagas, tune ORM queries, or execute data-ownership transfer migrations.Votes: 0GitHub stars: 2
- Service DiscoveryDesign and diagnose endpoint discovery when membership changes, clients cache stale information or bootstrap depends on an unavailable source. Define authority, update, expiry and failure contracts separately from load balancing.Votes: 0GitHub stars: 2
- Service Identity And TrustDesign trust between services when workloads authenticate, propagate user or tenant identity, delegate authority, or change credential issuance, rotation or revocation. Map trust boundaries, allowed operations and outage behavior; use when an internal network, gateway header or valid token is being treated as sufficient permission. Covers architecture and verification contracts, not Spring filter-chain implementation or identity-provider construction.Votes: 0GitHub stars: 2
- Spring Boot Clean ArchitectureImplement or repair Clean Architecture boundaries in Java/Spring Boot when domain policies, use-case orchestration and framework mechanisms are mixed. Allocate rules, distinguish source dependencies from execution flow, choose simple results or output presenters, and preserve transaction and authorization behavior during incremental migration. Excludes architecture-style selection and detailed HTTP, ORM or distributed-system design.Votes: 0GitHub stars: 2
- Spring Boot Hexagonal ArchitectureImplement or repair an agreed ports-and-adapters boundary in Java 25 and Spring Boot 4 applications. Use when one use case must serve multiple entry points, business rules leak into adapters, or external integration needs an application-owned contract. Owns port semantics, adapter substitution, Spring composition and boundary verification; excludes architecture-style selection, detailed MVC and ORM mechanics.Votes: 0GitHub stars: 2