Discord
Join the RedwoodJS Discord to chat with other developers and the core team.
RedwoodSDK is designed to be AI-friendly. By following “Zero Magic” principles and staying close to web standards, it ensures that what you see in your source code is exactly what runs in the browser and on the server. This makes RedwoodSDK code highly predictable for AI tools.
RedwoodSDK provides llms.txt and llms-full.txt files that contain the full documentation content in a format optimized for AI consumption. These files are located at the root of the documentation site.
Some AI tools, like Cursor or Windsurf, can auto-discover these files if you provide https://docs.rwsdk.com as a documentation source.
Because RedwoodSDK avoids hidden behavior and complex code generation, AI tools are less likely to hallucinate internal framework logic. When asking an AI to write code, emphasize that it should use standard Web APIs (Request, Response, Fetch) and idiomatic React Server Components.
create-rwsdk for ScaffoldingRather than asking an AI to set up a project from scratch, always start with the official starter:
npx create-rwsdk my-project-nameAI tools are generally well-versed in React, but they may need reminders about React Server Components (RSC) and Server Functions. If an AI is struggling with data fetching, remind it that it can use async/await directly in components or define "use server"; functions for server-side logic.
RedwoodSDK runs on the Cloudflare Workers runtime (workerd). When asking for infrastructure help (e.g., using D1, R2, or Durable Objects), remind the AI that these are available via standard Cloudflare bindings.
If you’re stuck or want to share how you’re using AI with RedwoodSDK, join our community:
Discord
Join the RedwoodJS Discord to chat with other developers and the core team.