Loading...
Loading...
Found 23 Skills
Component architecture, design patterns, state management strategies, module systems, build tools, and scalable application structure
Recommends and scaffolds frontend technology stack for new projects. Use when starting a new frontend project, selecting a framework, setting up a web app from scratch, or when the user asks about frontend tech stack, scaffolding, or architecture selection. Covers React/Next.js/Astro/Vue, TypeScript, Tailwind CSS, state management, data fetching, UI components, testing, and monorepo setup.
Build reusable, maintainable UI components following modern design patterns. Use when creating component libraries, implementing design systems, or building scalable frontend architectures. Handles React patterns, composition, prop design, TypeScript, and component best practices.
Codebase orientation. Use FIRST when exploring code, finding files, or understanding project structure.
Architectural guidance for building node-based UIs with React Flow. Use when designing flow-based applications, making decisions about state management, integration patterns, or evaluating whether React Flow fits a use case.
Apply Feature-Sliced Design (FSD) architecture to frontend projects. Triggers on: FSD, feature slicing, frontend architecture, layer structure, module boundaries, scalable frontend, slice organization. Use when: creating new features/components/pages, restructuring React/Next.js/Vue/Remix projects, organizing frontend code, setting up project structure, fixing import violations, or migrating legacy codebases.
Architect and design web application interfaces. Plans component systems, interaction flows, and responsive layouts for web platforms.
Achra Platform guidelines, business rules, architecture, and engineering patterns. Use when writing or refactoring Achra code, adding modules or components, creating or updating skeleton loaders, loading placeholders, Suspense fallbacks, or Next.js loading.tsx, answering questions about Achra architecture or business domains, deciding when to use feature flags, applying Achra naming and placement conventions, or answering which technologies and libraries the project uses.
Frontend architecture expert. Use when planning component architecture, state management strategies, performance optimization, or technology selection decisions.
Expert design systems leadership covering component libraries, design tokens, documentation, and design-development collaboration.
Guide for building, configuring, and deploying microfrontends on Vercel. Use this skill when the user mentions microfrontends, multi-zones, splitting an app across teams, independent deployments, cross-app routing, incremental migration, composing multiple frontends under one domain, microfrontends.json, @vercel/microfrontends, the microfrontends local proxy, or path-based routing between Vercel projects. Also use when the user asks about shared layouts across projects, navigation between microfrontends, fallback environments, asset prefixes, or feature flag controlled routing.
Official Feature-Sliced Design (FSD) v2.1 skill for applying the methodology to frontend projects. Use when the task involves organizing project structure with FSD layers, deciding where code belongs, defining public APIs and import boundaries, resolving cross-imports or evaluating the @x pattern, deciding whether logic should remain local or be extracted, migrating from FSD v2.0 or a non-FSD codebase, integrating FSD with frameworks, or implementing common patterns such as auth, API handling, Redux, and React Query within FSD.