Feature: nodespec create project - Initialize monorepo with NodeSpec standards

[deepracticexs]

User Story

As a developer, I want to run a single command to initialize a new monorepo project with all NodeSpec standards pre-configured, so that I can start building immediately without manual setup.

Expected Behavior

nodespec create project DeepracticeAccount

Should create a production-ready monorepo with:

Project Structure

DeepracticeAccount/
├── domains/      # Business logic layer
├── packages/     # Infrastructure layer  
├── configs/      # Configuration standards
├── apps/         # Application layer
├── services/     # Service layer
├── tools/        # Development tools
├── package.json
├── pnpm-workspace.yaml
├── turbo.json
├── tsconfig.json
├── lefthook.yml
├── commitlint.config.js
├── .gitignore
├── .npmrc
├── .nvmrc
├── .editorconfig
└── README.md

Pre-configured Standards

All @deepracticex/* configs should be automatically set up:

• ✅ ESLint (@deepracticex/eslint-config)
• ✅ Prettier (@deepracticex/prettier-config)
• ✅ TypeScript (@deepracticex/typescript-config)
• ✅ Commitlint (@deepracticex/commitlint-config)
• ✅ Vitest (@deepracticex/vitest-config)
• ✅ Cucumber (@deepracticex/cucumber-config)
• ✅ tsup (@deepracticex/tsup-config)

Immediate Usability

After command completion:

cd DeepracticeAccount
pnpm install     # Works immediately
git init         # Git hooks auto-configured
pnpm test        # Testing ready
pnpm build       # Build pipeline ready

Acceptance Criteria

• Command successfully creates all directory structure
• All config files are generated with correct content
• pnpm install works without errors
• Git hooks (lefthook) are functional
• Commitlint validates commit messages
• All configs reference correct @deepracticex/* packages
• Generated README includes project-specific instructions
• Zero manual configuration needed

Design Questions to Discuss

1. Interactive vs Non-interactive

   • Prompt for project details (name, description, author)?
   • Or accept all via CLI flags?

2. Template Source

   • Embedded templates in CLI?
   • Separate template repository?
   • Generate from code?

3. Customization Level

   • Support different project types (API, CLI, Library)?
   • Or single opinionated template?

4. Git Initialization

   • Auto git init?
   • Auto create first commit?
   • Or leave to user?

5. Package Manager

   • Auto run pnpm install?
   • Or just generate files?

6. Error Handling

   • What if directory already exists?
   • What if offline (can't fetch templates)?

Related

This is the first feature for Issue #1 - building CLI with DeepracticeAccount as the real-world test case.

Notes

This is a requirements issue - the specific design and implementation details need discussion before development.

🤖 Generated with Claude Code

[deepracticexs]

Design Decisions

After discussion, here are the finalized design decisions:

1. Interactive vs Non-interactive

Decision: Pure command-line (non-interactive)

• No prompts, all parameters via CLI arguments
• Simple and efficient
• AI-friendly automation

2. Template Source

Decision: NodeSpec itself is the template (self-hosting/bootstrapping)

• The DeepracticeNodeSpec repository structure serves as the template
• No separate template repository needed
• Always reflects the latest best practices

3. Customization Level

Decision: Single opinionated template (for now)

• Focus on one best practice
• Future: can add variants as needed
• Simplicity over flexibility initially

4. Git Initialization

Decision: Automatic

• Auto git init
• Ready to commit immediately
• Part of "zero configuration" goal

5. Package Manager

Decision: Automatic

• Auto run pnpm install
• Fully automated setup
• User can start coding immediately after command completes

6. Error Handling

Decision: CLI embeds template files

• Template files bundled with CLI during build
• No network dependency
• Fail fast if directory exists (with clear error message)

Implementation Strategy

Code Generation Approach

• Generate files programmatically (not static templates)
• Dynamic content based on project name
• Directly reference NodeSpec's latest configurations
• Smaller CLI bundle size

Next Steps

• Commit domains/ architecture changes
• Create apps/cli basic structure
• Implement nodespec create project command
• Test with DeepracticeAccount creation

---

🤖 Generated via github-issue-manager agent

[deepracticexs]

Updated Command Structure

Based on the finalized CLI design in #11, the command structure has been updated:

New command format:

nodespec dev monorepo init [project-name]

This aligns with our four-layer structure:

• dev - Role (Developer)
• monorepo - Domain (workspace = project root)
• init - Action (initialize)
• [project-name] - Object (project name, optional)

Features to implement:

1. Initialize monorepo structure in current directory
2. Create standard directories: apps/, services/, packages/
3. Generate configuration files: package.json, pnpm-workspace.yaml, tsconfig.json
4. Set up dev tooling: ESLint, Prettier, TypeScript configs
5. Initialize git repository (optional with --skip-git)
6. Install dependencies (optional with --skip-install)

Related commands:

nodespec dev monorepo validate    # Validate monorepo structure
nodespec dev monorepo info         # Display monorepo information

See #11 for the complete CLI design specification.