skills.rest
ArtisanCloud
ArtisanCloudOFFICIAL
Explore all skills by this author →
GitHub

crud-grpc

Standardize CRUD operations over gRPC for PowerX services.

357|65|Updated Jul 29, 2022
Search Tags:#crud#error-handling#grpc#multitenancy#proto#interceptor
One-click install
npx skills add https://github.com/ArtisanCloud/PowerX --skill crud-grpc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: crud-grpc
Source: https://github.com/ArtisanCloud/PowerX/tree/main/.codex/skills/crud/grpc
Command: npx skills add https://github.com/ArtisanCloud/PowerX --skill crud-grpc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It resolves inconsistencies between HTTP and gRPC CRUD implementations in PowerX, ensuring that all services follow a single, contract‑driven approach for multi‑tenant, paginated, and audited operations.

Core Features & Use Cases

  • Proto Contracts: Centralized .proto definitions with versioning via Buf.
  • Server Handlers: Auto‑generated gRPC servers that only bind request data, invoke services, and map errors.
  • Interceptors: Built‑in authentication, tenant resolution, tracing, and recovery layers.
  • Error & Pagination Mapping: Guarantees parity with HTTP error codes and paging semantics.
  • Use Case Example: Apply the Skill to the IAM module to expose Member and Team CRUD operations over gRPC without writing business logic in the transport layer.

Quick Start

Generate the gRPC CRUD layer for the IAM service following the Skill's guidelines.

Frequently Asked Questions about crud-grpc

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize CRUD operations over gRPC for multi-tenant services?▼

You standardize gRPC CRUD by applying centralized proto contracts, auto-generated server handlers, and built-in interceptors for tenant resolution. This enforces a contract-driven approach for paginated and audited multi-tenant operations.

How do I map gRPC error codes to match existing HTTP error semantics?▼

Mapping gRPC error codes to HTTP semantics requires an error translation layer. This guarantees parity with existing HTTP error codes and paging semantics across the service implementation.

Can I expose multi-tenant CRUD operations over gRPC without writing business logic in the transport layer?▼

Yes, auto-generated gRPC servers bind request data, invoke services, and map errors without transport-layer business logic. Built-in interceptors handle authentication, tenant resolution, tracing, and recovery automatically.

What's the best way to manage proto definitions and versioning for gRPC services?▼

Managing proto definitions and versioning is handled through centralized .proto files with versioning via Buf. This enforces consistent proto contracts across all gRPC server handlers and service implementations.

Does gRPC pagination mapping work consistently with existing HTTP paging semantics?▼

Yes, gRPC pagination mapping guarantees parity with existing HTTP paging semantics. This ensures consistent data retrieval behaviors across both transport implementations within the same module.

Related Skills

Explore More Software Engineering Skills→
ArtisanCloudArtisanCloud
357

crud-proto-gen

Generate protobuf definitions and Go stubs for PowerX services.

Official
Intermediate
vincent119vincent119

go-grpc

Standardize Go gRPC service development with Buf code generation and interceptor stacks.

Community
Advanced
ArtisanCloudArtisanCloud
357

crud-http-ruleset

Validate PowerX HTTP handlers for CRUD, tenant, and DTO conventions.

Official
Advanced
muratmirgunmuratmirgun
8

go-grpc

Design and harden Go gRPC services with versioned proto contracts and secure transport.

Community
Advanced