studio-best-practices
React and TypeScript best practices for Supabase Studio. Use when writing
Explore
139,097 skills indexed with the new KISS metadata standard.
React and TypeScript best practices for Supabase Studio. Use when writing
Error display and troubleshooting pattern for Supabase Studio. Use when
Expert integration of Supabase Auth with Next.js App Router
Testing strategy for Supabase Studio. Use when writing tests, deciding what
Use when planning or writing server-side code that uses @supabase/server — Edge Functions, Hono apps, webhook handlers, or any backend that creates Supabase clients or validates inbound auth. Trigger...
Vitest fast unit testing framework powered by Vite with Jest-compatible API. Use when writing tests, mocking, configuring coverage, or working with test filtering and fixtures.
Guide for building modern, accessible, and composable UI components. Use when building new components, implementing accessibility, creating composable APIs, setting up design tokens, publishing to npm...
Deploy, manage, inspect, and troubleshoot Vercel projects from the command line. Use for Vercel deployments, projects and teams, environment variables, domains and DNS, logs, metrics, Speed Insights,...
Build AI chat interfaces using ai-elements components — conversations, messages, tool displays, prompt inputs, and more. Use when the user wants to build a chatbot, AI assistant UI, or any AI-powered...
|
|
|
|
|
|
|
|
|
Creates, structures, and reviews technical documentation following the Diátaxis framework (tutorials, how-to guides, reference, and explanation pages). Use when a user needs to write or reorganize doc...
Generate comprehensive, developer-friendly API documentation from code, including endpoints, parameters, examples, and best practices
Technical documentation expert for creating clear, comprehensive documentation. Use when user asks to write docs, create README, or document code.
Documentation templates and structure guidelines. README, API docs, code comments, and AI-friendly documentation.
Documentation analysis — assess coverage, detect code-to-doc drift with plan reconcile, visualize dependencies with doc graph. Answers "what needs docs?" and "are docs still accurate?