cloudwerk-routing
Cloudwerk Routing
File-based routing conventions for Cloudwerk. The app/ directory structure maps directly to URL patterns, with special filenames determining behavior.
When to Apply
Reference these guidelines when:
- Creating new pages or API routes in a Cloudwerk app
- Adding layouts that wrap multiple pages
- Implementing middleware for auth, rate limiting, or request processing
- Using dynamic route segments (
[id],[...slug]) - Loading data with
loader()or handling mutations withaction() - Adding error or not-found boundaries
Rule Categories by Priority
More from squirrelsoft-dev/cloudwerk
cloudwerk-config
Configuration reference for Cloudwerk applications. Use when setting up cloudwerk.config.ts, choosing a renderer, configuring Vite plugins, or setting up path aliases. Triggers on tasks involving project configuration, renderer selection (hono-jsx vs react), Vite configuration, or Tailwind CSS setup.
6cloudwerk-handlers
Handler, middleware, and component patterns for Cloudwerk applications on Cloudflare Workers. Use when writing route handlers, middleware, page/layout components, or client-side interactive components. Triggers on tasks involving CloudwerkHandler, response helpers (json, redirect), Cloudflare bindings (D1, KV, R2), middleware composition, PageProps, LayoutProps, or client directives.
6cloudwerk-monorepo
Monorepo workflow for the Cloudwerk framework. Use when building, testing, or releasing Cloudwerk packages. Covers pnpm workspace commands, package structure, changeset requirements, and test workflows. Triggers on tasks involving building packages, running tests, creating changesets, or understanding the monorepo structure.
3