# Contributing to create-latest-mern-app

Contributions are welcome and appreciated.

## 1. Before You Start
- Check open issues first to avoid duplicate work.
- If you want to add a feature, open an issue with a short proposal before coding.

## 2. Local Setup

```bash
git clone https://github.com/pulkitgarg04/create-latest-mern-app.git
cd create-latest-mern-app
npm install
```

## 3. Branch Naming
- Use a dedicated branch per change.
- Suggested format: `feat/<short-name>`, `fix/<short-name>`, `docs/<short-name>`.

## 4. Commit Style
- Write clear, focused commit messages.
- Examples:
  - `feat: add backend-only template prompt`
  - `fix: handle invalid project name edge case`
  - `docs: improve quick start instructions`

## 5. Pull Request Checklist
- Keep PRs focused on one logical change.
- Update README or template docs if behavior changes.
- Test the CLI end-to-end:
  - frontend only
  - backend only
  - full stack
  - JavaScript and TypeScript options
- Include screenshots or terminal output when useful.

## 6. Code Quality Expectations
- Keep changes minimal and readable.
- Preserve existing code style.
- Avoid breaking template paths or prompt flow.
- Do not commit generated `node_modules` or `dist` files.

Thanks for helping improve this project.