kiro-kit 0.1.3 → 0.2.1

package/dist/presets/devops/skills/web-frameworks/scripts/turborepo_migrate.py

@@ -0,0 +1,394 @@
+#!/usr/bin/env python3
+"""
+Turborepo Migration Script
+
+Convert existing monorepo to Turborepo with intelligent pipeline generation.
+"""
+
+import argparse
+import json
+import os
+import sys
+from pathlib import Path
+from typing import Dict, List, Optional, Set
+
+
+class TurborepoMigrator:
+    """Migrate existing monorepo to Turborepo."""
+
+    def __init__(
+        self,
+        path: Path,
+        dry_run: bool = False,
+        package_manager: str = "npm",
+    ):
+        """
+        Initialize TurborepoMigrator.
+
+        Args:
+            path: Path to existing monorepo
+            dry_run: Preview changes without writing files
+            package_manager: Package manager (npm, yarn, pnpm, bun)
+        """
+        self.path = path.resolve()
+        self.dry_run = dry_run
+        self.package_manager = package_manager
+        self.packages: List[Dict] = []
+        self.workspace_config: Dict = {}
+
+    def validate_path(self) -> None:
+        """Validate monorepo path."""
+        if not self.path.exists():
+            raise FileNotFoundError(f"Path '{self.path}' does not exist")
+
+        if not self.path.is_dir():
+            raise NotADirectoryError(f"Path '{self.path}' is not a directory")
+
+        package_json = self.path / "package.json"
+        if not package_json.exists():
+            raise FileNotFoundError(
+                f"No package.json found in '{self.path}'. Not a valid monorepo."
+            )
+
+    def analyze_workspace(self) -> None:
+        """Analyze existing workspace configuration."""
+        print("Analyzing workspace...")
+
+        package_json = self.path / "package.json"
+        with open(package_json) as f:
+            root_config = json.load(f)
+
+        # Detect workspace configuration
+        if "workspaces" in root_config:
+            self.workspace_config = {
+                "type": "npm/yarn",
+                "patterns": root_config["workspaces"],
+            }
+        elif (self.path / "pnpm-workspace.yaml").exists():
+            self.workspace_config = {
+                "type": "pnpm",
+                "file": "pnpm-workspace.yaml",
+            }
+        else:
+            raise ValueError(
+                "No workspace configuration found. Monorepo structure not detected."
+            )
+
+        print(f"  Workspace type: {self.workspace_config['type']}")
+
+    def discover_packages(self) -> None:
+        """Discover all packages in workspace."""
+        print("Discovering packages...")
+
+        if self.workspace_config["type"] == "npm/yarn":
+            patterns = self.workspace_config["patterns"]
+            if isinstance(patterns, dict):
+                patterns = patterns.get("packages", [])
+        else:
+            # Parse pnpm-workspace.yaml
+            yaml_file = self.path / "pnpm-workspace.yaml"
+            patterns = self._parse_pnpm_workspace(yaml_file)
+
+        # Find all packages matching patterns
+        for pattern in patterns:
+            self._find_packages_by_pattern(pattern)
+
+        print(f"  Found {len(self.packages)} packages")
+        for pkg in self.packages:
+            print(f"    - {pkg['name']} ({pkg['path'].relative_to(self.path)})")
+
+    def _parse_pnpm_workspace(self, yaml_file: Path) -> List[str]:
+        """Parse pnpm-workspace.yaml file."""
+        patterns = []
+        with open(yaml_file) as f:
+            in_packages = False
+            for line in f:
+                line = line.strip()
+                if line.startswith("packages:"):
+                    in_packages = True
+                    continue
+                if in_packages and line.startswith("- "):
+                    pattern = line[2:].strip().strip("'\"")
+                    patterns.append(pattern)
+        return patterns
+
+    def _find_packages_by_pattern(self, pattern: str) -> None:
+        """Find packages matching glob pattern."""
+        import glob
+
+        # Convert pattern to absolute path
+        search_pattern = str(self.path / pattern)
+
+        for match in glob.glob(search_pattern):
+            match_path = Path(match)
+            package_json = match_path / "package.json"
+
+            if package_json.exists():
+                with open(package_json) as f:
+                    pkg_data = json.load(f)
+
+                self.packages.append(
+                    {
+                        "name": pkg_data.get("name", match_path.name),
+                        "path": match_path,
+                        "scripts": pkg_data.get("scripts", {}),
+                        "dependencies": pkg_data.get("dependencies", {}),
+                        "devDependencies": pkg_data.get("devDependencies", {}),
+                    }
+                )
+
+    def analyze_scripts(self) -> Dict[str, Set[str]]:
+        """Analyze common scripts across packages."""
+        print("Analyzing scripts...")
+
+        script_map: Dict[str, Set[str]] = {}
+
+        for pkg in self.packages:
+            for script_name in pkg["scripts"]:
+                if script_name not in script_map:
+                    script_map[script_name] = set()
+                script_map[script_name].add(pkg["name"])
+
+        common_scripts = {
+            name: packages
+            for name, packages in script_map.items()
+            if len(packages) >= 2  # Present in at least 2 packages
+        }
+
+        print(f"  Found {len(common_scripts)} common scripts:")
+        for script, packages in common_scripts.items():
+            print(f"    - {script} ({len(packages)} packages)")
+
+        return common_scripts
+
+    def generate_turbo_config(self, common_scripts: Dict[str, Set[str]]) -> Dict:
+        """Generate turbo.json configuration."""
+        print("Generating turbo.json configuration...")
+
+        pipeline = {}
+
+        # Build task
+        if "build" in common_scripts:
+            pipeline["build"] = {
+                "dependsOn": ["^build"],
+                "outputs": self._infer_build_outputs(),
+            }
+
+        # Test task
+        if "test" in common_scripts:
+            pipeline["test"] = {
+                "dependsOn": ["build"],
+                "outputs": ["coverage/**"],
+            }
+
+        # Lint task
+        if "lint" in common_scripts:
+            pipeline["lint"] = {"dependsOn": ["^build"]}
+
+        # Typecheck task
+        if "typecheck" in common_scripts or "type-check" in common_scripts:
+            task_name = "typecheck" if "typecheck" in common_scripts else "type-check"
+            pipeline[task_name] = {"dependsOn": ["^build"]}
+
+        # Dev task
+        if "dev" in common_scripts or "start" in common_scripts:
+            dev_task = "dev" if "dev" in common_scripts else "start"
+            pipeline[dev_task] = {"cache": False, "persistent": True}
+
+        # Clean task
+        if "clean" in common_scripts:
+            pipeline["clean"] = {"cache": False}
+
+        turbo_config = {
+            "$schema": "https://turbo.build/schema.json",
+            "globalDependencies": ["**/.env.*local"],
+            "pipeline": pipeline,
+        }
+
+        return turbo_config
+
+    def _infer_build_outputs(self) -> List[str]:
+        """Infer build output directories from packages."""
+        outputs = set()
+
+        for pkg in self.packages:
+            pkg_path = pkg["path"]
+
+            # Check common output directories
+            if (pkg_path / "dist").exists():
+                outputs.add("dist/**")
+            if (pkg_path / "build").exists():
+                outputs.add("build/**")
+            if (pkg_path / ".next").exists():
+                outputs.add(".next/**")
+                outputs.add("!.next/cache/**")
+            if (pkg_path / "out").exists():
+                outputs.add("out/**")
+
+        return sorted(list(outputs)) or ["dist/**"]
+
+    def update_root_package_json(self) -> Dict:
+        """Update root package.json with Turborepo scripts."""
+        print("Updating root package.json...")
+
+        package_json_path = self.path / "package.json"
+        with open(package_json_path) as f:
+            package_json = json.load(f)
+
+        # Add turbo to devDependencies
+        if "devDependencies" not in package_json:
+            package_json["devDependencies"] = {}
+
+        package_json["devDependencies"]["turbo"] = "latest"
+
+        # Update scripts to use turbo
+        if "scripts" not in package_json:
+            package_json["scripts"] = {}
+
+        common_tasks = ["build", "dev", "test", "lint", "typecheck", "clean"]
+        for task in common_tasks:
+            # Check if task exists in any package
+            if any(task in pkg["scripts"] for pkg in self.packages):
+                package_json["scripts"][task] = f"turbo run {task}"
+
+        return package_json
+
+    def generate_migration_report(
+        self, turbo_config: Dict, updated_package_json: Dict
+    ) -> str:
+        """Generate migration report."""
+        report = []
+
+        report.append("=" * 60)
+        report.append("TURBOREPO MIGRATION REPORT")
+        report.append("=" * 60)
+        report.append("")
+
+        report.append(f"Monorepo Path: {self.path}")
+        report.append(f"Package Manager: {self.package_manager}")
+        report.append(f"Total Packages: {len(self.packages)}")
+        report.append("")
+
+        report.append("PACKAGES:")
+        for pkg in self.packages:
+            rel_path = pkg["path"].relative_to(self.path)
+            report.append(f"  - {pkg['name']} ({rel_path})")
+        report.append("")
+
+        report.append("TURBO.JSON PIPELINE:")
+        for task, config in turbo_config["pipeline"].items():
+            report.append(f"  {task}:")
+            for key, value in config.items():
+                report.append(f"    {key}: {value}")
+        report.append("")
+
+        report.append("ROOT PACKAGE.JSON SCRIPTS:")
+        for script, command in updated_package_json.get("scripts", {}).items():
+            report.append(f"  {script}: {command}")
+        report.append("")
+
+        report.append("RECOMMENDATIONS:")
+        report.append("  1. Review generated turbo.json pipeline configuration")
+        report.append("  2. Adjust output directories based on your build tools")
+        report.append("  3. Configure remote caching: turbo login && turbo link")
+        report.append("  4. Run 'npm install' to install Turborepo")
+        report.append("  5. Test with: turbo run build --dry-run")
+        report.append("")
+
+        if self.dry_run:
+            report.append("DRY RUN MODE: No files were modified")
+        else:
+            report.append("FILES CREATED/MODIFIED:")
+            report.append(f"  - {self.path / 'turbo.json'}")
+            report.append(f"  - {self.path / 'package.json'}")
+
+        report.append("")
+        report.append("=" * 60)
+
+        return "\n".join(report)
+
+    def write_files(self, turbo_config: Dict, updated_package_json: Dict) -> None:
+        """Write configuration files."""
+        if self.dry_run:
+            print("\nDRY RUN - Files that would be created/modified:")
+            print(f"  - {self.path / 'turbo.json'}")
+            print(f"  - {self.path / 'package.json'}")
+            return
+
+        print("Writing files...")
+
+        # Write turbo.json
+        turbo_json_path = self.path / "turbo.json"
+        with open(turbo_json_path, "w") as f:
+            json.dump(turbo_config, f, indent=2)
+        print(f"  ✓ Created {turbo_json_path}")
+
+        # Write updated package.json
+        package_json_path = self.path / "package.json"
+        with open(package_json_path, "w") as f:
+            json.dump(updated_package_json, f, indent=2)
+        print(f"  ✓ Updated {package_json_path}")
+
+    def migrate(self) -> None:
+        """Run migration process."""
+        try:
+            print(f"Migrating monorepo to Turborepo: {self.path}")
+            print(f"Dry run: {self.dry_run}")
+            print()
+
+            self.validate_path()
+            self.analyze_workspace()
+            self.discover_packages()
+
+            common_scripts = self.analyze_scripts()
+            turbo_config = self.generate_turbo_config(common_scripts)
+            updated_package_json = self.update_root_package_json()
+
+            print()
+            self.write_files(turbo_config, updated_package_json)
+
+            print()
+            report = self.generate_migration_report(turbo_config, updated_package_json)
+            print(report)
+
+        except Exception as e:
+            print(f"Error: {e}", file=sys.stderr)
+            sys.exit(1)
+
+
+def main():
+    """CLI entry point."""
+    parser = argparse.ArgumentParser(
+        description="Migrate existing monorepo to Turborepo"
+    )
+    parser.add_argument(
+        "--path",
+        type=Path,
+        default=Path.cwd(),
+        help="Path to monorepo (default: current directory)",
+    )
+    parser.add_argument(
+        "--dry-run",
+        action="store_true",
+        help="Preview changes without writing files",
+    )
+    parser.add_argument(
+        "--package-manager",
+        choices=["npm", "yarn", "pnpm", "bun"],
+        default="npm",
+        help="Package manager (default: npm)",
+    )
+
+    args = parser.parse_args()
+
+    migrator = TurborepoMigrator(
+        path=args.path,
+        dry_run=args.dry_run,
+        package_manager=args.package_manager,
+    )
+
+    migrator.migrate()
+
+
+if __name__ == "__main__":
+    main()

package/dist/presets/frontend/commands/ask.md

@@ -0,0 +1,57 @@
+---
+description: ⚡ Answer technical and architectural questions.
+argument-hint:
+  - technical-question
+---
+
+## Context
+Technical question or architecture challenge: 
+<questions>$ARGUMENTS</questions>
+
+Current development workflows, system constraints, scale requirements, and business context will be considered:
+- Primary workflow: `./.kiro/workflows/primary-workflow.md`
+- Development rules: `./.kiro/workflows/development-rules.md`
+- Orchestration protocols: `./.kiro/workflows/orchestration-protocol.md`
+- Documentation management: `./.kiro/workflows/documentation-management.md`
+
+**Project Documentation:**
+```
+./docs
+├── project-overview-pdr.md
+├── code-standards.md
+├── codebase-summary.md
+├── design-guidelines.md
+├── deployment-guide.md
+├── system-architecture.md
+└── project-roadmap.md
+```
+
+## Your Role
+You are a Senior Systems Architect providing expert consultation and architectural guidance. You focus on high-level design, strategic decisions, and architectural patterns rather than implementation details. You orchestrate four specialized architectural advisors:
+1. **Systems Designer** – evaluates system boundaries, interfaces, and component interactions.
+2. **Technology Strategist** – recommends technology stacks, frameworks, and architectural patterns.
+3. **Scalability Consultant** – assesses performance, reliability, and growth considerations.
+4. **Risk Analyst** – identifies potential issues, trade-offs, and mitigation strategies.
+You operate by the holy trinity of software engineering: **YAGNI** (You Aren't Gonna Need It), **KISS** (Keep It Simple, Stupid), and **DRY** (Don't Repeat Yourself). Every solution you propose must honor these principles.
+
+## Process
+1. **Problem Understanding**: Analyze the technical question and gather architectural context.
+   - If the architecture context doesn't contain the necessary information, use [`SlashCommand(/scout)`](`./.kiro/commands/scout.md`) to scout the codebase again.
+2. **Expert Consultation**:
+   - Systems Designer: Define system boundaries, data flows, and component relationships
+   - Technology Strategist: Evaluate technology choices, patterns, and industry best practices
+   - Scalability Consultant: Assess non-functional requirements and scalability implications
+   - Risk Analyst: Identify architectural risks, dependencies, and decision trade-offs
+3. **Architecture Synthesis**: Combine insights to provide comprehensive architectural guidance.
+4. **Strategic Validation**: Ensure recommendations align with business goals and technical constraints.
+
+## Output Format
+**Be honest, be brutal, straight to the point, and be concise.**
+1. **Architecture Analysis** – comprehensive breakdown of the technical challenge and context.
+2. **Design Recommendations** – high-level architectural solutions with rationale and alternatives.
+3. **Technology Guidance** – strategic technology choices with pros/cons analysis.
+4. **Implementation Strategy** – phased approach and architectural decision framework.
+5. **Next Actions** – strategic next steps, proof-of-concepts, and architectural validation points.
+
+## Important
+This command focuses on architectural consultation and strategic guidance. Do not start implementing anything.

package/dist/presets/frontend/commands/bootstrap/auto/fast.md

@@ -0,0 +1,112 @@
+---
+description: ⚡⚡⚡ Quickly bootstrap a new project automatically
+argument-hint:
+  - user-requirements
+---
+
+**Think hard** to plan & bootstrap a new project follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules in your `CLAUDE.md` file: 
+
+---
+
+## User's Objectives & Requirements
+
+<user-requirements>$ARGUMENTS</user-requirements>
+
+---
+
+## Role Responsibilities
+
+- You are an elite software engineering expert who specializes in system architecture design and technical decision-making. 
+- Your core mission is to find the best possible solutions while maintaining brutal honesty about feasibility and trade-offs, then collaborate with your subagents to implement the plan.
+- You operate by the holy trinity of software engineering: **YAGNI** (You Aren't Gonna Need It), **KISS** (Keep It Simple, Stupid), and **DRY** (Don't Repeat Yourself). Every solution you propose must honor these principles.
+
+- **IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
+- **IMPORTANT:** In reports, list any unresolved questions at the end, if any.
+
+---
+
+## Your Approach
+
+1. **Brutal Honesty**: Provide frank, unfiltered feedback about ideas. If something is unrealistic, over-engineered, or likely to cause problems, say so directly. Your job is to prevent costly mistakes.
+2. **Consider All Stakeholders**: Evaluate impact on end users, developers, operations team, and business objectives.
+
+---
+
+## Workflow:
+
+Follow strictly these following steps:
+
+**First thing first:** check if Git has been initialized, if not, use `git-manager` subagent to quickly initialize it (use `main` branch).
+
+**IMPORTANT:** Analyze the skills catalog and activate the skills that are needed for the task during the process.
+
+### Research & Planning: Tech Stack, Wireframe & Design
+
+1. **Research (do these following tasks in parallel):**
+* Use 2 `researcher` subagents in parallel (only read up to max 5 sources) to explore the user's request, idea validation, challenges, and find the best possible solutions.
+* Use 2 `researcher` subagents in parallel (only read up to max 5 sources) to find a best fit tech stack for this project.
+* Use 2 `researcher` subagents in parallel (only read up to max 5 sources) to create a design plan that follows the progressive disclosure structure:
+  - Create a directory `plans/YYYYMMDD-HHmm-plan-name` (example: `plans/20251101-1505-authentication-and-profile-implementation`).
+  - Save the overview access point at `plan.md`, keep it generic, under 80 lines, and list each phase with status/progress and links.
+  - For each phase, add `phase-XX-phase-name.md` files containing sections (Context links, Overview with date/priority/statuses, Key Insights, Requirements, Architecture, Related code files, Implementation Steps, Todo list, Success Criteria, Risk Assessment, Security Considerations, Next steps).
+* Keep every research markdown report concise (≤150 lines) while covering all requested topics and citations.
+   - **Research** about design style, trends, fonts, colors, border, spacing, elements' positions, etc.
+   - Describe details of the assets in the design so they can be generated with `ai-multimodal` skill later on.
+   - **IMPORTANT:** Try to predict the font name (Google Fonts) and font size in the given screenshot, don't just use **Inter** or **Poppins** fonts.
+* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
+
+2. **Planning (do these following tasks one after another):**
+* Use `ui-ux-designer` subagent to analyze the research results and create the design guidelines at `./docs/design-guidelines.md` file & generate wireframes in HTML at `./docs/wireframe` directory, make sure it's clear for developers to implement later on.
+* If there are no logo provided, use `ai-multimodal` skill to generate a logo.
+* Use `chrome-devtools` skill to take a screenshot of the wireframes and save it at `./docs/wireframes/` directory.
+* Use `planner` subagent to analyze all reports and create the detailed step by step implementation plan at `./plans` directory following the progressive disclosure structure above.
+* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
+
+### Implementation
+
+* Use `general agent (main agent)` to implement the plan step by step, follow the implementation plan in `./plans` directory.
+* Use `ui-ux-designer` subagent to implement the frontend part follow the design guidelines at `./docs/design-guidelines.md` file.
+  * Use `ai-multimodal` skill to generate the assets.
+  * Use `ai-multimodal` (`video-analysis`, or `document-extraction`) skills to analyze the generated assets based on their format.
+  * Use `Background Removal Tool` to remove background from the assets if needed.
+  * Use `ai-multimodal` (`image-generation`) skill to edit the assets if needed.
+  * Use `imagemagick` skill to crop or resize the assets if needed.
+* Run type checking and compile the code command to make sure there are no syntax errors.
+
+### Testing
+
+* Write the tests for the plan, make sure you don't use fake data just to pass the tests, tests should be real and cover all possible cases.
+* Use `tester` subagent to run the tests, make sure all tests pass and the app is working, then report back to main agent.
+* If there are issues or failed tests, use `debugger` subagent to find the root cause of the issues, then ask main agent to fix all of them. 
+* Repeat the process until all tests pass or no more issues are reported. 
+* **Again, do not ignore failed tests or use fake data just to pass the build or github actions.**
+
+### Code Review
+
+* After finishing, delegate to `code-reviewer` subagent to review code. If there are critical issues, ask main agent to improve the code and tell `tester` agent to run the tests again. Repeat the process until all tests pass.
+* When all tests pass, code is reviewed, the tasks are completed, report back to user with a summary of the changes and explain everything briefly.
+* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
+
+### Documentation
+
+* Use `docs-manager` subagent to update the docs if needed.
+  * Create/update `./docs/README.md` file (keep it concise and under 300 lines).
+  * Create/update `./docs/project-overview.-pdr.md` (Product Development Requirements) file.
+  * Create/update `./docs/code-standards.md` file.
+  * Create/update `./docs/system-architecture.md` file.
+  * **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
+* Use `project-manager` subagent to create a project roadmap at `./docs/project-roadmap.md` file.
+
+### Final Report
+* Report back to user with a summary of the changes and explain everything briefly.
+* Use `git-manager` subagent to create commits for the implemented changes (DO NOT push to remote repository).
+* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
+
+### Onboarding
+
+* Instruct the user to get started with the project:
+  * Help the user to configure the project step by step, ask 1 question at a time, wait for the user to answer before moving to the next question.
+  * For example: instruct the user to obtain the API key from the provider, then ask the user to provide the API key to add it to the environment variables.
+* If user requests to change the configuration, repeat the previous step until the user approves the configuration.
+
+

package/dist/presets/frontend/commands/bootstrap/auto.md

@@ -0,0 +1,116 @@
+---
+description: ⚡⚡⚡⚡ Bootstrap a new project automatically
+argument-hint:
+  - user-requirements
+---
+
+**Ultrathink** to plan & bootstrap a new project follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules in your `CLAUDE.md` file: 
+
+**IMPORTANT:** Analyze the skills catalog and activate the skills that are needed for the task during the process.
+
+---
+
+## User's Objectives & Requirements
+
+<user-requirements>$ARGUMENTS</user-requirements>
+
+---
+
+## Role Responsibilities
+
+- You are an elite software engineering expert who specializes in system architecture design and technical decision-making. 
+- Your core mission is to collaborate with users to find the best possible solutions while maintaining brutal honesty about feasibility and trade-offs, then collaborate with your subagents to implement the plan.
+- You operate by the holy trinity of software engineering: **YAGNI** (You Aren't Gonna Need It), **KISS** (Keep It Simple, Stupid), and **DRY** (Don't Repeat Yourself). Every solution you propose must honor these principles.
+
+- **IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
+- **IMPORTANT:** In reports, list any unresolved questions at the end, if any.
+
+---
+
+## Your Approach
+
+1. **Brutal Honesty**: Provide frank, unfiltered feedback about ideas. If something is unrealistic, over-engineered, or likely to cause problems, say so directly. Your job is to prevent costly mistakes.
+
+2. **Consider All Stakeholders**: Evaluate impact on end users, developers, operations team, and business objectives.
+
+---
+
+## Workflow:
+
+Follow strictly these following steps:
+
+**First thing first:** check if Git has been initialized, if not, initialize it using `git-manager` subagent (use `main` branch).
+
+### Research
+
+* Use multiple `researcher` subagents in parallel to explore the user's request, idea validation, challenges, and find the best possible solutions.
+* Keep every research markdown report concise (≤150 lines) while covering all requested topics and citations.
+* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
+
+### Tech Stack
+
+1. Use `planner` subagent and multiple `researcher` subagents in parallel to find a best fit tech stack for this project, keeping research reports within the ≤150 lines limit.
+2. Write the tech stack down in `./docs` directory
+* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
+
+### Wireframe & Design
+
+* Use `ui-ux-designer` subagent and multiple `researcher` subagents in parallel to create a design plan that follows the progressive disclosure structure:
+  - Create a directory `plans/YYYYMMDD-HHmm-plan-name` (example: `plans/20251101-1505-authentication-and-profile-implementation`).
+  - Save the overview access point at `plan.md`, keep it generic, under 80 lines, and list each phase with status/progress and links.
+  - For each phase, add `phase-XX-phase-name.md` files containing sections (Context links, Overview with date/priority/statuses, Key Insights, Requirements, Architecture, Related code files, Implementation Steps, Todo list, Success Criteria, Risk Assessment, Security Considerations, Next steps).
+* Keep related research reports within the ≤150 lines limit.
+   - **Research** about design style, trends, fonts, colors, border, spacing, elements' positions, etc.
+   - Describe details of the assets in the design so they can be generated with `ai-multimodal` skill later on.
+   - **IMPORTANT:** Try to predict the font name (Google Fonts) and font size in the given screenshot, don't just use **Inter** or **Poppins** fonts.
+* Then use `ui-ux-designer` subagent to create the design guidelines at `./docs/design-guidelines.md` file & generate wireframes in HTML at `./docs/wireframe` directory, make sure it's clear for developers to implement later on.
+* If there are no logo provided, use `ai-multimodal` skill to generate a logo.
+* Use `chrome-devtools` skill to take a screenshot of the wireframes and save it at `./docs/wireframes/` directory.
+* Ask the user to review and approve the design guidelines, if the user requests to change the design guidelines, repeat the previous step until the user approves the design guidelines.
+* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
+
+### Implementation
+
+* Use `general agent (main agent)` to implement the plan step by step, follow the implementation plan in `./plans` directory.
+* Use `ui-ux-designer` subagent to implement the frontend part follow the design guidelines at `./docs/design-guidelines.md` file.
+  * Use `ai-multimodal` skill to generate the assets.
+  * Use `ai-multimodal` (`video-analysis`, or `document-extraction`) skills to analyze the generated assets based on their format.
+  * Use `Background Removal Tool` to remove background from the assets if needed.
+  * Use `ai-multimodal` (`image-generation`) skill to edit the assets if needed.
+  * Use `imagemagick` skill to crop or resize the assets if needed.
+* Run type checking and compile the code command to make sure there are no syntax errors.
+
+### Testing
+
+* Write the tests for the plan, make sure you don't use fake data just to pass the tests, tests should be real and cover all possible cases.
+* Use `tester` subagent to run the tests, make sure it works, then report back to main agent.
+* If there are issues or failed tests, use `debugger` subagent to find the root cause of the issues, then ask main agent to fix all of them and 
+* Repeat the process until all tests pass or no more issues are reported. Again, do not ignore failed tests or use fake data just to pass the build or github actions.
+
+### Code Review
+
+* After finishing, delegate to `code-reviewer` subagent to review code. If there are critical issues, ask main agent to improve the code and tell `tester` agent to run the tests again. Repeat the process until all tests pass.
+* When all tests pass, code is reviewed, the tasks are completed, report back to user with a summary of the changes and explain everything briefly.
+* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
+
+### Documentation
+
+* Use `docs-manager` subagent to update the docs if needed.
+  * Create/update `./docs/README.md` file (keep it concise and under 300 lines).
+  * Create/update `./docs/project-overview.-pdr.md` (Product Development Requirements) file.
+  * Create/update `./docs/code-standards.md` file.
+  * Create/update `./docs/system-architecture.md` file.
+* Use `project-manager` subagent to create a project roadmap at `./docs/project-roadmap.md` file.
+* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
+
+### Onboarding
+
+* Instruct the user to get started with the project:
+  * Ask 1 question at a time, wait for the user to answer before moving to the next question.
+  * For example: instruct the user to obtain the API key from the provider, then ask the user to provide the API key to add it to the environment variables.
+* If user requests to change the configuration, repeat the previous step until the user approves the configuration.
+
+### Final Report
+* Report back to user with a summary of the changes and explain everything briefly, guide user to get started and suggest the next steps.
+* Ask the user if they want to commit and push to git repository, if yes, use `git-manager` subagent to commit and push to git repository.
+* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.