T3d new context

Skill coolsocket/t3d/skills/t3d-new-context

DDD + TDD harness for Claude Code — 5 hooks enforce Domain layer purity, cross-context call rules, and red-green discipline at edit time. Ships 4 skills + project templates.

Install

npx -y skills add coolsocket/t3d --skill t3d-new-context

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Scaffold a new bounded context by copying contexts/_TEMPLATE/ to contexts/<name>/. Use when starting a new bounded context — keeps the 4-layer DDD skeleton (domain/application/infrastructure/ui) + tests/ + CONTEXT.md + INVARIANTS.md consistent across all contexts.

SKILL.md

2.2 KB, as published. Nobody here has run it

t3d-new-context

Create a fresh bounded context from the harness template.

Required arguments

The user invokes this as /t3d-new-context <context-name> or types the name when prompted. The name must:

Be snake_case (e.g. billing, user_profile, order_fulfillment)
NOT start with _ (reserved for _TEMPLATE and _shared_kernel)
NOT already exist under ${CLAUDE_PROJECT_DIR}/contexts/

If the name is missing or invalid, ask the user before proceeding.

Plan

Verify ${CLAUDE_PROJECT_DIR}/contexts/_TEMPLATE/ exists. If not, prompt the user to run /t3d-init first.
cp -r contexts/_TEMPLATE contexts/<name> (note: use the user's PROJECT _TEMPLATE, not the plugin's — /t3d-init should have copied it already, and the user may have customized it).
Print "next steps":
- Open contexts/<name>/CONTEXT.md — add 1-3 bounded ubiquitous-language terms
- Open contexts/<name>/INVARIANTS.md — add INV-001 (your first invariant)
- Open contexts/<name>/tests/unit/test_inv_001_*.py — write the failing test
- Then implement domain code until it passes (red → green → refactor)
(Optional) Add the new context to CONTEXT-MAP.md.

Required tool calls

Use Bash for the directory copy. Do NOT use Write — preserve template structure and any user customizations to _TEMPLATE/.

Reminders

The new context starts EMPTY. No domain model yet — that's intentional. TDD says: write the invariant + failing test FIRST, then add domain code.
The 4 layers (domain/, application/, infrastructure/, ui/) and 4 test categories (unit/, integration/, contract/, use_case/) are all pre-made as empty packages. Don't reorganize.
The hooks shipped with this plugin will enforce:
- No external imports in domain/ (PreToolUse on Edit/Write)
- No cross-context domain/ imports from other contexts
- Tests must be green at Stop if you touched domain/