start-core/server-routes

Define server-side API endpoints with HTTP method handlers and middleware.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/cill-i-am/task-tracker --skill start-core-server-routes-cill-i-am
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: start-core/server-routes
Source: https://github.com/cill-i-am/task-tracker/tree/main/.agents/skills/tanstack-start-server-routes
Command: npx skills add https://github.com/cill-i-am/task-tracker --skill start-core-server-routes-cill-i-am

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Server-side API endpoints are defined alongside app routes, enabling cohesive routing architecture and streamlined deployment.

Core Features & Use Cases

  • Server routes defined with the server property on createFileRoute
  • HTTP method handlers: GET, POST, PUT, DELETE
  • Per-handler middleware via createHandlers
  • Access to handler context (request, params, context) and request parsing
  • Consistent response helpers and file-name conventions for routes

Quick Start

Create a server route using createFileRoute with a server object, including GET/POST handlers, and optional middleware.

Frequently Asked Questions about start-core/server-routes

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

FAQPage Schema
How do I define API endpoints alongside app routes in TypeScript?

You can define API endpoints alongside app routes by using the server property on createFileRoute, allowing cohesive routing architecture with GET, POST, PUT, and DELETE handlers.

How do I add middleware to specific API endpoint handlers?

You can add per-handler middleware to API endpoints by using the createHandlers function, applying processing logic before the final request handler executes.

What context is available when processing server route requests?

Server route handlers access a structured context containing the request object, route params, and shared context for consistent request parsing and response generation.

Does this routing approach support file-based naming conventions for server routes?

Yes, server routes utilize consistent file-name conventions for route definitions, ensuring streamlined deployment and cohesive routing architecture across the application.

What is the best way to structure HTTP method handlers for server-side routes?

The best way to structure HTTP method handlers is defining GET, POST, PUT, and DELETE functions directly within the server object on createFileRoute for clear endpoint management.