skills.rest
Adrienenjalbert
AdrienenjalbertCOMMUNITY
Explore all skills by this author →
GitHub

repo-architecture

Automate code placement and boundary enforcement in Next.js repositories.

Updated Aug 27, 2026
Search Tags:#architecture#nextjs#repo#route-boundaries#code-placement#feature-organization
One-click install
npx skills add https://github.com/Adrienenjalbert/flex-carrer-hub --skill repo-architecture-adrienenjalbert
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repo-architecture
Source: https://github.com/Adrienenjalbert/flex-carrer-hub/tree/main/.agents/skills/repo-architecture
Command: npx skills add https://github.com/Adrienenjalbert/flex-carrer-hub --skill repo-architecture-adrienenjalbert

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams make consistent decisions about where code should live in the repo, how routes and features are organized, and how to structure files to align with the project's architecture rules.

Core Features & Use Cases

  • Enforces repository layout conventions for Next.js apps, e.g., place feature-owned code in src/features, keep src/app thin, and use src/lib for low-level utilities.
  • Guides decisions on where to place new routes, features, and code, ensuring alignment with dependency direction and architecture rules.
  • Validates that generated code follows the standardized architecture and avoids misplacements.

Quick Start

Provide a placement plan for a new route by outlining the target directories and file boundaries.

Frequently Asked Questions about repo-architecture

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

FAQPage Schema
How do I organize code placement in a Next.js repository?▼

Code placement in a Next.js repository is organized by enforcing conventions: keeping src/app thin, placing feature-owned code in src/features, using src/shared for cross-feature infrastructure, and src/lib for low-level utilities.

What is the best way to structure new routes and features in Next.js?▼

Structuring new routes and features requires aligning with dependency direction and architecture rules, ensuring the src/app directory remains thin while feature-owned code resides in src/features to maintain clean route boundaries.

Why does my Next.js app architecture have misplaced code across features?▼

Misplaced code occurs when repository layout conventions are not enforced, causing feature logic to leak into src/app instead of being isolated in src/features or src/shared for cross-feature infrastructure.

Can I use this to validate code relocation during an architecture review?▼

Yes, it automates architecture decisions during code relocation and architecture reviews, validating that modified files follow standardized conventions and avoid misplacements across src/app, src/features, src/shared, and src/lib.

When do I need to use src/shared instead of src/lib in Next.js?▼

Use src/shared for cross-feature infrastructure that multiple features depend on, and reserve src/lib for low-level utilities to ensure correct dependency direction and boundary enforcement in your Next.js project.

Related Skills

Explore More Software Engineering Skills→
flpbaladaflpbalada
280

project-structure

Organize React/Next.js/TypeScript projects by feature-based architecture.

Community
Basic
Tristan578Tristan578
5

arch-validator

Validate Rust engine architecture boundaries to prevent browser dependencies in core/.

Community
Intermediate
hopeoverturehopeoverture

worldcrafter-route-creator

Scaffold Next.js App Router routes with page, API, loading, and error files.

Community
Basic
ArieGoldkinArieGoldkin

architecture-navigator

Scan the DevPrep AI codebase and map its 7-folder architecture.

Community
Basic