project-architect

Plan Next.js App Router file placements using TREE.md as the source of truth.

Updated Nov 24, 2025
One-click install
npx skills add https://github.com/greentcsolutions-lab/tc-helper-app --skill project-architect-greentcsolutions-lab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-architect
Source: https://github.com/greentcsolutions-lab/tc-helper-app/tree/main/.claude/skills/project-architect
Command: npx skills add https://github.com/greentcsolutions-lab/tc-helper-app --skill project-architect-greentcsolutions-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams decide folder and file placement for Next.js App Router projects by enforcing a single source of truth (TREE.md) and guiding minimal, colocated changes.

Core Features & Use Cases

  • Colocation-first guidance for app/pages and route groups, prioritizing route folders and groupings over global shims.
  • Reads TREE.md as the single source of truth and ensures all proposals trace back to it.
  • Provides before/after subtree examples to facilitate quick approvals with minimal disruption.

Quick Start

Provide the current TREE.md and ask for a proposed colocated structure for a new route to begin.

Frequently Asked Questions about project-architect

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

FAQPage Schema
How do I organize new files in a Next.js App Router project structure?

Next.js App Router colocation places new files directly inside specific route folders or route groups rather than global shared directories, ensuring minimal disruption and localized changes guided by your project's TREE.md.

What is the best way to maintain a single source of truth for Next.js routing architecture?

Using a TREE.md file as the definitive source of truth ensures your Next.js routing architecture stays consistent by validating all proposed file placements against the existing project structure before applying changes.

How do I decide between route groups and shared folders for colocated components?

Decide between route groups and shared folders by reserving shared directories only for clearly cross-cutting concerns, defaulting to route folders and groupings for colocated components to avoid unnecessary global reuse.

Does this approach work for reviewing structural changes before modifying a Next.js project?

Yes, the approach outputs minimal changes alongside a before/after subtree snippet for review, allowing you to verify Next.js App Router structural modifications without making assumptions beyond your TREE.md content.

Why should I avoid global reuse when planning Next.js app structure?

Avoid global reuse to prevent bloated shared directories and maintain strict colocation in your Next.js app structure, routing files to the most specific route folders unless a component is clearly cross-cutting.