AgentStack
SKILL verified MIT Self-run

Split Monolith

skill-yerdaulet-damir-vibe-coding-rules-split-monolith · by yerdaulet-damir

Safe procedure for decomposing a god file (400+ LOC) into a sub-package without breaking any imports. Load when a file exceeds 400 lines or mixes multiple concerns. Implements vibecodex Principles A1 and A8 — folder-instead-of-file with backward-compatible re-exports.

No reviews yet
0 installs
6 views
0.0% view→install

Install

$ agentstack add skill-yerdaulet-damir-vibe-coding-rules-split-monolith

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Split Monolith? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

split-monolith

A file split done wrong breaks every caller. Follow this procedure exactly — it is reversible at every step.


Step 0 — Confirm the file needs splitting

wc -l app/services/.py

| Lines | Action | |-------|--------| | 600 | Split immediately (Principle A7 hard cap) |

Also ask: does this file mix multiple concerns? A file that is long but cohesive is better than a premature split.


Step 1 — Identify the domain splits

Do NOT split by size. Split by type of responsibility.

Good splits (by domain):

wallet_service.py (1200 LOC) →
  wallet/user.py      ← user-facing operations (charge, refund)
  wallet/admin.py     ← admin operations (top-up, override)
  wallet/history.py   ← read-only queries

Good splits (by layer):

generation_service.py (1000 LOC) →
  generation/orchestrator.py   ← coordinates the flow
  generation/cost.py           ← cost calculation logic
  generation/storage.py        ← result persistence

Bad splits (by size only — don't do this):

big_service.py →
  big_service_part1.py   ← meaningless
  big_service_part2.py   ← meaningless

Write the target structure before touching any file.


Step 2 — Create the package directory

mkdir app/services//

Do NOT move any code yet.


Step 3 — Create sub-files one at a time

For each sub-file, copy (not move) the relevant functions:

# Create the new file with the relevant subset
touch app/services//user.py
# Copy relevant classes/functions from the original

Each sub-file must:

  • Have its own imports (do not rely on * imports)
  • Be under 200 LOC (you're splitting — keep it lean)
  • Contain one cohesive responsibility

Step 4 — Create __init__.py with ALL old names re-exported

This is the most important step. Every name that existed in the original file must still be importable from the same path.

# app/services//__init__.py

# Principle A8: re-export everything so callers don't change.
from app.services..user import CreditsUserService
from app.services..admin import CreditsAdminService
from app.services..user import get_credits_user_service

# Backward-compat alias if the old class had a different name
CreditsService = CreditsUserService  # old name → new class

__all__ = [
    "CreditsUserService",
    "CreditsAdminService",
    "CreditsService",           # backward compat
    "get_credits_user_service",
]

Step 5 — Verify no import breaks

# Check every file that imported from the old module still works
python3 -c "from app.services. import "
python3 -c "from app.services. import "

# Run the full test suite
pytest tests/ -x -q

All tests must be GREEN before deleting the original file.


Step 6 — Delete the original file

Only after Step 5 passes:

rm app/services/.py

Run tests again:

pytest tests/ -x -q
bash scripts/lint-architecture.sh

Both must pass.


Common mistakes

| Mistake | Consequence | Prevention | |---------|------------|------------| | Split before writing __init__.py | Import errors everywhere | Always create __init__.py first | | Split by size, not responsibility | Sub-files still coupled | Ask: "what is the single job of this file?" | | Forget to re-export old names | Callers break silently | List every public name before splitting | | Move code instead of copy+verify | Can't roll back | Copy first, delete only after tests pass | | Split and refactor at same time | Impossible to debug | One PR = one split. No logic changes. |


Verification

The split was done correctly when:

  • [ ] All sub-files are under 200 LOC
  • [ ] __init__.py re-exports every name that existed before
  • [ ] python3 -c "from app.services. import " works
  • [ ] pytest tests/ -x -q is green
  • [ ] bash scripts/lint-architecture.sh exits 0
  • [ ] Original file is deleted

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.