[Setup] Project structure and core scaffolding

[huy1010]

Summary

Set up the initial project structure for js-template CLI scaffolding tool. This establishes the foundation for a Next.js + NestJS fullstack project generator.

Current State

The following directories and stub files

js-template/
├── src/
│   ├── cli.ts          # Entry point (stub)
│   ├── generator.ts    # Template copier (stub)
│   ├── addons.ts       # Addon registry (interface defined)
│   └── utils.ts        # Utilities (stub)
├── templates/
│   ├── frontend/       # Next.js template
│   ├── backend/        # NestJS template
├── addons/
│   ├── auth.ts         # JWT/OAuth addon (stub)
│   ├── database.ts     # Prisma addon (stub)
│   └── ci.ts           # CI addon (stub)
├── bin/
├── tests/
├── package.json
└── tsconfig.json

Tasks

• Install core dependencies (typescript, tsx, vitest, inquirer/prompts, commander)
• Configure TypeScript (tsconfig.json with proper paths)
• Set up bin entry point (bin/cli.js)
• Verify pnpm dev runs the CLI stub
• Verify pnpm build compiles to dist/
• Add basic test setup with vitest
• Setup claude and agentic folders

Acceptance Criteria

• pnpm install succeeds
• pnpm dev prints "js-template" to console
• pnpm build produces dist/ with compiled JS
• pnpm test runs (even if no tests yet)
• Project follows the architecture defined in CLAUDE.md

Related

This is the foundation for subsequent issues:

• CLI interactive prompts
• Template generation
• Addon system

[nvminhtue]

Hi @huy1010, the structure seems good to me already, but there are still some comments for consideration:

• As the new trend of AI, is it worth adding an agentic folder of rules? (Vercel best practice official rules are highly recommended)
• Is docker an addon? It should be mandatory instead, what do you think?
• There are loads of addons like BullMQ, ORMs stuff, so I think the list above is just for reference, isn't it?
• base should be on each stack, I don't see any use case that can be used for both, please correct me if I'm wrong

[huy1010]

@nvminhtue Thanks a lot for your comment

• Yes, we definitely add agentic to the template. I updated the task list
• Remove it from the addon, we have dedicated issues to address it, and agree that it should be mandatory
• Yes, it's just a reference for template structure, feel free to add an issue for a core feature that is worth having, I'm happy with that
• I dropped it out as discussed yesterday