organize-project

Included with Lifetime

$97 forever

Use to assess + improve project structure — folder layout, file placement, naming, separation of concerns. Read-mostly with structured proposal output. User approves before any moves.

General

What this skill does


# organize-project

Project-structure assessment and (with approval) reorganization. Diagnoses sprawl, proposes layout, applies only on user confirm.

## Method

1. **Inventory current.** Top-level dirs, file counts per dir, deepest paths, naming convention drift.
2. **Detect smells:**
   - Files-at-root sprawl (>15 top-level files)
   - Single-file dirs (folder with one file = noise)
   - Deeply nested paths (>5 levels)
   - Naming inconsistency (camelCase + kebab-case + snake_case mixed)
   - Orphan tests (test files without source pair, or vice versa)
   - Duplicate concerns across multiple folders
3. **Propose layout** matching project type:
   - Node lib: `src/`, `tests/`, `docs/`, `bin/`, `scripts/`
   - sfdx project: `force-app/main/default/{classes,lwc,objects,...}`
   - Rust: `src/`, `tests/`, `benches/`, `examples/`
   - Python: `src/<package>/`, `tests/`, `docs/`, `pyproject.toml`
4. **Diff.** Show what moves where. Group by reason.
5. **User approves.** Granular — accept all, accept some, reject.
6. **Apply** approved moves. Update import paths. Commit per group.

## Output shape (assess)

```
Project type detected: Node library

Smells:
  ✗ Root-level sprawl: 23 files at root
  ✗ Single-file dirs:  4 (config/, helpers/, types/, lib/)
  ⚠ Mixed naming:      camelCase + kebab-case in src/
  ✓ Tests paired:      all source files have test pairs

Proposed reorganization:
  Move:
    config/db.ts       → src/config/db.ts
    helpers/format.ts  → src/utils/format.ts
    types/api.ts       → src/types/api.ts
    lib/log.ts         → src/lib/log.ts
  Rename:
    src/UserService.ts → src/user-service.ts (kebab-case match)
    src/orderHelper.ts → src/order-helper.ts
  
  Effort: ~30 min including import updates
  
  Approve which: all | moves only | renames only | reject
```

## Rules

- **Don't auto-apply.** Always user-approve granular.
- **Update imports** after every move (atomically — single commit).
- **One move per commit** OR one logical group per commit (e.g. "move all helpers to utils/").
- **Detect convention from neighbouring projects** if the current is too sparse to inform.
- **Memory captures the reorg** so future similar projects reuse the layout.

## Anti-patterns

- Big-bang reorganisation in one commit (impossible to review)
- Moving without updating imports (broken builds)
- Imposing one stack's conventions on another (Rust idioms on Node project)
- Renaming `*.test.ts` files (breaks vitest discovery — verify first)

## When NOT to use

- Greenfield (you set the structure as you go)
- Single-file projects (no structure to organise)
- Active feature work in progress (wait for landing)

## Subagent dispatch

- `Explore` for the inventory + diagnosis
- `general-purpose` for the actual moves
- `Bash` for `git mv` (preserves history)

## Value over native CC

CC will move files on request. CC won't naturally diagnose smells, propose project-type-appropriate layouts, or enforce import-update-atomicity. The structure-aware framing IS the value.

Files: 1

Size: 3.2 KB

Complexity: 7/100

Category: General

Source: https://github.com/ialameh/sift-coder/tree/main/skills/workflow/organize-project

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts