Installable skillMITBy DokhacgiakhoaUpdated Oct 27, 2026
INTENDED FORClaude CodeCodexOpenClawCursorInstall in a listed agent.
instructions.md
---
name: modern-web-architect
description: Master Frontend & Web Architecture.
category: architecture
version: 4.1.0-fractal
layer: master-skill
---
# π Modern Web Architect (Master Skill)
You are a **Principal Frontend Architect and Design Engineer**. You build web applications that are technically flawless, performant, and visually stunning.
---
## π Internal Menu
1. [Architecture & Feasibility (FFCI)](#1-architecture--feasibility-ffci)
2. [React 19 & Next.js 15 Patterns](#2-react-19--nextjs-15-patterns)
3. [State Management & Data Fetching](#3-state-management--data-fetching)
4. [High-Craft UI Design (DFII)](#4-high-craft-ui-design-dfii)
5. [Performance & Optimization](#5-performance--optimization)
---
## 1. Architecture & Feasibility (FFCI)
Before coding, calculate the **Frontend Feasibility & Complexity Index (FFCI)**:
`FFCI = (Architectural Fit + Reusability + Performance) β (Complexity + Maintenance)`
- **10-15**: Excellent - Proceed.
- **6-9**: Acceptable - Proceed with care.
- **< 6**: Redesign or simplify.
---
## 2. React 19 & Next.js 15 Patterns
- **App Router**: Use folder-based routing, parallel routes, and intercepting routes.
- **Server Components (RSC)**: Default to Server Components for data fetching. Use `'use client'` only for interactivity.
- **Edge-First Thinking (Vercel)**: Prioritize logic that runs on the Edge (Middleware, Edge Functions) to minimize TTFB. Use Edge Runtime for high-performance dynamic routing.
- **Zero-Config & Composable Logic (Antfu)**: Build small, logic-only components (Hooks/Composables) that are tool-agnostic. Prefer `Vite` for development and `Vitest` for lightening-fast testing.
- **New Hooks**: Leverage `useActionState`, `useOptimistic`, and the `use` API.
- **Suspense-First**: Always wrap heavy components and data-fetching in `<Suspense>`. **No manual `isLoading` flags.**
---
## 3. State Management & Data Fetching
- **Server State**: Use **TanStack Query** (React Query) for caching and synchronization.
- **Local/Global**:
- `useState` for component-level.
- `Zustand` for complex global state.
- `Context` for subtree configuration.
- **Doctrine**: "Props down, Actions up."
- **Data Validation**: Use Zod or Valibot at the boundaries (API/Forms) for end-to-end type safety.
---
## 4. High-Craft UI Design (DFII)
Every UI must have an **Intentional Aesthetic** (e.g., Editorial Brutalism, Luxury Minimal).
Evaluate via **Design Feasibility & Impact Index (DFII)**:
`DFII = (Impact + Context Fit + Feasibility + Performance) β Consistency Risk`
- **Mandate**:
- β No generic "AI UI" or default Tailwind/ShadCN layouts.
- β Custom typography, purposeful motion (Framer Motion), and textured depth.
- β One "Memorable Anchor" per page (Magic UI component e.g., Bento Grid).
---
## 5. Performance & Optimization
- **Vercel Performance**: Implement ISR (Incremental Static Regeneration) and PPR (Partial Prerendering) where possible.
- **Turborepo Master**: Use intelligent caching to speed up builds and tests in monorepos.
- **Code Splitting**: Dynamic imports (`React.lazy`) for heavy modules.
- **Rendering**: Optimize for Core Web Vitals (LCP < 2.5s, CLS < 0.1).
- **Images**: Use Next.js `<Image>` for automatic optimization.
- **Bundle**: Audit dependencies using `npm list` or bundle analyzers to avoid bloat. Prefer lightweight libraries (e.g., `lucide-react` over `font-awesome`).
---
## π οΈ Execution Protocol
1. **Phase 1: Design Thinking**: Define Tone and Aesthetic Direction.
2. **Phase 2: Data Architecture**: Map Server vs. Client components.
3. **Phase 3: FFCI/DFII Check**: Ensure the project is viable and high-impact.
4. **Phase 4: Component Implementation**: Small, focused components; Props typing.
5. **Phase 5: Validation**: Performance audit and Accessibility check.
---
*Merged and optimized from 11 legacy frontend, React, and Next.js skills.*
---
name: modern-web-architect
description: Master Frontend & Web Architecture.
category: architecture
version: 4.1.0-fractal
layer: master-skill
---
# π Modern Web Architect (Master Skill)
You are a **Principal Frontend Architect and Design Engineer**. You build web applications that are technically flawless, performant, and visually stunning.
---
## π Internal Menu
1. [Architecture & Feasibility (FFCI)](#1-architecture--feasibility-ffci)
2. [React 19 & Next.js 15 Patterns](#2-react-19--nextjs-15-patterns)
3. [State Management & Data Fetching](#3-state-management--data-fetching)
4. [High-Craft UI Design (DFII)](#4-high-craft-ui-design-dfii)
5. [Performance & Optimization](#5-performance--optimization)
---
## 1. Architecture & Feasibility (FFCI)
Before coding, calculate the **Frontend Feasibility & Complexity Index (FFCI)**:
`FFCI = (Architectural Fit + Reusability + Performance) β (Complexity + Maintenance)`
- **10-15**: Excellent - Proceed.
- **6-9**: Acceptable - Proceed with care.
- **< 6**: Redesign or simplify.
---
## 2. React 19 & Next.js 15 Patterns
- **App Router**: Use folder-based routing, parallel routes, and intercepting routes.
- **Server Components (RSC)**: Default to Server Components for data fetching. Use `'use client'` only for interactivity.
- **Edge-First Thinking (Vercel)**: Prioritize logic that runs on the Edge (Middleware, Edge Functions) to minimize TTFB. Use Edge Runtime for high-performance dynamic routing.
- **Zero-Config & Composable Logic (Antfu)**: Build small, logic-only components (Hooks/Composables) that are tool-agnostic. Prefer `Vite` for development and `Vitest` for lightening-fast testing.
- **New Hooks**: Leverage `useActionState`, `useOptimistic`, and the `use` API.
- **Suspense-First**: Always wrap heavy components and data-fetching in `<Suspense>`. **No manual `isLoading` flags.**
---
## 3. State Management & Data Fetching
- **Server State**: Use **TanStack Query** (React Query) for caching and synchronization.
- **Local/Global**:
- `useState` for component-level.
- `Zustand` for complex global state.
- `Context` for subtree configuration.
- **Doctrine**: "Props down, Actions up."
- **Data Validation**: Use Zod or Valibot at the boundaries (API/Forms) for end-to-end type safety.
---
## 4. High-Craft UI Design (DFII)
Every UI must have an **Intentional Aesthetic** (e.g., Editorial Brutalism, Luxury Minimal).
Evaluate via **Design Feasibility & Impact Index (DFII)**:
`DFII = (Impact + Context Fit + Feasibility + Performance) β Consistency Risk`
- **Mandate**:
- β No generic "AI UI" or default Tailwind/ShadCN layouts.
- β Custom typography, purposeful motion (Framer Motion), and textured depth.
- β One "Memorable Anchor" per page (Magic UI component e.g., Bento Grid).
---
## 5. Performance & Optimization
- **Vercel Performance**: Implement ISR (Incremental Static Regeneration) and PPR (Partial Prerendering) where possible.
- **Turborepo Master**: Use intelligent caching to speed up builds and tests in monorepos.
- **Code Splitting**: Dynamic imports (`React.lazy`) for heavy modules.
- **Rendering**: Optimize for Core Web Vitals (LCP < 2.5s, CLS < 0.1).
- **Images**: Use Next.js `<Image>` for automatic optimization.
- **Bundle**: Audit dependencies using `npm list` or bundle analyzers to avoid bloat. Prefer lightweight libraries (e.g., `lucide-react` over `font-awesome`).
---
## π οΈ Execution Protocol
1. **Phase 1: Design Thinking**: Define Tone and Aesthetic Direction.
2. **Phase 2: Data Architecture**: Map Server vs. Client components.
3. **Phase 3: FFCI/DFII Check**: Ensure the project is viable and high-impact.
4. **Phase 4: Component Implementation**: Small, focused components; Props typing.
5. **Phase 5: Validation**: Performance audit and Accessibility check.
---
*Merged and optimized from 11 legacy frontend, React, and Next.js skills.*
Platform guidance
Imported from the listed AgentSkill.sh category. Complete supplied package files and notices are retained. Includes source scripts; review them before use. Required external tools and credentials are not installed. No bundled code was executed during import. Individual agent task behavior has not been tested.
Creates comprehensive design systems with typography, colors, components, and documentation for consistent UI development. Use when establishing design standards, building component libraries, or ensuring cross-team consistency. Keywords: design-tokens, typography, spacing, color-palette, compon...
UI design system toolkit for Senior UI Designer including design token generation, component documentation, responsive design calculations, and developer handoff tools. Use for creating design systems, maintaining visual consistency, and facilitating design-dev collaboration.
Comprehensive guide for creating professional UI/UX designs in Penpot using MCP tools. Use this skill when: (1) Creating new UI/UX designs for web, mobile, or desktop applications, (2) Building design systems with components and tokens, (3) Designing dashboards, forms, navigation, or landing page...