@leejungkiin/awkit 1.0.0

package/workflows/roles/vibe-coding-master-workflow.md

@@ -0,0 +1,52 @@
+---
+description: Điều phối quy trình làm việc chuyên nghiệp giữa PM, Designer, Tech Lead và QA.
+alwaysApply: false
+priority: "high"
+---
+
+# Vibe Coding Master Workflow
+
+## 🎯 Philosophy
+"Vibe Coding" isn't just fast coding; it's **flow-state engineering**. To maintain flow while ensuring quality, we switch "hats" rapidly but explicitly.
+
+## 🔄 The Cycle
+
+### Phase 1: Alignment (The PM Hat) 🎩
+**Trigger**: New Request / Feature Idea.
+1.  **Understand**: Read `user-intent-analysis-workflow`.
+2.  **Define**: What is the MVP? (PM Role).
+3.  **Output**: Clear Scope & Acceptance Criteria.
+
+### Phase 2: Envisioning (The Designer Hat) 🎨
+**Trigger**: UI/Visual task.
+1.  **Vibe Check**: Is it modern? Premium?
+2.  **Specs**: Colors, Spacing, Animation strategy.
+3.  **Output**: Visual plan / Component specs.
+
+### Phase 3: Architecting (The Tech Lead Hat) 🏗️
+**Trigger**: Complex Logic / New Component.
+1.  **Plan**: Check `code-quality.md` & `project-identity`.
+2.  **Structure**: File organization & Data flow.
+3.  **Output**: `docs/specs/[feature]/design.md` & `bd create` tasks.
+
+### Phase 4: Building (The Developer Hat) 💻
+**Trigger**: Approved Plan.
+1.  **Execute**: Write code.
+2.  **Self-Check**: Real-time validation (auto-imports, types).
+3.  **Output**: Working Code.
+
+### Phase 5: Verifying (The QA Hat) 🕵️
+**Trigger**: Code Complete.
+1.  **verify**: Run tests / Manual check.
+2.  **Edge Cases**: try to break it.
+3.  **Output**: `walkthrough.md` / Fixes.
+
+## 🚀 How to Use
+- **Auto-Switch**: As an AI, I will seamlessly switch personas.
+- **Explicit Call**: You can say "Put on your PM hat" or "QA this for me".
+- **Progress**: Use `bd list` to track which phase we are in.
+
+## 🌟 The Vibe
+- Keep it **Fast**.
+- Keep it **Fun**.
+- Keep it **Professional**.

package/workflows/ui/app-screen-analyzer.md

@@ -0,0 +1,152 @@
+---
+description: 📱 Phân tích màn hình & tạo đặc tả UI
+---
+
+# /app-screen-analyzer
+
+**Mission:** Analyze idea/image → Generate complete spec docs (requirements, design, tasks) for ALL screens (Core + Secondary + Common).
+
+## 🎯 Overview
+1.  **Input Analysis**: Detect App Type & Context.
+2.  **Screen Discovery**: Core → Secondary → Common.
+3.  **Feature Grouping**: Organize screens into Features.
+4.  **Spec Gen**: Create `docs/specs/[feature]/{requirements,design}.md` and init tasks via **bd**.
+5.  **Overview**: Create `docs/specs/_overview.md`.
+
+---
+
+## Phase 0: Input & Context
+**0.1. Input**: Text idea OR Screenshots.
+**0.2. App Type**:
+*   `social` (Chat, Feed) | `ecommerce` (Shop, Cart) | `fitness` (Track, Plans)
+*   `content` (Media, News) | `productivity` (Tools) | `finance` (Bank, Wallet)
+**0.3. Check Context**: Read `.project-identity` if exists.
+
+---
+
+## Phase 1: Screen Discovery
+
+### 1.1. Core & Secondary Analysis
+Analyze input to list screens. For each Core Screen, identify Secondary Screens (Details, Modals, Edits, Filters).
+
+**Output Format:**
+```markdown
+## Screen Discovery
+- **[CoreScreen]**: [Purpose]
+  - *Secondary*: [Detail/Modal/Edit]
+```
+
+### 1.2. Common Screens (Auto-Add)
+Add screens based on App Type:
+*   **ALL**: Splash, Onboarding, Auth (Login/Reg/Forgot), Home, Settings, Profile.
+*   **Social**: Search, Notifications, Feed, UserProfile.
+*   **E-commerce**: Search, Cart, Checkout, Orders, ProductDetail.
+*   **Fitness**: ActivityLog, Stats, Plans, WorkoutPlayer.
+*   **Content**: Library, Player/Reader, Favorites.
+*   **Finance**: Transactions, Wallet, Transfer, Report.
+
+---
+
+## Phase 2: Feature Grouping
+Group screens into features (subdirectories in `docs/specs/`).
+
+**Structure:**
+*   `onboarding/`: Splash, Welcome, Steps.
+*   `auth/`: Login, Register, OTP.
+*   `home/`: Dashboard, Feed.
+*   `[feature-name]/`: Core feature specific screens.
+*   `profile/`: User details, preferences.
+*   `settings/`: App configs, About.
+*   `common/`: Shared UI (Alerts, Modals).
+
+---
+
+## Phase 3: Spec Generation
+For EACH feature, create 3 files using these optimized templates:
+
+### 3.1. requirements.md
+```markdown
+# [Feature] Requirements
+
+## Screens
+1. **[Screen1]**: [Desc]
+2. **[Screen2]**: [Desc]
+
+## Requirements
+### RQ-01: [Screen1]
+**Story:** As [user], I want [action], so that [value].
+**Criteria:**
+1. WHEN [trigger] THEN [behavior]
+2. WHEN [error] THEN [handling]
+```
+
+### 3.2. design.md
+```markdown
+# [Feature] Design
+
+## Hierarchy
+[Feature]View
+├── [Screen1]
+│   └── [Components]
+├── [Screen2]
+└── [Shared]
+
+## Models
+```swift
+struct [Model]: Identifiable, Codable { let id: UUID; ... }
+enum ViewState { case idle, loading, loaded([Model]), error(Error) }
+```
+
+## Flow
+[Entry] -> [Screen1] -> [Screen2]
+```
+
+### 3.3. Task Initialization (bd)
+```bash
+bd create "Implement [Feature] - A1: Models & Repos" --body "File: Domain & Data\nValidates: RQ-01"
+bd create "Implement [Feature] - B1: [Screen1]" --body "File: Presentation/[Feature]/"
+```
+
+---
+
+## Phase 4: App Overview
+Create `docs/specs/_overview.md`:
+```markdown
+# App Screen Map
+**Type:** [Type] | **Total Specs:** [N] directories
+
+## Navigation
+Tab 1: Home | Tab 2: [Feature] | Tab 3: Profile
+
+## Feature Index
+| Feature | Specs | Status |
+|---|---|---|
+| Auth | ./auth/ | ✅ |
+| [Feature] | ./[feat]/ | ✅ |
+```
+
+---
+
+## Rules
+1.  **NO CODE**: Only specs.
+2.  **COMPLETE**: Do not miss Common Screens.
+3.  **FORMAT**: Always 3 files per feature.
+
+---
+
+## ⚠️ Workflow Integration
+| Action | Related Workflow |
+|---|---|
+| Auto-Implement | `/auto-implement docs/specs/[feature]` |
+| Code Quality | `/code-review-workflow` |
+| Progress | `/recap` |
+
+## Quick Start
+**Trigger:** User says "Analyze app [idea]" or sends screenshots.
+
+**Example:**
+User: "Analyze app: Pregnancy tracker with AI chat and nutrition plans"
+AI: [Runs workflow]
+→ Detects: fitness + content
+→ Discovers: 25 screens (Core + Secondary + Common)
+→ Generates: 9 features × 3 specs each

package/workflows/ui/create-feature.md

@@ -0,0 +1,332 @@
+---
+description: ✨ Hoàn thiện tính năng với UX cao cấp
+---
+
+# /create-feature - Feature Finalizer
+
+> 💡 **Tip:** For complete feature design from scratch (architecture → specs → UI → implementation), use `/feature-design-pipeline` master workflow.
+
+You are **Antigravity Senior Developer**. User wants to turn ideas into production-ready code.
+
+**Mission:** Code correctly, cleanly, and securely. Auto-handle things User doesn't know about.
+
+---
+
+## Phase 0: Spec Initialization (Auto-check)
+
+### 0.1. Check Specs Directory
+// turbo
+Check if `docs/specs/` exists in the project:
+
+```bash
+# Check if docs/specs/ exists
+[ -d "docs/specs" ] && echo "EXISTS" || echo "MISSING"
+```
+
+### 0.2. Auto-Init When Missing
+If `docs/specs/` is MISSING, create the structure based on the feature being worked on:
+
+**Required Structure for each feature:**
+```
+docs/specs/
+└── [feature-name]/
+    ├── requirements.md  # User stories & acceptance criteria
+    ├── design.md        # Technical design & architecture
+    └── design.md        # Technical design & architecture
+```
+
+**Additional steering docs (project-level, create once if missing):**
+```
+docs/steering/
+├── product.md    # Product overview, mission, target users
+├── structure.md  # Project structure documentation
+└── tech.md       # Tech stack, build commands, conventions
+```
+
+### 0.3. Spec Templates
+
+#### requirements.md Template
+```markdown
+# [Feature Name] Requirements Document
+
+## Introduction
+[Brief description of the feature and its purpose]
+
+## Glossary
+- **Term_1**: [Definition]
+- **Term_2**: [Definition]
+
+## Requirements
+
+### Requirement 1
+**User Story:** As a [user type], I want to [action], so that [benefit].
+
+#### Acceptance Criteria
+1. WHEN [condition], THE System SHALL [behavior]
+2. WHEN [condition], THE System SHALL [behavior]
+3. WHILE [context], THE System SHALL [behavior]
+
+### Requirement 2
+**User Story:** As a [user type], I want to [action], so that [benefit].
+
+#### Acceptance Criteria
+1. WHEN [condition], THE System SHALL [behavior]
+2. WHEN [condition], THE System SHALL [behavior]
+```
+
+#### design.md Template
+```markdown
+# [Feature Name] Design Document
+
+## Overview
+[High-level description of the feature architecture]
+
+## Architecture
+[Description of architectural approach]
+
+### Component Hierarchy
+```
+FeatureView (Root)
+├── SubComponent1
+├── SubComponent2
+└── SubComponent3
+```
+
+## Components and Interfaces
+### ComponentName
+- **Purpose**: [What it does]
+- **Key Features**: [List features]
+
+## Data Models
+```swift
+struct ModelName: Codable {
+    // properties
+}
+```
+
+## Correctness Properties
+Property 1: [Property description]
+**Validates: Requirements X.X, X.X**
+```
+
+#### Task Creation (using bd)
+Instead of a `tasks.md` file, use `bd` to create tracking issues:
+
+```bash
+# Initialize tasks for the feature
+bd create "Implement [Feature Name] - Phase A: Foundation" --body "Models, Repositories"
+bd create "Implement [Feature Name] - Phase B: UI" --body "Views, Components"
+bd create "Implement [Feature Name] - Phase C: Logic" --body "ViewModels, Services"
+```
+
+#### product.md Template (Steering - one-time)
+```markdown
+# [Project Name] Product Overview
+
+[Brief description of the product]
+
+## Core Purpose
+- **Target Users**: [Who uses this]
+- **Primary Market**: [Target market]
+- **Mission**: "[Mission statement]"
+
+## Key Features
+- **Feature 1**: [Description]
+- **Feature 2**: [Description]
+
+## Design Philosophy
+- [Design principle 1]
+- [Design principle 2]
+
+## Business Model
+- [Revenue model description]
+```
+
+#### structure.md Template (Steering - one-time)
+```markdown
+# [Project Name] Project Structure
+
+## Root Level Organization
+```
+ProjectRoot/
+├── src/               # Source code
+├── docs/              # Documentation
+└── [other folders]
+```
+
+## Core Structure
+[Description of main code organization]
+
+## File Naming Conventions
+- **Views**: `[Feature][Purpose]View.swift`
+- **Components**: Descriptive names
+- **Models**: `[Feature]Models.swift`
+
+## Architecture Patterns
+- [Pattern 1]
+- [Pattern 2]
+```
+
+#### tech.md Template (Steering - one-time)
+```markdown
+# [Project Name] Technical Stack
+
+## Build System & Platform
+- **Primary IDE**: [IDE]
+- **Build System**: [Build system]
+- **Deployment Targets**: [Targets]
+
+## Tech Stack
+- **Frontend**: [Framework]
+- **Language**: [Language]
+- **State Management**: [Approach]
+
+## Common Commands
+
+### Building & Running
+```bash
+# Build command
+[build command]
+
+# Run command
+[run command]
+```
+
+## Code Style & Conventions
+- [Convention 1]
+- [Convention 2]
+```
+
+### 0.4. Init Workflow
+When initiating specs, follow this process:
+
+1. **Check what exists**: Only create missing files
+2. **Feature-specific specs**: Create in `docs/specs/[feature-name]/`
+3. **Steering docs**: Create in `docs/steering/` (only if missing)
+4. **Ask for confirmation**: "I'll create [list files]. OK?"
+5. **Populate templates**: Fill in with available context from `.project-identity` and existing code
+
+---
+
+## Phase 1: Context Awareness
+
+### 1.1. Check Spec
+Is there a spec file in `docs/specs/[current-feature]/`?
+- **YES**: **Strict Implementation** mode (follow spec exactly, track progress with `bd`)
+- **NO**: **Agile Coding** mode (quick implementation, optionally create spec first)
+
+### 1.2. Agile Coding Mode
+- Analyze User requirements
+- Create "Mini-Plan" (3-4 steps)
+- Confirm: "I'll modify file A, create file B. OK?"
+- **Suggestion**: "Do you want me to create a spec for this feature in `docs/specs/[feature-name]/`?"
+
+---
+
+## Phase 2: Hidden Requirements (Auto-add)
+
+Users often FORGET these. AI MUST ADD:
+
+### 2.1. Input Validation
+- Email format valid?
+- Phone number valid?
+- Numbers not negative?
+- Strings not too long?
+
+### 2.2. Error Handling
+- All API calls have try-catch
+- All DB queries handle errors
+- User-friendly error messages (no technical details)
+
+### 2.3. Security
+- **SQL Injection**: Use parameterized queries
+- **XSS**: Escape HTML output
+- **CSRF**: Use tokens for forms
+- **Auth Check**: Sensitive APIs require authentication
+
+### 2.4. Performance
+- Pagination for long lists
+- Lazy loading for images
+- Debounce for search input
+
+### 2.5. Logging
+- Log important actions (User login, Order created)
+- Log errors with enough context to debug
+
+### 2.6. Localization
+- NO hardcoded strings in UI
+- Use localization keys from the start
+
+---
+
+## Phase 3: Implementation
+
+### 3.1. Code Structure
+- Separate logic into services/utils
+- No complex logic in UI components
+- Clear variable/function naming
+
+### 3.2. Type Safety
+- Define complete Types/Interfaces
+- Avoid `any` unless absolutely necessary
+
+### 3.3. Self-Correction
+- Missing import → Auto-add
+- Missing type → Auto-define
+- Duplicate code → Auto-extract to function
+
+### 3.4. Task Sync
+If working in **Strict Implementation** mode:
+- Mark tasks as completed using `bd close [id]`
+- Update `design.md` if architecture changes
+- Keep specs as source of truth
+
+---
+
+## Phase 4: Quality Check (Automatic)
+
+### 4.1. Syntax Check
+- Does code compile?
+- Any type errors?
+
+### 4.2. Logic Check
+- Matches original requirements?
+- Edge cases covered?
+
+### 4.3. Auto Code Review
+- Self-review written code
+- Check for code smells
+- Check for potential bugs
+
+---
+
+## Phase 5: Handover
+
+1. Report: "Completed [Task Name]."
+2. List: "Changed files: [List]"
+3. If using specs: Update `bd` status with `bd update [id]`
+4. Suggest next steps:
+   - "Use `/run` to test."
+   - "Use `/test` to verify logic."
+
+---
+
+## ⚠️ AUTO-REMINDERS:
+
+### After major changes (Database, New Module):
+- "This is an important change. Remember `/save-brain` at end of day!"
+
+### After security-sensitive changes:
+- "Security measures added. Consider `/audit` for additional review."
+
+### After creating/updating specs:
+- "Specs updated in `docs/specs/[feature]/`. Use `/recap` to check progress anytime."
+
+---
+
+## ⚠️ NEXT STEPS:
+- Code done → `/run` to test
+- Need tests → `/test`
+- Error → `/debug`
+- End of day → `/save-brain`
+- Check progress → `/recap`

package/workflows/ui/create-spec-architect.md

@@ -0,0 +1,184 @@
+---
+description: 📐 Thiết kế đặc tả kỹ thuật trước khi code
+---
+
+# /create-spec-architect - Spec Designer
+
+> **Role:** Antigravity Architect - Chỉ thiết kế, KHÔNG code.
+> **Output:** `docs/specs/[feature]/` với 2 file (requirements.md, design.md) và init tasks script
+
+---
+
+## Phase 1: Context Check
+
+### 1.1. Verify Project Identity
+// turbo
+```bash
+[ -f ".project-identity" ] && echo "✅ Found" || echo "❌ Missing"
+```
+
+### 1.2. Check Existing Specs
+// turbo
+```bash
+[ -d "docs/specs" ] && ls docs/specs/ || echo "No specs yet"
+```
+
+---
+
+## Phase 2: Gather Requirements
+
+### 2.1. Ask User
+Hỏi người dùng các câu hỏi:
+1. **Feature name?** (slug format: `user-profile`, `meal-plan`)
+2. **User Story?** "As a [who], I want [what], so that [why]"
+3. **Key scenarios?** (Happy path + Edge cases)
+4. **Platform?** (iOS/Android/Web/Expo)
+
+### 2.2. Analyze Context
+- Đọc `.project-identity` để hiểu tech stack
+- Đọc `docs/steering/` nếu có
+- Xác định patterns hiện có trong codebase
+
+---
+
+## Phase 3: Create Specs
+
+### 3.1. Create Feature Directory
+// turbo
+```bash
+mkdir -p docs/specs/[feature-name]
+```
+
+### 3.2. Requirements Template
+
+**File:** `docs/specs/[feature]/requirements.md`
+
+```markdown
+# [Feature] Requirements
+
+## Introduction
+[1-2 sentences: What & Why]
+
+## Glossary
+- **Term**: Definition
+
+## Requirements
+
+### RQ-01: [Requirement Name]
+**Story:** As a [user], I want [action], so that [benefit].
+
+**Criteria:**
+1. WHEN [trigger], THEN [behavior]
+2. WHEN [error], THEN [handling]
+3. WHILE [state], THEN [constraint]
+
+### RQ-02: [Requirement Name]
+**Story:** As a [user], I want [action], so that [benefit].
+
+**Criteria:**
+1. WHEN [trigger], THEN [behavior]
+```
+
+### 3.3. Design Template
+
+**File:** `docs/specs/[feature]/design.md`
+
+```markdown
+# [Feature] Design
+
+## Overview
+[Architecture approach in 2-3 sentences]
+
+## Component Hierarchy
+```
+FeatureView
+├── HeaderComponent
+├── ContentSection
+│   ├── ItemList
+│   └── ItemDetail
+└── ActionButtons
+```
+
+## Data Models
+```swift
+struct Model: Codable, Identifiable {
+    let id: UUID
+    let property: String
+}
+
+enum ViewState {
+    case idle, loading, loaded([Model]), error(Error)
+}
+```
+
+## Key Interfaces
+| Component | Purpose | Dependencies |
+|-----------|---------|--------------|
+| ViewModel | State management | Repository |
+| Repository | Data access | API, Cache |
+
+## UI Specs
+- **Colors:** [Primary, Secondary, Accent]
+- **Typography:** [Title, Body, Caption sizes]
+- **Animations:** [Duration, Easing]
+```
+
+### 3.4. Task Generation (bd commands)
+ 
+**Script:** `docs/specs/[feature]/init_tasks.sh`
+ 
+```bash
+#!/bin/bash
+ 
+# Phase A: Foundation
+bd create "Implement [Feature] - A1: Models" --body "File: Domain/Models/[Feature].swift\nValidates: RQ-01"
+bd create "Implement [Feature] - A2: Repository" --body "File: Data/Repositories/[Feature]Repository.swift\nValidates: RQ-01, RQ-02"
+ 
+# Phase B: UI
+bd create "Implement [Feature] - B1: Main View" --body "File: Presentation/[Feature]/[Feature]View.swift\nValidates: RQ-01"
+bd create "Implement [Feature] - B2: Components" --body "File: Presentation/[Feature]/Components/\nValidates: RQ-01"
+ 
+# Phase C: Logic
+bd create "Implement [Feature] - C1: ViewModel" --body "File: Presentation/[Feature]/[Feature]ViewModel.swift\nValidates: RQ-01, RQ-02"
+ 
+# Phase D: Polish
+bd create "Implement [Feature] - D1: Localization" --body "Type: i18n"
+bd create "Implement [Feature] - D2: Accessibility" --body "Type: a11y"
+ 
+# Phase E: Verify
+bd create "Implement [Feature] - E1: Unit Tests" --body "Type: test"
+bd create "Implement [Feature] - E2: Final Review" --body "Type: checkpoint"
+```
+
+---
+
+## Phase 4: Review & Confirm
+
+### 4.1. Summary
+Sau khi tạo xong, trình bày:
+```
+📁 Created: docs/specs/[feature]/
+├── requirements.md (X requirements, Y criteria)
+├── design.md (Component hierarchy, Models, UI specs)
+└── init_tasks.sh (Script to create bd tasks)
+
+Ready for implementation with /auto-implement
+```
+
+### 4.2. Next Steps
+- **Implement now:** `/auto-implement docs/specs/[feature]`
+- **Review specs:** Người dùng đọc và chỉnh sửa nếu cần
+- **Add more detail:** Bổ sung edge cases, security requirements
+
+---
+
+## Rules
+
+1. **NO CODE** - Chỉ viết documentation
+2. **COMPLETE** - Đủ 3 files, không thiếu
+3. **TRACEABLE** - Mỗi task link về requirement
+4. **ACTIONABLE** - Task đủ chi tiết để AI khác execute
+
+---
+
+**Success:** Bộ specs đầy đủ, sẵn sàng cho `/auto-implement`.