domain-scaffolder

Generate backend and frontend scaffolds from domain slice plans.

2|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/build000r/skillbox --skill domain-scaffolder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: domain-scaffolder
Source: https://github.com/build000r/skillbox/tree/main/workspace/client-planning-skills/domain-scaffolder
Command: npx skills add https://github.com/build000r/skillbox --skill domain-scaffolder

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Planning and scaffolding for domain-driven code is complex and error-prone; domain-scaffolder provides a canonical, mode-driven pathway to generate backend and frontend scaffolds from a domain slice plan, ensuring consistency with shared contracts and audit handoffs.

Core Features & Use Cases

  • Canonical shared scaffolder for domain slices that centralizes mode handling and surface resolution
  • Supports backend and frontend surfaces with unified plan-to-scaffold generation
  • Emits a structured audit handoff including surface, slice, mode file used, plan path, and validation results
  • Use case: scaffold a new domain slice after domain-planner finishes a slice plan for both backend and frontend

Quick Start

Ask the Domain Scaffolder to generate a scaffold from the active domain plan for a specified surface (backend or frontend).

Frequently Asked Questions about domain-scaffolder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate backend and frontend scaffolds from a domain slice plan?

To generate backend and frontend scaffolds from a domain slice plan, you use a mode-driven pathway to map slice plans to concrete templates. This handles surface selection and emits structured project skeletons with validated artifacts.

What is domain slice scaffolding and when do I need it?

Domain slice scaffolding is the canonical generation of project skeletons from domain plans. You need it when domain-driven code planning is complex and error-prone, ensuring consistent backend and frontend outputs with shared contracts and audit handoffs.

Do I need a valid slice plan and mode files before scaffolding domain slices?

Yes, you need a valid slice plan and domain-scaffolder mode files before scaffolding domain slices. The scaffolder requires these to perform mode resolution, surface selection, and handoff auditing to emit validated project skeletons.

Can I scaffold both backend and frontend surfaces from a single domain plan?

Yes, you can scaffold both backend and frontend surfaces from a single domain plan. The scaffolder supports unified plan-to-scaffold generation for both surfaces, emitting a structured audit handoff including the surface, slice, and mode file used.

What's the best way to ensure consistency when generating domain-driven code scaffolds?

The best way to ensure consistency when generating domain-driven code scaffolds is using a canonical, mode-driven pathway. This centralizes mode handling and surface resolution, emitting a structured audit handoff with validation results.