Detect environment variables and secrets that leak from the server into the client bundle via loader return values, hydration state, or accidental imports of server-only modules from client code paths. Use when asked to "audit secrets", "find leaked env vars", "is my API key exposed", "check client bundle for secrets", or "scan for credential leaks".
Audit pracht route loaders for serializability, leaked secrets, unsafe loader caching, browser-only API misuse, and missing AbortSignal plumbing. Use when asked to "audit loaders", "check loader data", "find serialization bugs", "are my loaders safe", or "loader security review".
Pracht deployment guide. Walks through adapter configuration, building, and deploying to Node.js, Cloudflare Workers, or Vercel. Handles wrangler config, Docker and production checklist. Use when asked to "deploy", "set up deployment", "configure adapter", "deploy to cloudflare", "deploy to vercel", or "production build".
Adapter-aware pre-deployment checklist for pracht apps targeting Node, Cloudflare Workers, or Vercel. Catches the issues that only surface in the production runtime: missing env vars, Node-only APIs in Cloudflare bundles, ISG manifest absence, oversized edge bundles, missing wrangler/vercel config. Use when asked to "pre-deploy check", "ready to ship?", "deployment checklist", "is my build production-safe", or before running `wrangler deploy` / `vercel deploy`.
Recommend the right pracht render mode (ssg, isg, ssr, spa) for each route based on what its loader actually does. Most apps pick a mode once and never revisit; this skill surfaces routes that are mis-tuned. Use when asked to "tune render modes", "make my site faster", "should this route be SSG", "audit render modes", or "review SSG/ISG/SSR choices".
Migrate a Next.js application to Pracht. Converts App Router pages, layouts, middleware, API routes, data fetching, and metadata to pracht equivalents. Handles React→Preact, className→class, server components→loaders, and manifest wiring. Use when asked to "migrate from next", "convert next.js app", "port from next to pracht", "nextjs migration", or "switch from next".
Add or maintain pracht typed routes, typed links, route-object navigation, and generated href helpers. Use when asked to "add typed routes", "fix typed links", "replace hard-coded hrefs", "run typegen", or make navigation route-id based instead of string based.
Pracht framework-aware debugging. Systematically investigates route matching, loader/API route errors, rendering issues, middleware, API routes, HMR, and build problems. Uses pracht's architecture knowledge to find root causes fast. Use when asked to "debug this", "fix this bug", "why is this broken", "blank page", "hydration mismatch", or "404 on my route". Proactively suggest when the user reports errors or unexpected behavior in a pracht application.