frontend-development
Skill4 starsChanged 6 months agoMITView on GitHub
Next.js frontend app development patterns with App Router, Tailwind CSS v4, Zustand, and TanStack Query. Use when creating pages, components, or API routes in the frontend app.
13 other projects use a version of this.
Adopted by
Most recently taken up by
- lubusIN/frappe-skillstheir own version, first seen Nov 4, 2026
- its-ash/skillstheir own version, first seen Nov 1, 2026
- liushikuan63/Qoder-Optimizationtheir own version, first seen Nov 1, 2026
- KMaruthi2002/universal-llm-skillstheir own version, first seen Oct 25, 2026
- taichuy/1flowbasetheir own version, first seen Oct 23, 2026
- typv/nest-turbo-startertheir own version, first seen Oct 8, 2026
Other versions13 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 13
- All-Hands-AI/OpenHands★ 93ksame name
- OpenHands/OpenHands★ 93ksame name
- taichuy/1flowbase★ 292same name
- typv/nest-turbo-starter★ 224same name
- ambient-code/platform★ 131same name
- avibebuilder/claude-prime★ 119same name
- lubusIN/frappe-skills★ 68same name
- aws-solutions/konductor★ 11same name
- liushikuan63/Qoder-Optimization★ 2same name
- dhslegen/digital-delivery-team★ 1same name
3 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- apple-appstore-setupSkill
- eas-mobile-deploymentSkill
- edge-functionsSkill
- google-play-setupSkill
- langfuse-tracingSkill
- mobile-developmentSkill
- posthog-analyticsSkill
- push-notificationsSkill
- revenuecatSkill
- sentry-integrationSkill
- social-auth-setupSkill
- stripe-paymentsSkill
- supabase-email-templatesSkill
- template-releaseSkill
- template-upgradeSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Use @/ path alias for src/: @/lib/supabase, @/components/Button.
- Very specific: line 34
Add new design tokens in @theme, not in config files.
- Very specific: line 80
Use react-hook-form + @hookform/resolvers + Zod for validation:
“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Frontend Development
Stack
Next.js 16 (App Router, Turbopack), React 19, Tailwind CSS v4, Zustand 5, TanStack Query v5, react-hook-form + Zod 4, TypeScript strict mode.
Imports
Use @/ path alias for src/: @/lib/supabase, @/components/Button.
Client vs Server
Mark interactive/stateful components with 'use client'. Default is server component.
Styling
Tailwind CSS v4 with @theme tokens in src/app/globals.css:
@import 'tailwindcss';
@theme {
--color-cream: #FCFAF7;
--color-slate-deep: #1B2030;
--color-emerald-glow: #10B981;
}Add new design tokens in @theme, not in config files.
Supabase Clients
Three clients for different contexts:
| Import | Use for | Context |
@/lib/supabase | General public queries | Client, graceful fallback if env missing |
@/lib/supabase-browser | Auth flows (login, signup) | Client ('use client') |
@/lib/supabase-admin | Admin operations | Server-only, createAdminClient() |
// Client component — auth flow
import { supabaseBrowser } from '@/lib/supabase-browser';
// Server component / action — admin
import { createAdminClient } from '@/lib/supabase-admin';
const supabase = createAdminClient();State Management
Zustand with persist middleware. Use partialize to persist only selected fields:
import { create } from 'zustand';
import { persist } from 'zustand/middleware';
export const useMyStore = create(
persist(
(set) => ({
value: '',
setValue: (v: string) => set({ value: v }),
}),
{ name: 'my-store', partialize: (s) => ({ value: s.value }) }
)
);Providers
Composed in src/app/layout.tsx. Order: QueryProvider → PostHogProvider → children. Add new providers inside QueryProvider.
Forms
Use react-hook-form + @hookform/resolvers + Zod for validation:
import { useForm } from 'react-hook-form';
import { zodResolver } from '@hookform/resolvers/zod';
import { z } from 'zod';
const schema = z.object({ email: z.string().email() });
const { register, handleSubmit } = useForm({
resolver: zodResolver(schema),
});Environment Variables
Public: NEXT_PUBLIC_*. Server-only: no prefix (e.g. SUPABASE_SERVICE_ROLE_KEY).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

