frontend-guidelines

Community

Standardize frontend patterns across Next.js apps

AuthorLiinkiing
Version1.0.0
Installs0

System Documentation

What problem does it solve?

This Skill provides frontend architecture guidelines to ensure consistent component placement, reuse, and maintainable code structure across a Next.js monorepo, reducing onboarding time and ambiguity.

Core Features & Use Cases

  • Collocate page-specific components inside the App Router page directory (the same directory as page.tsx, layout.tsx, etc.) and place them under a _components/ folder.
  • Centralize shared components and utilities under frontend/src/ following the existing project structure (src/ui/, src/shared/, src/theme/, etc.).
  • Promote shared usage when components or utilities are reused across routes, layouts, or features to maintain a single source of truth.

Quick Start

Use these guidelines to organize Next.js app code:

  • Place page-specific components in frontend/app/{route}/_components/ alongside page.tsx and layout.tsx.
  • Keep shared components and utilities in frontend/src/, adhering to the existing architecture and naming conventions.
  • Follow lint/format rules and prefer collocated components first before moving to shared directories.

Dependency Matrix

Required Modules

None required

Components

Standard package

💻 Claude Code Installation

Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.

Please help me install this Skill:
Name: frontend-guidelines
Download link: https://github.com/Liinkiing/larastack/archive/main.zip#frontend-guidelines

Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
View Source Repository

Agent Skills Search Helper

Install a tiny helper to your Agent, search and equip skill from 223,000+ vetted skills library on demand.