new-endpoint

Scaffold Express.js and TypeScript API endpoints with controllers, routes, and Swagger documentation.

Updated Aug 9, 2025

Search Tags:#typescript #scaffold #swagger #crud #endpoint #express #generate

Ready to run

npx skills add https://github.com/pabloibanezcom/fintrak --skill new-endpoint

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: new-endpoint
Source: https://github.com/pabloibanezcom/fintrak/tree/main/.claude/skills/new-endpoint
Command: npx skills add https://github.com/pabloibanezcom/fintrak --skill new-endpoint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates scaffolding a complete API endpoint by generating a controller, route, and Swagger documentation, reducing manual setup time.

Core Features & Use Cases

Create an Express.js + TypeScript endpoint with a ready-to-use controller, route, and Swagger docs.
Generate a standard CRUD skeleton and ensure API surface is documented for immediate testing.
Use Case: when adding a new resource like 'Feature', this skill creates all necessary files and wiring.

Quick Start

Run the new-endpoint workflow to generate the endpoint scaffold in your API project.

Frequently Asked Questions about new-endpoint

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

FAQPage Schema

How do I scaffold a new Express.js TypeScript API endpoint with CRUD routes?▼

To scaffold an Express.js TypeScript endpoint, run the workflow to generate a controller, route, and Swagger docs. It creates standard CRUD skeletons under your apps/api/src directory with proper imports and route wiring.

What is the fastest way to generate Swagger documentation for a new Express API resource?▼

Generating Swagger documentation is handled automatically when scaffolding a new endpoint. The workflow creates Swagger annotations alongside the controller and route files, ensuring the API surface is documented for immediate testing.

Do I need to manually wire routes when adding a new resource to an Express TypeScript project?▼

Manual route wiring is unnecessary because the scaffold process handles it automatically. When you generate a new resource, the workflow ensures proper imports and route wiring are applied directly in your apps/api/src folder.

Can I use this to generate a CRUD controller and route for a TypeScript Express API?▼

Yes, you can use this to generate a standard CRUD controller and route for a TypeScript Express API. It produces a ready-to-use skeleton with zero boilerplate, allowing you to immediately test the new resource endpoints.

What are the limitations of auto-scaffolding CRUD endpoints for an Express API?▼

Auto-scaffolding CRUD endpoints generates standard skeletons, meaning custom business logic must be implemented manually afterward. It applies specifically to Express.js and TypeScript APIs, creating files strictly under the apps/api/src directory structure.