How do I install the T3d Init skill?

Run npx skillmds@latest add coolsocket/t3d-init in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is T3d Init safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with T3d Init?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is T3d Init free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published T3d Init?

coolsocket (@coolsocket) published this skill. Their other Agent Skills are listed on their SkillMD profile.

T3d Init by coolsocket — Agent Skill

Name: T3d Init
Author: coolsocket

T3d Init

Initialize the current project with the DDD+TDD harness — copies CLAUDE.md, CONTEXT-MAP.md, contexts/_TEMPLATE/, contexts/_shared_kernel/, and docs/adr/ from the plugin. Use when adopting the harness in a fresh repo or onboarding an existing one. Run from the project root.

coolsocket 9c0a7e4 2.5 KB Updated Sep 17, 2026

File contents

t3d-init

Copy the harness templates into the current project root (the directory where Claude Code was launched).

Plan

Resolve the project root from ${CLAUDE_PROJECT_DIR}. Print it.
For each template file under ${CLAUDE_PLUGIN_ROOT}/templates/:
- Compute destination path under ${CLAUDE_PROJECT_DIR}/.
- If destination exists, ask the user before overwriting (do NOT silently clobber CLAUDE.md).
- Otherwise, cp it across, preserving directory structure.
After copying, print a "next steps" message:
- Open CLAUDE.md and fill the  project-identity section.
- Open CONTEXT-MAP.md and list your bounded contexts.
- Run /t3d-new-context <your-first-context> to scaffold the first context.

Required tool calls

You must use the Bash tool to run cp -r. Do not use the Write tool for copying — it would re-author files and lose timestamps/perms.

Templates to copy

The plugin ships this layout under ${CLAUDE_PLUGIN_ROOT}/templates/:

templates/
├── CLAUDE.md                # generic harness rules (with FILL IN placeholders)
├── CONTEXT-MAP.md           # empty bounded-context inventory
├── contexts/
│   ├── _TEMPLATE/           # 4-layer skeleton — copy-paste source for new contexts
│   └── _shared_kernel/      # example pure value objects (Money, Timestamp, ModelName, TokenCount)
└── docs/
    └── adr/
        ├── README.md        # Matt Pocock 3-condition ADR rule
        └── NNNN-template.md # ADR template

Conflict handling

If ${CLAUDE_PROJECT_DIR}/CLAUDE.md already exists, ask the user one of:

keep — leave existing, don't copy CLAUDE.md (default)
overwrite — replace with plugin version
view-diff — show diff first

Do not overwrite contexts/_shared_kernel/ if it exists either — that directory often has project-specific value objects.

Done criteria

After running, the user should be able to:

Edit a file at contexts/anything/domain/x.py containing import fastapi and see the PreToolUse hook DENY it.
Run /t3d-new-context billing and see contexts/billing/ appear with the full 4-layer skeleton.

---name: t3d-initdescription: Initialize the current project with the DDD+TDD harness — copies CLAUDE.md, CONTEXT-MAP.md, contexts/_TEMPLATE/, contexts/_shared_kernel/, and docs/adr/ from the plugin. Use when adopting the harness in a fresh repo or onboarding an existing one. Run from the project root.---# t3d-initCopy the harness templates into the **current project root** (the directorywhere Claude Code was launched).## Plan1. Resolve the project root from `${CLAUDE_PROJECT_DIR}`. Print it.2. For each template file under `${CLAUDE_PLUGIN_ROOT}/templates/`: - Compute destination path under `${CLAUDE_PROJECT_DIR}/`. - If destination exists, **ask the user** before overwriting (do NOT silently clobber `CLAUDE.md`). - Otherwise, `cp` it across, preserving directory structure.3. After copying, print a "next steps" message: - Open `CLAUDE.md` and fill the `` project-identity section. - Open `CONTEXT-MAP.md` and list your bounded contexts. - Run `/t3d-new-context <your-first-context>` to scaffold the first context.## Required tool callsYou must use the `Bash` tool to run `cp -r`. Do not use the `Write` tool forcopying — it would re-author files and lose timestamps/perms.## Templates to copyThe plugin ships this layout under `${CLAUDE_PLUGIN_ROOT}/templates/`:```templates/├── CLAUDE.md # generic harness rules (with FILL IN placeholders)├── CONTEXT-MAP.md # empty bounded-context inventory├── contexts/│ ├── _TEMPLATE/ # 4-layer skeleton — copy-paste source for new contexts│ └── _shared_kernel/ # example pure value objects (Money, Timestamp, ModelName, TokenCount)└── docs/ └── adr/ ├── README.md # Matt Pocock 3-condition ADR rule └── NNNN-template.md # ADR template```## Conflict handlingIf `${CLAUDE_PROJECT_DIR}/CLAUDE.md` already exists, ask the user one of:- `keep` — leave existing, don't copy CLAUDE.md (default)- `overwrite` — replace with plugin version- `view-diff` — show diff firstDo not overwrite `contexts/_shared_kernel/` if it exists either — thatdirectory often has project-specific value objects.## Done criteriaAfter running, the user should be able to:- Edit a file at `contexts/anything/domain/x.py` containing `import fastapi` and see the PreToolUse hook DENY it.- Run `/t3d-new-context billing` and see `contexts/billing/` appear with the full 4-layer skeleton.

Frequently asked questions