react-vite
React 18+ with Vite patterns - use for Mini App frontend development, component structure, hooks, and TypeScript setup
What this skill does
# React + Vite Patterns for Telegram Mini App
## Project Architecture
```
mini-app/
├── public/
│ └── favicon.ico
├── src/
│ ├── components/ # Reusable UI components
│ │ ├── common/ # Generic UI (Button, Card, Modal, etc.)
│ │ ├── layout/ # Layout components (AppLayout, Navigation)
│ │ └── features/ # Feature-specific components
│ │ ├── chat/ # Chat selector, chat card
│ │ ├── settings/ # Settings toggles, forms
│ │ ├── blocklist/ # Blocklist CRUD components
│ │ └── locks/ # Lock toggles, categories
│ ├── hooks/ # Custom React hooks
│ │ ├── api/ # Data fetching hooks
│ │ ├── telegram/ # Telegram-specific hooks
│ │ └── ui/ # UI state hooks
│ ├── pages/ # Route pages (one per route)
│ ├── services/ # API client and external services
│ ├── stores/ # Zustand stores (global state)
│ ├── types/ # TypeScript type definitions
│ ├── utils/ # Helper functions
│ ├── constants/ # App constants, enums
│ ├── App.tsx # App root with providers
│ ├── main.tsx # Entry point
│ ├── mockEnv.ts # Mock Telegram environment
│ └── vite-env.d.ts # Vite type declarations
├── index.html
├── package.json
├── tsconfig.json
├── vite.config.ts
└── .env.example
```
## Layer Responsibilities
### 1. Pages (Route Level)
- One file per route
- Compose feature components
- Handle route params
- Connect to stores if needed
### 2. Components
- **common/**: Generic, reusable across features
- **layout/**: App shell, navigation
- **features/**: Feature-specific, can use hooks
### 3. Hooks
- **api/**: `useQuery`-like data fetching
- **telegram/**: `useTelegramAuth`, `useMainButton`
- **ui/**: `useModal`, `useToast`
### 4. Stores (Zustand)
- Global state only (selected chat, user)
- Feature state stays in components
### 5. Services
- API client (single instance)
- Type-safe request/response
---
## Component Patterns
### Base Component Template
```tsx
// src/components/features/chat/ChatCard.tsx
import { memo } from 'react';
import { Cell } from '@telegram-apps/ui';
import type { Chat } from '@/types';
import styles from './ChatCard.module.css';
interface ChatCardProps {
chat: Chat;
isActive?: boolean;
onSelect: (chatId: number) => void;
}
export const ChatCard = memo(function ChatCard({
chat,
isActive = false,
onSelect,
}: ChatCardProps) {
return (
<Cell
className={isActive ? styles.active : undefined}
onClick={() => onSelect(chat.id)}
subtitle={`${chat.memberCount} members`}
>
{chat.title}
</Cell>
);
});
```
### Page Component Pattern
```tsx
// src/pages/SettingsPage.tsx
import { useParams, Navigate } from 'react-router-dom';
import { Section, Spinner, Placeholder } from '@telegram-apps/ui';
import { useSettings } from '@/hooks/api/useSettings';
import { SettingsForm } from '@/components/features/settings/SettingsForm';
import { useSelectedChat } from '@/stores/chatStore';
export function SettingsPage() {
const { chatId } = useParams<{ chatId: string }>();
const numericChatId = Number(chatId);
const { data: settings, isLoading, error } = useSettings(numericChatId);
if (!chatId || isNaN(numericChatId)) {
return <Navigate to="/" replace />;
}
if (isLoading) {
return <Spinner size="large" />;
}
if (error || !settings) {
return (
<Placeholder
header="Error"
description={error?.message || 'Failed to load settings'}
/>
);
}
return (
<Section header="Chat Settings">
<SettingsForm settings={settings} chatId={numericChatId} />
</Section>
);
}
```
### Compound Component Pattern (For Complex UI)
```tsx
// src/components/features/locks/LockGrid.tsx
import { createContext, useContext, ReactNode } from 'react';
import type { LockType, LockCategory } from '@/types';
interface LockGridContextValue {
lockedTypes: Set<LockType>;
onToggle: (type: LockType) => void;
}
const LockGridContext = createContext<LockGridContextValue | null>(null);
function useLockGridContext() {
const ctx = useContext(LockGridContext);
if (!ctx) throw new Error('LockGrid.* must be used within LockGrid');
return ctx;
}
// Root component
interface LockGridProps {
lockedTypes: Set<LockType>;
onToggle: (type: LockType) => void;
children: ReactNode;
}
function LockGridRoot({ lockedTypes, onToggle, children }: LockGridProps) {
return (
<LockGridContext.Provider value={{ lockedTypes, onToggle }}>
<div className="lock-grid">{children}</div>
</LockGridContext.Provider>
);
}
// Category component
interface CategoryProps {
category: LockCategory;
types: LockType[];
}
function Category({ category, types }: CategoryProps) {
const { lockedTypes, onToggle } = useLockGridContext();
return (
<Section header={category}>
{types.map(type => (
<LockToggle
key={type}
type={type}
locked={lockedTypes.has(type)}
onToggle={() => onToggle(type)}
/>
))}
</Section>
);
}
// Export compound component
export const LockGrid = Object.assign(LockGridRoot, {
Category,
});
// Usage:
// <LockGrid lockedTypes={locked} onToggle={handleToggle}>
// <LockGrid.Category category="CONTENT" types={contentTypes} />
// <LockGrid.Category category="URL" types={urlTypes} />
// </LockGrid>
```
---
## Hooks Patterns
### Data Fetching Hook (SWR-like)
```tsx
// src/hooks/api/useSettings.ts
import { useState, useEffect, useCallback } from 'react';
import { api } from '@/services/api';
import type { ChatSettings } from '@/types';
interface UseSettingsResult {
data: ChatSettings | null;
isLoading: boolean;
error: Error | null;
mutate: (settings: Partial<ChatSettings>) => Promise<void>;
refetch: () => Promise<void>;
}
export function useSettings(chatId: number): UseSettingsResult {
const [data, setData] = useState<ChatSettings | null>(null);
const [isLoading, setIsLoading] = useState(true);
const [error, setError] = useState<Error | null>(null);
const fetchSettings = useCallback(async () => {
try {
setIsLoading(true);
setError(null);
const settings = await api.getSettings(chatId);
setData(settings);
} catch (err) {
setError(err as Error);
} finally {
setIsLoading(false);
}
}, [chatId]);
useEffect(() => {
fetchSettings();
}, [fetchSettings]);
const mutate = useCallback(async (updates: Partial<ChatSettings>) => {
// Optimistic update
setData(prev => prev ? { ...prev, ...updates } : null);
try {
const updated = await api.updateSettings(chatId, updates);
setData(updated);
} catch (err) {
// Rollback on error
await fetchSettings();
throw err;
}
}, [chatId, fetchSettings]);
return {
data,
isLoading,
error,
mutate,
refetch: fetchSettings,
};
}
```
### Telegram Hooks
```tsx
// src/hooks/telegram/useTelegramAuth.ts
import { useMemo } from 'react';
import { useInitData, useInitDataRaw } from '@telegram-apps/sdk-react';
export interface TelegramUser {
id: number;
firstName: string;
lastName?: string;
username?: string;
isPremium: boolean;
languageCode?: string;
}
export function useTelegramAuth() {
const initData = useInitData();
const initDataRaw = useInitDataRaw();
const user = useMemo<TelegramUser | null>(() => {
if (!initData?.user) return null;
return {
id: initData.user.id,
firstName: initData.user.firstName,
lastName: initData.user.lastName,
username: initData.user.username,
isPremium: initData.user.isPremium ?? false,
languageCode: initData.user.languageCode,
};
}, [initData]);
const getAuthHeader = useCallback(() => {
if (!initDataRaw) return {};
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.