Skip to content

avibebuilder/claude-prime / .claude/starter-skills/frontend-development

frontend-development

Verified

Use this skill for ANY work involving React, Next.js, TypeScript, or Tailwind in the browser layer. This includes building components and pages, but equally covers debugging and fixing frontend issues: CSS/Tailwind classes not applying, form validation behavior, hydration mismatches between server and client renders, styling bugs, layout shifts, and rendering problems. Also use for refactoring components (e.g., splitting Server vs Client Components), data fetching patterns, state management, bundle optimization, and frontend tooling. If the problem involves what users see or interact with in a web browser — whether building, fixing, or refactoring — use this skill. Not for backend APIs, databases, infrastructure, or DevOps.

references/typescript.md

View on GitHub
# TypeScript Conventions

## Type vs Interface

- **ALWAYS** `interface` for object shapes and props
- **ONLY** use `type` for:
  - Unions: `type Status = 'loading' | 'success' | 'error'`
  - Primitives: `type UserId = string`
  - Zod inference: `type FormData = z.infer<typeof schema>`
  - Database inference: `type User = Tables<'users'>`
  - Complex mapped types

```typescript
// ✅ Interface for objects
interface UserProfileProps {
  user: User;
  onUpdate: (data: Partial<User>) => void;
}

// ✅ Type for unions/inference
type Status = 'loading' | 'success' | 'error';
type CreateUserInput = z.infer<typeof createUserSchema>;
```

## Constants & Enums

- **NEVER** use `enum` - use `as const` instead
- **ALWAYS** SCREAMING_SNAKE_CASE for constants

```typescript
// ✅ as const pattern
const USER_ROLES = {
  ADMIN: 'admin',
  USER: 'user',
  SYSTEM_ADMIN: 'system_admin',
} as const;

type UserRole = typeof USER_ROLES[keyof typeof USER_ROLES];
```

## Naming Conventions

| Element | Convention | Example |
|---------|------------|---------|
| Props interface | `{Component}Props` | `ButtonProps` |
| Interfaces/Types | PascalCase | `UserProfile` |
| Constants | SCREAMING_SNAKE_CASE | `API_BASE_URL` |
| Variables/Functions | camelCase | `fetchUser` |
| Event handlers | `handle*` | `handleSubmit` |
| Callback props | `on*` | `onSubmit` |

## Code Style

- **ALWAYS** curly braces for block statements (if, for, while)
- Arrow functions CAN skip braces for simple expressions

```typescript
// ✅ Always braces for blocks
if (condition) { doSomething(); }
for (const item of items) { process(item); }

// ✅ Arrow functions - braces optional for simple
const getName = (user: User) => user.name;
items.filter(item => item.active);
```

## Imports

- **ALWAYS** use `type` keyword for type-only imports

```typescript
import type { User } from './types';
import { someFunction, type SomeType } from './module';
```
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 321kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 197kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall