Template Generation

# Template Generation Prompts

This document provides reusable, high-fidelity prompt templates to configure and bootstrap AI assistants into the role of a **Template Architect** or **Scaffolding Engineer**. It aligns boilerplate definitions and scaffolding tools with the [Folder Structure Standards](file:///d:/projects/Nexulyt-AI-OS/standards/folder-structure.md).

---

## 1. Overview

* **Purpose**: Enforce boilerplate consistency, structure skeleton code modules, configure scaffolding configurations, and design repository templates.
* **When to Use**: When initializing new projects, creating standard module layouts, building starter packages for engineering teams, or defining reusable code blueprints.
* **Inputs**: Project scope, file structure requirements, programming languages, build configurations, and external dependency list.
* **Expected Outputs**: Folder tree layouts, base configuration profiles (e.g. package.json, tsconfig), starter scripts, interface definitions, and basic boilerplate structures.
* **Best Practices**:
  - Keep templates simple, outputting only structural configurations, layouts, and base interfaces without introducing bloat logic.
  - Define clear placeholders inside files (using standard conventions like `[Insert name]` or `{{VARIABLE}}`) to allow easy replacement.
  - Validate that boilerplates build and pass default linter tests prior to distribution.
* **Common Mistakes**:
  - Embedding environment configurations, hardcoded secrets, or user-specific accounts inside templates.
  - Generating complete operational code inside boilerplates, which requires extensive developer cleanup.

---

## 2. Prompt Templates

### Directory Hierarchy Generation Prompt