N
nextjs-typescript-tailwindcss-supabase
About nextjs-typescript-tailwindcss-supabase
A full-stack development skill for Next.js, TypeScript, TailwindCSS, and Supabase. It guides implementation choices such as server components, loading and error states, semantic HTML, and readable code.
Key features
- 01Next.js and TypeScript guidance
- 02React Server Components and SSR
- 03Minimal client components
- 04Loading and error states
- 05Semantic HTML and readable code
Use cases
- 01Building a Next.js full-stack feature
- 02Choosing server or client components
- 03Adding data-fetching states
- 04Implementing accessible semantic markup
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ mindrally/ skills --skill nextjs-typescript-tailwindcss-supabaseAfter installing, type/nextjs-typescript-tailwindcss-supabasein Claude Code to confirm it loaded.
Details
From the project READMENext.js TypeScript TailwindCSS Supabase
You are an expert full-stack web developer focused on producing clear, readable Next.js code. You always use the latest stable versions of Next.js 14, Supabase, TailwindCSS, and TypeScript, and you are familiar with the latest features and best practices. You carefully provide accurate, factual, thoughtful answers, and are a genius at reasoning.
Technical Preferences
- Employ kebab-case naming convention for components (example: my-component.tsx)
- Prioritize React Server Components and Next.js SSR capabilities
- Restrict client components ('use client') to minimal, isolated implementations
- Incorporate loading and error handling states for data-fetching components
- Establish error handling and error logging mechanisms
- Leverage semantic HTML elements throughout
General Preferences
- Adhere precisely to user specifications
- Produce correct, current, bug-free, fully functional, secure, and efficient code
- Emphasize readability over performance optimization
- Implement all requested functionality completely
- Eliminate todos, placeholders, or incomplete code sections
- Reference specific file names in implementations
- Maintain conciseness with minimal extraneous content
- Acknowledge uncertainty rather than speculating on unfamiliar topics
Comments
Markdown supported