Web Development Skill

Architect TypeScript, React, and Next.js frontends with Feature-Sliced Design layers.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/evanisnor/quotecraft --skill web-development-skill-evanisnor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Web Development Skill
Source: https://github.com/evanisnor/quotecraft/tree/main/.claude/skills/webdev
Command: npx skills add https://github.com/evanisnor/quotecraft --skill web-development-skill-evanisnor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill codifies best practices and architectural guidelines for building modern frontend applications using TypeScript, React, and Next.js, enabling consistent, scalable codebases.

Core Features & Use Cases

  • Enforces Feature-Sliced Design layers and segment boundaries to maintain clear separation between app, pages, widgets, features, entities, and shared code.
  • Provides structured guidance for ES module usage, public API surfaces, and naming conventions to improve team collaboration and maintainability.
  • Offers practical patterns for state management (hooks, context, reducers), effects, and Next.js SSR considerations to reduce bugs and onboarding time.

Quick Start

Review existing project structure and refactor a sample module to follow Feature-Sliced Design guidelines.

Frequently Asked Questions about Web Development Skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is Feature-Sliced Design in React and Next.js architectures?

Feature-Sliced Design is an architectural methodology that structures frontend codebases into app, pages, widgets, features, entities, and shared layers to ensure clear separation of concerns and scalable architecture for TypeScript, React, and Next.js projects.

How do I structure a Next.js project using Feature-Sliced Design layers?

You structure a Next.js project by organizing code across app, pages, widgets, features, entities, and shared layers. This Skill provides guidelines for ES module usage, public API exposure, and rigorous layer-boundary rules to maintain testable code.

Can I use Feature-Sliced Design for state management and SSR in TypeScript?

Yes, Feature-Sliced Design applies to TypeScript projects and offers practical patterns for state management using hooks, context, and reducers. It also covers Next.js SSR considerations to reduce bugs and onboarding time.

What's the best way to enforce layer boundaries in a React frontend codebase?

The best way to enforce layer boundaries is by adhering to rigorous layer-boundary rules within Feature-Sliced Design. This Skill codifies segment boundaries and public API surfaces to maintain clear separation between architectural layers.

Why do I need public API exposure rules in frontend architecture?

Public API exposure rules are needed in frontend architecture to improve team collaboration and maintainability. They provide structured guidance for ES module usage and naming conventions, ensuring clear boundaries between features and entities.