🎨 🎨 Fix code formatting with Prettier

- Apply consistent formatting to CONTRIBUTING.md
- Format docs/STACKS.md for better readability
- Fix TypeScript type formatting in ui.ts and scaffold.ts
- Ensure all files follow project code style guidelines

Author: YagoBorba

CONTRIBUTING.md

@@ -101,11 +101,13 @@ packages/core/src/templates/your-stack-name/
 ```
 
 **Important**: Use these replacement variables in your templates:
+
 - `{{projectName}}` - The project name
 - `{{description}}` - Project description
 - `{{authorName}}` - Author name
 
 **Example package.json.tpl:**
+
 ```json
 {
   "name": "{{projectName}}",
@@ -137,22 +139,42 @@ dist/
 Add your new stack to the type definitions:
 
 **In `packages/core/src/scaffold.ts`:**
+
 ```typescript
 export interface ProjectOptions {
   projectPath: string;
-  stack: "node-js" | "node-ts" | "react" | "vue" | "python" | "java" | "go" | "php" | "your-stack-name";
+  stack:
+    | "node-js"
+    | "node-ts"
+    | "react"
+    | "vue"
+    | "python"
+    | "java"
+    | "go"
+    | "php"
+    | "your-stack-name";
   features: ("docker" | "husky")[];
   replacements: Record<string, string>;
 }
 ```
 
 **In `packages/cli/src/commands/ui.ts`:**
+
 ```typescript
 export interface InitAnswers {
   projectName: string;
   description: string;
   authorName: string;
-  stack: "node-js" | "node-ts" | "react" | "vue" | "python" | "java" | "go" | "php" | "your-stack-name";
+  stack:
+    | "node-js"
+    | "node-ts"
+    | "react"
+    | "vue"
+    | "python"
+    | "java"
+    | "go"
+    | "php"
+    | "your-stack-name";
   features: ("docker" | "husky")[];
   commitValidation?: boolean;
 }
@@ -176,7 +198,7 @@ Update the stack choices in `packages/cli/src/commands/ui.ts`:
     { name: "Java + Spring", value: "java" },
     { name: "Go + Gin", value: "go" },
     { name: "PHP + Laravel", value: "php" },
-    { name: "Your Stack + Framework", value: "your-stack-name" }, 
+    { name: "Your Stack + Framework", value: "your-stack-name" },
   ],
 }
 ```
@@ -206,6 +228,7 @@ if (answers.stack === "python") {
 ### 3. Best Practices for New Stacks
 
 #### Template Structure Guidelines:
+
 - **Follow conventions**: Use the technology's standard project structure
 - **Include essentials**: Configuration files, build tools, testing setup
 - **Add documentation**: Include basic README template
@@ -215,6 +238,7 @@ if (answers.stack === "python") {
 #### Example Folder Structures:
 
 **Frontend Stack (SPA):**
+
 ```
 src/
 ├── components/
@@ -226,6 +250,7 @@ src/
 ```
 
 **Backend Stack (API):**
+
 ```
 src/
 ├── controllers/
@@ -237,6 +262,7 @@ src/
 ```
 
 **Full-Stack Framework:**
+
 ```
 src/
 ├── components/

docs/STACKS.md

@@ -7,6 +7,7 @@ StackCode supports multiple technology stacks, each designed with best practices
 ### Frontend Stacks
 
 #### React + TypeScript
+
 - **Framework**: React 18 with TypeScript
 - **Build Tool**: Vite
 - **Styling**: TailwindCSS
@@ -15,6 +16,7 @@ StackCode supports multiple technology stacks, each designed with best practices
 - **Features**: Modern JSX Transform, ESLint configuration, component structure
 
 **Generated Structure:**
+
 ```
 ├── src/
 │   ├── components/
@@ -30,6 +32,7 @@ StackCode supports multiple technology stacks, each designed with best practices
 ```
 
 #### Vue.js + TypeScript
+
 - **Framework**: Vue 3 with Composition API and TypeScript
 - **Build Tool**: Vite
 - **Styling**: TailwindCSS
@@ -38,6 +41,7 @@ StackCode supports multiple technology stacks, each designed with best practices
 - **Features**: SFC (Single File Components), modern Vue patterns
 
 **Generated Structure:**
+
 ```
 ├── src/
 │   ├── components/         # Reusable components
@@ -54,11 +58,13 @@ StackCode supports multiple technology stacks, each designed with best practices
 ### Backend Stacks
 
 #### Node.js + JavaScript
+
 - **Runtime**: Node.js with ES6+
 - **Testing**: Jest
 - **Features**: Express.js structure, middleware, controllers, routes
 
 **Generated Structure:**
+
 ```
 ├── src/
 │   ├── controllers/        # Request handlers
@@ -72,11 +78,13 @@ StackCode supports multiple technology stacks, each designed with best practices
 ```
 
 #### Node.js + TypeScript
+
 - **Runtime**: Node.js with TypeScript
 - **Testing**: Vitest
 - **Features**: Type-safe development, modern TypeScript configuration
 
 **Generated Structure:**
+
 ```
 ├── src/
 │   ├── controllers/        # Type-safe controllers
@@ -88,23 +96,27 @@ StackCode supports multiple technology stacks, each designed with best practices
 ```
 
 #### Python + FastAPI
+
 - **Framework**: FastAPI
 - **Package Management**: pip with pyproject.toml
 - **Features**: Modern Python async API development
 
 **Generated Structure:**
+
 ```
 ├── src/
 │   └── main.py
 └── pyproject.toml
 ```
 
 #### Java + Spring
+
 - **Framework**: Spring Boot
 - **Build Tool**: Maven
 - **Features**: Enterprise Java development structure
 
 **Generated Structure:**
+
 ```
 ├── src/main/java/com/example/app/
 │   ├── Application.java
@@ -114,22 +126,26 @@ StackCode supports multiple technology stacks, each designed with best practices
 ```
 
 #### Go + Gin
+
 - **Framework**: Gin web framework
 - **Package Management**: Go modules
 - **Features**: High-performance Go web development
 
 **Generated Structure:**
+
 ```
 ├── main.go
 └── go.mod
 ```
 
 #### PHP + Laravel
+
 - **Framework**: Laravel
 - **Package Management**: Composer
 - **Features**: Modern PHP development with MVC structure
 
 **Generated Structure:**
+
 ```
 ├── app/Http/Controllers/
 ├── bootstrap/
@@ -141,7 +157,9 @@ StackCode supports multiple technology stacks, each designed with best practices
 ## 🔧 Stack Features
 
 ### Automatic Configuration
+
 Each stack includes:
+
 - ✅ **Optimized package.json** (or equivalent) with relevant dependencies
 - ✅ **TypeScript configuration** (where applicable)
 - ✅ **Build tool setup** (Vite, Maven, etc.)
@@ -150,18 +168,23 @@ Each stack includes:
 - ✅ **Best practice folder structure**
 
 ### Smart Package Management
+
 StackCode automatically uses the appropriate package manager:
+
 - **npm** for Node.js-based stacks (React, Vue, Node.js)
 - **pip** for Python projects
-- **maven** for Java projects  
+- **maven** for Java projects
 - **go mod** for Go projects
 - **composer** for PHP projects
 
 ### Docker Support
+
 All stacks can include Docker configuration when the Docker feature is selected during project initialization.
 
 ### Git Integration
+
 Every generated project includes:
+
 - ✅ **Stack-specific .gitignore** files
 - ✅ **Git repository initialization**
 - ✅ **Conventional commit setup** (with Husky)
@@ -181,12 +204,13 @@ Then select your preferred technology stack from the interactive menu.
 Interested in adding support for a new technology stack? Check out our comprehensive guide in [CONTRIBUTING.md](../CONTRIBUTING.md#adding-new-technology-stacks).
 
 The process involves:
+
 1. Creating template files
-2. Updating type definitions  
+2. Updating type definitions
 3. Adding CLI options
 4. Configuring package management
 5. Testing thoroughly
 
 ---
 
-*For more information about StackCode, visit our [main documentation](../README.md).*
+_For more information about StackCode, visit our [main documentation](../README.md)._

packages/cli/src/commands/ui.ts

@@ -194,7 +194,15 @@ export interface InitAnswers {
   projectName: string;
   description: string;
   authorName: string;
-  stack: "node-js" | "node-ts" | "react" | "vue" | "python" | "java" | "go" | "php";
+  stack:
+    | "node-js"
+    | "node-ts"
+    | "react"
+    | "vue"
+    | "python"
+    | "java"
+    | "go"
+    | "php";
   features: ("docker" | "husky")[];
   commitValidation?: boolean;
 }

packages/core/src/scaffold.ts

@@ -39,7 +39,15 @@ async function copyTemplateFiles(
 
 export interface ProjectOptions {
   projectPath: string;
-  stack: "node-js" | "node-ts" | "react" | "vue" | "python" | "java" | "go" | "php";
+  stack:
+    | "node-js"
+    | "node-ts"
+    | "react"
+    | "vue"
+    | "python"
+    | "java"
+    | "go"
+    | "php";
   features: ("docker" | "husky")[];
   replacements: Record<string, string>;
 }