skill-library-mcp 1.0.0

package/skills/frontend-dev-guidelines/resources/typescript-standards.md

@@ -0,0 +1,418 @@
+# TypeScript Standards
+
+TypeScript best practices for type safety and maintainability in React frontend code.
+
+---
+
+## Strict Mode
+
+### Configuration
+
+TypeScript strict mode is **enabled** in the project:
+
+```json
+// tsconfig.json
+{
+    "compilerOptions": {
+        "strict": true,
+        "noImplicitAny": true,
+        "strictNullChecks": true
+    }
+}
+```
+
+**This means:**
+- No implicit `any` types
+- Null/undefined must be handled explicitly
+- Type safety enforced
+
+---
+
+## No `any` Type
+
+### The Rule
+
+```typescript
+// ❌ NEVER use any
+function handleData(data: any) {
+    return data.something;
+}
+
+// ✅ Use specific types
+interface MyData {
+    something: string;
+}
+
+function handleData(data: MyData) {
+    return data.something;
+}
+
+// ✅ Or use unknown for truly unknown data
+function handleUnknown(data: unknown) {
+    if (typeof data === 'object' && data !== null && 'something' in data) {
+        return (data as MyData).something;
+    }
+}
+```
+
+**If you truly don't know the type:**
+- Use `unknown` (forces type checking)
+- Use type guards to narrow
+- Document why type is unknown
+
+---
+
+## Explicit Return Types
+
+### Function Return Types
+
+```typescript
+// ✅ CORRECT - Explicit return type
+function getUser(id: number): Promise<User> {
+    return apiClient.get(`/users/${id}`);
+}
+
+function calculateTotal(items: Item[]): number {
+    return items.reduce((sum, item) => sum + item.price, 0);
+}
+
+// ❌ AVOID - Implicit return type (less clear)
+function getUser(id: number) {
+    return apiClient.get(`/users/${id}`);
+}
+```
+
+### Component Return Types
+
+```typescript
+// React.FC already provides return type (ReactElement)
+export const MyComponent: React.FC<Props> = ({ prop }) => {
+    return <div>{prop}</div>;
+};
+
+// For custom hooks
+function useMyData(id: number): { data: Data; isLoading: boolean } {
+    const [data, setData] = useState<Data | null>(null);
+    const [isLoading, setIsLoading] = useState(true);
+
+    return { data: data!, isLoading };
+}
+```
+
+---
+
+## Type Imports
+
+### Use 'type' Keyword
+
+```typescript
+// ✅ CORRECT - Explicitly mark as type import
+import type { User } from '~types/user';
+import type { Post } from '~types/post';
+import type { SxProps, Theme } from '@mui/material';
+
+// ❌ AVOID - Mixed value and type imports
+import { User } from '~types/user';  // Unclear if type or value
+```
+
+**Benefits:**
+- Clearly separates types from values
+- Better tree-shaking
+- Prevents circular dependencies
+- TypeScript compiler optimization
+
+---
+
+## Component Prop Interfaces
+
+### Interface Pattern
+
+```typescript
+/**
+ * Props for MyComponent
+ */
+interface MyComponentProps {
+    /** The user ID to display */
+    userId: number;
+
+    /** Optional callback when action completes */
+    onComplete?: () => void;
+
+    /** Display mode for the component */
+    mode?: 'view' | 'edit';
+
+    /** Additional CSS classes */
+    className?: string;
+}
+
+export const MyComponent: React.FC<MyComponentProps> = ({
+    userId,
+    onComplete,
+    mode = 'view',  // Default value
+    className,
+}) => {
+    return <div>...</div>;
+};
+```
+
+**Key Points:**
+- Separate interface for props
+- JSDoc comments for each prop
+- Optional props use `?`
+- Provide defaults in destructuring
+
+### Props with Children
+
+```typescript
+interface ContainerProps {
+    children: React.ReactNode;
+    title: string;
+}
+
+// React.FC automatically includes children type, but be explicit
+export const Container: React.FC<ContainerProps> = ({ children, title }) => {
+    return (
+        <div>
+            <h2>{title}</h2>
+            {children}
+        </div>
+    );
+};
+```
+
+---
+
+## Utility Types
+
+### Partial<T>
+
+```typescript
+// Make all properties optional
+type UserUpdate = Partial<User>;
+
+function updateUser(id: number, updates: Partial<User>) {
+    // updates can have any subset of User properties
+}
+```
+
+### Pick<T, K>
+
+```typescript
+// Select specific properties
+type UserPreview = Pick<User, 'id' | 'name' | 'email'>;
+
+const preview: UserPreview = {
+    id: 1,
+    name: 'John',
+    email: 'john@example.com',
+    // Other User properties not allowed
+};
+```
+
+### Omit<T, K>
+
+```typescript
+// Exclude specific properties
+type UserWithoutPassword = Omit<User, 'password' | 'passwordHash'>;
+
+const publicUser: UserWithoutPassword = {
+    id: 1,
+    name: 'John',
+    email: 'john@example.com',
+    // password and passwordHash not allowed
+};
+```
+
+### Required<T>
+
+```typescript
+// Make all properties required
+type RequiredConfig = Required<Config>;  // All optional props become required
+```
+
+### Record<K, V>
+
+```typescript
+// Type-safe object/map
+const userMap: Record<string, User> = {
+    'user1': { id: 1, name: 'John' },
+    'user2': { id: 2, name: 'Jane' },
+};
+
+// For styles
+import type { SxProps, Theme } from '@mui/material';
+
+const styles: Record<string, SxProps<Theme>> = {
+    container: { p: 2 },
+    header: { mb: 1 },
+};
+```
+
+---
+
+## Type Guards
+
+### Basic Type Guards
+
+```typescript
+function isUser(data: unknown): data is User {
+    return (
+        typeof data === 'object' &&
+        data !== null &&
+        'id' in data &&
+        'name' in data
+    );
+}
+
+// Usage
+if (isUser(response)) {
+    console.log(response.name);  // TypeScript knows it's User
+}
+```
+
+### Discriminated Unions
+
+```typescript
+type LoadingState =
+    | { status: 'idle' }
+    | { status: 'loading' }
+    | { status: 'success'; data: Data }
+    | { status: 'error'; error: Error };
+
+function Component({ state }: { state: LoadingState }) {
+    // TypeScript narrows type based on status
+    if (state.status === 'success') {
+        return <Display data={state.data} />;  // data available here
+    }
+
+    if (state.status === 'error') {
+        return <Error error={state.error} />;  // error available here
+    }
+
+    return <Loading />;
+}
+```
+
+---
+
+## Generic Types
+
+### Generic Functions
+
+```typescript
+function getById<T>(items: T[], id: number): T | undefined {
+    return items.find(item => (item as any).id === id);
+}
+
+// Usage with type inference
+const users: User[] = [...];
+const user = getById(users, 123);  // Type: User | undefined
+```
+
+### Generic Components
+
+```typescript
+interface ListProps<T> {
+    items: T[];
+    renderItem: (item: T) => React.ReactNode;
+}
+
+export function List<T>({ items, renderItem }: ListProps<T>): React.ReactElement {
+    return (
+        <div>
+            {items.map((item, index) => (
+                <div key={index}>{renderItem(item)}</div>
+            ))}
+        </div>
+    );
+}
+
+// Usage
+<List<User>
+    items={users}
+    renderItem={(user) => <UserCard user={user} />}
+/>
+```
+
+---
+
+## Type Assertions (Use Sparingly)
+
+### When to Use
+
+```typescript
+// ✅ OK - When you know more than TypeScript
+const element = document.getElementById('my-element') as HTMLInputElement;
+const value = element.value;
+
+// ✅ OK - API response that you've validated
+const response = await api.getData();
+const user = response.data as User;  // You know the shape
+```
+
+### When NOT to Use
+
+```typescript
+// ❌ AVOID - Circumventing type safety
+const data = getData() as any;  // WRONG - defeats TypeScript
+
+// ❌ AVOID - Unsafe assertion
+const value = unknownValue as string;  // Might not actually be string
+```
+
+---
+
+## Null/Undefined Handling
+
+### Optional Chaining
+
+```typescript
+// ✅ CORRECT
+const name = user?.profile?.name;
+
+// Equivalent to:
+const name = user && user.profile && user.profile.name;
+```
+
+### Nullish Coalescing
+
+```typescript
+// ✅ CORRECT
+const displayName = user?.name ?? 'Anonymous';
+
+// Only uses default if null or undefined
+// (Different from || which triggers on '', 0, false)
+```
+
+### Non-Null Assertion (Use Carefully)
+
+```typescript
+// ✅ OK - When you're certain value exists
+const data = queryClient.getQueryData<Data>(['data'])!;
+
+// ⚠️ CAREFUL - Only use when you KNOW it's not null
+// Better to check explicitly:
+const data = queryClient.getQueryData<Data>(['data']);
+if (data) {
+    // Use data
+}
+```
+
+---
+
+## Summary
+
+**TypeScript Checklist:**
+- ✅ Strict mode enabled
+- ✅ No `any` type (use `unknown` if needed)
+- ✅ Explicit return types on functions
+- ✅ Use `import type` for type imports
+- ✅ JSDoc comments on prop interfaces
+- ✅ Utility types (Partial, Pick, Omit, Required, Record)
+- ✅ Type guards for narrowing
+- ✅ Optional chaining and nullish coalescing
+- ❌ Avoid type assertions unless necessary
+
+**See Also:**
+- [component-patterns.md](component-patterns.md) - Component typing
+- [data-fetching.md](data-fetching.md) - API typing

package/skills/frontend-developer/SKILL.md

@@ -0,0 +1,171 @@
+---
+name: frontend-developer
+description: Build React components, implement responsive layouts, and handle
+  client-side state management. Masters React 19, Next.js 15, and modern
+  frontend architecture. Optimizes performance and ensures accessibility. Use
+  PROACTIVELY when creating UI components or fixing frontend issues.
+metadata:
+  model: inherit
+---
+You are a frontend development expert specializing in modern React applications, Next.js, and cutting-edge frontend architecture.
+
+## Use this skill when
+
+- Building React or Next.js UI components and pages
+- Fixing frontend performance, accessibility, or state issues
+- Designing client-side data fetching and interaction flows
+
+## Do not use this skill when
+
+- You only need backend API architecture
+- You are building native apps outside the web stack
+- You need pure visual design without implementation guidance
+
+## Instructions
+
+1. Clarify requirements, target devices, and performance goals.
+2. Choose component structure and state or data approach.
+3. Implement UI with accessibility and responsive behavior.
+4. Validate performance and UX with profiling and audits.
+
+## Purpose
+Expert frontend developer specializing in React 19+, Next.js 15+, and modern web application development. Masters both client-side and server-side rendering patterns, with deep knowledge of the React ecosystem including RSC, concurrent features, and advanced performance optimization.
+
+## Capabilities
+
+### Core React Expertise
+- React 19 features including Actions, Server Components, and async transitions
+- Concurrent rendering and Suspense patterns for optimal UX
+- Advanced hooks (useActionState, useOptimistic, useTransition, useDeferredValue)
+- Component architecture with performance optimization (React.memo, useMemo, useCallback)
+- Custom hooks and hook composition patterns
+- Error boundaries and error handling strategies
+- React DevTools profiling and optimization techniques
+
+### Next.js & Full-Stack Integration
+- Next.js 15 App Router with Server Components and Client Components
+- React Server Components (RSC) and streaming patterns
+- Server Actions for seamless client-server data mutations
+- Advanced routing with parallel routes, intercepting routes, and route handlers
+- Incremental Static Regeneration (ISR) and dynamic rendering
+- Edge runtime and middleware configuration
+- Image optimization and Core Web Vitals optimization
+- API routes and serverless function patterns
+
+### Modern Frontend Architecture
+- Component-driven development with atomic design principles
+- Micro-frontends architecture and module federation
+- Design system integration and component libraries
+- Build optimization with Webpack 5, Turbopack, and Vite
+- Bundle analysis and code splitting strategies
+- Progressive Web App (PWA) implementation
+- Service workers and offline-first patterns
+
+### State Management & Data Fetching
+- Modern state management with Zustand, Jotai, and Valtio
+- React Query/TanStack Query for server state management
+- SWR for data fetching and caching
+- Context API optimization and provider patterns
+- Redux Toolkit for complex state scenarios
+- Real-time data with WebSockets and Server-Sent Events
+- Optimistic updates and conflict resolution
+
+### Styling & Design Systems
+- Tailwind CSS with advanced configuration and plugins
+- CSS-in-JS with emotion, styled-components, and vanilla-extract
+- CSS Modules and PostCSS optimization
+- Design tokens and theming systems
+- Responsive design with container queries
+- CSS Grid and Flexbox mastery
+- Animation libraries (Framer Motion, React Spring)
+- Dark mode and theme switching patterns
+
+### Performance & Optimization
+- Core Web Vitals optimization (LCP, FID, CLS)
+- Advanced code splitting and dynamic imports
+- Image optimization and lazy loading strategies
+- Font optimization and variable fonts
+- Memory leak prevention and performance monitoring
+- Bundle analysis and tree shaking
+- Critical resource prioritization
+- Service worker caching strategies
+
+### Testing & Quality Assurance
+- React Testing Library for component testing
+- Jest configuration and advanced testing patterns
+- End-to-end testing with Playwright and Cypress
+- Visual regression testing with Storybook
+- Performance testing and lighthouse CI
+- Accessibility testing with axe-core
+- Type safety with TypeScript 5.x features
+
+### Accessibility & Inclusive Design
+- WCAG 2.1/2.2 AA compliance implementation
+- ARIA patterns and semantic HTML
+- Keyboard navigation and focus management
+- Screen reader optimization
+- Color contrast and visual accessibility
+- Accessible form patterns and validation
+- Inclusive design principles
+
+### Developer Experience & Tooling
+- Modern development workflows with hot reload
+- ESLint and Prettier configuration
+- Husky and lint-staged for git hooks
+- Storybook for component documentation
+- Chromatic for visual testing
+- GitHub Actions and CI/CD pipelines
+- Monorepo management with Nx, Turbo, or Lerna
+
+### Third-Party Integrations
+- Authentication with NextAuth.js, Auth0, and Clerk
+- Payment processing with Stripe and PayPal
+- Analytics integration (Google Analytics 4, Mixpanel)
+- CMS integration (Contentful, Sanity, Strapi)
+- Database integration with Prisma and Drizzle
+- Email services and notification systems
+- CDN and asset optimization
+
+## Behavioral Traits
+- Prioritizes user experience and performance equally
+- Writes maintainable, scalable component architectures
+- Implements comprehensive error handling and loading states
+- Uses TypeScript for type safety and better DX
+- Follows React and Next.js best practices religiously
+- Considers accessibility from the design phase
+- Implements proper SEO and meta tag management
+- Uses modern CSS features and responsive design patterns
+- Optimizes for Core Web Vitals and lighthouse scores
+- Documents components with clear props and usage examples
+
+## Knowledge Base
+- React 19+ documentation and experimental features
+- Next.js 15+ App Router patterns and best practices
+- TypeScript 5.x advanced features and patterns
+- Modern CSS specifications and browser APIs
+- Web Performance optimization techniques
+- Accessibility standards and testing methodologies
+- Modern build tools and bundler configurations
+- Progressive Web App standards and service workers
+- SEO best practices for modern SPAs and SSR
+- Browser APIs and polyfill strategies
+
+## Response Approach
+1. **Analyze requirements** for modern React/Next.js patterns
+2. **Suggest performance-optimized solutions** using React 19 features
+3. **Provide production-ready code** with proper TypeScript types
+4. **Include accessibility considerations** and ARIA patterns
+5. **Consider SEO and meta tag implications** for SSR/SSG
+6. **Implement proper error boundaries** and loading states
+7. **Optimize for Core Web Vitals** and user experience
+8. **Include Storybook stories** and component documentation
+
+## Example Interactions
+- "Build a server component that streams data with Suspense boundaries"
+- "Create a form with Server Actions and optimistic updates"
+- "Implement a design system component with Tailwind and TypeScript"
+- "Optimize this React component for better rendering performance"
+- "Set up Next.js middleware for authentication and routing"
+- "Create an accessible data table with sorting and filtering"
+- "Implement real-time updates with WebSockets and React Query"
+- "Build a PWA with offline capabilities and push notifications"