crud-index

Route CRUD tasks to appropriate sub-skills across HTTP, gRPC, migrations, models, repositories, and services.

357|65|Updated Jul 29, 2022
One-click install
npx skills add https://github.com/ArtisanCloud/PowerX --skill crud-index
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: crud-index
Source: https://github.com/ArtisanCloud/PowerX/tree/main/.codex/skills/crud/index
Command: npx skills add https://github.com/ArtisanCloud/PowerX --skill crud-index

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The CRUD index consolidates and routes CRUD-related tasks to the appropriate atomic sub-skills based on the task channel, enabling predictable and maintainable data operations across the PowerX platform.

Core Features & Use Cases

  • Route tasks to the correct sub-skill (crud/http, crud/grpc, crud/migration, crud/model, crud/repository, crud/service) based on the channel.
  • Coordinate cross-cutting concerns such as task boundaries, channel priorities, and frontend linkage when needed (e.g., frontend/nuxt).
  • Use Case: A new data record needs to be created via HTTP; the index dispatches to crud/http, handles response routing, and aggregates results from subsequent sub-skills.

Quick Start

Route a sample CRUD task through the index to the appropriate sub-skill (http/grpc/migration/model/repository/service) and verify end-to-end execution.

Frequently Asked Questions about crud-index

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

FAQPage Schema
How do I coordinate CRUD tasks across HTTP and gRPC channels?

Routing CRUD operations by channel dispatches HTTP and gRPC requests to dedicated sub-skills, coordinating execution flow, aggregating results, and enforcing boundaries for consistent data operations across the platform.

What is the best way to route a new data record creation via HTTP to the correct service?

Using a CRUD index dispatches the HTTP creation request to the http sub-skill, routes the response, and aggregates results from subsequent service and repository sub-skills for end-to-end execution.

Does the CRUD index support routing to database migration and model sub-skills?

Yes, the index routes tasks to crud/migration and crud/model alongside http, grpc, repository, and service sub-skills, applying modular coordination to ensure consistent task flow and predictable results.

Can I use this routing approach to coordinate frontend linkage with Nuxt?

Yes, the index coordinates cross-cutting concerns including frontend linkage with nuxt, managing task boundaries and channel priorities to ensure proper handoffs and predictable results across the stack.

Why does my CRUD task execution fail to maintain consistent flow across different protocols?

Inconsistent CRUD flow occurs without a central index to enforce task boundaries and channel routing. The index applies modular coordination to dispatch operations to the correct sub-skills, ensuring predictable results.