new-domain-endpoint

Generate full-stack API endpoints and domain files in the GameLab monorepo.

Updated Feb 10, 2026
One-click install
npx skills add https://github.com/Jason-hub-star/GameLab --skill new-domain-endpoint-jason-hub-star
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: new-domain-endpoint
Source: https://github.com/Jason-hub-star/GameLab/tree/main/.claude/skills/page-skills/page/new-domain-endpoint
Command: npx skills add https://github.com/Jason-hub-star/GameLab --skill new-domain-endpoint-jason-hub-star

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers often need to add new backend routes and matching frontend clients manually, which is time‑consuming and error‑prone.

Core Features & Use Cases

  • Automated scaffold: Generates backend model, router, and updates main registration.
  • Frontend sync: Creates TypeScript types, API client, and updates barrel files.
  • Validation: Enforces naming conventions, adds header comments, and runs pre‑commit checks.
  • Use case: When a product team decides to expose a new resource like “Project” or “Label”, this skill creates all necessary files across the monorepo in seconds.

Quick Start

Ask the assistant to create a new domain named “project” with a GET endpoint.

Frequently Asked Questions about new-domain-endpoint

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

FAQPage Schema
How do I generate a full-stack API endpoint and domain files in a monorepo?

To generate a full-stack API endpoint, specify the domain name, HTTP method, request and response shapes, and an optional Supabase table. The skill automatically creates backend models, routers, frontend TypeScript types, and API clients across the monorepo.

What is the best way to scaffold a new backend resource and frontend client together?

Scaffolding a new backend resource and frontend client together is best handled by automating file generation. This approach updates router registration, barrel exports, and TypeScript types simultaneously, preventing manual synchronization errors between backend routes and frontend API clients.

Do I need a Supabase table to create a new domain endpoint?

You do not need a Supabase table to create a new domain endpoint; it is an optional specification. The core requirement is providing the domain name, HTTP method, and the request and response shapes to generate the necessary full-stack domain files.

Can I enforce naming conventions and pre-commit validation when adding an API endpoint?

You can enforce naming conventions and pre-commit validation when adding an API endpoint. The generated files include header comments and run pre-commit checks to ensure the new backend resource and frontend client align with the monorepo standards.

Why does manually adding backend routes and frontend clients cause errors?

Manually adding backend routes and frontend clients causes errors because it requires updating router registration, barrel exports, and TypeScript types separately. This time-consuming manual synchronization process is inherently prone to human error across the monorepo.