Validate PowerX HTTP handlers for CRUD, tenant, and DTO conventions.
npx skills add https://github.com/ArtisanCloud/PowerX --skill crud-http-ruleset
Please help me install this Agent Skill. Skill: crud-http-ruleset Source: https://github.com/ArtisanCloud/PowerX/tree/main/.codex/skills/crud/http-ruleset Command: npx skills add https://github.com/ArtisanCloud/PowerX --skill crud-http-ruleset
Enforces consistent, transport-layer-only HTTP CRUD behavior across the PowerX codebase so handlers remain thin, multi-tenant aware, and semantically equivalent to service and gRPC layers, reducing bugs and architectural drift.
Run the ruleset checks against internal/transport/http, fix any handler violations to align routes, tenant handling, DTO usage, and remove DB/IO from handlers.
High-intent search queries and answers about installing and using this skill.
To enforce HTTP CRUD conventions for Go API handlers, apply a ruleset that validates handler signatures, route prefixes under /api/v1/admin, and DTO usage. This guarantees a consistent API surface and detects architectural drift before production.
To prevent direct database access inside HTTP handlers, use a ruleset that forbids DB or external IO operations in the transport layer. This mandates handlers remain thin and centralizes audit, RBAC, and IO in the Service layer.
To standardize error and pagination responses for multi-tenant APIs, validate the use of unified DTOs for success envelopes, errors, and pagination. This ensures HTTP semantics remain equivalent to gRPC responses across your codebase.
Yes, you can validate tenant context injection in Go HTTP handlers. The ruleset mandates tenant context enforcement for handlers, ensuring they are multi-tenant aware and semantically equivalent to service and gRPC layers.
The best way to check route registration prefixes for admin endpoints is to run ruleset checks against files under internal/transport/http and validate that routes are registered under the /api/v1/admin prefix to guarantee a consistent API surface.
HTTP handlers should remain thin and avoid external IO in multi-tenant architectures to maintain separation of concerns. Centralizing audit, RBAC, and database operations in the Service layer reduces bugs and prevents architectural drift.
ArtisanCloudEnforce HTTP handler separation with DTO binding and service-layer business logic.
open-haxHalts task completion when lint or type errors are detected in codebase.
ArtisanCloudEnforce transactional boundaries, auditing, and standardized error translation in CRUD service layers.
chaorenex1Format and fix code errors across Python, JavaScript/TypeScript, Java, Go, and Rust.
