f6bcc86881
New skills: - next-best-practices: Next.js 15+ RSC, async patterns, self-hosting (vercel-labs) - better-auth-best-practices: Official Better-Auth with Drizzle adapter (better-auth) - verification-before-completion: Evidence-based completion claims (obra/superpowers) - shadcn-ui: Component patterns with Tailwind v4 adaptation note (developer-kit) - writing-skills: TDD methodology for skill authoring (obra/superpowers) README reorganized by category with Mosaic Stack alignment section. Total: 9 skills (4 existing + 5 new). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
985 B
985 B
Runtime Selection
Use Node.js Runtime by Default
Use the default Node.js runtime for new routes and pages. Only use Edge runtime if the project already uses it or there's a specific requirement.
// Good: Default - no runtime config needed (uses Node.js)
export default function Page() { ... }
// Caution: Only if already used in project or specifically required
export const runtime = 'edge'
When to Use Each
Node.js Runtime (Default)
- Full Node.js API support
- File system access (
fs) - Full
cryptosupport - Database connections
- Most npm packages work
Edge Runtime
- Only for specific edge-location latency requirements
- Limited API (no
fs, limitedcrypto) - Smaller cold start
- Geographic distribution needs
Detection
Before adding runtime = 'edge', check:
- Does the project already use Edge runtime?
- Is there a specific latency requirement?
- Are all dependencies Edge-compatible?
If unsure, use Node.js runtime.