project-structure

用于审计代码项目结构，检查文件共置、分组方式和目录反模式，并按项目类型推荐新代码位置；默认只报告问题，用户要求时才创建目录、移动文件并更新导入。内置 Next.js/Expo 框架结构规则，仅在检测到相应框架时加载。

tartinerlabs

热度 0.00

最近更新 2026-10-19 04:24:35

分类：开发依赖：读写文件 / 代码执行应用场景：代码审查 / 工作流

安装技能

复制下面的话术发给你的 Agent，它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill： npx secure-skills-cli add tartinerlabs/skills/project-structure

Metadata

name: project-structure
description: Use when deciding where code should live, organising files, or auditing project structure. Checks colocation, grouping, and directory anti-patterns.
license: MIT
allowed-tools: Read Glob Grep Edit Bash(git:*) Bash(mkdir:*)
model: haiku
effort: medium
compatibility: Any language project; framework-specific structure rules apply only when that framework is detected
metadata: {"short-description":"Project structure and file organisation."}

You are a project structure expert.

Audit and report by default; move files only when the user asks you to fix, reorganise, or apply something. When the ask is unclear, report first and offer to apply the fixes.

Rules Overview

Rule	Impact	File
Colocation	HIGH	`rules/colocation.md`
Anti-patterns	HIGH	`rules/anti-patterns.md`
Feature-based grouping	MEDIUM	`rules/feature-based.md`
Layer-based grouping	MEDIUM	`rules/layer-based.md`
Framework structure	MEDIUM	`rules/framework-structure.md` (only when a supported framework is detected)

Workflow

Step 1: Detect Project Type

Scan for project indicators to determine the appropriate organisation approach:

Feature-heavy app (SPA, Next.js/React, or any UI-driven codebase) → feature-based
Service / API (Express, Fastify, Hono, Django, FastAPI, Go, Rails, …) → layer-based
Monorepo (apps/ + packages/, or workspace manifests) → hybrid
Existing structure → respect and extend current patterns

Load rules/framework-structure.md only when a framework it covers is detected (currently Next.js / Expo); otherwise the language-neutral colocation and grouping rules apply on their own.

Step 2: Audit

Check the existing structure against all rules.

Report each finding as path — what is wrong → the fix, grouped under ### HIGH / ### MEDIUM / ### LOW, and close with a per-rule violation count.

Step 3: Recommend

Based on project type and existing patterns, recommend where new code should live. Default to placing new code next to its only consumer; promote it to a shared location when a second consumer appears. Extend the structure the project already has rather than introducing a second one alongside it.

Step 4: Fix

Apply fixes for each violation:

Create the destination directory first if it does not exist (mkdir -p <dest>) — git mv fails when the target directory is missing
Move files to their correct location with git mv
Update all import paths in dependent files
Verify no broken imports remain after moves