rwsdk

Audit a deployed RedwoodSDK application for errors, performance issues, and health

Safely update or add shadcn/ui components in a RedwoodSDK project with backup/restore

Look up RedwoodSDK documentation for a specific topic

Diagnose and fix frontend layout/styling issues in a RedwoodSDK app using the 4-phase visual workflow

Scaffold a new RedwoodSDK project or add a new feature (route, page, component) to an existing one

Sync the rwsdk-docs skill references with the latest official RedwoodSDK documentation

This skill should be used when the user asks to "audit my deployed app", "check production errors", "is my worker healthy", "check logs", "investigate production issues", "analyze worker performance", or any request to inspect a deployed RedwoodSDK/Cloudflare Worker application. Trigger on mentions of production errors, Cloudflare Worker logs, observability, metrics, latency issues, error rates, deployment health checks, or "pnpm release" follow-up verification. Also trigger when the user asks "is everything working" or wants to verify a recent deployment succeeded. Uses cloudflare-observability MCP for real-time worker telemetry and rwsdk-docs skill for best practice verification. Provides a structured 6-phase audit workflow with automated report generation.

This skill should be used when the user is building, debugging, or asking questions about a RedwoodSDK (rwsdk) application on Cloudflare Workers. Trigger on any mention of RedwoodSDK, rwsdk, defineApp, route(), render(), React Server Components on Cloudflare, server functions, serverQuery, serverAction, "use server", Durable Objects, passkey authentication, Cloudflare Workers email/queues/R2/cron, wrangler.jsonc, D1 database, requestInfo, getRequestInfo, client navigation, prefetch, or RSC hydration issues. Also trigger when the user asks about routing patterns, middleware, layouts, error handling, environment variables, deployment, or any Cloudflare Workers + React full-stack development — even if they don't explicitly say "RedwoodSDK". This is the primary reference for all RedwoodSDK documentation and should be consulted before writing or modifying any rwsdk project code.

This skill should be used when the user has frontend layout, styling, or visual issues in a RedwoodSDK application. Trigger when the user mentions "fix layout", "mobile looks broken", "responsive design", "Tailwind not working", "CSS issues", "styling problems", "shadcn component looks wrong", "UI is off", or any visual/rendering complaint in an rwsdk project. Also trigger when the user asks about Tailwind v4 configuration in RSC, server component styling, dark mode setup, or wants to debug why components render differently on mobile vs desktop. Provides a mandatory 4-phase workflow (context gathering, visual testing, design solution, verification) that ensures thorough visual analysis before making any changes. Always use this skill instead of guessing at CSS fixes — it requires actually seeing the running app.

This skill should be used when the user wants to "add a shadcn component", "update shadcn components", "install shadcn", "fix shadcn", "setup shadcn in rwsdk", or manage shadcn/ui components in a RedwoodSDK project. Trigger on any mention of shadcn/ui combined with RedwoodSDK, including adding new components, updating existing components, troubleshooting component rendering issues, configuring components.json, ensuring RSC compliance for shadcn components, preserving custom modifications during updates, or setting up the shadcn MCP server. Also trigger when the user asks about "use client" directives for interactive shadcn components, Radix UI issues, or component backup/restore workflows. This skill detects custom components automatically and provides safe update workflows with backup/restore.

This skill should be used when the user asks to "update the docs", "refresh rwsdk docs", "sync RedwoodSDK documentation", "pull latest docs", or when the rwsdk-docs references appear stale or outdated. Trigger when the user mentions that documentation seems wrong, out of date, or when they want to ensure they have the latest RedwoodSDK API changes. Fetches the latest official documentation from the redwoodjs/sdk GitHub repository and rebuilds the rwsdk-docs skill reference index. Run this periodically or after major RedwoodSDK releases to keep the documentation current.