skills.rest
TimeKast
TimeKastOFFICIAL
Explore all skills by this author →
WebsiteGitHub

sk-project-structure

Map new files and refactors to correct directories in the TimeKast Starter Kit.

Updated May 19, 2026
Search Tags:#project structure#feature slicing#path aliases#codebase refactor#architecture conventions#shared vs domain#file placement
One-click install
npx skills add https://github.com/TimeKast/AgendaInteligente --skill sk-project-structure
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sk-project-structure
Source: https://github.com/TimeKast/AgendaInteligente/tree/main/.claude/skills/sk-project-structure
Command: npx skills add https://github.com/TimeKast/AgendaInteligente --skill sk-project-structure

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates confusion and inconsistencies about where code and files should live in the TimeKast Starter Kit, so developers and AI agents refactor and add features without breaking conventions.

Core Features & Use Cases

  • Shared vs Domain import rule: Enforces that Shared/Infra never imports Domain, preventing circular coupling and feature leakage.
  • Feature slice extraction guidance: Defines when to keep code in the global layout versus when to create src/features/{domain}/ for larger, cohesive domains.
  • Deterministic “where does this file go?” decision table: Provides a consistent mapping for Next.js routes, Server Actions, DB schema, Zod validations, tests, tooling scripts, and runtime config.
  • Path alias conventions: Standardizes @/components/*, @/lib/*, and @/config/* so imports remain uniform across the codebase.

Quick Start

Ask an AI agent to audit a proposed refactor or new file change, and tell it to map each file to the correct target directory using the skill’s “where does this file go?” rules and naming conventions.

Frequently Asked Questions about sk-project-structure

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

FAQPage Schema
How do I structure a Next.js project to prevent circular imports between shared and domain code?▼

To prevent circular imports, structure your project so Shared/Infra directories never import Domain code. Enforcing this dependency constraint stops feature leakage and architectural boundary violations in your codebase.

When should I extract a feature slice instead of using the global layout?▼

Extract a feature slice into `src/features/{domain}/` when a domain grows large and requires cohesive boundaries. Keep cross-cutting concerns in the global layout to maintain clear architectural separation and prevent feature leakage.

What are the standard path alias conventions for a feature-sliced codebase?▼

Standard path alias conventions use `@/components/*`, `@/lib/*`, and `@/config/*` for uniform imports. Applying these aliases keeps import paths consistent across global directories and extracted feature slices.

How do I decide where to place tooling scripts and runtime config in a feature-sliced architecture?▼

Map tooling scripts and runtime config using deterministic placement rules that separate global utilities from domain-specific logic. This ensures standard path aliases and naming conventions remain consistent across the project.

Related Skills

Explore More Software Engineering Skills→
salemazielsalemaziel

project-conventions

Define project directory structures, file naming conventions, and working standards.

Community
Basic
flosrnflosrn

architect

Analyze codebase structure, detect architectural smells, and propose restructuring plans.

Community
Advanced
chiubakachiubaka
1

runtime-boundary-validation-zod

Validate untrusted JSON data at runtime using Zod schemas.

Community
Advanced
machenjiemachenjie
4

module-boundary-design

Design module boundaries with explicit contracts and enforced dependency direction.

Community
Advanced