How do I install the Dlc Scaffold Modules skill?

Run npx get-skill add delacournz/dlc-scaffold-modules 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 Dlc Scaffold Modules safe to use?

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

Which AI agents work with Dlc Scaffold Modules?

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 Dlc Scaffold Modules free to use?

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

Who published Dlc Scaffold Modules?

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

Dlc Scaffold Modules by delacournz — Agent Skill

Name: Dlc Scaffold Modules
Rating: 4.5 (4 reviews)
Author: delacournz

Dlc Scaffold Modules

Scaffold the colocated module pattern under `src/modules/` for any app. Creates `src/modules/` plus `AGENTS.md` and `CLAUDE.md` documenting the per-domain convention (`components/`, `sheets/`, `contexts/`, `hooks/`, `utils/` added on demand). No code, no empty folders, no example module. Delegates the full procedure to `references/modules.md`. Use when the user asks to set up a module structure, scaffold `src/modules`, establish a colocated feature/domain folder convention, or add the module pattern to an existing app. Triggers on phrases like "scaffold module structure", "set up src/modules", "module pattern", "colocated modules", "domain folder structure".

delacournz Updated Nov 14, 2026

File contents

Scaffold Module Structure

Establish the colocated module pattern under src/modules/ so domain code has a consistent home. Each domain (e.g. auth, trade, transactions) owns its own components/, sheets/, contexts/, hooks/, and utils/ subfolders, created on demand. This skill writes only src/modules/ plus two markdown files, no code, so future agents follow the same convention when adding features.

When to Use

User asks to set up a module structure or scaffold src/modules
User wants a colocated feature/domain folder convention for a new app
User asks to add the module pattern to an existing app that lacks one
Triggers: "scaffold module structure", "set up src/modules", "module pattern", "colocated modules", "domain folder structure"

Rules / Steps

Follow the full procedure in references/modules.md. Do not skip steps and do not paraphrase the file contents, copy them exactly as written.

High-level outline:

Create the src/modules/ directory.
Write src/modules/AGENTS.md documenting the per-domain components/ / sheets/ / contexts/ / hooks/ / utils/ convention.
Write src/modules/CLAUDE.md pointing at AGENTS.md.
Do not create subfolders up front, do not add .gitkeep files, and do not scaffold an example module. Subfolders are added on demand the first time a module needs them.

---name: dlc-scaffold-modulesdescription: Scaffold the colocated module pattern under `src/modules/` for any app. Creates `src/modules/` plus `AGENTS.md` and `CLAUDE.md` documenting the per-domain convention (`components/`, `sheets/`, `contexts/`, `hooks/`, `utils/` added on demand). No code, no empty folders, no example module. Delegates the full procedure to `references/modules.md`. Use when the user asks to set up a module structure, scaffold `src/modules`, establish a colocated feature/domain folder convention, or add the module pattern to an existing app. Triggers on phrases like "scaffold module structure", "set up src/modules", "module pattern", "colocated modules", "domain folder structure".metadata: source: https://skillmd.com/skills/delacournz/dlc-scaffold-modules author: chris@delacour.co.nz version: "0.1.0" category: architecture tags: [architecture, modules, scaffolding, project-structure, conventions, agents-md]---# Scaffold Module StructureEstablish the colocated **module pattern** under `src/modules/` so domain code has a consistent home. Each domain (e.g. `auth`, `trade`, `transactions`) owns its own `components/`, `sheets/`, `contexts/`, `hooks/`, and `utils/` subfolders, created on demand. This skill writes only `src/modules/` plus two markdown files, no code, so future agents follow the same convention when adding features.## When to Use- User asks to set up a module structure or scaffold `src/modules`- User wants a colocated feature/domain folder convention for a new app- User asks to add the module pattern to an existing app that lacks one- Triggers: "scaffold module structure", "set up src/modules", "module pattern", "colocated modules", "domain folder structure"## Rules / StepsFollow the full procedure in [references/modules.md](./references/modules.md). Do not skip steps and do not paraphrase the file contents, copy them exactly as written.High-level outline:1. Create the `src/modules/` directory.2. Write `src/modules/AGENTS.md` documenting the per-domain `components/` / `sheets/` / `contexts/` / `hooks/` / `utils/` convention.3. Write `src/modules/CLAUDE.md` pointing at `AGENTS.md`.4. Do not create subfolders up front, do not add `.gitkeep` files, and do not scaffold an example module. Subfolders are added on demand the first time a module needs them.

Frequently asked questions