Stacks Documentation
SkillsChangelog
TeamSponsorsPartnersPostcardwareAwesome StacksContributing

Routes

Copy page
Copy page as Markdown for LLMs
View as Markdown
View this page as plain text
Open in ChatGPT
Copy content and open ChatGPT
Open in Claude
Copy content and open Claude
Open in Perplexity
Search with Perplexity AI
On this page 5

stacks-routes · Backend and API · model-invoked

Where route files live and how they get registered. The organisational half of routing: files under routes/, the app/Routes.ts registry, prefixes and middleware groups.

When to reach for it

  • Creating route files in routes/
  • Registering them in app/Routes.ts
  • Using route prefixes and middleware groups
  • The default API routes structure

Inside the skill

The sections an agent reads once the skill loads.

  • Key Paths
  • Route Registry (app/Routes.ts)
  • Creating a Route File
  • Default API Routes (routes/api.ts)
  • Versioned Routes (routes/v1.ts)
  • Handler Types
  • CLI Commands
  • Gotchas

Where the code lives

  • Route files: routes/ (api.ts, v1.ts, buddy.ts, users.ts)
  • Route registry: app/Routes.ts

Using it

This one is model-invoked. Your agent reaches for it on its own when the task matches, and you can also call it by name:

/stacks-routes

Source: stacks-routes/SKILL.md. Shadow it for one project with app/Skills/stacks-routes/SKILL.md, then re-run buddy setup:ai. See Writing your own.