skills.rest
dinogit
dinogitCOMMUNITY
Explore all skills by this author →
GitHub

feature-scaffolding

Automates scaffolding of feature pages with standard project structure.

1|Updated Dec 30, 2025
Search Tags:#templates#consistency#routing#scaffold#feature#project-structure#pages
One-click install
npx skills add https://github.com/dinogit/motocho --skill feature-scaffolding
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature-scaffolding
Source: https://github.com/dinogit/motocho/tree/main/.claude/skills-disabled/feature-scaffolding
Command: npx skills add https://github.com/dinogit/motocho --skill feature-scaffolding

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scaffolds new feature pages following project patterns. Use when creating new pages, features, routes, or when user asks to set up a new section. Works with component-organization skill for structure.

Core Features & Use Cases

  • Standard structure: Provides the standard src/features/{feature-name}/ layout including page.tsx, a components/ directory with component-name.tsx files, and optional types.ts.
  • Guided templates: Enforces one component per file, kebab-case filenames, and named exports to ensure consistency.
  • Use Case: When expanding the app with a new feature or route, it rapidly generates a cohesive starting point that follows established patterns.

Quick Start

Create a new feature by adding a folder under src/features/{feature-name}/ with page.tsx, a components/ directory, and optional types.ts as needed. For example, to scaffold a dashboard feature, create src/features/dashboard/ with page.tsx and components/dashboard-widget.tsx.

Frequently Asked Questions about feature-scaffolding

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

FAQPage Schema
How do I scaffold a new feature page with a consistent project structure?▼

Scaffold new feature pages by creating a src/features/{feature-name}/ directory containing page.tsx, a components/ folder, and optional types.ts. This enforces consistent project structure by automatically applying conventions like kebab-case filenames and named exports.

What is the standard file structure for adding a new route or feature section?▼

The standard feature section structure uses a src/features/{feature-name}/ layout. It includes a page.tsx file for main route logic, a components/ directory for isolated UI pieces, and an optional types.ts file for TypeScript definitions.

Do I need to follow specific naming conventions when generating new page components?▼

Yes, you must follow specific naming conventions when generating page components. The scaffolding enforces one component per file, kebab-case filenames for all component-name.tsx files, and named exports to ensure codebase consistency.

Can I use this scaffolding approach for both new pages and standalone feature routes?▼

Yes, you can use this scaffolding approach for both new pages and standalone feature routes. It automates the creation of a cohesive starting point following established project patterns, ensuring consistent structure whether adding a simple page or a complex feature section.

Related Skills

Explore More Software Engineering Skills→
gileckgileck

feature-based-structure

Organize client-side code into feature-based folders under src/client/features.

Community
Basic
AgentiveCityAgentiveCity
2

nextjs-routes-and-layouts

Plan, implement, and refactor Next.js App Router routes and layouts.

Official
Intermediate
gileckgileck

react-component-organization

Organize React components into route, feature, and shared UI folders.

Community
Basic
BrunoAlpezdevBrunoAlpezdev

scaffold

Generate Atomic Design boilerplate for Next.js components and TypeScript types.

Community
Intermediate