mindrally/skills

nextjs-typescript-tailwindcss-supabase

Full-stack Next.js 14 development with TypeScript, TailwindCSS, and Supabase for building production-ready web applications.

All-time #8556 Hot #2705 First seen Jan 25, 2026
8-week activity · all time api

Installation

$ npx skills add mindrally/skills --skill nextjs-typescript-tailwindcss-supabase

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from mindrally/skills · top by installs.

npx skills add mindrally/skills

Browse all from mindrally/skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Also listed on

Alternate registries and mirrors of this skill.

Repository health

Stars 258
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,509 B
  • docs SUMMARY.md 1,483 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1,234 installs

SKILL.md

Next.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