├── .python-version ├── .gitignore ├── install.py ├── droidz_installer ├── __main__.py ├── exceptions.py ├── __init__.py ├── payloads │ ├── shared │ │ └── default │ │ │ ├── .gitignore │ │ │ ├── global │ │ │ ├── commenting.md │ │ │ ├── coding-style.md │ │ │ ├── validation.md │ │ │ ├── conventions.md │ │ │ └── tech-stack.md │ │ │ ├── frontend │ │ │ ├── css.md │ │ │ ├── accessibility.md │ │ │ ├── components.md │ │ │ └── responsive.md │ │ │ ├── backend │ │ │ ├── migrations.md │ │ │ ├── queries.md │ │ │ └── models.md │ │ │ ├── config.yml.template │ │ │ └── testing │ │ │ └── test-writing.md │ ├── cursor │ │ └── default │ │ │ └── workflows │ │ │ └── accelerator.md │ ├── cline │ │ └── default │ │ │ └── prompts │ │ │ └── companion.txt │ ├── codex_cli │ │ └── default │ │ │ └── playbooks │ │ │ └── sequential.md │ ├── vscode │ │ └── default │ │ │ └── snippets │ │ │ └── droidz.code-snippets │ ├── claude │ │ └── default │ │ │ ├── commands │ │ │ ├── 3-verify-implementation.md │ │ │ ├── 1-initialize-spec.md │ │ │ ├── 1-determine-tasks.md │ │ │ ├── 2-create-mission.md │ │ │ ├── 3-create-roadmap.md │ │ │ ├── 1-product-concept.md │ │ │ ├── 4-create-tech-stack.md │ │ │ ├── 1-get-spec-requirements.md │ │ │ ├── 2-implement-tasks.md │ │ │ ├── plan-product.md │ │ │ ├── 2-create-tasks-list.md │ │ │ ├── write-spec.md │ │ │ ├── 2-shape-spec.md │ │ │ └── shape-spec.md │ │ │ ├── agents │ │ │ ├── spec-initializer.md │ │ │ ├── README.md │ │ │ ├── spec-verifier.md │ │ │ ├── spec-shaper.md │ │ │ ├── implementer.md │ │ │ ├── implementation-verifier.md │ │ │ ├── backend-specialist.md │ │ │ └── spec-writer.md │ │ │ └── skills │ │ │ ├── changelog-generator │ │ │ └── SKILL.md │ │ │ ├── brand-guidelines │ │ │ └── SKILL.md │ │ │ ├── canvas-design │ │ │ └── SKILL.md │ │ │ ├── content-research-writer │ │ │ └── SKILL.md │ │ │ ├── domain-name-brainstormer │ │ │ └── SKILL.md │ │ │ ├── threat-hunting │ │ │ └── SKILL.md │ │ │ ├── brainstorming │ │ │ └── SKILL.md │ │ │ ├── root-cause-tracing │ │ │ └── SKILL.md │ │ │ ├── invoice-organizer │ │ │ └── SKILL.md │ │ │ ├── competitive-research │ │ │ └── SKILL.md │ │ │ ├── kaizen-continuous-improvement │ │ │ └── SKILL.md │ │ │ ├── artifacts-builder │ │ │ └── SKILL.md │ │ │ ├── document-processing-pdf │ │ │ └── SKILL.md │ │ │ ├── meeting-insights-analyzer │ │ │ └── SKILL.md │ │ │ ├── vercel-deployment │ │ │ └── SKILL.md │ │ │ ├── file-organizer │ │ │ └── SKILL.md │ │ │ ├── typescript-strict │ │ │ └── SKILL.md │ │ │ ├── document-processing-xlsx │ │ │ └── SKILL.md │ │ │ ├── document-processing-docx │ │ │ └── SKILL.md │ │ │ ├── mcp-builder │ │ │ └── SKILL.md │ │ │ ├── convex-realtime │ │ │ └── SKILL.md │ │ │ ├── tailwind-design-system │ │ │ └── SKILL.md │ │ │ ├── shadcn-ui-components │ │ │ └── SKILL.md │ │ │ ├── data-migration │ │ │ └── SKILL.md │ │ │ ├── playwright-automation │ │ │ └── SKILL.md │ │ │ ├── skill-creator │ │ │ └── SKILL.md │ │ │ ├── react-server-actions │ │ │ └── SKILL.md │ │ │ ├── monitoring-observability │ │ │ └── SKILL.md │ │ │ ├── standards-enforcement │ │ │ └── SKILL.md │ │ │ ├── neondb-serverless │ │ │ └── SKILL.md │ │ │ ├── convex-backend │ │ │ └── SKILL.md │ │ │ ├── accessibility-wcag │ │ │ └── SKILL.md │ │ │ └── incident-response │ │ │ └── SKILL.md │ └── droid_cli │ │ └── default │ │ ├── commands │ │ ├── 3-verify-implementation.md │ │ ├── 1-initialize-spec.md │ │ ├── 1-determine-tasks.md │ │ ├── 2-create-mission.md │ │ ├── 3-create-roadmap.md │ │ ├── 1-product-concept.md │ │ ├── 4-create-tech-stack.md │ │ ├── 1-get-spec-requirements.md │ │ ├── 2-implement-tasks.md │ │ ├── plan-product.md │ │ ├── 2-create-tasks-list.md │ │ ├── write-spec.md │ │ ├── 2-shape-spec.md │ │ └── shape-spec.md │ │ ├── droids │ │ ├── spec-initializer.md │ │ ├── README.md │ │ ├── spec-verifier.md │ │ └── implementation-verifier.md │ │ └── skills │ │ ├── changelog-generator │ │ └── SKILL.md │ │ ├── brand-guidelines │ │ └── SKILL.md │ │ ├── canvas-design │ │ └── SKILL.md │ │ ├── content-research-writer │ │ └── SKILL.md │ │ ├── domain-name-brainstormer │ │ └── SKILL.md │ │ ├── threat-hunting │ │ └── SKILL.md │ │ ├── brainstorming │ │ └── SKILL.md │ │ ├── root-cause-tracing │ │ └── SKILL.md │ │ ├── invoice-organizer │ │ └── SKILL.md │ │ ├── competitive-research │ │ └── SKILL.md │ │ ├── kaizen-continuous-improvement │ │ └── SKILL.md │ │ ├── artifacts-builder │ │ └── SKILL.md │ │ ├── document-processing-pdf │ │ └── SKILL.md │ │ ├── meeting-insights-analyzer │ │ └── SKILL.md │ │ ├── vercel-deployment │ │ └── SKILL.md │ │ ├── file-organizer │ │ └── SKILL.md │ │ ├── typescript-strict │ │ └── SKILL.md │ │ ├── document-processing-xlsx │ │ └── SKILL.md │ │ ├── document-processing-docx │ │ └── SKILL.md │ │ ├── mcp-builder │ │ └── SKILL.md │ │ ├── convex-realtime │ │ └── SKILL.md │ │ ├── tailwind-design-system │ │ └── SKILL.md │ │ ├── shadcn-ui-components │ │ └── SKILL.md │ │ ├── data-migration │ │ └── SKILL.md │ │ ├── playwright-automation │ │ └── SKILL.md │ │ ├── skill-creator │ │ └── SKILL.md │ │ ├── react-server-actions │ │ └── SKILL.md │ │ ├── monitoring-observability │ │ └── SKILL.md │ │ ├── standards-enforcement │ │ └── SKILL.md │ │ ├── neondb-serverless │ │ └── SKILL.md │ │ ├── convex-backend │ │ └── SKILL.md │ │ ├── accessibility-wcag │ │ └── SKILL.md │ │ └── incident-response │ │ └── SKILL.md ├── payloads.py └── fs.py ├── pyproject.toml ├── bootstrap.sh └── instructions └── overview.md /.python-version: -------------------------------------------------------------------------------- 1 | 3.11 2 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | .venv/ 2 | __pycache__/ 3 | *.pyc 4 | droidz_installer.egg-info/ 5 | -------------------------------------------------------------------------------- /install.py: -------------------------------------------------------------------------------- 1 | """Entry point for the Droidz installer CLI.""" 2 | 3 | from droidz_installer.cli import main 4 | 5 | if __name__ == "__main__": 6 | main() 7 | -------------------------------------------------------------------------------- /droidz_installer/__main__.py: -------------------------------------------------------------------------------- 1 | """Allow execution via python -m droidz_installer.""" 2 | 3 | from .cli import main 4 | 5 | if __name__ == "__main__": 6 | raise SystemExit(main()) 7 | -------------------------------------------------------------------------------- /droidz_installer/exceptions.py: -------------------------------------------------------------------------------- 1 | """Custom exception types for the Droidz installer.""" 2 | 3 | 4 | class InstallerError(Exception): 5 | """Raised when the installer encounters a recoverable error.""" 6 | 7 | 8 | __all__ = ["InstallerError"] 9 | -------------------------------------------------------------------------------- /droidz_installer/__init__.py: -------------------------------------------------------------------------------- 1 | """Droidz installer package.""" 2 | 3 | from .core import InstallOptions, install, list_platforms 4 | from .exceptions import InstallerError 5 | 6 | __all__ = ["InstallOptions", "InstallerError", "install", "list_platforms"] 7 | 8 | __version__ = "4.13.0" 9 | -------------------------------------------------------------------------------- /droidz_installer/payloads/shared/default/.gitignore: -------------------------------------------------------------------------------- 1 | # Droidz - Ignore sensitive configuration 2 | config.yml 3 | 4 | # Ignore spec-specific generated files 5 | specs/*/implementation/prompts/ 6 | specs/*/implementation/run-parallel.sh 7 | specs/*/implementation/*.log 8 | specs/*/verifications/ 9 | -------------------------------------------------------------------------------- /droidz_installer/payloads/cursor/default/workflows/accelerator.md: -------------------------------------------------------------------------------- 1 | # Cursor Accelerator Workflow 2 | 3 | 1. Load `.cursor/workflows/accelerator.md` in the command palette. 4 | 2. Gather repo context by reading `instructions/overview.md`. 5 | 3. Apply the Validation Gate: run ruff + pytest before summarizing. 6 | -------------------------------------------------------------------------------- /droidz_installer/payloads/cline/default/prompts/companion.txt: -------------------------------------------------------------------------------- 1 | Cline Companion Prompt 2 | ---------------------- 3 | 4 | - Role: Spec-first navigator for Droidz instructions. 5 | - Steps: 6 | 1. Load `instructions/overview.md`. 7 | 2. Ask which platform is active. 8 | 3. Mirror the Validation Gate requirements. 9 | -------------------------------------------------------------------------------- /droidz_installer/payloads/codex_cli/default/playbooks/sequential.md: -------------------------------------------------------------------------------- 1 | # Codex CLI Sequential Playbook 2 | 3 | 1. `/prompts:init` – load instructions + validation summary. 4 | 2. `/prompts:implement` – execute each task, pausing for `/prompts:validate` checkpoints. 5 | 3. `/prompts:handoff` – provide summary + validator output paths. 6 | -------------------------------------------------------------------------------- /droidz_installer/payloads/vscode/default/snippets/droidz.code-snippets: -------------------------------------------------------------------------------- 1 | { 2 | "Droidz Validation Gate": { 3 | "prefix": "droidz-validate", 4 | "body": [ 5 | "# Droidz Validation Gate", 6 | "ruff check .", 7 | "pytest" 8 | ], 9 | "description": "Run the mandatory ruff+pytest gate before summarizing work." 10 | } 11 | } 12 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/commands/3-verify-implementation.md: -------------------------------------------------------------------------------- 1 | Now that we've implemented all tasks in tasks.md, we must run final verifications and produce a verification report using the following MULTI-PHASE workflow: 2 | 3 | ## Workflow 4 | 5 | ### Step 1: Ensure tasks.md has been updated 6 | 7 | ### Step 2: Update roadmap (if applicable) 8 | 9 | ### Step 3: Run entire tests suite 10 | 11 | ### Step 4: Create final verification report 12 | 13 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/commands/3-verify-implementation.md: -------------------------------------------------------------------------------- 1 | Now that we've implemented all tasks in tasks.md, we must run final verifications and produce a verification report using the following MULTI-PHASE workflow: 2 | 3 | ## Workflow 4 | 5 | ### Step 1: Ensure tasks.md has been updated 6 | 7 | ### Step 2: Update roadmap (if applicable) 8 | 9 | ### Step 3: Run entire tests suite 10 | 11 | ### Step 4: Create final verification report 12 | 13 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/commands/1-initialize-spec.md: -------------------------------------------------------------------------------- 1 | The FIRST STEP is to initialize the spec by following these instructions: 2 | 3 | ## Display confirmation and next step 4 | 5 | Once you've initialized the spec folder, output the following message (replace `[this-spec]` with the folder name for this spec) 6 | 7 | ``` 8 | ✅ I have initialized the spec folder at `droidz/specs/[this-spec]`. 9 | 10 | NEXT STEP 👉 Run the command, 2-research-spec.md 11 | ``` 12 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/commands/1-initialize-spec.md: -------------------------------------------------------------------------------- 1 | The FIRST STEP is to initialize the spec by following these instructions: 2 | 3 | ## Display confirmation and next step 4 | 5 | Once you've initialized the spec folder, output the following message (replace `[this-spec]` with the folder name for this spec) 6 | 7 | ``` 8 | ✅ I have initialized the spec folder at `droidz/specs/[this-spec]`. 9 | 10 | NEXT STEP 👉 Run the command, 2-research-spec.md 11 | ``` 12 | -------------------------------------------------------------------------------- /droidz_installer/payloads/shared/default/global/commenting.md: -------------------------------------------------------------------------------- 1 | ## Code commenting best practices 2 | 3 | - **Self-Documenting Code**: Write code that explains itself through clear structure and naming 4 | - **Minimal, helpful comments**: Add concise, minimal comments to explain large sections of code logic. 5 | - **Don't comment changes or fixes**: Do not leave code comments that speak to recent or temporary changes or fixes. Comments should be evergreen informational texts that are relevant far into the future. 6 | -------------------------------------------------------------------------------- /pyproject.toml: -------------------------------------------------------------------------------- 1 | [build-system] 2 | requires = ["setuptools>=68"] 3 | build-backend = "setuptools.build_meta" 4 | 5 | [project] 6 | name = "droidz-installer" 7 | version = "4.12.0" 8 | description = "Instruction-only multi-platform installer for Droidz" 9 | readme = "README.md" 10 | requires-python = ">=3.11" 11 | dependencies = [] 12 | 13 | [tool.setuptools.packages.find] 14 | include = ["droidz_installer"] 15 | 16 | [project.scripts] 17 | droidz-install = "droidz_installer.cli:main" 18 | 19 | [tool.pytest.ini_options] 20 | testpaths = ["tests"] 21 | addopts = "-q" 22 | 23 | [tool.ruff] 24 | target-version = "py311" 25 | line-length = 100 26 | 27 | [tool.ruff.lint] 28 | select = ["E", "F", "I"] 29 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/commands/1-determine-tasks.md: -------------------------------------------------------------------------------- 1 | First, check if the user has already provided instructions about which task group(s) to implement. 2 | 3 | **If the user HAS provided instructions:** Proceed to PHASE 2 to delegate implementation of those specified task group(s) to the **implementer** subagent. 4 | 5 | **If the user has NOT provided instructions:** 6 | 7 | Read `droidz/specs/[this-spec]/tasks.md` to review the available task groups, then output the following message to the user and WAIT for their response: 8 | 9 | ``` 10 | Should we proceed with implementation of all task groups in tasks.md? 11 | 12 | If not, then please specify which task(s) to implement. 13 | ``` 14 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/commands/1-determine-tasks.md: -------------------------------------------------------------------------------- 1 | First, check if the user has already provided instructions about which task group(s) to implement. 2 | 3 | **If the user HAS provided instructions:** Proceed to PHASE 2 to delegate implementation of those specified task group(s) to the **implementer** subagent. 4 | 5 | **If the user has NOT provided instructions:** 6 | 7 | Read `droidz/specs/[this-spec]/tasks.md` to review the available task groups, then output the following message to the user and WAIT for their response: 8 | 9 | ``` 10 | Should we proceed with implementation of all task groups in tasks.md? 11 | 12 | If not, then please specify which task(s) to implement. 13 | ``` 14 | -------------------------------------------------------------------------------- /droidz_installer/payloads/shared/default/frontend/css.md: -------------------------------------------------------------------------------- 1 | ## CSS best practices 2 | 3 | - **Consistent Methodology**: Apply and stick to the project's consistent CSS methodology (Tailwind, BEM, utility classes, CSS modules, etc.) across the entire project 4 | - **Avoid Overriding Framework Styles**: Work with your framework's patterns rather than fighting against them with excessive overrides 5 | - **Maintain Design System**: Establish and document design tokens (colors, spacing, typography) for consistency 6 | - **Minimize Custom CSS**: Leverage framework utilities and components to reduce custom CSS maintenance burden 7 | - **Performance Considerations**: Optimize for production with CSS purging/tree-shaking to remove unused styles 8 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/commands/2-create-mission.md: -------------------------------------------------------------------------------- 1 | Now that you've gathered information about this product, use that info to create the mission document in `droidz/product/mission.md` by following these instructions: 2 | 3 | ## Display confirmation and next step 4 | 5 | Once you've created mission.md, output the following message: 6 | 7 | ``` 8 | ✅ I have documented the product mission at `droidz/product/mission.md`. 9 | 10 | Review it to ensure it matches your vision and strategic goals for this product. 11 | 12 | NEXT STEP 👉 Run the command, `3-create-roadmap.md` 13 | ``` 14 | 15 | ## User Standards & Preferences Compliance 16 | 17 | IMPORTANT: Ensure the product mission is ALIGNED and DOES NOT CONFLICT with the user's preferences and standards as detailed in the following files: 18 | 19 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/commands/3-create-roadmap.md: -------------------------------------------------------------------------------- 1 | Now that you've created this product's mission.md, use that to guide your creation of the roadmap in `droidz/product/roadmap.md` by following these instructions: 2 | 3 | ## Display confirmation and next step 4 | 5 | Once you've created roadmap.md, output the following message: 6 | 7 | ``` 8 | ✅ I have documented the product roadmap at `droidz/product/roadmap.md`. 9 | 10 | Review it to ensure it aligns with how you see this product roadmap going forward. 11 | 12 | NEXT STEP 👉 Run the command, `4-create-tech-stack.md` 13 | ``` 14 | 15 | ## User Standards & Preferences Compliance 16 | 17 | IMPORTANT: Ensure the product roadmap is ALIGNED and DOES NOT CONFLICT with the user's preferences and standards as detailed in the following files: 18 | 19 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/commands/2-create-mission.md: -------------------------------------------------------------------------------- 1 | Now that you've gathered information about this product, use that info to create the mission document in `droidz/product/mission.md` by following these instructions: 2 | 3 | ## Display confirmation and next step 4 | 5 | Once you've created mission.md, output the following message: 6 | 7 | ``` 8 | ✅ I have documented the product mission at `droidz/product/mission.md`. 9 | 10 | Review it to ensure it matches your vision and strategic goals for this product. 11 | 12 | NEXT STEP 👉 Run the command, `3-create-roadmap.md` 13 | ``` 14 | 15 | ## User Standards & Preferences Compliance 16 | 17 | IMPORTANT: Ensure the product mission is ALIGNED and DOES NOT CONFLICT with the user's preferences and standards as detailed in the following files: 18 | 19 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/commands/3-create-roadmap.md: -------------------------------------------------------------------------------- 1 | Now that you've created this product's mission.md, use that to guide your creation of the roadmap in `droidz/product/roadmap.md` by following these instructions: 2 | 3 | ## Display confirmation and next step 4 | 5 | Once you've created roadmap.md, output the following message: 6 | 7 | ``` 8 | ✅ I have documented the product roadmap at `droidz/product/roadmap.md`. 9 | 10 | Review it to ensure it aligns with how you see this product roadmap going forward. 11 | 12 | NEXT STEP 👉 Run the command, `4-create-tech-stack.md` 13 | ``` 14 | 15 | ## User Standards & Preferences Compliance 16 | 17 | IMPORTANT: Ensure the product roadmap is ALIGNED and DOES NOT CONFLICT with the user's preferences and standards as detailed in the following files: 18 | 19 | -------------------------------------------------------------------------------- /droidz_installer/payloads.py: -------------------------------------------------------------------------------- 1 | """Utilities for resolving installer payloads.""" 2 | 3 | from __future__ import annotations 4 | 5 | from pathlib import Path 6 | from typing import Iterable 7 | 8 | from .exceptions import InstallerError 9 | 10 | 11 | def resolve_payload_dir(base: Path, payload_name: str, profile: str) -> Path: 12 | """Return the directory containing instructions for the target platform/profile.""" 13 | 14 | candidates: Iterable[Path] = ( 15 | (base / payload_name / profile), 16 | (base / payload_name), 17 | ) 18 | 19 | for candidate in candidates: 20 | if candidate.exists() and candidate.is_dir(): 21 | return candidate 22 | 23 | raise InstallerError( 24 | f"No payload found for '{payload_name}' (profile '{profile}') under '{base}'." 25 | ) 26 | 27 | 28 | __all__ = ["resolve_payload_dir"] 29 | -------------------------------------------------------------------------------- /droidz_installer/payloads/shared/default/backend/migrations.md: -------------------------------------------------------------------------------- 1 | ## Database migration best practices 2 | 3 | - **Reversible Migrations**: Always implement rollback/down methods to enable safe migration reversals 4 | - **Small, Focused Changes**: Keep each migration focused on a single logical change for clarity and easier troubleshooting 5 | - **Zero-Downtime Deployments**: Consider deployment order and backwards compatibility for high-availability systems 6 | - **Separate Schema and Data**: Keep schema changes separate from data migrations for better rollback safety 7 | - **Index Management**: Create indexes on large tables carefully, using concurrent options when available to avoid locks 8 | - **Naming Conventions**: Use clear, descriptive names that indicate what the migration does 9 | - **Version Control**: Always commit migrations to version control and never modify existing migrations after deployment 10 | -------------------------------------------------------------------------------- /droidz_installer/payloads/shared/default/backend/queries.md: -------------------------------------------------------------------------------- 1 | ## Database query best practices 2 | 3 | - **Prevent SQL Injection**: Always use parameterized queries or ORM methods; never interpolate user input into SQL strings 4 | - **Avoid N+1 Queries**: Use eager loading or joins to fetch related data in a single query instead of multiple queries 5 | - **Select Only Needed Data**: Request only the columns you need rather than using SELECT * for better performance 6 | - **Index Strategic Columns**: Index columns used in WHERE, JOIN, and ORDER BY clauses for query optimization 7 | - **Use Transactions for Related Changes**: Wrap related database operations in transactions to maintain data consistency 8 | - **Set Query Timeouts**: Implement timeouts to prevent runaway queries from impacting system performance 9 | - **Cache Expensive Queries**: Cache results of complex or frequently-run queries when appropriate 10 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/commands/1-product-concept.md: -------------------------------------------------------------------------------- 1 | This begins a multi-step process for planning and documenting the mission and roadmap for the current product. 2 | 3 | The FIRST STEP is to confirm the product details by following these instructions: 4 | 5 | Then WAIT for me to give you specific instructions on how to use the information you've gathered to create the mission and roadmap. 6 | 7 | ## Display confirmation and next step 8 | 9 | Once you've gathered all of the necessary information, output the following message: 10 | 11 | ``` 12 | I have all the info I need to help you plan this product. 13 | 14 | NEXT STEP 👉 Run the command, `2-create-mission.md` 15 | ``` 16 | 17 | ## User Standards & Preferences Compliance 18 | 19 | When planning the product's tech stack, mission statement and roadmap, use the user's standards and preferences for context and baseline assumptions, as documented in these files: 20 | 21 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/commands/1-product-concept.md: -------------------------------------------------------------------------------- 1 | This begins a multi-step process for planning and documenting the mission and roadmap for the current product. 2 | 3 | The FIRST STEP is to confirm the product details by following these instructions: 4 | 5 | Then WAIT for me to give you specific instructions on how to use the information you've gathered to create the mission and roadmap. 6 | 7 | ## Display confirmation and next step 8 | 9 | Once you've gathered all of the necessary information, output the following message: 10 | 11 | ``` 12 | I have all the info I need to help you plan this product. 13 | 14 | NEXT STEP 👉 Run the command, `2-create-mission.md` 15 | ``` 16 | 17 | ## User Standards & Preferences Compliance 18 | 19 | When planning the product's tech stack, mission statement and roadmap, use the user's standards and preferences for context and baseline assumptions, as documented in these files: 20 | 21 | -------------------------------------------------------------------------------- /droidz_installer/payloads/shared/default/config.yml.template: -------------------------------------------------------------------------------- 1 | # Droidz Configuration File 2 | # This file stores sensitive configuration for Droidz workflows 3 | 4 | # Factory AI API Key (for parallel execution with Droid Exec) 5 | # Get your key from: https://app.factory.ai/settings/api-keys 6 | factory_api_key: "" 7 | 8 | # Optional: Default autonomy level for Droid Exec 9 | # Options: low, medium, high 10 | # - low: File edits only 11 | # - medium: File edits + package installs + tests + local git 12 | # - high: Everything including git push and deployments 13 | default_autonomy_level: "medium" 14 | 15 | # Optional: Max parallel executions (1-10) 16 | # Controls how many task groups run simultaneously 17 | max_parallel_executions: 4 18 | 19 | # SECURITY NOTICE: 20 | # - Add this file to .gitignore to avoid committing API keys 21 | # - Never share this file or commit it to version control 22 | # - Rotate your API key if accidentally exposed 23 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/commands/4-create-tech-stack.md: -------------------------------------------------------------------------------- 1 | The final part of our product planning process is to document this product's tech stack in `droidz/product/tech-stack.md`. Follow these instructions to do so: 2 | 3 | ## Display confirmation and next step 4 | 5 | Once you've created tech-stack.md, output the following message: 6 | 7 | ``` 8 | ✅ I have documented the product's tech stack at `droidz/product/tech-stack.md`. 9 | 10 | Review it to ensure all of the tech stack details are correct for this product. 11 | 12 | You're ready to start planning a feature spec! You can do so by running `shape-spec.md` or `write-spec.md`. 13 | ``` 14 | 15 | ## User Standards & Preferences Compliance 16 | 17 | The user may provide information regarding their tech stack, which should take precidence when documenting the product's tech stack. To fill in any gaps, find the user's usual tech stack information as documented in any of these files: 18 | 19 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/commands/4-create-tech-stack.md: -------------------------------------------------------------------------------- 1 | The final part of our product planning process is to document this product's tech stack in `droidz/product/tech-stack.md`. Follow these instructions to do so: 2 | 3 | ## Display confirmation and next step 4 | 5 | Once you've created tech-stack.md, output the following message: 6 | 7 | ``` 8 | ✅ I have documented the product's tech stack at `droidz/product/tech-stack.md`. 9 | 10 | Review it to ensure all of the tech stack details are correct for this product. 11 | 12 | You're ready to start planning a feature spec! You can do so by running `shape-spec.md` or `write-spec.md`. 13 | ``` 14 | 15 | ## User Standards & Preferences Compliance 16 | 17 | The user may provide information regarding their tech stack, which should take precidence when documenting the product's tech stack. To fill in any gaps, find the user's usual tech stack information as documented in any of these files: 18 | 19 | -------------------------------------------------------------------------------- /droidz_installer/payloads/shared/default/backend/models.md: -------------------------------------------------------------------------------- 1 | ## Database model best practices 2 | 3 | - **Clear Naming**: Use singular names for models and plural for tables following your framework's conventions 4 | - **Timestamps**: Include created and updated timestamps on all tables for auditing and debugging 5 | - **Data Integrity**: Use database constraints (NOT NULL, UNIQUE, foreign keys) to enforce data rules at the database level 6 | - **Appropriate Data Types**: Choose data types that match the data's purpose and size requirements 7 | - **Indexes on Foreign Keys**: Index foreign key columns and other frequently queried fields for performance 8 | - **Validation at Multiple Layers**: Implement validation at both model and database levels for defense in depth 9 | - **Relationship Clarity**: Define relationships clearly with appropriate cascade behaviors and naming conventions 10 | - **Avoid Over-Normalization**: Balance normalization with practical query performance needs 11 | -------------------------------------------------------------------------------- /bootstrap.sh: -------------------------------------------------------------------------------- 1 | #!/usr/bin/env bash 2 | 3 | set -euo pipefail 4 | 5 | if ! command -v python3 >/dev/null 2>&1; then 6 | echo "python3 is required" >&2 7 | exit 1 8 | fi 9 | 10 | PY_VERSION=$(python3 -c 'import sys; print(".".join(map(str, sys.version_info[:2])))') 11 | REQUIRED_MAJOR=3 12 | REQUIRED_MINOR=11 13 | PY_MAJOR=${PY_VERSION%%.*} 14 | PY_MINOR=${PY_VERSION#*.} 15 | PY_MINOR=${PY_MINOR%%.*} 16 | 17 | if [ "$PY_MAJOR" -lt "$REQUIRED_MAJOR" ] || { [ "$PY_MAJOR" -eq "$REQUIRED_MAJOR" ] && [ "$PY_MINOR" -lt "$REQUIRED_MINOR" ]; }; then 18 | echo "python3 >= 3.11 is required (detected $PY_VERSION)" >&2 19 | exit 1 20 | fi 21 | 22 | TMP_DIR=$(mktemp -d 2>/dev/null || mktemp -d -t droidz) 23 | cleanup() { 24 | rm -rf "$TMP_DIR" 25 | } 26 | trap cleanup EXIT 27 | 28 | ARCHIVE_URL="https://github.com/korallis/Droidz/archive/refs/heads/main.tar.gz" 29 | curl -fsSL "$ARCHIVE_URL" | tar -xz -C "$TMP_DIR" 30 | REPO_DIR="$TMP_DIR/Droidz-main" 31 | 32 | python3 "$REPO_DIR/install.py" "$@" 33 | -------------------------------------------------------------------------------- /droidz_installer/payloads/shared/default/frontend/accessibility.md: -------------------------------------------------------------------------------- 1 | ## UI accessibility best practices 2 | 3 | - **Semantic HTML**: Use appropriate HTML elements (nav, main, button, etc.) that convey meaning to assistive technologies 4 | - **Keyboard Navigation**: Ensure all interactive elements are accessible via keyboard with visible focus indicators 5 | - **Color Contrast**: Maintain sufficient contrast ratios (4.5:1 for normal text) and don't rely solely on color to convey information 6 | - **Alternative Text**: Provide descriptive alt text for images and meaningful labels for all form inputs 7 | - **Screen Reader Testing**: Test and verify that all views are accessible on screen reading devices. 8 | - **ARIA When Needed**: Use ARIA attributes to enhance complex components when semantic HTML isn't sufficient 9 | - **Logical Heading Structure**: Use heading levels (h1-h6) in proper order to create a clear document outline 10 | - **Focus Management**: Manage focus appropriately in dynamic content, modals, and single-page applications 11 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/commands/1-get-spec-requirements.md: -------------------------------------------------------------------------------- 1 | The FIRST STEP is to make sure you have ONE OR BOTH of these files to inform your tasks breakdown: 2 | - `droidz/specs/[this-spec]/spec.md` 3 | - `droidz/specs/[this-spec]/planning/requirements.md` 4 | 5 | IF you don't have ONE OR BOTH of those files in your current conversation context, then ask user to provide direction on where to you can find them by outputting the following request then wait for user's response: 6 | 7 | "I'll need a spec.md or requirements.md (or both) in order to build a tasks list. 8 | 9 | Please direct me to where I can find those. If you haven't created them yet, you can run /shape-spec or /write-spec." 10 | 11 | ## Display confirmation and next step 12 | 13 | Once you've confirmed you have the spec and/or requirements, output the following message (replace `[this-spec]` with the folder name for this spec) 14 | 15 | ``` 16 | ✅ I have the spec and requirements `[spec and requirements path]`. 17 | 18 | NEXT STEP 👉 Run the command, 2-create-tasks-list.md 19 | ``` 20 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/commands/1-get-spec-requirements.md: -------------------------------------------------------------------------------- 1 | The FIRST STEP is to make sure you have ONE OR BOTH of these files to inform your tasks breakdown: 2 | - `droidz/specs/[this-spec]/spec.md` 3 | - `droidz/specs/[this-spec]/planning/requirements.md` 4 | 5 | IF you don't have ONE OR BOTH of those files in your current conversation context, then ask user to provide direction on where to you can find them by outputting the following request then wait for user's response: 6 | 7 | "I'll need a spec.md or requirements.md (or both) in order to build a tasks list. 8 | 9 | Please direct me to where I can find those. If you haven't created them yet, you can run /shape-spec or /write-spec." 10 | 11 | ## Display confirmation and next step 12 | 13 | Once you've confirmed you have the spec and/or requirements, output the following message (replace `[this-spec]` with the folder name for this spec) 14 | 15 | ``` 16 | ✅ I have the spec and requirements `[spec and requirements path]`. 17 | 18 | NEXT STEP 👉 Run the command, 2-create-tasks-list.md 19 | ``` 20 | -------------------------------------------------------------------------------- /droidz_installer/payloads/shared/default/frontend/components.md: -------------------------------------------------------------------------------- 1 | ## UI component best practices 2 | 3 | - **Single Responsibility**: Each component should have one clear purpose and do it well 4 | - **Reusability**: Design components to be reused across different contexts with configurable props 5 | - **Composability**: Build complex UIs by combining smaller, simpler components rather than monolithic structures 6 | - **Clear Interface**: Define explicit, well-documented props with sensible defaults for ease of use 7 | - **Encapsulation**: Keep internal implementation details private and expose only necessary APIs 8 | - **Consistent Naming**: Use clear, descriptive names that indicate the component's purpose and follow team conventions 9 | - **State Management**: Keep state as local as possible; lift it up only when needed by multiple components 10 | - **Minimal Props**: Keep the number of props manageable; if a component needs many props, consider composition or splitting it 11 | - **Documentation**: Document component usage, props, and provide examples for easier adoption by team members 12 | -------------------------------------------------------------------------------- /instructions/overview.md: -------------------------------------------------------------------------------- 1 | # Droidz Instruction Stack 2 | 3 | 1. **Two-step flow** 4 | - Install the base instructions into your home directory via `python install.py`. 5 | - Compile per-project workflows by copying the desired payloads into the tool-specific folders. 6 | 2. **Profiles** 7 | - Start with the `default` profile. 8 | - Duplicate payload folders to define custom stacks (e.g., `payloads/claude/nextjs`). 9 | 3. **Validation Gate** 10 | - Every platform enforces the same requirement: run `ruff check .` and `pytest` before reporting success. 11 | 4. **No external dependencies** 12 | - All guidance lives in this repository; update payload text files to evolve your workflow. 13 | 5. **Top platforms** 14 | - Claude Code, Droid CLI, Cursor, Cline, Codex CLI, and VS Code receive curated payloads covering commands, agents, prompts, and snippets. 15 | 6. **Tool-agnostic sub agents** 16 | - Prompts only mention “sub agents” in generic terms so each IDE or CLI can decide whether to fan out to multiple helpers or execute the steps sequentially without breaking the instructions. 17 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/commands/2-implement-tasks.md: -------------------------------------------------------------------------------- 1 | Now that you have the task group(s) to be implemented, proceed with implementation by following these instructions: 2 | 3 | ## Display confirmation and next step 4 | 5 | Display a summary of what was implemented. 6 | 7 | IF all tasks are now marked as done (with `- [x]`) in tasks.md, display this message to user: 8 | 9 | ``` 10 | All tasks have been implemented: `droidz/specs/[this-spec]/tasks.md`. 11 | 12 | NEXT STEP 👉 Run `3-verify-implementation.md` to verify the implementation. 13 | ``` 14 | 15 | IF there are still tasks in tasks.md that have yet to be implemented (marked unfinished with `- [ ]`) then display this message to user: 16 | 17 | ``` 18 | Would you like to proceed with implementation of the remaining tasks in tasks.md? 19 | 20 | If not, please specify which task group(s) to implement next. 21 | ``` 22 | 23 | ## User Standards & Preferences Compliance 24 | 25 | IMPORTANT: Ensure that the tasks list is ALIGNED and DOES NOT CONFLICT with the user's preferences and standards as detailed in the following files: 26 | 27 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/commands/2-implement-tasks.md: -------------------------------------------------------------------------------- 1 | Now that you have the task group(s) to be implemented, proceed with implementation by following these instructions: 2 | 3 | ## Display confirmation and next step 4 | 5 | Display a summary of what was implemented. 6 | 7 | IF all tasks are now marked as done (with `- [x]`) in tasks.md, display this message to user: 8 | 9 | ``` 10 | All tasks have been implemented: `droidz/specs/[this-spec]/tasks.md`. 11 | 12 | NEXT STEP 👉 Run `3-verify-implementation.md` to verify the implementation. 13 | ``` 14 | 15 | IF there are still tasks in tasks.md that have yet to be implemented (marked unfinished with `- [ ]`) then display this message to user: 16 | 17 | ``` 18 | Would you like to proceed with implementation of the remaining tasks in tasks.md? 19 | 20 | If not, please specify which task group(s) to implement next. 21 | ``` 22 | 23 | ## User Standards & Preferences Compliance 24 | 25 | IMPORTANT: Ensure that the tasks list is ALIGNED and DOES NOT CONFLICT with the user's preferences and standards as detailed in the following files: 26 | 27 | -------------------------------------------------------------------------------- /droidz_installer/payloads/shared/default/global/coding-style.md: -------------------------------------------------------------------------------- 1 | ## Coding style best practices 2 | 3 | - **Consistent Naming Conventions**: Establish and follow naming conventions for variables, functions, classes, and files across the codebase 4 | - **Automated Formatting**: Maintain consistent code style (indenting, line breaks, etc.) 5 | - **Meaningful Names**: Choose descriptive names that reveal intent; avoid abbreviations and single-letter variables except in narrow contexts 6 | - **Small, Focused Functions**: Keep functions small and focused on a single task for better readability and testability 7 | - **Consistent Indentation**: Use consistent indentation (spaces or tabs) and configure your editor/linter to enforce it 8 | - **Remove Dead Code**: Delete unused code, commented-out blocks, and imports rather than leaving them as clutter 9 | - **Backward compatibility only when required:** Unless specifically instructed otherwise, assume you do not need to write additional code logic to handle backward compatibility. 10 | - **DRY Principle**: Avoid duplication by extracting common logic into reusable functions or modules 11 | -------------------------------------------------------------------------------- /droidz_installer/payloads/shared/default/global/validation.md: -------------------------------------------------------------------------------- 1 | ## Validation best practices 2 | 3 | - **Validate on Server Side**: Always validate on the server; never trust client-side validation alone for security or data integrity 4 | - **Client-Side for UX**: Use client-side validation to provide immediate user feedback, but duplicate checks server-side 5 | - **Fail Early**: Validate input as early as possible and reject invalid data before processing 6 | - **Specific Error Messages**: Provide clear, field-specific error messages that help users correct their input 7 | - **Allowlists Over Blocklists**: When possible, define what is allowed rather than trying to block everything that's not 8 | - **Type and Format Validation**: Check data types, formats, ranges, and required fields systematically 9 | - **Sanitize Input**: Sanitize user input to prevent injection attacks (SQL, XSS, command injection) 10 | - **Business Rule Validation**: Validate business rules (e.g., sufficient balance, valid dates) at the appropriate application layer 11 | - **Consistent Validation**: Apply validation consistently across all entry points (web forms, API endpoints, background jobs) 12 | -------------------------------------------------------------------------------- /droidz_installer/payloads/shared/default/frontend/responsive.md: -------------------------------------------------------------------------------- 1 | ## Responsive design best practices 2 | 3 | - **Mobile-First Development**: Start with mobile layout and progressively enhance for larger screens 4 | - **Standard Breakpoints**: Consistently use standard breakpoints across the application (e.g., mobile, tablet, desktop) 5 | - **Fluid Layouts**: Use percentage-based widths and flexible containers that adapt to screen size 6 | - **Relative Units**: Prefer rem/em units over fixed pixels for better scalability and accessibility 7 | - **Test Across Devices**: Test and verify UI changes across multiple screen sizes from mobile to tablet to desktop screen sizes and ensure a balanced, user-friendly viewing and reading experience on all 8 | - **Touch-Friendly Design**: Ensure tap targets are appropriately sized (minimum 44x44px) for mobile users 9 | - **Performance on Mobile**: Optimize images and assets for mobile network conditions and smaller screens 10 | - **Readable Typography**: Maintain readable font sizes across all breakpoints without requiring zoom 11 | - **Content Priority**: Show the most important content first on smaller screens through thoughtful layout decisions 12 | -------------------------------------------------------------------------------- /droidz_installer/payloads/shared/default/testing/test-writing.md: -------------------------------------------------------------------------------- 1 | ## Test coverage best practices 2 | 3 | - **Write Minimal Tests During Development**: Do NOT write tests for every change or intermediate step. Focus on completing the feature implementation first, then add strategic tests only at logical completion points 4 | - **Test Only Core User Flows**: Write tests exclusively for critical paths and primary user workflows. Skip writing tests for non-critical utilities and secondary workflows until if/when you're instructed to do so. 5 | - **Defer Edge Case Testing**: Do NOT test edge cases, error states, or validation logic unless they are business-critical. These can be addressed in dedicated testing phases, not during feature development. 6 | - **Test Behavior, Not Implementation**: Focus tests on what the code does, not how it does it, to reduce brittleness 7 | - **Clear Test Names**: Use descriptive names that explain what's being tested and the expected outcome 8 | - **Mock External Dependencies**: Isolate units by mocking databases, APIs, file systems, and other external services 9 | - **Fast Execution**: Keep unit tests fast (milliseconds) so developers run them frequently during development 10 | -------------------------------------------------------------------------------- /droidz_installer/payloads/shared/default/global/conventions.md: -------------------------------------------------------------------------------- 1 | ## General development conventions 2 | 3 | - **Consistent Project Structure**: Organize files and directories in a predictable, logical structure that team members can navigate easily 4 | - **Clear Documentation**: Maintain up-to-date README files with setup instructions, architecture overview, and contribution guidelines 5 | - **Version Control Best Practices**: Use clear commit messages, feature branches, and meaningful pull/merge requests with descriptions 6 | - **Environment Configuration**: Use environment variables for configuration; never commit secrets or API keys to version control 7 | - **Dependency Management**: Keep dependencies up-to-date and minimal; document why major dependencies are used 8 | - **Code Review Process**: Establish a consistent code review process with clear expectations for reviewers and authors 9 | - **Testing Requirements**: Define what level of testing is required before merging (unit tests, integration tests, etc.) 10 | - **Feature Flags**: Use feature flags for incomplete features rather than long-lived feature branches 11 | - **Changelog Maintenance**: Keep a changelog or release notes to track significant changes and improvements 12 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/agents/spec-initializer.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: spec-initializer 3 | description: Use proactively to initialize spec folder and save raw idea 4 | color: green 5 | model: sonnet 6 | --- 7 | 8 | You are a spec initialization specialist. Your role is to create the spec folder structure and save the user's raw idea. 9 | 10 | 11 | ## Specification Initialization Process 12 | 13 | ### 1. Gather Basic Information 14 | 15 | Collect essential details: 16 | - Project name 17 | - Brief description 18 | - Primary goals 19 | - Target users 20 | 21 | ### 2. Create Initial Structure 22 | 23 | Set up spec template with sections: 24 | ```markdown 25 | # [Project Name] Specification 26 | 27 | ## 1. Overview 28 | - Purpose 29 | - Goals 30 | - Target audience 31 | 32 | ## 2. Features 33 | (To be detailed) 34 | 35 | ## 3. Technical Requirements 36 | (To be determined) 37 | 38 | ## 4. Success Criteria 39 | (To be defined) 40 | ``` 41 | 42 | ### 3. Identify Key Stakeholders 43 | 44 | - Who needs to review this? 45 | - Who will implement it? 46 | - Who are the end users? 47 | 48 | ### 4. Set Next Steps 49 | 50 | - What questions need answering? 51 | - What research is needed? 52 | - Who should be consulted? 53 | 54 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/droids/spec-initializer.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: spec-initializer 3 | description: Use proactively to initialize spec folder and save raw idea 4 | color: green 5 | model: sonnet 6 | --- 7 | 8 | You are a spec initialization specialist. Your role is to create the spec folder structure and save the user's raw idea. 9 | 10 | 11 | ## Specification Initialization Process 12 | 13 | ### 1. Gather Basic Information 14 | 15 | Collect essential details: 16 | - Project name 17 | - Brief description 18 | - Primary goals 19 | - Target users 20 | 21 | ### 2. Create Initial Structure 22 | 23 | Set up spec template with sections: 24 | ```markdown 25 | # [Project Name] Specification 26 | 27 | ## 1. Overview 28 | - Purpose 29 | - Goals 30 | - Target audience 31 | 32 | ## 2. Features 33 | (To be detailed) 34 | 35 | ## 3. Technical Requirements 36 | (To be determined) 37 | 38 | ## 4. Success Criteria 39 | (To be defined) 40 | ``` 41 | 42 | ### 3. Identify Key Stakeholders 43 | 44 | - Who needs to review this? 45 | - Who will implement it? 46 | - Who are the end users? 47 | 48 | ### 4. Set Next Steps 49 | 50 | - What questions need answering? 51 | - What research is needed? 52 | - Who should be consulted? 53 | 54 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/agents/README.md: -------------------------------------------------------------------------------- 1 | # Claude Code Agents 2 | 3 | These agents inherit ALL tools from **Claude Code**, not from parent agents. 4 | 5 | ## Tool Inheritance 6 | 7 | **DO NOT** specify `tools:` in agent YAML frontmatter. 8 | 9 | When no `tools:` is specified, agents automatically inherit the complete tool set from Claude Code: 10 | - Read, LS, Execute, Edit, ApplyPatch 11 | - Grep, Glob, Create 12 | - WebSearch, FetchUrl 13 | - TodoWrite, Skill 14 | - And any other tools available in the Claude Code environment 15 | 16 | ## Why No Tool Specification? 17 | 18 | 1. **Sub-agent chains**: When agent A calls agent B, and agent B calls agent C, they all need access to the same tools from Claude Code 19 | 2. **Future-proof**: New tools added to Claude Code automatically become available 20 | 3. **No conflicts**: Prevents "Invalid tools" errors from tool name mismatches 21 | 4. **Flexibility**: Agents can use any tool provided by the system 22 | 23 | ## Example Agent Configuration 24 | 25 | ```yaml 26 | --- 27 | name: my-agent 28 | description: Does something useful 29 | color: blue 30 | model: inherit 31 | --- 32 | 33 | Agent instructions here... 34 | ``` 35 | 36 | **Note**: No `tools:` line - inherits from Claude Code automatically. 37 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/droids/README.md: -------------------------------------------------------------------------------- 1 | # Factory Droid CLI Droids 2 | 3 | These droids inherit ALL tools from **Factory Droid CLI**, not from parent droids. 4 | 5 | ## Tool Inheritance 6 | 7 | **DO NOT** specify `tools:` in droid YAML frontmatter. 8 | 9 | When no `tools:` is specified, droids automatically inherit the complete tool set from Factory Droid CLI: 10 | - Read, LS, Execute, Edit, ApplyPatch 11 | - Grep, Glob, Create 12 | - WebSearch, FetchUrl 13 | - TodoWrite, Skill 14 | - And any other tools available in the Factory.ai environment 15 | 16 | ## Why No Tool Specification? 17 | 18 | 1. **Sub-droid chains**: When droid A calls droid B, and droid B calls droid C, they all need access to the same tools from Factory Droid CLI 19 | 2. **Future-proof**: New tools added to Factory.ai automatically become available 20 | 3. **No conflicts**: Prevents "Invalid tools" errors from tool name mismatches 21 | 4. **Flexibility**: Droids can use any tool provided by the system 22 | 23 | ## Example Droid Configuration 24 | 25 | ```yaml 26 | --- 27 | name: my-droid 28 | description: Does something useful 29 | color: green 30 | model: inherit 31 | --- 32 | 33 | Droid instructions here... 34 | ``` 35 | 36 | **Note**: No `tools:` line - inherits from Factory Droid CLI automatically. 37 | -------------------------------------------------------------------------------- /droidz_installer/payloads/shared/default/global/tech-stack.md: -------------------------------------------------------------------------------- 1 | ## Tech stack 2 | 3 | Define your technical stack below. This serves as a reference for all team members and helps maintain consistency across the project. 4 | 5 | ### Framework & Runtime 6 | - **Application Framework:** [e.g., Rails, Django, Next.js, Express] 7 | - **Language/Runtime:** [e.g., Ruby, Python, Node.js, Java] 8 | - **Package Manager:** [e.g., bundler, pip, npm, yarn] 9 | 10 | ### Frontend 11 | - **JavaScript Framework:** [e.g., React, Vue, Svelte, Alpine, vanilla JS] 12 | - **CSS Framework:** [e.g., Tailwind CSS, Bootstrap, custom] 13 | - **UI Components:** [e.g., shadcn/ui, Material UI, custom library] 14 | 15 | ### Database & Storage 16 | - **Database:** [e.g., PostgreSQL, MySQL, MongoDB] 17 | - **ORM/Query Builder:** [e.g., ActiveRecord, Prisma, Sequelize] 18 | - **Caching:** [e.g., Redis, Memcached] 19 | 20 | ### Testing & Quality 21 | - **Test Framework:** [e.g., Jest, RSpec, pytest] 22 | - **Linting/Formatting:** [e.g., ESLint, Prettier, RuboCop] 23 | 24 | ### Deployment & Infrastructure 25 | - **Hosting:** [e.g., Heroku, AWS, Vercel, Railway] 26 | - **CI/CD:** [e.g., GitHub Actions, CircleCI] 27 | 28 | ### Third-Party Services 29 | - **Authentication:** [e.g., Auth0, Devise, NextAuth] 30 | - **Email:** [e.g., SendGrid, Postmark] 31 | - **Monitoring:** [e.g., Sentry, Datadog] 32 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/skills/changelog-generator/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: changelog-generator 3 | description: Generate comprehensive changelogs from Git history, commit messages, pull requests, and issue tracking for release documentation. Use when preparing releases, documenting changes, creating release notes, categorizing commits, generating version summaries, maintaining project history, or automating changelog updates. 4 | --- 5 | 6 | # Changelog Generator - Automated Release Notes 7 | 8 | ## When to use this skill 9 | 10 | - Preparing software releases 11 | - Documenting changes between versions 12 | - Creating release notes from commits 13 | - Categorizing changes (features, fixes, breaking) 14 | - Generating version summaries 15 | - Maintaining project changelog files 16 | - Automating changelog updates in CI 17 | - Creating GitHub release notes 18 | - Tracking breaking changes 19 | - Communicating changes to users 20 | - Following Conventional Commits standard 21 | - Building release announcement content 22 | 23 | ## When to use this skill 24 | 25 | - Generating changelogs from git commits. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Generating changelogs from git commits. 30 | 31 | ## Pattern 32 | \`\`\`bash 33 | git log --oneline --pretty=format:"- %s" v1.0.0..HEAD 34 | \`\`\` 35 | 36 | ## Resources 37 | - [Keep a Changelog](https://keepachangelog.com/) 38 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/skills/changelog-generator/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: changelog-generator 3 | description: Generate comprehensive changelogs from Git history, commit messages, pull requests, and issue tracking for release documentation. Use when preparing releases, documenting changes, creating release notes, categorizing commits, generating version summaries, maintaining project history, or automating changelog updates. 4 | --- 5 | 6 | # Changelog Generator - Automated Release Notes 7 | 8 | ## When to use this skill 9 | 10 | - Preparing software releases 11 | - Documenting changes between versions 12 | - Creating release notes from commits 13 | - Categorizing changes (features, fixes, breaking) 14 | - Generating version summaries 15 | - Maintaining project changelog files 16 | - Automating changelog updates in CI 17 | - Creating GitHub release notes 18 | - Tracking breaking changes 19 | - Communicating changes to users 20 | - Following Conventional Commits standard 21 | - Building release announcement content 22 | 23 | ## When to use this skill 24 | 25 | - Generating changelogs from git commits. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Generating changelogs from git commits. 30 | 31 | ## Pattern 32 | \`\`\`bash 33 | git log --oneline --pretty=format:"- %s" v1.0.0..HEAD 34 | \`\`\` 35 | 36 | ## Resources 37 | - [Keep a Changelog](https://keepachangelog.com/) 38 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/skills/brand-guidelines/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: brand-guidelines 3 | description: Create and maintain comprehensive brand guidelines including visual identity, tone of voice, messaging, color palettes, typography, and usage rules for consistent brand expression. Use when establishing brand identity, creating style guides, defining visual standards, setting tone of voice, creating brand assets, or ensuring brand consistency. 4 | --- 5 | 6 | # Brand Guidelines - Design Consistency 7 | 8 | ## When to use this skill 9 | 10 | - Establishing brand identity and guidelines 11 | - Creating comprehensive style guides 12 | - Defining visual design standards 13 | - Setting brand tone of voice 14 | - Creating brand color palettes 15 | - Defining typography systems 16 | - Creating logo usage rules 17 | - Ensuring brand consistency 18 | - Defining messaging frameworks 19 | - Creating brand asset libraries 20 | - Building design systems 21 | - Documenting brand values and positioning 22 | 23 | ## When to use this skill 24 | 25 | - Enforcing brand colors, typography, design standards. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Enforcing brand colors, typography, design standards. 30 | 31 | ## Example 32 | \`\`\`typescript 33 | export const colors = { 34 | primary: '#FF6B6B', 35 | secondary: '#4ECDC4' 36 | }; 37 | 38 | export const fonts = { 39 | heading: 'Inter', 40 | body: 'Open Sans' 41 | }; 42 | \`\`\` 43 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/skills/canvas-design/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: canvas-design 3 | description: Create visual designs, graphics, and layouts using HTML Canvas API or design tools for data visualization, graphics, animations, and interactive visual content. Use when creating data visualizations, building interactive graphics, implementing drawing tools, creating charts and diagrams, building game graphics, implementing image manipulation, or creating dynamic visual content. 4 | --- 5 | 6 | # Canvas Design - Visual Art Creation 7 | 8 | ## When to use this skill 9 | 10 | - Creating custom data visualizations 11 | - Building interactive graphics and diagrams 12 | - Implementing drawing and sketching tools 13 | - Creating charts that go beyond libraries 14 | - Building 2D game graphics and sprites 15 | - Implementing image filters and manipulation 16 | - Creating dynamic animations 17 | - Building signature capture tools 18 | - Creating custom visual effects 19 | - Implementing visual editors 20 | - Building infographic generators 21 | - Creating interactive maps and diagrams 22 | 23 | ## When to use this skill 24 | 25 | - Creating posters, designs, static visuals. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Creating posters, designs, static visuals. 30 | 31 | ## Tools 32 | - Figma 33 | - Canva 34 | - Adobe Creative Suite 35 | 36 | ## Principles 37 | - Visual hierarchy 38 | - Color theory 39 | - Typography 40 | - White space 41 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/skills/brand-guidelines/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: brand-guidelines 3 | description: Create and maintain comprehensive brand guidelines including visual identity, tone of voice, messaging, color palettes, typography, and usage rules for consistent brand expression. Use when establishing brand identity, creating style guides, defining visual standards, setting tone of voice, creating brand assets, or ensuring brand consistency. 4 | --- 5 | 6 | # Brand Guidelines - Design Consistency 7 | 8 | ## When to use this skill 9 | 10 | - Establishing brand identity and guidelines 11 | - Creating comprehensive style guides 12 | - Defining visual design standards 13 | - Setting brand tone of voice 14 | - Creating brand color palettes 15 | - Defining typography systems 16 | - Creating logo usage rules 17 | - Ensuring brand consistency 18 | - Defining messaging frameworks 19 | - Creating brand asset libraries 20 | - Building design systems 21 | - Documenting brand values and positioning 22 | 23 | ## When to use this skill 24 | 25 | - Enforcing brand colors, typography, design standards. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Enforcing brand colors, typography, design standards. 30 | 31 | ## Example 32 | \`\`\`typescript 33 | export const colors = { 34 | primary: '#FF6B6B', 35 | secondary: '#4ECDC4' 36 | }; 37 | 38 | export const fonts = { 39 | heading: 'Inter', 40 | body: 'Open Sans' 41 | }; 42 | \`\`\` 43 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/skills/canvas-design/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: canvas-design 3 | description: Create visual designs, graphics, and layouts using HTML Canvas API or design tools for data visualization, graphics, animations, and interactive visual content. Use when creating data visualizations, building interactive graphics, implementing drawing tools, creating charts and diagrams, building game graphics, implementing image manipulation, or creating dynamic visual content. 4 | --- 5 | 6 | # Canvas Design - Visual Art Creation 7 | 8 | ## When to use this skill 9 | 10 | - Creating custom data visualizations 11 | - Building interactive graphics and diagrams 12 | - Implementing drawing and sketching tools 13 | - Creating charts that go beyond libraries 14 | - Building 2D game graphics and sprites 15 | - Implementing image filters and manipulation 16 | - Creating dynamic animations 17 | - Building signature capture tools 18 | - Creating custom visual effects 19 | - Implementing visual editors 20 | - Building infographic generators 21 | - Creating interactive maps and diagrams 22 | 23 | ## When to use this skill 24 | 25 | - Creating posters, designs, static visuals. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Creating posters, designs, static visuals. 30 | 31 | ## Tools 32 | - Figma 33 | - Canva 34 | - Adobe Creative Suite 35 | 36 | ## Principles 37 | - Visual hierarchy 38 | - Color theory 39 | - Typography 40 | - White space 41 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/skills/content-research-writer/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: content-research-writer 3 | description: Research topics thoroughly and write comprehensive, well-structured content including articles, documentation, blog posts, and technical writing with proper citations and sources. Use when writing blog posts, creating technical articles, researching topics, gathering sources, writing documentation, creating educational content, or producing research-backed content. 4 | --- 5 | 6 | # Content Research Writer - Research-Backed Writing 7 | 8 | ## When to use this skill 9 | 10 | - Writing blog posts and articles 11 | - Creating technical documentation 12 | - Researching topics comprehensively 13 | - Gathering credible sources and citations 14 | - Writing educational content 15 | - Producing research-backed writing 16 | - Creating white papers and reports 17 | - Writing case studies 18 | - Developing content strategies 19 | - Creating SEO-optimized content 20 | - Writing tutorials and guides 21 | - Producing thought leadership content 22 | 23 | ## When to use this skill 24 | 25 | - Writing technical content with citations. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Writing technical content with citations. 30 | 31 | ## Process 32 | 1. Research sources 33 | 2. Extract key points 34 | 3. Add citations 35 | 4. Review for accuracy 36 | 37 | ## Resources 38 | - [Technical Writing Guide](https://developers.google.com/tech-writing) 39 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/skills/domain-name-brainstormer/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: domain-name-brainstormer 3 | description: Generate creative, memorable, and available domain name ideas for projects, products, and businesses with consideration for branding, SEO, and availability. Use when naming new projects, finding available domains, creating memorable brand names, generating naming ideas, checking domain availability, or establishing online presence. 4 | --- 5 | 6 | # Domain Name Brainstormer - Name Generation 7 | 8 | ## When to use this skill 9 | 10 | - Naming new projects or products 11 | - Finding available domain names 12 | - Creating memorable brand names 13 | - Generating creative naming ideas 14 | - Checking domain name availability 15 | - Establishing online brand presence 16 | - Creating names that reflect brand values 17 | - Generating SEO-friendly names 18 | - Finding short, memorable domains 19 | - Creating unique, brandable names 20 | - Exploring naming alternatives 21 | - Naming startups or side projects 22 | 23 | ## When to use this skill 24 | 25 | - Generating domain name ideas, checking availability. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Generating domain name ideas, checking availability. 30 | 31 | ## Process 32 | 1. Generate variations 33 | 2. Check DNS availability 34 | 3. Rank by memorability 35 | 4. Check trademark conflicts 36 | 37 | ## Resources 38 | - [Namecheap API](https://www.namecheap.com/support/api/) 39 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/skills/threat-hunting/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: threat-hunting 3 | description: Proactively search for security threats, vulnerabilities, and suspicious patterns in applications and infrastructure before they cause damage. Use when conducting security audits, identifying vulnerabilities, analyzing security logs, detecting suspicious patterns, investigating potential breaches, performing penetration testing, or implementing security monitoring. 4 | --- 5 | 6 | # Threat Hunting - Security Analysis 7 | 8 | ## When to use this skill 9 | 10 | - Conducting proactive security audits 11 | - Identifying vulnerabilities before exploitation 12 | - Analyzing security logs for threats 13 | - Detecting suspicious access patterns 14 | - Investigating potential security breaches 15 | - Performing penetration testing 16 | - Implementing security monitoring 17 | - Reviewing authentication logs 18 | - Detecting anomalous behavior 19 | - Identifying security misconfigurations 20 | - Analyzing attack surfaces 21 | - Building threat detection systems 22 | 23 | ## When to use this skill 24 | 25 | - Proactive security monitoring, threat detection. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Proactive security monitoring, threat detection. 30 | 31 | ## Patterns 32 | - Unusual network traffic 33 | - Failed auth attempts 34 | - Privilege escalation 35 | - Data exfiltration 36 | 37 | ## Resources 38 | - [MITRE ATT&CK](https://attack.mitre.org/) 39 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/skills/content-research-writer/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: content-research-writer 3 | description: Research topics thoroughly and write comprehensive, well-structured content including articles, documentation, blog posts, and technical writing with proper citations and sources. Use when writing blog posts, creating technical articles, researching topics, gathering sources, writing documentation, creating educational content, or producing research-backed content. 4 | --- 5 | 6 | # Content Research Writer - Research-Backed Writing 7 | 8 | ## When to use this skill 9 | 10 | - Writing blog posts and articles 11 | - Creating technical documentation 12 | - Researching topics comprehensively 13 | - Gathering credible sources and citations 14 | - Writing educational content 15 | - Producing research-backed writing 16 | - Creating white papers and reports 17 | - Writing case studies 18 | - Developing content strategies 19 | - Creating SEO-optimized content 20 | - Writing tutorials and guides 21 | - Producing thought leadership content 22 | 23 | ## When to use this skill 24 | 25 | - Writing technical content with citations. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Writing technical content with citations. 30 | 31 | ## Process 32 | 1. Research sources 33 | 2. Extract key points 34 | 3. Add citations 35 | 4. Review for accuracy 36 | 37 | ## Resources 38 | - [Technical Writing Guide](https://developers.google.com/tech-writing) 39 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/skills/domain-name-brainstormer/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: domain-name-brainstormer 3 | description: Generate creative, memorable, and available domain name ideas for projects, products, and businesses with consideration for branding, SEO, and availability. Use when naming new projects, finding available domains, creating memorable brand names, generating naming ideas, checking domain availability, or establishing online presence. 4 | --- 5 | 6 | # Domain Name Brainstormer - Name Generation 7 | 8 | ## When to use this skill 9 | 10 | - Naming new projects or products 11 | - Finding available domain names 12 | - Creating memorable brand names 13 | - Generating creative naming ideas 14 | - Checking domain name availability 15 | - Establishing online brand presence 16 | - Creating names that reflect brand values 17 | - Generating SEO-friendly names 18 | - Finding short, memorable domains 19 | - Creating unique, brandable names 20 | - Exploring naming alternatives 21 | - Naming startups or side projects 22 | 23 | ## When to use this skill 24 | 25 | - Generating domain name ideas, checking availability. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Generating domain name ideas, checking availability. 30 | 31 | ## Process 32 | 1. Generate variations 33 | 2. Check DNS availability 34 | 3. Rank by memorability 35 | 4. Check trademark conflicts 36 | 37 | ## Resources 38 | - [Namecheap API](https://www.namecheap.com/support/api/) 39 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/skills/threat-hunting/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: threat-hunting 3 | description: Proactively search for security threats, vulnerabilities, and suspicious patterns in applications and infrastructure before they cause damage. Use when conducting security audits, identifying vulnerabilities, analyzing security logs, detecting suspicious patterns, investigating potential breaches, performing penetration testing, or implementing security monitoring. 4 | --- 5 | 6 | # Threat Hunting - Security Analysis 7 | 8 | ## When to use this skill 9 | 10 | - Conducting proactive security audits 11 | - Identifying vulnerabilities before exploitation 12 | - Analyzing security logs for threats 13 | - Detecting suspicious access patterns 14 | - Investigating potential security breaches 15 | - Performing penetration testing 16 | - Implementing security monitoring 17 | - Reviewing authentication logs 18 | - Detecting anomalous behavior 19 | - Identifying security misconfigurations 20 | - Analyzing attack surfaces 21 | - Building threat detection systems 22 | 23 | ## When to use this skill 24 | 25 | - Proactive security monitoring, threat detection. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Proactive security monitoring, threat detection. 30 | 31 | ## Patterns 32 | - Unusual network traffic 33 | - Failed auth attempts 34 | - Privilege escalation 35 | - Data exfiltration 36 | 37 | ## Resources 38 | - [MITRE ATT&CK](https://attack.mitre.org/) 39 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/skills/brainstorming/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: brainstorming 3 | description: Facilitate ideation, explore alternatives, and refine concepts through structured brainstorming techniques before implementation. Use when starting new projects, designing features, exploring solutions, evaluating tradeoffs, challenging assumptions, generating creative ideas, planning architecture, or refining rough concepts into detailed designs. 4 | --- 5 | 6 | # Brainstorming - Idea Refinement 7 | 8 | ## When to use this skill 9 | 10 | - Starting new projects or features 11 | - Designing system architecture 12 | - Exploring multiple solution approaches 13 | - Evaluating tradeoffs and alternatives 14 | - Challenging assumptions and constraints 15 | - Generating creative ideas for problems 16 | - Planning feature implementations 17 | - Refining vague requirements into clear specs 18 | - Identifying edge cases and considerations 19 | - Exploring technical possibilities 20 | - Designing user experiences 21 | - Before writing code for complex features 22 | 23 | ## When to use this skill 24 | 25 | - Developing ideas before coding, exploring alternatives. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Developing ideas before coding, exploring alternatives. 30 | 31 | ## Process 32 | 1. Question assumptions 33 | 2. Explore alternatives 34 | 3. Validate incrementally 35 | 4. Refine design 36 | 37 | ## Resources 38 | - [Design Thinking](https://www.ideo.com/post/design-thinking) 39 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/skills/brainstorming/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: brainstorming 3 | description: Facilitate ideation, explore alternatives, and refine concepts through structured brainstorming techniques before implementation. Use when starting new projects, designing features, exploring solutions, evaluating tradeoffs, challenging assumptions, generating creative ideas, planning architecture, or refining rough concepts into detailed designs. 4 | --- 5 | 6 | # Brainstorming - Idea Refinement 7 | 8 | ## When to use this skill 9 | 10 | - Starting new projects or features 11 | - Designing system architecture 12 | - Exploring multiple solution approaches 13 | - Evaluating tradeoffs and alternatives 14 | - Challenging assumptions and constraints 15 | - Generating creative ideas for problems 16 | - Planning feature implementations 17 | - Refining vague requirements into clear specs 18 | - Identifying edge cases and considerations 19 | - Exploring technical possibilities 20 | - Designing user experiences 21 | - Before writing code for complex features 22 | 23 | ## When to use this skill 24 | 25 | - Developing ideas before coding, exploring alternatives. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Developing ideas before coding, exploring alternatives. 30 | 31 | ## Process 32 | 1. Question assumptions 33 | 2. Explore alternatives 34 | 3. Validate incrementally 35 | 4. Refine design 36 | 37 | ## Resources 38 | - [Design Thinking](https://www.ideo.com/post/design-thinking) 39 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/agents/spec-verifier.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: spec-verifier 3 | description: Use proactively to verify the spec and tasks list 4 | color: pink 5 | model: sonnet 6 | --- 7 | 8 | You are a software product specifications verifier. Your role is to verify the spec and tasks list. 9 | 10 | 11 | ## Specification Verification Process 12 | 13 | ### 1. Completeness Check 14 | 15 | Verify spec includes: 16 | - Clear overview and goals 17 | - Detailed feature descriptions 18 | - Technical requirements 19 | - Data models 20 | - API specifications 21 | - UI/UX requirements 22 | - Testing strategy 23 | - Deployment plan 24 | 25 | ### 2. Clarity Check 26 | 27 | Ensure spec is: 28 | - Unambiguous 29 | - Specific (not vague) 30 | - Understandable by developers 31 | - Free of contradictions 32 | 33 | ### 3. Implementability Check 34 | 35 | Confirm: 36 | - Requirements are technically feasible 37 | - Dependencies are identified 38 | - Edge cases are considered 39 | - Error handling is specified 40 | 41 | ### 4. Acceptance Criteria Check 42 | 43 | Verify each feature has: 44 | - Clear success criteria 45 | - Testable outcomes 46 | - Measurable goals 47 | 48 | ### 5. Report Issues 49 | 50 | Document any: 51 | - Missing information 52 | - Unclear requirements 53 | - Contradictions 54 | - Technical concerns 55 | 56 | 57 | ## User Standards & Preferences Compliance 58 | 59 | IMPORTANT: Ensure that the spec and tasks list are ALIGNED and DO NOT CONFLICT with any of user's preferred tech stack, coding conventions, or common patterns as detailed in the following files: 60 | 61 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/skills/root-cause-tracing/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: root-cause-tracing 3 | description: Trace bugs backward through call stacks and execution flows to identify the original source of errors, invalid data, or incorrect behavior. Use when debugging complex issues, tracing error origins, investigating data corruption, following execution paths, identifying where invalid data enters the system, or finding root causes of cascading failures. 4 | --- 5 | 6 | # Root Cause Tracing - Debugging Deep Errors 7 | 8 | ## When to use this skill 9 | 10 | - Debugging complex, multi-layered issues 11 | - Tracing errors back through call stacks 12 | - Investigating data corruption sources 13 | - Following execution paths through systems 14 | - Identifying where invalid data originates 15 | - Finding root causes of cascading failures 16 | - Debugging integration issues 17 | - Tracing state changes backward 18 | - Investigating intermittent bugs 19 | - Following data flow through transformations 20 | - Identifying the first point of failure 21 | - Debugging asynchronous or distributed systems 22 | 23 | ## When to use this skill 24 | 25 | - Tracing bugs backward through call stacks. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Tracing bugs backward through call stacks. 30 | 31 | ## Process 32 | 1. Reproduce issue reliably 33 | 2. Add instrumentation 34 | 3. Trace backwards 35 | 4. Find original trigger 36 | 5. Fix root cause 37 | 38 | ## Resources 39 | - [Debugging Guide](https://jvns.ca/) 40 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/skills/root-cause-tracing/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: root-cause-tracing 3 | description: Trace bugs backward through call stacks and execution flows to identify the original source of errors, invalid data, or incorrect behavior. Use when debugging complex issues, tracing error origins, investigating data corruption, following execution paths, identifying where invalid data enters the system, or finding root causes of cascading failures. 4 | --- 5 | 6 | # Root Cause Tracing - Debugging Deep Errors 7 | 8 | ## When to use this skill 9 | 10 | - Debugging complex, multi-layered issues 11 | - Tracing errors back through call stacks 12 | - Investigating data corruption sources 13 | - Following execution paths through systems 14 | - Identifying where invalid data originates 15 | - Finding root causes of cascading failures 16 | - Debugging integration issues 17 | - Tracing state changes backward 18 | - Investigating intermittent bugs 19 | - Following data flow through transformations 20 | - Identifying the first point of failure 21 | - Debugging asynchronous or distributed systems 22 | 23 | ## When to use this skill 24 | 25 | - Tracing bugs backward through call stacks. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Tracing bugs backward through call stacks. 30 | 31 | ## Process 32 | 1. Reproduce issue reliably 33 | 2. Add instrumentation 34 | 3. Trace backwards 35 | 4. Find original trigger 36 | 5. Fix root cause 37 | 38 | ## Resources 39 | - [Debugging Guide](https://jvns.ca/) 40 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/skills/invoice-organizer/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: invoice-organizer 3 | description: Organize, categorize, track, and manage invoices systematically with automated extraction of invoice data, payment tracking, and financial organization. Use when processing invoice uploads, extracting invoice details (date, amount, vendor), categorizing expenses, tracking payment status, organizing receipts, generating financial reports, or building accounting and bookkeeping systems. 4 | --- 5 | 6 | # Invoice Organizer - Receipt Management 7 | 8 | ## When to use this skill 9 | 10 | - Processing uploaded invoice PDFs and images 11 | - Extracting invoice data (date, amount, vendor, items) 12 | - Categorizing expenses and business costs 13 | - Tracking invoice payment status 14 | - Organizing receipts for tax purposes 15 | - Generating financial reports from invoices 16 | - Building expense tracking applications 17 | - Implementing automated bookkeeping 18 | - Creating invoice approval workflows 19 | - Matching invoices with purchase orders 20 | - Detecting duplicate invoices 21 | - Building accounting and finance tools 22 | 23 | ## When to use this skill 24 | 25 | - Organizing invoices, extracting metadata. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Organizing invoices, extracting metadata. 30 | 31 | ## Pattern 32 | \`\`\`typescript 33 | const invoiceDate = extractDate(filename); 34 | const newName = `${invoiceDate}_${vendor}_${amount}.pdf`; 35 | fs.renameSync(oldPath, newPath); 36 | \`\`\` 37 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/droids/spec-verifier.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: spec-verifier 3 | description: Use proactively to verify the spec and tasks list 4 | color: pink 5 | model: sonnet 6 | --- 7 | 8 | You are a software product specifications verifier. Your role is to verify the spec and tasks list. 9 | 10 | 11 | ## Specification Verification Process 12 | 13 | ### 1. Completeness Check 14 | 15 | Verify spec includes: 16 | - Clear overview and goals 17 | - Detailed feature descriptions 18 | - Technical requirements 19 | - Data models 20 | - API specifications 21 | - UI/UX requirements 22 | - Testing strategy 23 | - Deployment plan 24 | 25 | ### 2. Clarity Check 26 | 27 | Ensure spec is: 28 | - Unambiguous 29 | - Specific (not vague) 30 | - Understandable by developers 31 | - Free of contradictions 32 | 33 | ### 3. Implementability Check 34 | 35 | Confirm: 36 | - Requirements are technically feasible 37 | - Dependencies are identified 38 | - Edge cases are considered 39 | - Error handling is specified 40 | 41 | ### 4. Acceptance Criteria Check 42 | 43 | Verify each feature has: 44 | - Clear success criteria 45 | - Testable outcomes 46 | - Measurable goals 47 | 48 | ### 5. Report Issues 49 | 50 | Document any: 51 | - Missing information 52 | - Unclear requirements 53 | - Contradictions 54 | - Technical concerns 55 | 56 | 57 | ## User Standards & Preferences Compliance 58 | 59 | IMPORTANT: Ensure that the spec and tasks list are ALIGNED and DO NOT CONFLICT with any of user's preferred tech stack, coding conventions, or common patterns as detailed in the following files: 60 | 61 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/skills/invoice-organizer/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: invoice-organizer 3 | description: Organize, categorize, track, and manage invoices systematically with automated extraction of invoice data, payment tracking, and financial organization. Use when processing invoice uploads, extracting invoice details (date, amount, vendor), categorizing expenses, tracking payment status, organizing receipts, generating financial reports, or building accounting and bookkeeping systems. 4 | --- 5 | 6 | # Invoice Organizer - Receipt Management 7 | 8 | ## When to use this skill 9 | 10 | - Processing uploaded invoice PDFs and images 11 | - Extracting invoice data (date, amount, vendor, items) 12 | - Categorizing expenses and business costs 13 | - Tracking invoice payment status 14 | - Organizing receipts for tax purposes 15 | - Generating financial reports from invoices 16 | - Building expense tracking applications 17 | - Implementing automated bookkeeping 18 | - Creating invoice approval workflows 19 | - Matching invoices with purchase orders 20 | - Detecting duplicate invoices 21 | - Building accounting and finance tools 22 | 23 | ## When to use this skill 24 | 25 | - Organizing invoices, extracting metadata. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Organizing invoices, extracting metadata. 30 | 31 | ## Pattern 32 | \`\`\`typescript 33 | const invoiceDate = extractDate(filename); 34 | const newName = `${invoiceDate}_${vendor}_${amount}.pdf`; 35 | fs.renameSync(oldPath, newPath); 36 | \`\`\` 37 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/skills/competitive-research/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: competitive-research 3 | description: Research competitors, analyze market positioning, identify differentiators, and understand competitive landscape to inform product strategy and positioning. Use when researching competitors, analyzing features, identifying market gaps, understanding pricing strategies, evaluating competitive advantages, researching market trends, or informing product decisions. 4 | --- 5 | 6 | # Competitive Research - Market Analysis 7 | 8 | ## When to use this skill 9 | 10 | - Researching competitor products and features 11 | - Analyzing competitive positioning 12 | - Identifying market gaps and opportunities 13 | - Understanding competitor pricing strategies 14 | - Evaluating competitive advantages 15 | - Researching market trends and directions 16 | - Informing product strategy decisions 17 | - Creating competitive feature matrices 18 | - Analyzing competitor user experiences 19 | - Identifying differentiators 20 | - Researching emerging competitors 21 | - Building competitive intelligence 22 | 23 | ## When to use this skill 24 | 25 | - Analyzing competitors, extracting insights. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Analyzing competitors, extracting insights. 30 | 31 | ## Process 32 | 1. Identify competitors 33 | 2. Analyze features 34 | 3. Extract messaging 35 | 4. Benchmark performance 36 | 37 | ## Resources 38 | - [Competitive Analysis Guide](https://www.hubspot.com/competitor-analysis-template) 39 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/skills/competitive-research/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: competitive-research 3 | description: Research competitors, analyze market positioning, identify differentiators, and understand competitive landscape to inform product strategy and positioning. Use when researching competitors, analyzing features, identifying market gaps, understanding pricing strategies, evaluating competitive advantages, researching market trends, or informing product decisions. 4 | --- 5 | 6 | # Competitive Research - Market Analysis 7 | 8 | ## When to use this skill 9 | 10 | - Researching competitor products and features 11 | - Analyzing competitive positioning 12 | - Identifying market gaps and opportunities 13 | - Understanding competitor pricing strategies 14 | - Evaluating competitive advantages 15 | - Researching market trends and directions 16 | - Informing product strategy decisions 17 | - Creating competitive feature matrices 18 | - Analyzing competitor user experiences 19 | - Identifying differentiators 20 | - Researching emerging competitors 21 | - Building competitive intelligence 22 | 23 | ## When to use this skill 24 | 25 | - Analyzing competitors, extracting insights. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Analyzing competitors, extracting insights. 30 | 31 | ## Process 32 | 1. Identify competitors 33 | 2. Analyze features 34 | 3. Extract messaging 35 | 4. Benchmark performance 36 | 37 | ## Resources 38 | - [Competitive Analysis Guide](https://www.hubspot.com/competitor-analysis-template) 39 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/skills/kaizen-continuous-improvement/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: kaizen-continuous-improvement 3 | description: Apply continuous improvement principles to iteratively enhance processes, code quality, team practices, and system performance through small, incremental changes. Use when improving development processes, optimizing workflows, reducing waste, enhancing code quality over time, implementing retrospective learnings, or fostering a culture of continuous improvement. 4 | --- 5 | 6 | # Kaizen - Continuous Improvement 7 | 8 | ## When to use this skill 9 | 10 | - Improving development processes incrementally 11 | - Optimizing team workflows and practices 12 | - Reducing waste and inefficiencies 13 | - Enhancing code quality over time 14 | - Implementing retrospective learnings 15 | - Fostering continuous improvement culture 16 | - Identifying process bottlenecks 17 | - Streamlining development pipelines 18 | - Improving code review processes 19 | - Optimizing deployment workflows 20 | - Reducing technical debt systematically 21 | - Implementing small, incremental improvements 22 | 23 | ## When to use this skill 24 | 25 | - Applying incremental improvements, retrospectives. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Applying incremental improvements, retrospectives. 30 | 31 | ## Process 32 | 1. Identify bottleneck 33 | 2. Propose small change 34 | 3. Implement quickly 35 | 4. Measure impact 36 | 5. Iterate 37 | 38 | ## Resources 39 | - [Kaizen Philosophy](https://en.wikipedia.org/wiki/Kaizen) 40 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/skills/kaizen-continuous-improvement/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: kaizen-continuous-improvement 3 | description: Apply continuous improvement principles to iteratively enhance processes, code quality, team practices, and system performance through small, incremental changes. Use when improving development processes, optimizing workflows, reducing waste, enhancing code quality over time, implementing retrospective learnings, or fostering a culture of continuous improvement. 4 | --- 5 | 6 | # Kaizen - Continuous Improvement 7 | 8 | ## When to use this skill 9 | 10 | - Improving development processes incrementally 11 | - Optimizing team workflows and practices 12 | - Reducing waste and inefficiencies 13 | - Enhancing code quality over time 14 | - Implementing retrospective learnings 15 | - Fostering continuous improvement culture 16 | - Identifying process bottlenecks 17 | - Streamlining development pipelines 18 | - Improving code review processes 19 | - Optimizing deployment workflows 20 | - Reducing technical debt systematically 21 | - Implementing small, incremental improvements 22 | 23 | ## When to use this skill 24 | 25 | - Applying incremental improvements, retrospectives. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Applying incremental improvements, retrospectives. 30 | 31 | ## Process 32 | 1. Identify bottleneck 33 | 2. Propose small change 34 | 3. Implement quickly 35 | 4. Measure impact 36 | 5. Iterate 37 | 38 | ## Resources 39 | - [Kaizen Philosophy](https://en.wikipedia.org/wiki/Kaizen) 40 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/skills/artifacts-builder/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: artifacts-builder 3 | description: Create interactive, self-contained artifacts like mini-apps, visualizations, calculators, and tools that can be embedded or used standalone. Use when building interactive calculators, creating data visualizations, making mini web apps, building embeddable widgets, creating interactive demos, making tools for specific tasks, or generating standalone HTML/JS applications. 4 | --- 5 | 6 | # Artifacts Builder - Claude.ai HTML Artifacts 7 | 8 | ## When to use this skill 9 | 10 | - Building interactive calculators and converters 11 | - Creating data visualizations and charts 12 | - Making mini web applications 13 | - Building embeddable widgets for websites 14 | - Creating interactive demos and prototypes 15 | - Making tools for specific tasks (generators, validators) 16 | - Generating standalone HTML/JavaScript apps 17 | - Building interactive forms and quizzes 18 | - Creating educational interactive content 19 | - Making API testing or debugging tools 20 | - Building configuration generators 21 | - Creating shareable interactive examples 22 | 23 | ## When to use this skill 24 | 25 | - Creating interactive HTML artifacts in Claude.ai. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Creating interactive HTML artifacts in Claude.ai. 30 | 31 | ## Pattern 32 | \`\`\`html 33 | 34 | 35 | 36 | 37 |
Content here
38 | 39 | 40 | \`\`\` 41 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/skills/document-processing-pdf/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: document-processing-pdf 3 | description: Process, parse, create, and manipulate PDF documents using libraries like pdf-lib, PDFKit, or pdf-parse for document generation, data extraction, and PDF manipulation. Use when generating PDFs from HTML, extracting text from PDFs, merging or splitting PDFs, adding watermarks, filling PDF forms, creating invoices and reports, parsing legal documents, or building document management systems. 4 | --- 5 | 6 | # Document Processing - PDF Files 7 | 8 | ## When to use this skill 9 | 10 | - Generating PDFs from HTML templates 11 | - Extracting text and data from PDF documents 12 | - Merging multiple PDFs into one document 13 | - Splitting large PDFs into smaller files 14 | - Adding watermarks or stamps to PDFs 15 | - Filling PDF forms programmatically 16 | - Creating invoices, receipts, and reports as PDFs 17 | - Parsing legal documents and contracts 18 | - Converting PDFs to images or text 19 | - Building document management systems 20 | - Extracting tables and structured data from PDFs 21 | - Creating searchable PDFs (OCR integration) 22 | 23 | ## When to use this skill 24 | 25 | - Generating, extracting data from PDFs. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Generating, extracting data from PDFs. 30 | 31 | ## Example 32 | \`\`\`typescript 33 | import PDFDocument from 'pdfkit'; 34 | 35 | const doc = new PDFDocument(); 36 | doc.text('Hello World'); 37 | doc.end(); 38 | \`\`\` 39 | 40 | ## Resources 41 | - [PDFKit](https://pdfkit.org/) 42 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/skills/artifacts-builder/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: artifacts-builder 3 | description: Create interactive, self-contained artifacts like mini-apps, visualizations, calculators, and tools that can be embedded or used standalone. Use when building interactive calculators, creating data visualizations, making mini web apps, building embeddable widgets, creating interactive demos, making tools for specific tasks, or generating standalone HTML/JS applications. 4 | --- 5 | 6 | # Artifacts Builder - Claude.ai HTML Artifacts 7 | 8 | ## When to use this skill 9 | 10 | - Building interactive calculators and converters 11 | - Creating data visualizations and charts 12 | - Making mini web applications 13 | - Building embeddable widgets for websites 14 | - Creating interactive demos and prototypes 15 | - Making tools for specific tasks (generators, validators) 16 | - Generating standalone HTML/JavaScript apps 17 | - Building interactive forms and quizzes 18 | - Creating educational interactive content 19 | - Making API testing or debugging tools 20 | - Building configuration generators 21 | - Creating shareable interactive examples 22 | 23 | ## When to use this skill 24 | 25 | - Creating interactive HTML artifacts in Claude.ai. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Creating interactive HTML artifacts in Claude.ai. 30 | 31 | ## Pattern 32 | \`\`\`html 33 | 34 | 35 | 36 | 37 |
Content here
38 | 39 | 40 | \`\`\` 41 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/skills/document-processing-pdf/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: document-processing-pdf 3 | description: Process, parse, create, and manipulate PDF documents using libraries like pdf-lib, PDFKit, or pdf-parse for document generation, data extraction, and PDF manipulation. Use when generating PDFs from HTML, extracting text from PDFs, merging or splitting PDFs, adding watermarks, filling PDF forms, creating invoices and reports, parsing legal documents, or building document management systems. 4 | --- 5 | 6 | # Document Processing - PDF Files 7 | 8 | ## When to use this skill 9 | 10 | - Generating PDFs from HTML templates 11 | - Extracting text and data from PDF documents 12 | - Merging multiple PDFs into one document 13 | - Splitting large PDFs into smaller files 14 | - Adding watermarks or stamps to PDFs 15 | - Filling PDF forms programmatically 16 | - Creating invoices, receipts, and reports as PDFs 17 | - Parsing legal documents and contracts 18 | - Converting PDFs to images or text 19 | - Building document management systems 20 | - Extracting tables and structured data from PDFs 21 | - Creating searchable PDFs (OCR integration) 22 | 23 | ## When to use this skill 24 | 25 | - Generating, extracting data from PDFs. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Generating, extracting data from PDFs. 30 | 31 | ## Example 32 | \`\`\`typescript 33 | import PDFDocument from 'pdfkit'; 34 | 35 | const doc = new PDFDocument(); 36 | doc.text('Hello World'); 37 | doc.end(); 38 | \`\`\` 39 | 40 | ## Resources 41 | - [PDFKit](https://pdfkit.org/) 42 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/skills/meeting-insights-analyzer/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: meeting-insights-analyzer 3 | description: Analyze meeting transcripts, recordings, and notes to extract action items, key decisions, topics, sentiment, and generate summaries using NLP and AI. Use when processing meeting transcripts, extracting action items, summarizing discussions, identifying key decisions, tracking topics and themes, analyzing sentiment, generating meeting notes, or building collaboration and productivity tools. 4 | --- 5 | 6 | # Meeting Insights - Transcript Analysis 7 | 8 | ## When to use this skill 9 | 10 | - Processing meeting transcripts and recordings 11 | - Extracting action items and tasks from meetings 12 | - Summarizing long discussions and meetings 13 | - Identifying key decisions and outcomes 14 | - Tracking recurring topics and themes 15 | - Analyzing sentiment and engagement levels 16 | - Generating automated meeting notes 17 | - Building collaboration productivity tools 18 | - Creating meeting insights dashboards 19 | - Tracking action item completion 20 | - Identifying meeting patterns and trends 21 | - Building AI-powered meeting assistants 22 | 23 | ## When to use this skill 24 | 25 | - Analyzing meeting transcripts, extracting insights. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Analyzing meeting transcripts, extracting insights. 30 | 31 | ## Metrics 32 | - Speaking time distribution 33 | - Filler words count 34 | - Sentiment analysis 35 | - Action items extraction 36 | 37 | ## Resources 38 | - [Natural Language Processing](https://www.nltk.org/) 39 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/skills/meeting-insights-analyzer/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: meeting-insights-analyzer 3 | description: Analyze meeting transcripts, recordings, and notes to extract action items, key decisions, topics, sentiment, and generate summaries using NLP and AI. Use when processing meeting transcripts, extracting action items, summarizing discussions, identifying key decisions, tracking topics and themes, analyzing sentiment, generating meeting notes, or building collaboration and productivity tools. 4 | --- 5 | 6 | # Meeting Insights - Transcript Analysis 7 | 8 | ## When to use this skill 9 | 10 | - Processing meeting transcripts and recordings 11 | - Extracting action items and tasks from meetings 12 | - Summarizing long discussions and meetings 13 | - Identifying key decisions and outcomes 14 | - Tracking recurring topics and themes 15 | - Analyzing sentiment and engagement levels 16 | - Generating automated meeting notes 17 | - Building collaboration productivity tools 18 | - Creating meeting insights dashboards 19 | - Tracking action item completion 20 | - Identifying meeting patterns and trends 21 | - Building AI-powered meeting assistants 22 | 23 | ## When to use this skill 24 | 25 | - Analyzing meeting transcripts, extracting insights. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Analyzing meeting transcripts, extracting insights. 30 | 31 | ## Metrics 32 | - Speaking time distribution 33 | - Filler words count 34 | - Sentiment analysis 35 | - Action items extraction 36 | 37 | ## Resources 38 | - [Natural Language Processing](https://www.nltk.org/) 39 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/skills/vercel-deployment/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: vercel-deployment 3 | description: Deploy and optimize applications on Vercel with preview deployments, edge functions, environment variables, and performance monitoring. Use when deploying Next.js applications, setting up preview deployments per pull request, configuring environment variables, using Vercel Edge Functions, optimizing build performance, implementing redirects and rewrites, configuring custom domains, or monitoring application performance with Vercel Analytics. 4 | --- 5 | 6 | # Vercel Deployment - Production Deployments 7 | 8 | ## When to use this skill 9 | 10 | - Deploying Next.js applications to Vercel 11 | - Setting up automatic preview deployments 12 | - Configuring environment variables per environment 13 | - Using Vercel Edge Functions at the edge 14 | - Optimizing build times and caching 15 | - Implementing redirects, rewrites, and headers 16 | - Configuring custom domains and SSL 17 | - Monitoring performance with Vercel Analytics 18 | - Implementing incremental static regeneration 19 | - Setting up monorepo deployments with Turborepo 20 | - Configuring serverless function regions 21 | - Using Vercel KV, Postgres, or Blob storage 22 | 23 | ## When to use this skill 24 | 25 | - Deploying Next.js apps, configuring edge functions, analytics. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Deploying Next.js apps, configuring edge functions, analytics. 30 | 31 | ## Deploy 32 | \`\`\`bash 33 | vercel --prod 34 | \`\`\` 35 | 36 | ## Resources 37 | - [Vercel Docs](https://vercel.com/docs) 38 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/skills/vercel-deployment/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: vercel-deployment 3 | description: Deploy and optimize applications on Vercel with preview deployments, edge functions, environment variables, and performance monitoring. Use when deploying Next.js applications, setting up preview deployments per pull request, configuring environment variables, using Vercel Edge Functions, optimizing build performance, implementing redirects and rewrites, configuring custom domains, or monitoring application performance with Vercel Analytics. 4 | --- 5 | 6 | # Vercel Deployment - Production Deployments 7 | 8 | ## When to use this skill 9 | 10 | - Deploying Next.js applications to Vercel 11 | - Setting up automatic preview deployments 12 | - Configuring environment variables per environment 13 | - Using Vercel Edge Functions at the edge 14 | - Optimizing build times and caching 15 | - Implementing redirects, rewrites, and headers 16 | - Configuring custom domains and SSL 17 | - Monitoring performance with Vercel Analytics 18 | - Implementing incremental static regeneration 19 | - Setting up monorepo deployments with Turborepo 20 | - Configuring serverless function regions 21 | - Using Vercel KV, Postgres, or Blob storage 22 | 23 | ## When to use this skill 24 | 25 | - Deploying Next.js apps, configuring edge functions, analytics. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Deploying Next.js apps, configuring edge functions, analytics. 30 | 31 | ## Deploy 32 | \`\`\`bash 33 | vercel --prod 34 | \`\`\` 35 | 36 | ## Resources 37 | - [Vercel Docs](https://vercel.com/docs) 38 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/skills/file-organizer/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: file-organizer 3 | description: Organize, categorize, rename, and manage files systematically using automated rules, naming conventions, and folder structures for efficient file management. Use when organizing uploaded files, implementing file naming conventions, categorizing files by type or metadata, creating folder structures, cleaning up messy directories, automating file movements, implementing media libraries, or building file management systems. 4 | --- 5 | 6 | # File Organizer - Intelligent File Management 7 | 8 | ## When to use this skill 9 | 10 | - Organizing large numbers of uploaded files 11 | - Implementing systematic file naming conventions 12 | - Categorizing files by type, date, or metadata 13 | - Creating logical folder structures 14 | - Cleaning up messy or disorganized directories 15 | - Automating file movements based on rules 16 | - Building media libraries with categorization 17 | - Implementing file tagging systems 18 | - Organizing downloads or document repositories 19 | - Creating searchable file systems 20 | - Implementing version control for files 21 | - Building document management workflows 22 | 23 | ## When to use this skill 24 | 25 | - Organizing files, finding duplicates, renaming. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Organizing files, finding duplicates, renaming. 30 | 31 | ## Pattern 32 | \`\`\`typescript 33 | const groupedFiles = files.reduce((acc, file) => { 34 | const ext = path.extname(file); 35 | if (!acc[ext]) acc[ext] = []; 36 | acc[ext].push(file); 37 | return acc; 38 | }, {}); 39 | \`\`\` 40 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/skills/file-organizer/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: file-organizer 3 | description: Organize, categorize, rename, and manage files systematically using automated rules, naming conventions, and folder structures for efficient file management. Use when organizing uploaded files, implementing file naming conventions, categorizing files by type or metadata, creating folder structures, cleaning up messy directories, automating file movements, implementing media libraries, or building file management systems. 4 | --- 5 | 6 | # File Organizer - Intelligent File Management 7 | 8 | ## When to use this skill 9 | 10 | - Organizing large numbers of uploaded files 11 | - Implementing systematic file naming conventions 12 | - Categorizing files by type, date, or metadata 13 | - Creating logical folder structures 14 | - Cleaning up messy or disorganized directories 15 | - Automating file movements based on rules 16 | - Building media libraries with categorization 17 | - Implementing file tagging systems 18 | - Organizing downloads or document repositories 19 | - Creating searchable file systems 20 | - Implementing version control for files 21 | - Building document management workflows 22 | 23 | ## When to use this skill 24 | 25 | - Organizing files, finding duplicates, renaming. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Organizing files, finding duplicates, renaming. 30 | 31 | ## Pattern 32 | \`\`\`typescript 33 | const groupedFiles = files.reduce((acc, file) => { 34 | const ext = path.extname(file); 35 | if (!acc[ext]) acc[ext] = []; 36 | acc[ext].push(file); 37 | return acc; 38 | }, {}); 39 | \`\`\` 40 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/skills/typescript-strict/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: typescript-strict 3 | description: Write type-safe TypeScript code with strict mode enabled, comprehensive type definitions, proper error handling, and elimination of any types. Use when enabling TypeScript strict mode, adding types to existing JavaScript, fixing type errors, creating type definitions, using utility types, implementing type guards, avoiding any types, creating generic types, or ensuring complete type safety across the codebase. 4 | --- 5 | 6 | # TypeScript Strict - Type Safety Best Practices 7 | 8 | ## When to use this skill 9 | 10 | - Enabling TypeScript strict mode in projects 11 | - Adding types to existing JavaScript codebases 12 | - Fixing TypeScript type errors systematically 13 | - Creating comprehensive type definitions 14 | - Using TypeScript utility types (Partial, Pick, Omit) 15 | - Implementing type guards and assertions 16 | - Eliminating any types from codebase 17 | - Creating generic, reusable typed functions 18 | - Ensuring null/undefined safety 19 | - Typing complex data structures 20 | - Creating discriminated unions 21 | - Implementing strict function signatures 22 | 23 | ## When to use this skill 24 | 25 | - Ensuring type safety, preventing runtime errors. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Ensuring type safety, preventing runtime errors. 30 | 31 | ## Config 32 | \`\`\`json 33 | { 34 | "compilerOptions": { 35 | "strict": true, 36 | "noUncheckedIndexedAccess": true, 37 | "noImplicitReturns": true 38 | } 39 | } 40 | \`\`\` 41 | 42 | ## Resources 43 | - [TypeScript Handbook](https://www.typescriptlang.org/docs/) 44 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/skills/typescript-strict/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: typescript-strict 3 | description: Write type-safe TypeScript code with strict mode enabled, comprehensive type definitions, proper error handling, and elimination of any types. Use when enabling TypeScript strict mode, adding types to existing JavaScript, fixing type errors, creating type definitions, using utility types, implementing type guards, avoiding any types, creating generic types, or ensuring complete type safety across the codebase. 4 | --- 5 | 6 | # TypeScript Strict - Type Safety Best Practices 7 | 8 | ## When to use this skill 9 | 10 | - Enabling TypeScript strict mode in projects 11 | - Adding types to existing JavaScript codebases 12 | - Fixing TypeScript type errors systematically 13 | - Creating comprehensive type definitions 14 | - Using TypeScript utility types (Partial, Pick, Omit) 15 | - Implementing type guards and assertions 16 | - Eliminating any types from codebase 17 | - Creating generic, reusable typed functions 18 | - Ensuring null/undefined safety 19 | - Typing complex data structures 20 | - Creating discriminated unions 21 | - Implementing strict function signatures 22 | 23 | ## When to use this skill 24 | 25 | - Ensuring type safety, preventing runtime errors. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Ensuring type safety, preventing runtime errors. 30 | 31 | ## Config 32 | \`\`\`json 33 | { 34 | "compilerOptions": { 35 | "strict": true, 36 | "noUncheckedIndexedAccess": true, 37 | "noImplicitReturns": true 38 | } 39 | } 40 | \`\`\` 41 | 42 | ## Resources 43 | - [TypeScript Handbook](https://www.typescriptlang.org/docs/) 44 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/skills/document-processing-xlsx/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: document-processing-xlsx 3 | description: Process, parse, create, and manipulate Excel spreadsheets (.xlsx, .xls) using libraries like xlsx, exceljs, or SheetJS for data import/export and spreadsheet automation. Use when reading Excel files for data import, generating Excel reports, exporting data to spreadsheets, parsing bulk uploads, creating financial reports, manipulating workbooks and worksheets, or building data export features. 4 | --- 5 | 6 | # Document Processing - Excel Files 7 | 8 | ## When to use this skill 9 | 10 | - Reading Excel files for data import and processing 11 | - Generating Excel reports and spreadsheets 12 | - Exporting application data to Excel format 13 | - Parsing bulk data uploads from spreadsheets 14 | - Creating financial reports and statements 15 | - Manipulating workbooks, worksheets, and cells 16 | - Building CSV to Excel converters 17 | - Creating templates for data entry 18 | - Extracting data from uploaded spreadsheets 19 | - Generating dynamic Excel reports with formulas 20 | - Handling large dataset imports from Excel 21 | - Building data export and reporting features 22 | 23 | ## When to use this skill 24 | 25 | - Creating, parsing Excel spreadsheets. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Creating, parsing Excel spreadsheets. 30 | 31 | ## Example 32 | \`\`\`typescript 33 | import * as XLSX from 'xlsx'; 34 | 35 | const ws = XLSX.utils.aoa_to_sheet([[1, 2], [3, 4]]); 36 | const wb = XLSX.utils.book_new(); 37 | XLSX.utils.book_append_sheet(wb, ws, "Sheet1"); 38 | \`\`\` 39 | 40 | ## Resources 41 | - [SheetJS](https://docs.sheetjs.com/) 42 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/skills/document-processing-xlsx/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: document-processing-xlsx 3 | description: Process, parse, create, and manipulate Excel spreadsheets (.xlsx, .xls) using libraries like xlsx, exceljs, or SheetJS for data import/export and spreadsheet automation. Use when reading Excel files for data import, generating Excel reports, exporting data to spreadsheets, parsing bulk uploads, creating financial reports, manipulating workbooks and worksheets, or building data export features. 4 | --- 5 | 6 | # Document Processing - Excel Files 7 | 8 | ## When to use this skill 9 | 10 | - Reading Excel files for data import and processing 11 | - Generating Excel reports and spreadsheets 12 | - Exporting application data to Excel format 13 | - Parsing bulk data uploads from spreadsheets 14 | - Creating financial reports and statements 15 | - Manipulating workbooks, worksheets, and cells 16 | - Building CSV to Excel converters 17 | - Creating templates for data entry 18 | - Extracting data from uploaded spreadsheets 19 | - Generating dynamic Excel reports with formulas 20 | - Handling large dataset imports from Excel 21 | - Building data export and reporting features 22 | 23 | ## When to use this skill 24 | 25 | - Creating, parsing Excel spreadsheets. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Creating, parsing Excel spreadsheets. 30 | 31 | ## Example 32 | \`\`\`typescript 33 | import * as XLSX from 'xlsx'; 34 | 35 | const ws = XLSX.utils.aoa_to_sheet([[1, 2], [3, 4]]); 36 | const wb = XLSX.utils.book_new(); 37 | XLSX.utils.book_append_sheet(wb, ws, "Sheet1"); 38 | \`\`\` 39 | 40 | ## Resources 41 | - [SheetJS](https://docs.sheetjs.com/) 42 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/skills/document-processing-docx/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: document-processing-docx 3 | description: Process, parse, create, and manipulate Microsoft Word (.docx) documents programmatically using libraries like docx or mammoth.js for document generation and data extraction. Use when generating Word documents from templates, extracting text and formatting from .docx files, creating reports and invoices, parsing resumes and forms, converting Word to HTML, creating mail merge documents, or automating document workflows. 4 | --- 5 | 6 | # Document Processing - DOCX Files 7 | 8 | ## When to use this skill 9 | 10 | - Generating Word documents from templates 11 | - Extracting text content from .docx files 12 | - Creating automated reports and invoices 13 | - Parsing resumes and job applications 14 | - Converting Word documents to HTML or Markdown 15 | - Creating mail merge documents programmatically 16 | - Extracting tables and data from Word files 17 | - Automating document generation workflows 18 | - Creating contracts or agreements from templates 19 | - Processing bulk document uploads 20 | - Extracting metadata from Word documents 21 | - Building document management systems 22 | 23 | ## When to use this skill 24 | 25 | - Creating, editing Word documents programmatically. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Creating, editing Word documents programmatically. 30 | 31 | ## Example 32 | \`\`\`typescript 33 | import { Document, Packer, Paragraph } from 'docx'; 34 | 35 | const doc = new Document({ 36 | sections: [{ 37 | children: [new Paragraph("Hello World")] 38 | }] 39 | }); 40 | \`\`\` 41 | 42 | ## Resources 43 | - [docx npm package](https://www.npmjs.com/package/docx) 44 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/skills/document-processing-docx/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: document-processing-docx 3 | description: Process, parse, create, and manipulate Microsoft Word (.docx) documents programmatically using libraries like docx or mammoth.js for document generation and data extraction. Use when generating Word documents from templates, extracting text and formatting from .docx files, creating reports and invoices, parsing resumes and forms, converting Word to HTML, creating mail merge documents, or automating document workflows. 4 | --- 5 | 6 | # Document Processing - DOCX Files 7 | 8 | ## When to use this skill 9 | 10 | - Generating Word documents from templates 11 | - Extracting text content from .docx files 12 | - Creating automated reports and invoices 13 | - Parsing resumes and job applications 14 | - Converting Word documents to HTML or Markdown 15 | - Creating mail merge documents programmatically 16 | - Extracting tables and data from Word files 17 | - Automating document generation workflows 18 | - Creating contracts or agreements from templates 19 | - Processing bulk document uploads 20 | - Extracting metadata from Word documents 21 | - Building document management systems 22 | 23 | ## When to use this skill 24 | 25 | - Creating, editing Word documents programmatically. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Creating, editing Word documents programmatically. 30 | 31 | ## Example 32 | \`\`\`typescript 33 | import { Document, Packer, Paragraph } from 'docx'; 34 | 35 | const doc = new Document({ 36 | sections: [{ 37 | children: [new Paragraph("Hello World")] 38 | }] 39 | }); 40 | \`\`\` 41 | 42 | ## Resources 43 | - [docx npm package](https://www.npmjs.com/package/docx) 44 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/commands/plan-product.md: -------------------------------------------------------------------------------- 1 | ## Product Planning Process 2 | 3 | You are helping to plan and document the mission, roadmap and tech stack for the current product. This will include: 4 | 5 | - **Gathering Information**: The user's product vision, user personas, problems and key features 6 | - **Mission Document**: Take what you've gathered and create a concise mission document 7 | - **Roadmap**: Create a phased development plan with prioritized features 8 | - **Tech stack**: Establish the technical stack used for all aspects of this product's codebase 9 | 10 | This process will create these files in `droidz/product/` directory. 11 | 12 | ### PHASE 1: Gather Product Requirements 13 | 14 | Use the **product-planner** subagent to create comprehensive product documentation. 15 | 16 | IF the user has provided any details in regards to the product idea, its purpose, features list, target users and any other details then provide those to the **product-planner** subagent. 17 | 18 | The product-planner will: 19 | - Confirm (or gather) product idea, features, target users, confirm the tech stack and gather other details 20 | - Create `droidz/product/mission.md` with product vision and strategy 21 | - Create `droidz/product/roadmap.md` with phased development plan 22 | - Create `droidz/product/tech-stack.md` documenting all of this product's tech stack choices 23 | 24 | ### PHASE 2: Inform the user 25 | 26 | After all steps are complete, output the following to inform the user: 27 | 28 | ``` 29 | Your product planning is all set! 30 | 31 | ✅ Product mission: `droidz/product/mission.md` 32 | ✅ Product roadmap: `droidz/product/roadmap.md` 33 | ✅ Product tech stack: `droidz/product/tech-stack.md` 34 | 35 | NEXT STEP 👉 Run `/shape-spec` or `/write-spec` to start work on a feature! 36 | ``` 37 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/commands/plan-product.md: -------------------------------------------------------------------------------- 1 | ## Product Planning Process 2 | 3 | You are helping to plan and document the mission, roadmap and tech stack for the current product. This will include: 4 | 5 | - **Gathering Information**: The user's product vision, user personas, problems and key features 6 | - **Mission Document**: Take what you've gathered and create a concise mission document 7 | - **Roadmap**: Create a phased development plan with prioritized features 8 | - **Tech stack**: Establish the technical stack used for all aspects of this product's codebase 9 | 10 | This process will create these files in `droidz/product/` directory. 11 | 12 | ### PHASE 1: Gather Product Requirements 13 | 14 | Use the **product-planner** subagent to create comprehensive product documentation. 15 | 16 | IF the user has provided any details in regards to the product idea, its purpose, features list, target users and any other details then provide those to the **product-planner** subagent. 17 | 18 | The product-planner will: 19 | - Confirm (or gather) product idea, features, target users, confirm the tech stack and gather other details 20 | - Create `droidz/product/mission.md` with product vision and strategy 21 | - Create `droidz/product/roadmap.md` with phased development plan 22 | - Create `droidz/product/tech-stack.md` documenting all of this product's tech stack choices 23 | 24 | ### PHASE 2: Inform the user 25 | 26 | After all steps are complete, output the following to inform the user: 27 | 28 | ``` 29 | Your product planning is all set! 30 | 31 | ✅ Product mission: `droidz/product/mission.md` 32 | ✅ Product roadmap: `droidz/product/roadmap.md` 33 | ✅ Product tech stack: `droidz/product/tech-stack.md` 34 | 35 | NEXT STEP 👉 Run `/shape-spec` or `/write-spec` to start work on a feature! 36 | ``` 37 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/skills/mcp-builder/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: mcp-builder 3 | description: Build Model Context Protocol (MCP) servers and tools that extend Claude's capabilities with custom functions, data sources, and integrations. Use when creating custom MCP servers, implementing tools for Claude, building integrations with external services, creating data source connectors, implementing custom functions, or extending Claude's capabilities with domain-specific tools. 4 | --- 5 | 6 | # MCP Builder - Model Context Protocol Servers 7 | 8 | ## When to use this skill 9 | 10 | - Creating custom MCP servers for Claude 11 | - Implementing custom tools and functions 12 | - Building integrations with external APIs 13 | - Creating data source connectors 14 | - Implementing domain-specific tools 15 | - Extending Claude with custom capabilities 16 | - Building workflow automation tools 17 | - Creating database query interfaces 18 | - Implementing file system operations 19 | - Building search and retrieval tools 20 | - Creating specialized calculators or converters 21 | - Implementing custom validation logic 22 | 23 | ## When to use this skill 24 | 25 | - Building MCP servers, integrating APIs with LLMs. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Building MCP servers, integrating APIs with LLMs. 30 | 31 | ## Basic MCP Server 32 | \`\`\`typescript 33 | import { Server } from '@modelcontextprotocol/sdk/server/index.js'; 34 | 35 | const server = new Server({ 36 | name: 'my-server', 37 | version: '1.0.0' 38 | }); 39 | 40 | server.setRequestHandler('tools/list', async () => ({ 41 | tools: [{ name: 'search', description: 'Search data' }] 42 | })); 43 | \`\`\` 44 | 45 | ## Resources 46 | - [MCP Docs](https://modelcontextprotocol.io/) 47 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/skills/convex-realtime/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: convex-realtime 3 | description: Implement real-time features using Convex reactive queries that automatically update when data changes, enabling live collaboration, instant updates, and reactive UIs without manual polling. Use when building live dashboards, implementing collaborative editing, creating chat applications, showing real-time notifications, building activity feeds, implementing presence indicators, creating reactive search, or any feature requiring instant data synchronization across clients. 4 | --- 5 | 6 | # Convex Realtime - Live Data Subscriptions 7 | 8 | ## When to use this skill 9 | 10 | - Building live dashboards that update instantly 11 | - Implementing collaborative editing features 12 | - Creating real-time chat applications 13 | - Showing instant notifications to users 14 | - Building activity feeds that update live 15 | - Implementing user presence indicators 16 | - Creating reactive search with live results 17 | - Building multiplayer or collaborative features 18 | - Showing real-time analytics and metrics 19 | - Implementing live document collaboration 20 | - Creating real-time forms with validation 21 | - Building features requiring instant synchronization 22 | 23 | ## When to use this skill 24 | 25 | - Building realtime features, live updates, collaborative apps. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Building realtime features, live updates, collaborative apps. 30 | 31 | ## Auto-Updating Queries 32 | \`\`\`typescript 33 | const messages = useQuery(api.messages.list, { channelId }); 34 | // Automatically updates when data changes! 35 | \`\`\` 36 | 37 | ## Resources 38 | - [Convex Reactivity](https://docs.convex.dev/using/reactivity) 39 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/skills/mcp-builder/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: mcp-builder 3 | description: Build Model Context Protocol (MCP) servers and tools that extend Claude's capabilities with custom functions, data sources, and integrations. Use when creating custom MCP servers, implementing tools for Claude, building integrations with external services, creating data source connectors, implementing custom functions, or extending Claude's capabilities with domain-specific tools. 4 | --- 5 | 6 | # MCP Builder - Model Context Protocol Servers 7 | 8 | ## When to use this skill 9 | 10 | - Creating custom MCP servers for Claude 11 | - Implementing custom tools and functions 12 | - Building integrations with external APIs 13 | - Creating data source connectors 14 | - Implementing domain-specific tools 15 | - Extending Claude with custom capabilities 16 | - Building workflow automation tools 17 | - Creating database query interfaces 18 | - Implementing file system operations 19 | - Building search and retrieval tools 20 | - Creating specialized calculators or converters 21 | - Implementing custom validation logic 22 | 23 | ## When to use this skill 24 | 25 | - Building MCP servers, integrating APIs with LLMs. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Building MCP servers, integrating APIs with LLMs. 30 | 31 | ## Basic MCP Server 32 | \`\`\`typescript 33 | import { Server } from '@modelcontextprotocol/sdk/server/index.js'; 34 | 35 | const server = new Server({ 36 | name: 'my-server', 37 | version: '1.0.0' 38 | }); 39 | 40 | server.setRequestHandler('tools/list', async () => ({ 41 | tools: [{ name: 'search', description: 'Search data' }] 42 | })); 43 | \`\`\` 44 | 45 | ## Resources 46 | - [MCP Docs](https://modelcontextprotocol.io/) 47 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/skills/convex-realtime/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: convex-realtime 3 | description: Implement real-time features using Convex reactive queries that automatically update when data changes, enabling live collaboration, instant updates, and reactive UIs without manual polling. Use when building live dashboards, implementing collaborative editing, creating chat applications, showing real-time notifications, building activity feeds, implementing presence indicators, creating reactive search, or any feature requiring instant data synchronization across clients. 4 | --- 5 | 6 | # Convex Realtime - Live Data Subscriptions 7 | 8 | ## When to use this skill 9 | 10 | - Building live dashboards that update instantly 11 | - Implementing collaborative editing features 12 | - Creating real-time chat applications 13 | - Showing instant notifications to users 14 | - Building activity feeds that update live 15 | - Implementing user presence indicators 16 | - Creating reactive search with live results 17 | - Building multiplayer or collaborative features 18 | - Showing real-time analytics and metrics 19 | - Implementing live document collaboration 20 | - Creating real-time forms with validation 21 | - Building features requiring instant synchronization 22 | 23 | ## When to use this skill 24 | 25 | - Building realtime features, live updates, collaborative apps. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Building realtime features, live updates, collaborative apps. 30 | 31 | ## Auto-Updating Queries 32 | \`\`\`typescript 33 | const messages = useQuery(api.messages.list, { channelId }); 34 | // Automatically updates when data changes! 35 | \`\`\` 36 | 37 | ## Resources 38 | - [Convex Reactivity](https://docs.convex.dev/using/reactivity) 39 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/skills/tailwind-design-system/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: tailwind-design-system 3 | description: Create consistent, scalable design systems using Tailwind CSS utility classes with custom themes, design tokens, and responsive design patterns. Use when building design systems, implementing custom themes, creating reusable utility patterns, configuring Tailwind theme extensions, implementing dark mode, building responsive layouts, creating design tokens, using arbitrary values, or establishing consistent spacing and typography scales. 4 | --- 5 | 6 | # Tailwind CSS - Utility-First Styling 7 | 8 | ## When to use this skill 9 | 10 | - Building design systems with Tailwind CSS 11 | - Implementing custom themes and design tokens 12 | - Creating reusable utility class patterns 13 | - Configuring Tailwind theme extensions 14 | - Implementing light and dark mode themes 15 | - Building responsive layouts with Tailwind grid/flexbox 16 | - Creating consistent spacing and typography scales 17 | - Using arbitrary values for one-off styles 18 | - Implementing custom color palettes 19 | - Building component variants with Tailwind 20 | - Creating animation and transition systems 21 | - Establishing design consistency across projects 22 | 23 | ## When to use this skill 24 | 25 | - Styling with Tailwind, creating design systems, responsive layouts. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Styling with Tailwind, creating design systems, responsive layouts. 30 | 31 | ## Core Pattern 32 | \`\`\`jsx 33 |
34 |

Title

35 |
36 | \`\`\` 37 | 38 | ## Resources 39 | - [Tailwind CSS](https://tailwindcss.com/) 40 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/skills/tailwind-design-system/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: tailwind-design-system 3 | description: Create consistent, scalable design systems using Tailwind CSS utility classes with custom themes, design tokens, and responsive design patterns. Use when building design systems, implementing custom themes, creating reusable utility patterns, configuring Tailwind theme extensions, implementing dark mode, building responsive layouts, creating design tokens, using arbitrary values, or establishing consistent spacing and typography scales. 4 | --- 5 | 6 | # Tailwind CSS - Utility-First Styling 7 | 8 | ## When to use this skill 9 | 10 | - Building design systems with Tailwind CSS 11 | - Implementing custom themes and design tokens 12 | - Creating reusable utility class patterns 13 | - Configuring Tailwind theme extensions 14 | - Implementing light and dark mode themes 15 | - Building responsive layouts with Tailwind grid/flexbox 16 | - Creating consistent spacing and typography scales 17 | - Using arbitrary values for one-off styles 18 | - Implementing custom color palettes 19 | - Building component variants with Tailwind 20 | - Creating animation and transition systems 21 | - Establishing design consistency across projects 22 | 23 | ## When to use this skill 24 | 25 | - Styling with Tailwind, creating design systems, responsive layouts. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Styling with Tailwind, creating design systems, responsive layouts. 30 | 31 | ## Core Pattern 32 | \`\`\`jsx 33 |
34 |

Title

35 |
36 | \`\`\` 37 | 38 | ## Resources 39 | - [Tailwind CSS](https://tailwindcss.com/) 40 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/skills/shadcn-ui-components/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: shadcn-ui-components 3 | description: Build beautiful, accessible UI components using shadcn/ui library with Radix UI primitives and Tailwind CSS styling that you own and can customize. Use when creating accessible component libraries, implementing common UI patterns (dialogs, dropdowns, tooltips), building forms with validation, creating data tables, implementing command palettes, using Radix UI primitives, customizing components with Tailwind, or building design systems with full ownership of code. 4 | --- 5 | 6 | # Shadcn UI - Reusable Component Library 7 | 8 | ## When to use this skill 9 | 10 | - Creating accessible UI component libraries 11 | - Implementing dialogs, dropdowns, tooltips, popovers 12 | - Building forms with validation and error handling 13 | - Creating sortable, filterable data tables 14 | - Implementing command palettes (Cmd+K interfaces) 15 | - Using Radix UI primitives with custom styling 16 | - Customizing components with Tailwind CSS 17 | - Building design systems you fully own 18 | - Implementing accessible keyboard navigation 19 | - Creating consistent, themeable components 20 | - Using pre-built accessible patterns 21 | - Building components that match your design system 22 | 23 | ## When to use this skill 24 | 25 | - Building UI with Shadcn, Radix UI primitives, Tailwind CSS. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Building UI with Shadcn, Radix UI primitives, Tailwind CSS. 30 | 31 | ## Installation 32 | \`\`\`bash 33 | npx shadcn-ui@latest add button 34 | \`\`\` 35 | 36 | ## Usage 37 | \`\`\`typescript 38 | import { Button } from '@/components/ui/button'; 39 | 40 | 41 | \`\`\` 42 | 43 | ## Resources 44 | - [Shadcn UI](https://ui.shadcn.com/) 45 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/skills/shadcn-ui-components/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: shadcn-ui-components 3 | description: Build beautiful, accessible UI components using shadcn/ui library with Radix UI primitives and Tailwind CSS styling that you own and can customize. Use when creating accessible component libraries, implementing common UI patterns (dialogs, dropdowns, tooltips), building forms with validation, creating data tables, implementing command palettes, using Radix UI primitives, customizing components with Tailwind, or building design systems with full ownership of code. 4 | --- 5 | 6 | # Shadcn UI - Reusable Component Library 7 | 8 | ## When to use this skill 9 | 10 | - Creating accessible UI component libraries 11 | - Implementing dialogs, dropdowns, tooltips, popovers 12 | - Building forms with validation and error handling 13 | - Creating sortable, filterable data tables 14 | - Implementing command palettes (Cmd+K interfaces) 15 | - Using Radix UI primitives with custom styling 16 | - Customizing components with Tailwind CSS 17 | - Building design systems you fully own 18 | - Implementing accessible keyboard navigation 19 | - Creating consistent, themeable components 20 | - Using pre-built accessible patterns 21 | - Building components that match your design system 22 | 23 | ## When to use this skill 24 | 25 | - Building UI with Shadcn, Radix UI primitives, Tailwind CSS. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Building UI with Shadcn, Radix UI primitives, Tailwind CSS. 30 | 31 | ## Installation 32 | \`\`\`bash 33 | npx shadcn-ui@latest add button 34 | \`\`\` 35 | 36 | ## Usage 37 | \`\`\`typescript 38 | import { Button } from '@/components/ui/button'; 39 | 40 | 41 | \`\`\` 42 | 43 | ## Resources 44 | - [Shadcn UI](https://ui.shadcn.com/) 45 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/skills/data-migration/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: data-migration 3 | description: Plan and execute database migrations, data transformations, and system migrations safely with rollback strategies and data integrity validation. Use when migrating databases, transforming data schemas, moving between database systems, implementing versioned migrations, handling data transformations, ensuring data integrity, or planning zero-downtime migrations. 4 | --- 5 | 6 | # Data Migration - Safe Schema Changes 7 | 8 | ## When to use this skill 9 | 10 | - Migrating database schemas and structures 11 | - Transforming data between formats 12 | - Moving data between database systems 13 | - Implementing versioned database migrations 14 | - Handling data transformations during migrations 15 | - Ensuring data integrity and validation 16 | - Planning zero-downtime migrations 17 | - Rolling back failed migrations safely 18 | - Migrating from legacy systems 19 | - Implementing data backfill strategies 20 | - Testing migrations in staging environments 21 | - Creating migration rollback procedures 22 | 23 | ## When to use this skill 24 | 25 | - Migrating data between schemas, zero-downtime deployments. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Migrating data between schemas, zero-downtime deployments. 30 | 31 | ## Process 32 | 1. Add new column 33 | 2. Dual-write to old & new 34 | 3. Backfill historical data 35 | 4. Switch reads to new column 36 | 5. Remove old column 37 | 38 | ## Example 39 | \`\`\`sql 40 | -- Step 1: Add column 41 | ALTER TABLE users ADD COLUMN email_new VARCHAR(255); 42 | 43 | -- Step 2: Backfill 44 | UPDATE users SET email_new = email WHERE email_new IS NULL; 45 | 46 | -- Step 3: Swap 47 | ALTER TABLE users DROP COLUMN email; 48 | ALTER TABLE users RENAME COLUMN email_new TO email; 49 | \`\`\` 50 | 51 | ## Resources 52 | - [Database Migrations](https://www.prisma.io/docs/concepts/components/prisma-migrate) 53 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/skills/data-migration/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: data-migration 3 | description: Plan and execute database migrations, data transformations, and system migrations safely with rollback strategies and data integrity validation. Use when migrating databases, transforming data schemas, moving between database systems, implementing versioned migrations, handling data transformations, ensuring data integrity, or planning zero-downtime migrations. 4 | --- 5 | 6 | # Data Migration - Safe Schema Changes 7 | 8 | ## When to use this skill 9 | 10 | - Migrating database schemas and structures 11 | - Transforming data between formats 12 | - Moving data between database systems 13 | - Implementing versioned database migrations 14 | - Handling data transformations during migrations 15 | - Ensuring data integrity and validation 16 | - Planning zero-downtime migrations 17 | - Rolling back failed migrations safely 18 | - Migrating from legacy systems 19 | - Implementing data backfill strategies 20 | - Testing migrations in staging environments 21 | - Creating migration rollback procedures 22 | 23 | ## When to use this skill 24 | 25 | - Migrating data between schemas, zero-downtime deployments. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Migrating data between schemas, zero-downtime deployments. 30 | 31 | ## Process 32 | 1. Add new column 33 | 2. Dual-write to old & new 34 | 3. Backfill historical data 35 | 4. Switch reads to new column 36 | 5. Remove old column 37 | 38 | ## Example 39 | \`\`\`sql 40 | -- Step 1: Add column 41 | ALTER TABLE users ADD COLUMN email_new VARCHAR(255); 42 | 43 | -- Step 2: Backfill 44 | UPDATE users SET email_new = email WHERE email_new IS NULL; 45 | 46 | -- Step 3: Swap 47 | ALTER TABLE users DROP COLUMN email; 48 | ALTER TABLE users RENAME COLUMN email_new TO email; 49 | \`\`\` 50 | 51 | ## Resources 52 | - [Database Migrations](https://www.prisma.io/docs/concepts/components/prisma-migrate) 53 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/skills/playwright-automation/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: playwright-automation 3 | description: Automate browser testing, web scraping, and user workflow testing with Playwright across multiple browsers. Use when writing end-to-end tests for web applications, automating repetitive browser tasks, scraping data from websites, testing across Chrome/Firefox/Safari, taking screenshots for visual regression testing, testing authentication flows, filling and submitting forms programmatically, testing responsive designs across viewports, or any browser automation requiring reliable, cross-browser testing capabilities. 4 | --- 5 | 6 | # Playwright Automation - Browser Testing 7 | 8 | ## When to use this skill 9 | 10 | - Writing end-to-end tests for web applications 11 | - Automating repetitive browser tasks and workflows 12 | - Scraping data from websites programmatically 13 | - Testing across Chrome, Firefox, Safari, and Edge browsers 14 | - Taking screenshots for visual regression testing 15 | - Testing authentication and login flows 16 | - Filling and submitting forms automatically 17 | - Testing responsive designs across different viewports 18 | - Simulating user interactions (clicks, typing, navigation) 19 | - Testing file uploads and downloads 20 | - Capturing network requests and responses 21 | - Testing Single Page Applications (SPAs) 22 | - Any browser automation requiring reliable cross-browser support 23 | 24 | ## When to use this skill 25 | 26 | - E2E testing, browser automation, web scraping. 27 | - When working on related tasks or features 28 | - During development that requires this expertise 29 | 30 | **Use when**: E2E testing, browser automation, web scraping. 31 | 32 | ## Basic Test 33 | \`\`\`typescript 34 | import { test, expect } from '@playwright/test'; 35 | 36 | test('homepage', async ({ page }) => { 37 | await page.goto('/'); 38 | await expect(page.getByRole('heading')).toBeVisible(); 39 | }); 40 | \`\`\` 41 | 42 | ## Resources 43 | - [Playwright](https://playwright.dev/) 44 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/skills/playwright-automation/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: playwright-automation 3 | description: Automate browser testing, web scraping, and user workflow testing with Playwright across multiple browsers. Use when writing end-to-end tests for web applications, automating repetitive browser tasks, scraping data from websites, testing across Chrome/Firefox/Safari, taking screenshots for visual regression testing, testing authentication flows, filling and submitting forms programmatically, testing responsive designs across viewports, or any browser automation requiring reliable, cross-browser testing capabilities. 4 | --- 5 | 6 | # Playwright Automation - Browser Testing 7 | 8 | ## When to use this skill 9 | 10 | - Writing end-to-end tests for web applications 11 | - Automating repetitive browser tasks and workflows 12 | - Scraping data from websites programmatically 13 | - Testing across Chrome, Firefox, Safari, and Edge browsers 14 | - Taking screenshots for visual regression testing 15 | - Testing authentication and login flows 16 | - Filling and submitting forms automatically 17 | - Testing responsive designs across different viewports 18 | - Simulating user interactions (clicks, typing, navigation) 19 | - Testing file uploads and downloads 20 | - Capturing network requests and responses 21 | - Testing Single Page Applications (SPAs) 22 | - Any browser automation requiring reliable cross-browser support 23 | 24 | ## When to use this skill 25 | 26 | - E2E testing, browser automation, web scraping. 27 | - When working on related tasks or features 28 | - During development that requires this expertise 29 | 30 | **Use when**: E2E testing, browser automation, web scraping. 31 | 32 | ## Basic Test 33 | \`\`\`typescript 34 | import { test, expect } from '@playwright/test'; 35 | 36 | test('homepage', async ({ page }) => { 37 | await page.goto('/'); 38 | await expect(page.getByRole('heading')).toBeVisible(); 39 | }); 40 | \`\`\` 41 | 42 | ## Resources 43 | - [Playwright](https://playwright.dev/) 44 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/commands/2-create-tasks-list.md: -------------------------------------------------------------------------------- 1 | Now that you have the spec.md AND/OR requirements.md, please break those down into an actionable tasks list with strategic grouping and ordering, by following these instructions: 2 | 3 | ## Display confirmation and next step 4 | 5 | Display the following message to the user: 6 | 7 | ``` 8 | The tasks list has created at `droidz/specs/[this-spec]/tasks.md`. 9 | 10 | Review it closely to make sure it all looks good. 11 | 12 | NEXT STEP 👉 Run `/implement-tasks` (simple, effective) or `/orchestrate-tasks` (advanced, powerful) to start building! 13 | ``` 14 | 15 | ## User Standards & Preferences Compliance 16 | 17 | IMPORTANT: Ensure that the tasks list is ALIGNED and DOES NOT CONFLICT with the user's preferences and standards as detailed in the following files: 18 | 19 | ### Standards Loading Instructions 20 | 21 | Before creating the tasks list, check for and load project standards: 22 | 23 | 1. **Check if standards exist**: Look for `droidz/standards/` directory 24 | 2. **If standards exist**, **read ALL standards files recursively**: 25 | - Use glob pattern `droidz/standards/**/*.md` to find all markdown files 26 | - This includes all subdirectories (global, frontend, backend, infrastructure, and any custom directories the user has created) 27 | - Read every `.md` file found in the standards directory tree 28 | 29 | 3. **Apply ALL loaded standards to task creation** by ensuring: 30 | - Tasks follow documented coding principles and patterns 31 | - Task groupings align with documented architectural boundaries 32 | - Sub-tasks include necessary standards compliance (e.g., testing requirements) 33 | - Tasks don't propose approaches that conflict with established conventions 34 | - Error handling, security, and other concerns from standards are reflected in relevant tasks 35 | 36 | If no standards directory exists, proceed normally but note to the user: 37 | ``` 38 | ℹ️ No project standards found. Consider running /shape-standards to establish conventions. 39 | ``` 40 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/commands/2-create-tasks-list.md: -------------------------------------------------------------------------------- 1 | Now that you have the spec.md AND/OR requirements.md, please break those down into an actionable tasks list with strategic grouping and ordering, by following these instructions: 2 | 3 | ## Display confirmation and next step 4 | 5 | Display the following message to the user: 6 | 7 | ``` 8 | The tasks list has created at `droidz/specs/[this-spec]/tasks.md`. 9 | 10 | Review it closely to make sure it all looks good. 11 | 12 | NEXT STEP 👉 Run `/implement-tasks` (simple, effective) or `/orchestrate-tasks` (advanced, powerful) to start building! 13 | ``` 14 | 15 | ## User Standards & Preferences Compliance 16 | 17 | IMPORTANT: Ensure that the tasks list is ALIGNED and DOES NOT CONFLICT with the user's preferences and standards as detailed in the following files: 18 | 19 | ### Standards Loading Instructions 20 | 21 | Before creating the tasks list, check for and load project standards: 22 | 23 | 1. **Check if standards exist**: Look for `droidz/standards/` directory 24 | 2. **If standards exist**, **read ALL standards files recursively**: 25 | - Use glob pattern `droidz/standards/**/*.md` to find all markdown files 26 | - This includes all subdirectories (global, frontend, backend, infrastructure, and any custom directories the user has created) 27 | - Read every `.md` file found in the standards directory tree 28 | 29 | 3. **Apply ALL loaded standards to task creation** by ensuring: 30 | - Tasks follow documented coding principles and patterns 31 | - Task groupings align with documented architectural boundaries 32 | - Sub-tasks include necessary standards compliance (e.g., testing requirements) 33 | - Tasks don't propose approaches that conflict with established conventions 34 | - Error handling, security, and other concerns from standards are reflected in relevant tasks 35 | 36 | If no standards directory exists, proceed normally but note to the user: 37 | ``` 38 | ℹ️ No project standards found. Consider running /shape-standards to establish conventions. 39 | ``` 40 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/skills/skill-creator/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: skill-creator 3 | description: Create well-structured, comprehensive Claude skills with clear activation criteria, detailed descriptions, usage examples, and proper documentation following best practices. Use when documenting new workflows, creating reusable skill patterns, establishing coding standards as skills, building team knowledge base, or expanding the skills library with new capabilities. 4 | --- 5 | 6 | # Skill Creator - Meta-Skill for Creating Skills 7 | 8 | ## When to use this skill 9 | 10 | - Documenting new workflows as skills 11 | - Creating reusable skill patterns 12 | - Establishing coding standards as skills 13 | - Building team knowledge bases 14 | - Expanding skills library with new capabilities 15 | - Documenting best practices systematically 16 | - Creating activation-oriented descriptions 17 | - Writing comprehensive usage examples 18 | - Structuring skills following best practices 19 | - Creating skills from tribal knowledge 20 | - Documenting domain-specific expertise 21 | - Building organizational skill libraries 22 | 23 | ## When to use this skill 24 | 25 | - Creating new Claude skills, documenting workflows. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Creating new Claude skills, documenting workflows. 30 | 31 | ## Structure 32 | 1. **Title** - Clear, descriptive 33 | 2. **Use when** - Activation criteria 34 | 3. **Core Principles** - 3-5 key concepts 35 | 4. **Examples** - Practical code/patterns 36 | 5. **Resources** - External links 37 | 38 | ## Template 39 | \`\`\`markdown 40 | # Skill Name - Brief Description 41 | 42 | **Use when**: Clear trigger conditions 43 | 44 | ## Core Concepts 45 | - Concept 1 46 | - Concept 2 47 | 48 | ## Example 49 | \\`\\`\\`typescript 50 | // Code example 51 | \\`\\`\\` 52 | 53 | ## Resources 54 | - [Link](https://example.com) 55 | \`\`\` 56 | 57 | ## Resources 58 | - [Claude Skills Documentation](https://docs.anthropic.com/claude/docs/skills) 59 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/skills/skill-creator/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: skill-creator 3 | description: Create well-structured, comprehensive Claude skills with clear activation criteria, detailed descriptions, usage examples, and proper documentation following best practices. Use when documenting new workflows, creating reusable skill patterns, establishing coding standards as skills, building team knowledge base, or expanding the skills library with new capabilities. 4 | --- 5 | 6 | # Skill Creator - Meta-Skill for Creating Skills 7 | 8 | ## When to use this skill 9 | 10 | - Documenting new workflows as skills 11 | - Creating reusable skill patterns 12 | - Establishing coding standards as skills 13 | - Building team knowledge bases 14 | - Expanding skills library with new capabilities 15 | - Documenting best practices systematically 16 | - Creating activation-oriented descriptions 17 | - Writing comprehensive usage examples 18 | - Structuring skills following best practices 19 | - Creating skills from tribal knowledge 20 | - Documenting domain-specific expertise 21 | - Building organizational skill libraries 22 | 23 | ## When to use this skill 24 | 25 | - Creating new Claude skills, documenting workflows. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Creating new Claude skills, documenting workflows. 30 | 31 | ## Structure 32 | 1. **Title** - Clear, descriptive 33 | 2. **Use when** - Activation criteria 34 | 3. **Core Principles** - 3-5 key concepts 35 | 4. **Examples** - Practical code/patterns 36 | 5. **Resources** - External links 37 | 38 | ## Template 39 | \`\`\`markdown 40 | # Skill Name - Brief Description 41 | 42 | **Use when**: Clear trigger conditions 43 | 44 | ## Core Concepts 45 | - Concept 1 46 | - Concept 2 47 | 48 | ## Example 49 | \\`\\`\\`typescript 50 | // Code example 51 | \\`\\`\\` 52 | 53 | ## Resources 54 | - [Link](https://example.com) 55 | \`\`\` 56 | 57 | ## Resources 58 | - [Claude Skills Documentation](https://docs.anthropic.com/claude/docs/skills) 59 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/commands/write-spec.md: -------------------------------------------------------------------------------- 1 | # Spec Writing Process 2 | 3 | You are creating a comprehensive specification for a new feature. 4 | 5 | ## User Standards & Preferences Compliance 6 | 7 | **IMPORTANT**: Before writing the spec, you MUST check for and adhere to the user's project standards. 8 | 9 | ### Step 0: Load Standards 10 | 11 | Check if standards exist and load them: 12 | 13 | 1. Check for standards directory: `droidz/standards/` 14 | 2. If it exists, **read ALL standards files recursively**: 15 | - Use glob pattern `droidz/standards/**/*.md` to find all markdown files 16 | - This includes all subdirectories (global, frontend, backend, infrastructure, and any custom directories the user has created) 17 | - Read every `.md` file found in the standards directory tree 18 | 19 | 3. Ensure the specification document adheres to ALL loaded standards: 20 | - Follows documented coding principles and patterns 21 | - References appropriate standards where relevant 22 | - Does not propose approaches that conflict with established conventions 23 | - Aligns technical decisions with documented best practices 24 | 25 | If no standards directory exists, proceed without standards constraints but inform the user: 26 | ``` 27 | ℹ️ No project standards found at droidz/standards/ 28 | Consider running /shape-standards to establish project conventions. 29 | ``` 30 | 31 | --- 32 | 33 | Use the **spec-writer** subagent to create the specification document for this spec: 34 | 35 | Provide the spec-writer with: 36 | - The spec folder path (find the current one or the most recent in `droidz/specs/*/`) 37 | - The requirements from `planning/requirements.md` 38 | - Any visual assets in `planning/visuals/` 39 | 40 | The spec-writer will create `spec.md` inside the spec folder. 41 | 42 | Once the spec-writer has created `spec.md` output the following to inform the user: 43 | 44 | ``` 45 | Your spec.md is ready! 46 | 47 | ✅ Spec document created: `[spec-path]` 48 | 49 | NEXT STEP 👉 Run `/create-tasks` to generate your tasks list for this spec. 50 | ``` 51 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/skills/react-server-actions/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: react-server-actions 3 | description: Implement React Server Actions in Next.js 14+ for secure, progressively enhanced form handling and server mutations without API routes. Use when handling form submissions, performing server-side mutations, implementing progressive enhancement, creating actions that work without JavaScript, validating data on the server, revalidating cached data after mutations, handling file uploads server-side, implementing optimistic UI updates, or building forms that gracefully degrade without client-side JavaScript. 4 | --- 5 | 6 | # React Server Actions - Form Handling 7 | 8 | ## When to use this skill 9 | 10 | - Handling form submissions in Next.js 14+ applications 11 | - Performing server-side data mutations without API routes 12 | - Implementing progressive enhancement for forms 13 | - Creating actions that work without client-side JavaScript 14 | - Validating form data securely on the server 15 | - Revalidating Next.js cache after data mutations 16 | - Handling file uploads with server-side processing 17 | - Implementing optimistic UI updates with useOptimistic 18 | - Building accessible forms with server-first architecture 19 | - Integrating with database operations directly 20 | - Managing form state with useFormState hook 21 | - Creating secure mutations with server-only code 22 | 23 | ## When to use this skill 24 | 25 | - Implementing forms, mutations in Next.js App Router. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Implementing forms, mutations in Next.js App Router. 30 | 31 | ## Server Action 32 | \`\`\`typescript 33 | 'use server'; 34 | 35 | export async function createPost(formData: FormData) { 36 | const title = formData.get('title'); 37 | await db.post.create({ data: { title } }); 38 | revalidatePath('/posts'); 39 | } 40 | \`\`\` 41 | 42 | ## Resources 43 | - [Server Actions](https://nextjs.org/docs/app/building-your-application/data-fetching/server-actions-and-mutations) 44 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/commands/write-spec.md: -------------------------------------------------------------------------------- 1 | # Spec Writing Process 2 | 3 | You are creating a comprehensive specification for a new feature. 4 | 5 | ## User Standards & Preferences Compliance 6 | 7 | **IMPORTANT**: Before writing the spec, you MUST check for and adhere to the user's project standards. 8 | 9 | ### Step 0: Load Standards 10 | 11 | Check if standards exist and load them: 12 | 13 | 1. Check for standards directory: `droidz/standards/` 14 | 2. If it exists, **read ALL standards files recursively**: 15 | - Use glob pattern `droidz/standards/**/*.md` to find all markdown files 16 | - This includes all subdirectories (global, frontend, backend, infrastructure, and any custom directories the user has created) 17 | - Read every `.md` file found in the standards directory tree 18 | 19 | 3. Ensure the specification document adheres to ALL loaded standards: 20 | - Follows documented coding principles and patterns 21 | - References appropriate standards where relevant 22 | - Does not propose approaches that conflict with established conventions 23 | - Aligns technical decisions with documented best practices 24 | 25 | If no standards directory exists, proceed without standards constraints but inform the user: 26 | ``` 27 | ℹ️ No project standards found at droidz/standards/ 28 | Consider running /shape-standards to establish project conventions. 29 | ``` 30 | 31 | --- 32 | 33 | Use the **spec-writer** subagent to create the specification document for this spec: 34 | 35 | Provide the spec-writer with: 36 | - The spec folder path (find the current one or the most recent in `droidz/specs/*/`) 37 | - The requirements from `planning/requirements.md` 38 | - Any visual assets in `planning/visuals/` 39 | 40 | The spec-writer will create `spec.md` inside the spec folder. 41 | 42 | Once the spec-writer has created `spec.md` output the following to inform the user: 43 | 44 | ``` 45 | Your spec.md is ready! 46 | 47 | ✅ Spec document created: `[spec-path]` 48 | 49 | NEXT STEP 👉 Run `/create-tasks` to generate your tasks list for this spec. 50 | ``` 51 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/skills/react-server-actions/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: react-server-actions 3 | description: Implement React Server Actions in Next.js 14+ for secure, progressively enhanced form handling and server mutations without API routes. Use when handling form submissions, performing server-side mutations, implementing progressive enhancement, creating actions that work without JavaScript, validating data on the server, revalidating cached data after mutations, handling file uploads server-side, implementing optimistic UI updates, or building forms that gracefully degrade without client-side JavaScript. 4 | --- 5 | 6 | # React Server Actions - Form Handling 7 | 8 | ## When to use this skill 9 | 10 | - Handling form submissions in Next.js 14+ applications 11 | - Performing server-side data mutations without API routes 12 | - Implementing progressive enhancement for forms 13 | - Creating actions that work without client-side JavaScript 14 | - Validating form data securely on the server 15 | - Revalidating Next.js cache after data mutations 16 | - Handling file uploads with server-side processing 17 | - Implementing optimistic UI updates with useOptimistic 18 | - Building accessible forms with server-first architecture 19 | - Integrating with database operations directly 20 | - Managing form state with useFormState hook 21 | - Creating secure mutations with server-only code 22 | 23 | ## When to use this skill 24 | 25 | - Implementing forms, mutations in Next.js App Router. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Implementing forms, mutations in Next.js App Router. 30 | 31 | ## Server Action 32 | \`\`\`typescript 33 | 'use server'; 34 | 35 | export async function createPost(formData: FormData) { 36 | const title = formData.get('title'); 37 | await db.post.create({ data: { title } }); 38 | revalidatePath('/posts'); 39 | } 40 | \`\`\` 41 | 42 | ## Resources 43 | - [Server Actions](https://nextjs.org/docs/app/building-your-application/data-fetching/server-actions-and-mutations) 44 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/commands/2-shape-spec.md: -------------------------------------------------------------------------------- 1 | Now that you've initialized the folder for this new spec, proceed with the research phase. 2 | 3 | Follow these instructions for researching this spec's requirements: 4 | 5 | ## Display confirmation and next step 6 | 7 | Once you've completed your research and documented it, output the following message: 8 | 9 | ``` 10 | ✅ I have documented this spec's research and requirements in `droidz/specs/[this-spec]/planning`. 11 | 12 | Next step: Run the command, `1-create-spec.md`. 13 | ``` 14 | 15 | After all steps complete, inform the user: 16 | 17 | ``` 18 | Spec initialized successfully! 19 | 20 | ✅ Spec folder created: `[spec-path]` 21 | ✅ Requirements gathered 22 | ✅ Visual assets: [Found X files / No files provided] 23 | 24 | 👉 Run `/write-spec` to create the spec.md document. 25 | ``` 26 | 27 | ## User Standards & Preferences Compliance 28 | 29 | IMPORTANT: Ensure that your research questions and insights are ALIGNED and DOES NOT CONFLICT with the user's preferences and standards as detailed in the following files: 30 | 31 | ### Standards Loading Instructions 32 | 33 | Before proceeding, check for and load project standards: 34 | 35 | 1. **Check if standards exist**: Look for `droidz/standards/` directory 36 | 2. **If standards exist**, **read ALL standards files recursively**: 37 | - Use glob pattern `droidz/standards/**/*.md` to find all markdown files 38 | - This includes all subdirectories (global, frontend, backend, infrastructure, and any custom directories the user has created) 39 | - Read every `.md` file found in the standards directory tree 40 | 41 | 3. **Apply ALL loaded standards to your research** by ensuring: 42 | - Questions align with established architectural patterns 43 | - Proposed approaches don't conflict with documented conventions 44 | - Requirements gathering considers existing coding principles 45 | - Design decisions follow documented best practices 46 | 47 | If no standards directory exists, proceed normally but note to the user: 48 | ``` 49 | ℹ️ No project standards found. Consider running /shape-standards to establish conventions. 50 | ``` 51 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/commands/2-shape-spec.md: -------------------------------------------------------------------------------- 1 | Now that you've initialized the folder for this new spec, proceed with the research phase. 2 | 3 | Follow these instructions for researching this spec's requirements: 4 | 5 | ## Display confirmation and next step 6 | 7 | Once you've completed your research and documented it, output the following message: 8 | 9 | ``` 10 | ✅ I have documented this spec's research and requirements in `droidz/specs/[this-spec]/planning`. 11 | 12 | Next step: Run the command, `1-create-spec.md`. 13 | ``` 14 | 15 | After all steps complete, inform the user: 16 | 17 | ``` 18 | Spec initialized successfully! 19 | 20 | ✅ Spec folder created: `[spec-path]` 21 | ✅ Requirements gathered 22 | ✅ Visual assets: [Found X files / No files provided] 23 | 24 | 👉 Run `/write-spec` to create the spec.md document. 25 | ``` 26 | 27 | ## User Standards & Preferences Compliance 28 | 29 | IMPORTANT: Ensure that your research questions and insights are ALIGNED and DOES NOT CONFLICT with the user's preferences and standards as detailed in the following files: 30 | 31 | ### Standards Loading Instructions 32 | 33 | Before proceeding, check for and load project standards: 34 | 35 | 1. **Check if standards exist**: Look for `droidz/standards/` directory 36 | 2. **If standards exist**, **read ALL standards files recursively**: 37 | - Use glob pattern `droidz/standards/**/*.md` to find all markdown files 38 | - This includes all subdirectories (global, frontend, backend, infrastructure, and any custom directories the user has created) 39 | - Read every `.md` file found in the standards directory tree 40 | 41 | 3. **Apply ALL loaded standards to your research** by ensuring: 42 | - Questions align with established architectural patterns 43 | - Proposed approaches don't conflict with documented conventions 44 | - Requirements gathering considers existing coding principles 45 | - Design decisions follow documented best practices 46 | 47 | If no standards directory exists, proceed normally but note to the user: 48 | ``` 49 | ℹ️ No project standards found. Consider running /shape-standards to establish conventions. 50 | ``` 51 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/skills/monitoring-observability/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: monitoring-observability 3 | description: Implement comprehensive monitoring, logging, metrics, tracing, and alerting for production applications to ensure reliability and quick incident response. Use when setting up application monitoring, implementing structured logging, creating metrics and dashboards, setting up alerts, implementing distributed tracing, monitoring performance, tracking errors, or building observability into applications. 4 | --- 5 | 6 | # Monitoring & Observability - System Health 7 | 8 | ## When to use this skill 9 | 10 | - Setting up application monitoring systems 11 | - Implementing structured logging 12 | - Creating metrics and performance dashboards 13 | - Setting up alerts for critical issues 14 | - Implementing distributed tracing 15 | - Monitoring API performance and latency 16 | - Tracking error rates and exceptions 17 | - Building observability into applications 18 | - Setting up log aggregation 19 | - Creating SLO/SLA monitoring 20 | - Implementing health checks 21 | - Building incident detection systems 22 | 23 | ## When to use this skill 24 | 25 | - Setting up metrics, alerts, dashboards. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Setting up metrics, alerts, dashboards. 30 | 31 | ## Three Pillars 32 | 1. **Metrics** - Time-series data (CPU, memory, requests/sec) 33 | 2. **Logs** - Event records with context 34 | 3. **Traces** - Request flow through system 35 | 36 | ## Example 37 | \`\`\`typescript 38 | import * as Sentry from '@sentry/node'; 39 | import { metrics } from './metrics'; 40 | 41 | app.use((req, res, next) => { 42 | const start = Date.now(); 43 | res.on('finish', () => { 44 | metrics.histogram('request_duration', Date.now() - start, { 45 | method: req.method, 46 | route: req.route?.path, 47 | status: res.statusCode 48 | }); 49 | }); 50 | next(); 51 | }); 52 | \`\`\` 53 | 54 | ## Resources 55 | - [Observability Guide](https://www.honeycomb.io/what-is-observability) 56 | - [Grafana](https://grafana.com/) 57 | - [Sentry](https://sentry.io/) 58 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/skills/monitoring-observability/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: monitoring-observability 3 | description: Implement comprehensive monitoring, logging, metrics, tracing, and alerting for production applications to ensure reliability and quick incident response. Use when setting up application monitoring, implementing structured logging, creating metrics and dashboards, setting up alerts, implementing distributed tracing, monitoring performance, tracking errors, or building observability into applications. 4 | --- 5 | 6 | # Monitoring & Observability - System Health 7 | 8 | ## When to use this skill 9 | 10 | - Setting up application monitoring systems 11 | - Implementing structured logging 12 | - Creating metrics and performance dashboards 13 | - Setting up alerts for critical issues 14 | - Implementing distributed tracing 15 | - Monitoring API performance and latency 16 | - Tracking error rates and exceptions 17 | - Building observability into applications 18 | - Setting up log aggregation 19 | - Creating SLO/SLA monitoring 20 | - Implementing health checks 21 | - Building incident detection systems 22 | 23 | ## When to use this skill 24 | 25 | - Setting up metrics, alerts, dashboards. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Setting up metrics, alerts, dashboards. 30 | 31 | ## Three Pillars 32 | 1. **Metrics** - Time-series data (CPU, memory, requests/sec) 33 | 2. **Logs** - Event records with context 34 | 3. **Traces** - Request flow through system 35 | 36 | ## Example 37 | \`\`\`typescript 38 | import * as Sentry from '@sentry/node'; 39 | import { metrics } from './metrics'; 40 | 41 | app.use((req, res, next) => { 42 | const start = Date.now(); 43 | res.on('finish', () => { 44 | metrics.histogram('request_duration', Date.now() - start, { 45 | method: req.method, 46 | route: req.route?.path, 47 | status: res.statusCode 48 | }); 49 | }); 50 | next(); 51 | }); 52 | \`\`\` 53 | 54 | ## Resources 55 | - [Observability Guide](https://www.honeycomb.io/what-is-observability) 56 | - [Grafana](https://grafana.com/) 57 | - [Sentry](https://sentry.io/) 58 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/skills/standards-enforcement/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: standards-enforcement 3 | description: Establish and enforce coding standards, best practices, and architectural patterns across the codebase using linters, formatters, and code review processes. Use when setting up ESLint/Prettier, configuring linting rules, creating code style guides, implementing pre-commit hooks, establishing naming conventions, enforcing TypeScript strict mode, maintaining consistency, conducting architecture reviews, or defining team coding standards. 4 | --- 5 | 6 | # Standards Enforcement - Maintaining Code Quality 7 | 8 | ## When to use this skill 9 | 10 | - Setting up ESLint, Prettier, and code formatters 11 | - Configuring linting rules and code standards 12 | - Creating team code style guides 13 | - Implementing pre-commit hooks with Husky 14 | - Establishing naming conventions 15 | - Enforcing TypeScript strict mode 16 | - Maintaining code consistency across team 17 | - Conducting code review for standards compliance 18 | - Defining architectural patterns and rules 19 | - Setting up import ordering and organization 20 | - Enforcing test coverage requirements 21 | - Creating and maintaining coding guidelines 22 | 23 | ## When to use this skill 24 | 25 | - Setting up project guidelines, code reviews, enforcing best practices, maintaining consistency. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Setting up project guidelines, code reviews, enforcing best practices, maintaining consistency. 30 | 31 | ## Tools 32 | 33 | ### ESLint 34 | ```json 35 | { 36 | "extends": ["eslint:recommended", "plugin:@typescript-eslint/recommended"], 37 | "rules": { 38 | "no-console": "warn", 39 | "no-unused-vars": "error", 40 | "@typescript-eslint/no-explicit-any": "error" 41 | } 42 | } 43 | ``` 44 | 45 | ### Prettier 46 | ```json 47 | { 48 | "semi": true, 49 | "singleQuote": true, 50 | "tabWidth": 2, 51 | "trailingComma": "es5" 52 | } 53 | ``` 54 | 55 | ### Husky + lint-staged 56 | ```json 57 | { 58 | "lint-staged": { 59 | "*.{js,ts,tsx}": ["eslint --fix", "prettier --write"], 60 | "*.{json,md}": ["prettier --write"] 61 | } 62 | } 63 | ``` 64 | 65 | ## Resources 66 | - [ESLint](https://eslint.org/) 67 | - [Prettier](https://prettier.io/) 68 | - [Husky](https://typicode.github.io/husky/) 69 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/skills/standards-enforcement/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: standards-enforcement 3 | description: Establish and enforce coding standards, best practices, and architectural patterns across the codebase using linters, formatters, and code review processes. Use when setting up ESLint/Prettier, configuring linting rules, creating code style guides, implementing pre-commit hooks, establishing naming conventions, enforcing TypeScript strict mode, maintaining consistency, conducting architecture reviews, or defining team coding standards. 4 | --- 5 | 6 | # Standards Enforcement - Maintaining Code Quality 7 | 8 | ## When to use this skill 9 | 10 | - Setting up ESLint, Prettier, and code formatters 11 | - Configuring linting rules and code standards 12 | - Creating team code style guides 13 | - Implementing pre-commit hooks with Husky 14 | - Establishing naming conventions 15 | - Enforcing TypeScript strict mode 16 | - Maintaining code consistency across team 17 | - Conducting code review for standards compliance 18 | - Defining architectural patterns and rules 19 | - Setting up import ordering and organization 20 | - Enforcing test coverage requirements 21 | - Creating and maintaining coding guidelines 22 | 23 | ## When to use this skill 24 | 25 | - Setting up project guidelines, code reviews, enforcing best practices, maintaining consistency. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Setting up project guidelines, code reviews, enforcing best practices, maintaining consistency. 30 | 31 | ## Tools 32 | 33 | ### ESLint 34 | ```json 35 | { 36 | "extends": ["eslint:recommended", "plugin:@typescript-eslint/recommended"], 37 | "rules": { 38 | "no-console": "warn", 39 | "no-unused-vars": "error", 40 | "@typescript-eslint/no-explicit-any": "error" 41 | } 42 | } 43 | ``` 44 | 45 | ### Prettier 46 | ```json 47 | { 48 | "semi": true, 49 | "singleQuote": true, 50 | "tabWidth": 2, 51 | "trailingComma": "es5" 52 | } 53 | ``` 54 | 55 | ### Husky + lint-staged 56 | ```json 57 | { 58 | "lint-staged": { 59 | "*.{js,ts,tsx}": ["eslint --fix", "prettier --write"], 60 | "*.{json,md}": ["prettier --write"] 61 | } 62 | } 63 | ``` 64 | 65 | ## Resources 66 | - [ESLint](https://eslint.org/) 67 | - [Prettier](https://prettier.io/) 68 | - [Husky](https://typicode.github.io/husky/) 69 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/skills/neondb-serverless/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: neondb-serverless 3 | description: Use Neon serverless Postgres with branching, connection pooling, and instant scalability for modern applications with Prisma or Drizzle ORM integration. Use when setting up serverless Postgres databases, implementing database branching for preview environments, configuring connection pooling, optimizing for serverless cold starts, using Prisma with Neon, implementing database migrations, scaling databases automatically, or building applications on Vercel/Netlify with Postgres. 4 | --- 5 | 6 | # NeonDB Serverless - PostgreSQL for Modern Apps 7 | 8 | ## When to use this skill 9 | 10 | - Setting up serverless Postgres databases 11 | - Implementing database branching for previews 12 | - Configuring connection pooling for serverless 13 | - Optimizing database for cold starts 14 | - Using Prisma or Drizzle ORM with Neon 15 | - Implementing automated database migrations 16 | - Scaling databases without manual intervention 17 | - Building Next.js apps with Postgres on Vercel 18 | - Creating preview databases per Git branch 19 | - Implementing instant database rollbacks 20 | - Using Postgres in serverless functions 21 | - Optimizing connection management for edge functions 22 | 23 | ## When to use this skill 24 | 25 | - Using NeonDB serverless PostgreSQL, implementing connection pooling, or building edge-compatible database apps. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Using NeonDB serverless PostgreSQL, implementing connection pooling, or building edge-compatible database apps. 30 | 31 | ## Key Patterns 32 | 33 | ### Connection Pooling (Critical!) 34 | \`\`\`typescript 35 | import { Pool } from '@neondatabase/serverless'; 36 | 37 | const pool = new Pool({ connectionString: process.env.DATABASE_URL }); 38 | 39 | export async function query(text: string, params: any[]) { 40 | const client = await pool.connect(); 41 | try { 42 | return await client.query(text, params); 43 | } finally { 44 | client.release(); 45 | } 46 | } 47 | \`\`\` 48 | 49 | ### Edge Runtime Compatible 50 | \`\`\`typescript 51 | import { neon } from '@neondatabase/serverless'; 52 | 53 | const sql = neon(process.env.DATABASE_URL!); 54 | 55 | export const runtime = 'edge'; 56 | 57 | export async function GET() { 58 | const users = await sql`SELECT * FROM users`; 59 | return Response.json(users); 60 | } 61 | \`\`\` 62 | 63 | ## Resources 64 | - [NeonDB Docs](https://neon.tech/docs) 65 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/skills/neondb-serverless/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: neondb-serverless 3 | description: Use Neon serverless Postgres with branching, connection pooling, and instant scalability for modern applications with Prisma or Drizzle ORM integration. Use when setting up serverless Postgres databases, implementing database branching for preview environments, configuring connection pooling, optimizing for serverless cold starts, using Prisma with Neon, implementing database migrations, scaling databases automatically, or building applications on Vercel/Netlify with Postgres. 4 | --- 5 | 6 | # NeonDB Serverless - PostgreSQL for Modern Apps 7 | 8 | ## When to use this skill 9 | 10 | - Setting up serverless Postgres databases 11 | - Implementing database branching for previews 12 | - Configuring connection pooling for serverless 13 | - Optimizing database for cold starts 14 | - Using Prisma or Drizzle ORM with Neon 15 | - Implementing automated database migrations 16 | - Scaling databases without manual intervention 17 | - Building Next.js apps with Postgres on Vercel 18 | - Creating preview databases per Git branch 19 | - Implementing instant database rollbacks 20 | - Using Postgres in serverless functions 21 | - Optimizing connection management for edge functions 22 | 23 | ## When to use this skill 24 | 25 | - Using NeonDB serverless PostgreSQL, implementing connection pooling, or building edge-compatible database apps. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Using NeonDB serverless PostgreSQL, implementing connection pooling, or building edge-compatible database apps. 30 | 31 | ## Key Patterns 32 | 33 | ### Connection Pooling (Critical!) 34 | \`\`\`typescript 35 | import { Pool } from '@neondatabase/serverless'; 36 | 37 | const pool = new Pool({ connectionString: process.env.DATABASE_URL }); 38 | 39 | export async function query(text: string, params: any[]) { 40 | const client = await pool.connect(); 41 | try { 42 | return await client.query(text, params); 43 | } finally { 44 | client.release(); 45 | } 46 | } 47 | \`\`\` 48 | 49 | ### Edge Runtime Compatible 50 | \`\`\`typescript 51 | import { neon } from '@neondatabase/serverless'; 52 | 53 | const sql = neon(process.env.DATABASE_URL!); 54 | 55 | export const runtime = 'edge'; 56 | 57 | export async function GET() { 58 | const users = await sql`SELECT * FROM users`; 59 | return Response.json(users); 60 | } 61 | \`\`\` 62 | 63 | ## Resources 64 | - [NeonDB Docs](https://neon.tech/docs) 65 | -------------------------------------------------------------------------------- /droidz_installer/fs.py: -------------------------------------------------------------------------------- 1 | """Filesystem helpers for the Droidz installer.""" 2 | 3 | from __future__ import annotations 4 | 5 | import shutil 6 | import stat 7 | from datetime import datetime, timezone 8 | from pathlib import Path 9 | from shutil import move, rmtree 10 | from typing import Iterable, Optional 11 | 12 | 13 | def expand_path(path: str | Path) -> Path: 14 | """Return an absolute, user-expanded path.""" 15 | 16 | return Path(path).expanduser().resolve() 17 | 18 | 19 | def prepare_destination(path: Path, *, force: bool, dry_run: bool) -> Optional[Path]: 20 | """Ensure the destination is ready and return backup path if one was created.""" 21 | 22 | if not path.exists(): 23 | if not dry_run: 24 | path.mkdir(parents=True, exist_ok=True) 25 | return None 26 | 27 | if force: 28 | if dry_run: 29 | return None 30 | # Check if path is the current working directory to avoid deleting it 31 | try: 32 | is_cwd = path.samefile(Path.cwd()) 33 | except (FileNotFoundError, OSError): 34 | is_cwd = False 35 | 36 | if is_cwd: 37 | # Clear contents without removing the directory itself 38 | for item in path.iterdir(): 39 | if item.is_dir(): 40 | rmtree(item) 41 | else: 42 | item.unlink() 43 | else: 44 | # Safe to remove and recreate 45 | rmtree(path) 46 | path.mkdir(parents=True, exist_ok=True) 47 | return None 48 | 49 | timestamp = datetime.now(timezone.utc).strftime("%Y%m%d-%H%M%S") 50 | backup = path.with_name(f"{path.name}.backup-{timestamp}") 51 | 52 | if dry_run: 53 | return backup 54 | 55 | move(str(path), str(backup)) 56 | path.mkdir(parents=True, exist_ok=True) 57 | return backup 58 | 59 | 60 | def copy_tree(src: Path, dest: Path, *, dry_run: bool) -> None: 61 | """Copy a payload directory into the destination path.""" 62 | 63 | if dry_run: 64 | return 65 | 66 | shutil.copytree(src, dest, dirs_exist_ok=True) 67 | 68 | 69 | def chmod_targets(dest: Path, globs: Iterable[str], *, dry_run: bool) -> None: 70 | """Apply executable bits to the provided glob patterns within dest.""" 71 | 72 | for pattern in globs: 73 | for candidate in dest.glob(pattern): 74 | if dry_run: 75 | continue 76 | current_mode = candidate.stat().st_mode 77 | candidate.chmod(current_mode | stat.S_IXUSR | stat.S_IXGRP | stat.S_IXOTH) 78 | 79 | 80 | __all__ = ["expand_path", "prepare_destination", "copy_tree", "chmod_targets"] 81 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/skills/convex-backend/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: convex-backend 3 | description: Build real-time, reactive backend applications with Convex using TypeScript queries, mutations, and actions with automatic reactivity and optimistic updates. Use when building real-time collaborative applications, implementing reactive data synchronization, writing serverless backend functions, creating queries that auto-update, implementing mutations with transactional guarantees, handling file uploads with Convex storage, implementing authentication with Convex Auth, designing reactive database schemas, or building applications requiring instant data synchronization. 4 | --- 5 | 6 | # Convex Backend - Realtime Database & Functions 7 | 8 | ## When to use this skill 9 | 10 | - Building real-time collaborative applications 11 | - Implementing reactive data that auto-updates 12 | - Writing Convex queries, mutations, and actions 13 | - Creating serverless backend functions with TypeScript 14 | - Implementing optimistic UI updates 15 | - Handling file uploads with Convex storage 16 | - Implementing authentication with Convex Auth 17 | - Designing Convex database schemas 18 | - Building chat applications or live dashboards 19 | - Creating applications with instant data sync 20 | - Implementing scheduled functions (crons) 21 | - Building backends without managing infrastructure 22 | 23 | ## When to use this skill 24 | 25 | - Building realtime apps with Convex, implementing reactive queries, or managing backend logic with type-safe functions. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Building realtime apps with Convex, implementing reactive queries, or managing backend logic with type-safe functions. 30 | 31 | ## Core Concepts 32 | 33 | ### Queries (Read Data) 34 | \`\`\`typescript 35 | import { query } from './_generated/server'; 36 | import { v } from 'convex/values'; 37 | 38 | export const list = query({ 39 | args: {}, 40 | handler: async (ctx) => { 41 | return await ctx.db.query('users').collect(); 42 | } 43 | }); 44 | 45 | export const get = query({ 46 | args: { id: v.id('users') }, 47 | handler: async (ctx, args) => { 48 | return await ctx.db.get(args.id); 49 | } 50 | }); 51 | \`\`\` 52 | 53 | ### Mutations (Write Data) 54 | \`\`\`typescript 55 | import { mutation } from './_generated/server'; 56 | 57 | export const create = mutation({ 58 | args: { name: v.string(), email: v.string() }, 59 | handler: async (ctx, args) => { 60 | return await ctx.db.insert('users', args); 61 | } 62 | }); 63 | \`\`\` 64 | 65 | ## Resources 66 | - [Convex Docs](https://docs.convex.dev/) 67 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/skills/convex-backend/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: convex-backend 3 | description: Build real-time, reactive backend applications with Convex using TypeScript queries, mutations, and actions with automatic reactivity and optimistic updates. Use when building real-time collaborative applications, implementing reactive data synchronization, writing serverless backend functions, creating queries that auto-update, implementing mutations with transactional guarantees, handling file uploads with Convex storage, implementing authentication with Convex Auth, designing reactive database schemas, or building applications requiring instant data synchronization. 4 | --- 5 | 6 | # Convex Backend - Realtime Database & Functions 7 | 8 | ## When to use this skill 9 | 10 | - Building real-time collaborative applications 11 | - Implementing reactive data that auto-updates 12 | - Writing Convex queries, mutations, and actions 13 | - Creating serverless backend functions with TypeScript 14 | - Implementing optimistic UI updates 15 | - Handling file uploads with Convex storage 16 | - Implementing authentication with Convex Auth 17 | - Designing Convex database schemas 18 | - Building chat applications or live dashboards 19 | - Creating applications with instant data sync 20 | - Implementing scheduled functions (crons) 21 | - Building backends without managing infrastructure 22 | 23 | ## When to use this skill 24 | 25 | - Building realtime apps with Convex, implementing reactive queries, or managing backend logic with type-safe functions. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Building realtime apps with Convex, implementing reactive queries, or managing backend logic with type-safe functions. 30 | 31 | ## Core Concepts 32 | 33 | ### Queries (Read Data) 34 | \`\`\`typescript 35 | import { query } from './_generated/server'; 36 | import { v } from 'convex/values'; 37 | 38 | export const list = query({ 39 | args: {}, 40 | handler: async (ctx) => { 41 | return await ctx.db.query('users').collect(); 42 | } 43 | }); 44 | 45 | export const get = query({ 46 | args: { id: v.id('users') }, 47 | handler: async (ctx, args) => { 48 | return await ctx.db.get(args.id); 49 | } 50 | }); 51 | \`\`\` 52 | 53 | ### Mutations (Write Data) 54 | \`\`\`typescript 55 | import { mutation } from './_generated/server'; 56 | 57 | export const create = mutation({ 58 | args: { name: v.string(), email: v.string() }, 59 | handler: async (ctx, args) => { 60 | return await ctx.db.insert('users', args); 61 | } 62 | }); 63 | \`\`\` 64 | 65 | ## Resources 66 | - [Convex Docs](https://docs.convex.dev/) 67 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/agents/spec-shaper.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: spec-shaper 3 | description: Use proactively to gather detailed requirements through targeted questions and visual analysis 4 | color: blue 5 | model: inherit 6 | --- 7 | 8 | You are a software product requirements research specialist. Your role is to gather comprehensive requirements through targeted questions and visual analysis. 9 | 10 | ## Research Tools (Use When Available) 11 | 12 | When gathering requirements and shaping specifications, leverage these research tools if available: 13 | 14 | **Exa Code Context** - For researching: 15 | - Technical architecture patterns 16 | - Similar feature implementations 17 | - Framework-specific best practices 18 | - Design pattern recommendations 19 | 20 | **Ref Documentation** - For referencing: 21 | - Official framework documentation 22 | - API design guidelines 23 | - Database schema patterns 24 | - Authentication/authorization approaches 25 | 26 | **Usage Pattern**: 27 | ``` 28 | Try: Use Exa or Ref to research technical approaches 29 | If unavailable: Continue with general knowledge and established patterns 30 | ``` 31 | 32 | These tools enhance specification quality but are not required. 33 | 34 | 35 | ## Specification Shaping Process 36 | 37 | ### 1. Research the Domain 38 | 39 | - Understand the problem space 40 | - Research similar solutions 41 | - Identify best practices 42 | - Note common pitfalls 43 | 44 | ### 2. Clarify Requirements 45 | 46 | Ask questions to refine understanding: 47 | - What are the exact user needs? 48 | - What are the constraints? 49 | - What are the priorities? 50 | - What's in scope vs out of scope? 51 | 52 | ### 3. Define Clear Boundaries 53 | 54 | - Explicitly state what's included 55 | - Clearly note what's excluded 56 | - Identify future considerations 57 | - Set realistic expectations 58 | 59 | ### 4. Structure the Specification 60 | 61 | Organize into logical sections: 62 | - Overview and goals 63 | - Detailed requirements 64 | - Technical approach 65 | - Success criteria 66 | 67 | ### 5. Add Technical Details 68 | 69 | For each feature: 70 | - Data requirements 71 | - API contracts 72 | - UI requirements 73 | - Integration points 74 | - Error handling 75 | 76 | ### 6. Validate Completeness 77 | 78 | Ensure spec answers: 79 | - What needs to be built? 80 | - Why is it needed? 81 | - How should it work? 82 | - How will we know it's complete? 83 | 84 | 85 | ## User Standards & Preferences Compliance 86 | 87 | IMPORTANT: Ensure that all of your questions and final documented requirements ARE ALIGNED and DO NOT CONFLICT with any of user's preferred tech-stack, coding conventions, or common patterns as detailed in the following files: 88 | 89 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/agents/implementer.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: implementer 3 | description: Use proactively to implement a feature by following a given tasks.md for a spec. 4 | color: red 5 | model: inherit 6 | --- 7 | 8 | You are a full stack software developer with deep expertise in front-end, back-end, database, API and user interface development. Your role is to implement a given set of tasks for the implementation of a feature, by closely following the specifications documented in a given tasks.md, spec.md, and/or requirements.md. 9 | 10 | ## Research Tools (Use When Available) 11 | 12 | When implementing features, leverage these research tools if available: 13 | 14 | **Exa Code Context** - For researching: 15 | - Code examples and patterns for specific implementations 16 | - Framework-specific best practices 17 | - Common solutions to implementation challenges 18 | - Package/library usage examples 19 | - Error handling patterns 20 | 21 | **Ref Documentation** - For referencing: 22 | - Official API documentation 23 | - Framework method signatures 24 | - Configuration options 25 | - Troubleshooting guides 26 | 27 | **Usage Pattern**: 28 | ``` 29 | Try: Research implementation patterns, code examples, and solutions 30 | If unavailable: Use established patterns and general programming knowledge 31 | ``` 32 | 33 | Research helps find optimal solutions faster and avoid common pitfalls. 34 | 35 | 36 | ## Implementation Workflow 37 | 38 | ### 1. Understand the Task 39 | 40 | - Read task description thoroughly 41 | - Review acceptance criteria 42 | - Check dependencies are completed 43 | - Clarify any ambiguities 44 | 45 | ### 2. Plan the Implementation 46 | 47 | - Break down into subtasks if large 48 | - Identify files that need changes 49 | - Plan test strategy 50 | - Consider edge cases 51 | 52 | ### 3. Write Tests First (TDD) 53 | 54 | - Write failing tests that describe desired behavior 55 | - Cover happy path and edge cases 56 | - Include error scenarios 57 | 58 | ### 4. Implement the Feature 59 | 60 | - Write minimal code to pass tests 61 | - Follow coding standards 62 | - Keep functions small and focused 63 | - Add necessary error handling 64 | 65 | ### 5. Refactor and Clean Up 66 | 67 | - Remove duplication 68 | - Improve naming 69 | - Add comments only where needed 70 | - Ensure code is readable 71 | 72 | ### 6. Verify Completion 73 | 74 | - All tests pass 75 | - Meets acceptance criteria 76 | - No regressions introduced 77 | - Code reviewed (if team) 78 | 79 | ### 7. Document Changes 80 | 81 | - Update relevant documentation 82 | - Add code comments for complex logic 83 | - Update changelog if needed 84 | 85 | 86 | ## User Standards & Preferences Compliance 87 | 88 | IMPORTANT: Ensure that the tasks list you create IS ALIGNED and DOES NOT CONFLICT with any of user's preferred tech stack, coding conventions, or common patterns as detailed in the following files: 89 | 90 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/commands/shape-spec.md: -------------------------------------------------------------------------------- 1 | # Spec Shaping Process 2 | 3 | You are helping me shape and plan the scope for a new feature. The following process is aimed at documenting our key decisions regarding scope, design and architecture approach. We will use our findings from this process later when we write the formal spec document (but we are NOT writing the formal spec yet). 4 | 5 | ## User Standards & Preferences Compliance 6 | 7 | **IMPORTANT**: Before proceeding with spec shaping, you MUST check for and adhere to the user's project standards. 8 | 9 | ### Step 0: Load Standards 10 | 11 | Check if standards exist and load them: 12 | 13 | 1. Check for standards directory: `droidz/standards/` 14 | 2. If it exists, **read ALL standards files recursively**: 15 | - Use glob pattern `droidz/standards/**/*.md` to find all markdown files 16 | - This includes all subdirectories (global, frontend, backend, infrastructure, and any custom directories the user has created) 17 | - Read every `.md` file found in the standards directory tree 18 | 19 | 3. Keep ALL standards in mind throughout the spec shaping process to ensure: 20 | - Research questions align with established patterns 21 | - Proposed approaches don't conflict with existing standards 22 | - Architecture decisions follow documented conventions 23 | 24 | If no standards directory exists, proceed without standards constraints but inform the user: 25 | ``` 26 | ℹ️ No project standards found at droidz/standards/ 27 | Consider running /shape-standards to establish project conventions. 28 | ``` 29 | 30 | --- 31 | 32 | This process will follow 3 main phases, each with their own workflow steps: 33 | 34 | Process overview (details to follow) 35 | 36 | PHASE 1. Initilize spec 37 | PHASE 2. Research requirements for this spec 38 | PHASE 3. Inform the user that the spec has been initialized 39 | 40 | Follow each of these phases and their individual workflows IN SEQUENCE: 41 | 42 | ## Multi-Phase Process: 43 | 44 | ### PHASE 1: Initialize Spec 45 | 46 | Use the **spec-shaper** subagent to initialize a new spec. 47 | 48 | IF the user has provided a description, provide that to the spec-initializer. 49 | 50 | The spec-initializer will provide the path to the dated spec folder (YYYY-MM-DD-spec-name) they've created. 51 | 52 | ### PHASE 2: Research Requirements 53 | 54 | After spec-initializer completes, immediately use the **spec-shaper** subagent: 55 | 56 | Provide the spec-shaper with: 57 | - The spec folder path from spec-initializer 58 | 59 | The spec-shaper will give you several separate responses that you MUST show to the user. These include: 60 | 1. Numbered clarifying questions along with a request for visual assets (show these to user, wait for user's response) 61 | 2. Follow-up questions if needed (based on user's answers and provided visuals) 62 | 63 | **IMPORTANT**: 64 | - Display these questions to the user and wait for their response 65 | - The spec-shaper may ask you to relay follow-up questions that you must present to user 66 | 67 | ### PHASE 3: Inform the user 68 | 69 | After all steps complete, inform the user: 70 | 71 | ``` 72 | Spec shaping is complete! 73 | 74 | ✅ Spec folder created: `[spec-path]` 75 | ✅ Requirements gathered 76 | ✅ Visual assets: [Found X files / No files provided] 77 | 78 | NEXT STEP 👉 Run `/write-spec` to generate the detailed specification document. 79 | ``` 80 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/commands/shape-spec.md: -------------------------------------------------------------------------------- 1 | # Spec Shaping Process 2 | 3 | You are helping me shape and plan the scope for a new feature. The following process is aimed at documenting our key decisions regarding scope, design and architecture approach. We will use our findings from this process later when we write the formal spec document (but we are NOT writing the formal spec yet). 4 | 5 | ## User Standards & Preferences Compliance 6 | 7 | **IMPORTANT**: Before proceeding with spec shaping, you MUST check for and adhere to the user's project standards. 8 | 9 | ### Step 0: Load Standards 10 | 11 | Check if standards exist and load them: 12 | 13 | 1. Check for standards directory: `droidz/standards/` 14 | 2. If it exists, **read ALL standards files recursively**: 15 | - Use glob pattern `droidz/standards/**/*.md` to find all markdown files 16 | - This includes all subdirectories (global, frontend, backend, infrastructure, and any custom directories the user has created) 17 | - Read every `.md` file found in the standards directory tree 18 | 19 | 3. Keep ALL standards in mind throughout the spec shaping process to ensure: 20 | - Research questions align with established patterns 21 | - Proposed approaches don't conflict with existing standards 22 | - Architecture decisions follow documented conventions 23 | 24 | If no standards directory exists, proceed without standards constraints but inform the user: 25 | ``` 26 | ℹ️ No project standards found at droidz/standards/ 27 | Consider running /shape-standards to establish project conventions. 28 | ``` 29 | 30 | --- 31 | 32 | This process will follow 3 main phases, each with their own workflow steps: 33 | 34 | Process overview (details to follow) 35 | 36 | PHASE 1. Initilize spec 37 | PHASE 2. Research requirements for this spec 38 | PHASE 3. Inform the user that the spec has been initialized 39 | 40 | Follow each of these phases and their individual workflows IN SEQUENCE: 41 | 42 | ## Multi-Phase Process: 43 | 44 | ### PHASE 1: Initialize Spec 45 | 46 | Use the **spec-shaper** subagent to initialize a new spec. 47 | 48 | IF the user has provided a description, provide that to the spec-initializer. 49 | 50 | The spec-initializer will provide the path to the dated spec folder (YYYY-MM-DD-spec-name) they've created. 51 | 52 | ### PHASE 2: Research Requirements 53 | 54 | After spec-initializer completes, immediately use the **spec-shaper** subagent: 55 | 56 | Provide the spec-shaper with: 57 | - The spec folder path from spec-initializer 58 | 59 | The spec-shaper will give you several separate responses that you MUST show to the user. These include: 60 | 1. Numbered clarifying questions along with a request for visual assets (show these to user, wait for user's response) 61 | 2. Follow-up questions if needed (based on user's answers and provided visuals) 62 | 63 | **IMPORTANT**: 64 | - Display these questions to the user and wait for their response 65 | - The spec-shaper may ask you to relay follow-up questions that you must present to user 66 | 67 | ### PHASE 3: Inform the user 68 | 69 | After all steps complete, inform the user: 70 | 71 | ``` 72 | Spec shaping is complete! 73 | 74 | ✅ Spec folder created: `[spec-path]` 75 | ✅ Requirements gathered 76 | ✅ Visual assets: [Found X files / No files provided] 77 | 78 | NEXT STEP 👉 Run `/write-spec` to generate the detailed specification document. 79 | ``` 80 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/agents/implementation-verifier.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: implementation-verifier 3 | description: Use proactively to verify the end-to-end implementation of a spec 4 | color: green 5 | model: inherit 6 | --- 7 | 8 | You are a product spec verifier responsible for verifying the end-to-end implementation of a spec, updating the product roadmap (if necessary), and producing a final verification report. 9 | 10 | ## Core Responsibilities 11 | 12 | 1. **Ensure tasks.md has been updated**: Check this spec's `tasks.md` to ensure all tasks and sub-tasks have been marked complete with `- [x]` 13 | 2. **Update roadmap (if applicable)**: Check `droidz/product/roadmap.md` and check items that have been completed as a result of this spec's implementation by marking their checkbox(s) with `- [x]`. 14 | 3. **Run entire tests suite**: Verify that all tests pass and there have been no regressions as a result of this implementation. 15 | 4. **Create final verification report**: Write your final verification report for this spec's implementation. 16 | 17 | ## Workflow 18 | 19 | ### Step 1: Ensure tasks.md has been updated 20 | 21 | 22 | ## Implementation Verification Process 23 | 24 | ### Step 1: Verify Tasks Completion 25 | 26 | For each task: 27 | - Code is implemented 28 | - Tests are written and passing 29 | - Acceptance criteria met 30 | - No regressions introduced 31 | 32 | ### Step 2: Update Project Roadmap 33 | 34 | - Mark completed tasks 35 | - Update progress percentage 36 | - Note any blockers 37 | - Adjust timeline if needed 38 | 39 | ### Step 3: Run All Tests 40 | 41 | **First, detect the project's package manager** by checking for lockfiles: 42 | - `bun.lockb` → Use **bun** 43 | - `pnpm-lock.yaml` → Use **pnpm** 44 | - `yarn.lock` → Use **yarn** 45 | - `package-lock.json` → Use **npm** 46 | 47 | Execute comprehensive test suite using the **detected package manager**: 48 | 49 | | Test Type | npm | yarn | pnpm | bun | 50 | |-----------|-----|------|------|-----| 51 | | Unit tests | `npm test` | `yarn test` | `pnpm test` | `bun test` | 52 | | Integration | `npm run test:integration` | `yarn test:integration` | `pnpm test:integration` | `bun run test:integration` | 53 | | E2E tests | `npm run test:e2e` | `yarn test:e2e` | `pnpm test:e2e` | `bun run test:e2e` | 54 | | Type check | `npm run type-check` | `yarn type-check` | `pnpm type-check` | `bun run type-check` | 55 | | Linting | `npm run lint` | `yarn lint` | `pnpm lint` | `bun run lint` | 56 | 57 | **Note**: Only run tests that are available in the project's `package.json` scripts. 58 | 59 | ### Step 4: Create Verification Report 60 | 61 | Document: 62 | - Tasks completed 63 | - Tests passing 64 | - Known issues 65 | - Next steps 66 | - Overall status 67 | 68 | Report Template: 69 | ```markdown 70 | # Implementation Verification Report 71 | 72 | ## Summary 73 | - Total tasks: X 74 | - Completed: Y 75 | - In progress: Z 76 | - Blocked: W 77 | 78 | ## Test Results 79 | - Unit tests: ✓ Passing 80 | - Integration tests: ✓ Passing 81 | - E2E tests: ✓ Passing 82 | 83 | ## Issues Found 84 | 1. [Issue description] 85 | 2. [Issue description] 86 | 87 | ## Recommendations 88 | 1. [Recommendation] 89 | 2. [Recommendation] 90 | 91 | ## Next Steps 92 | 1. [Next step] 93 | 2. [Next step] 94 | ``` 95 | 96 | 97 | ### Step 2: Update roadmap (if applicable) 98 | 99 | ### Step 3: Run entire tests suite 100 | 101 | ### Step 4: Create final verification report 102 | 103 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/droids/implementation-verifier.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: implementation-verifier 3 | description: Use proactively to verify the end-to-end implementation of a spec 4 | color: green 5 | model: inherit 6 | --- 7 | 8 | You are a product spec verifier responsible for verifying the end-to-end implementation of a spec, updating the product roadmap (if necessary), and producing a final verification report. 9 | 10 | ## Core Responsibilities 11 | 12 | 1. **Ensure tasks.md has been updated**: Check this spec's `tasks.md` to ensure all tasks and sub-tasks have been marked complete with `- [x]` 13 | 2. **Update roadmap (if applicable)**: Check `droidz/product/roadmap.md` and check items that have been completed as a result of this spec's implementation by marking their checkbox(s) with `- [x]`. 14 | 3. **Run entire tests suite**: Verify that all tests pass and there have been no regressions as a result of this implementation. 15 | 4. **Create final verification report**: Write your final verification report for this spec's implementation. 16 | 17 | ## Workflow 18 | 19 | ### Step 1: Ensure tasks.md has been updated 20 | 21 | 22 | ## Implementation Verification Process 23 | 24 | ### Step 1: Verify Tasks Completion 25 | 26 | For each task: 27 | - Code is implemented 28 | - Tests are written and passing 29 | - Acceptance criteria met 30 | - No regressions introduced 31 | 32 | ### Step 2: Update Project Roadmap 33 | 34 | - Mark completed tasks 35 | - Update progress percentage 36 | - Note any blockers 37 | - Adjust timeline if needed 38 | 39 | ### Step 3: Run All Tests 40 | 41 | **First, detect the project's package manager** by checking for lockfiles: 42 | - `bun.lockb` → Use **bun** 43 | - `pnpm-lock.yaml` → Use **pnpm** 44 | - `yarn.lock` → Use **yarn** 45 | - `package-lock.json` → Use **npm** 46 | 47 | Execute comprehensive test suite using the **detected package manager**: 48 | 49 | | Test Type | npm | yarn | pnpm | bun | 50 | |-----------|-----|------|------|-----| 51 | | Unit tests | `npm test` | `yarn test` | `pnpm test` | `bun test` | 52 | | Integration | `npm run test:integration` | `yarn test:integration` | `pnpm test:integration` | `bun run test:integration` | 53 | | E2E tests | `npm run test:e2e` | `yarn test:e2e` | `pnpm test:e2e` | `bun run test:e2e` | 54 | | Type check | `npm run type-check` | `yarn type-check` | `pnpm type-check` | `bun run type-check` | 55 | | Linting | `npm run lint` | `yarn lint` | `pnpm lint` | `bun run lint` | 56 | 57 | **Note**: Only run tests that are available in the project's `package.json` scripts. 58 | 59 | ### Step 4: Create Verification Report 60 | 61 | Document: 62 | - Tasks completed 63 | - Tests passing 64 | - Known issues 65 | - Next steps 66 | - Overall status 67 | 68 | Report Template: 69 | ```markdown 70 | # Implementation Verification Report 71 | 72 | ## Summary 73 | - Total tasks: X 74 | - Completed: Y 75 | - In progress: Z 76 | - Blocked: W 77 | 78 | ## Test Results 79 | - Unit tests: ✓ Passing 80 | - Integration tests: ✓ Passing 81 | - E2E tests: ✓ Passing 82 | 83 | ## Issues Found 84 | 1. [Issue description] 85 | 2. [Issue description] 86 | 87 | ## Recommendations 88 | 1. [Recommendation] 89 | 2. [Recommendation] 90 | 91 | ## Next Steps 92 | 1. [Next step] 93 | 2. [Next step] 94 | ``` 95 | 96 | 97 | ### Step 2: Update roadmap (if applicable) 98 | 99 | ### Step 3: Run entire tests suite 100 | 101 | ### Step 4: Create final verification report 102 | 103 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/skills/accessibility-wcag/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: accessibility-wcag 3 | description: Build accessible web applications following WCAG 2.1/2.2 guidelines with proper semantic HTML, ARIA attributes, keyboard navigation, screen reader support, and inclusive design. Use when implementing ARIA labels and roles, ensuring keyboard navigation, supporting screen readers, providing text alternatives for images, managing focus, creating accessible forms, building inclusive UI components, testing with accessibility tools, meeting WCAG compliance levels, or designing for users with disabilities. 4 | --- 5 | 6 | # Accessibility (WCAG) - Building Inclusive Web Applications 7 | 8 | ## When to use this skill 9 | 10 | - Implementing ARIA labels, roles, and properties 11 | - Ensuring full keyboard navigation support 12 | - Supporting screen readers (NVDA, JAWS, VoiceOver) 13 | - Providing text alternatives for images and media 14 | - Managing focus and focus indicators 15 | - Creating accessible forms with proper labels 16 | - Building inclusive, usable UI components 17 | - Testing with axe DevTools or similar tools 18 | - Meeting WCAG 2.1/2.2 AA or AAA compliance 19 | - Designing for color blindness and low vision 20 | - Implementing skip links and landmarks 21 | - Ensuring sufficient color contrast ratios 22 | 23 | ## When to use this skill 24 | 25 | - Designing UIs, implementing components, ensuring compliance with accessibility standards (WCAG 2.1/2.2). 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Designing UIs, implementing components, ensuring compliance with accessibility standards (WCAG 2.1/2.2). 30 | 31 | ## Core Principles (POUR) 32 | 33 | 1. **Perceivable** - Information available to all senses 34 | 2. **Operable** - Interface elements functional for all users 35 | 3. **Understandable** - Content and interface are clear 36 | 4. **Robust** - Works across technologies including assistive devices 37 | 38 | ## Essential Patterns 39 | 40 | ### Semantic HTML 41 | ```html 42 | 43 |
44 |

45 | 46 | 47 | 48 |
49 | ``` 50 | 51 | ### ARIA Labels & Roles 52 | ```html 53 | 54 | 55 | 56 |
Success
57 | ``` 58 | 59 | ### Keyboard Navigation 60 | ```typescript 61 | function Modal({ onClose }: { onClose: () => void }) { 62 | useEffect(() => { 63 | const handleEscape = (e: KeyboardEvent) => { 64 | if (e.key === 'Escape') onClose(); 65 | }; 66 | document.addEventListener('keydown', handleEscape); 67 | return () => document.removeEventListener('keydown', handleEscape); 68 | }, [onClose]); 69 | 70 | return
...
; 71 | } 72 | ``` 73 | 74 | ### Focus Management 75 | ```typescript 76 | const firstFocusableElement = dialogRef.current?.querySelectorAll( 77 | 'button, [href], input, select, textarea, [tabindex]:not([tabindex="-1"])' 78 | )[0]; 79 | firstFocusableElement?.focus(); 80 | ``` 81 | 82 | ## Resources 83 | - [WCAG 2.1 Guidelines](https://www.w3.org/WAI/WCAG21/quickref/) 84 | - [MDN Accessibility](https://developer.mozilla.org/en-US/docs/Web/Accessibility) 85 | - [axe DevTools](https://www.deque.com/axe/devtools/) 86 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/skills/accessibility-wcag/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: accessibility-wcag 3 | description: Build accessible web applications following WCAG 2.1/2.2 guidelines with proper semantic HTML, ARIA attributes, keyboard navigation, screen reader support, and inclusive design. Use when implementing ARIA labels and roles, ensuring keyboard navigation, supporting screen readers, providing text alternatives for images, managing focus, creating accessible forms, building inclusive UI components, testing with accessibility tools, meeting WCAG compliance levels, or designing for users with disabilities. 4 | --- 5 | 6 | # Accessibility (WCAG) - Building Inclusive Web Applications 7 | 8 | ## When to use this skill 9 | 10 | - Implementing ARIA labels, roles, and properties 11 | - Ensuring full keyboard navigation support 12 | - Supporting screen readers (NVDA, JAWS, VoiceOver) 13 | - Providing text alternatives for images and media 14 | - Managing focus and focus indicators 15 | - Creating accessible forms with proper labels 16 | - Building inclusive, usable UI components 17 | - Testing with axe DevTools or similar tools 18 | - Meeting WCAG 2.1/2.2 AA or AAA compliance 19 | - Designing for color blindness and low vision 20 | - Implementing skip links and landmarks 21 | - Ensuring sufficient color contrast ratios 22 | 23 | ## When to use this skill 24 | 25 | - Designing UIs, implementing components, ensuring compliance with accessibility standards (WCAG 2.1/2.2). 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Designing UIs, implementing components, ensuring compliance with accessibility standards (WCAG 2.1/2.2). 30 | 31 | ## Core Principles (POUR) 32 | 33 | 1. **Perceivable** - Information available to all senses 34 | 2. **Operable** - Interface elements functional for all users 35 | 3. **Understandable** - Content and interface are clear 36 | 4. **Robust** - Works across technologies including assistive devices 37 | 38 | ## Essential Patterns 39 | 40 | ### Semantic HTML 41 | ```html 42 | 43 |
44 |

45 | 46 | 47 | 48 |
49 | ``` 50 | 51 | ### ARIA Labels & Roles 52 | ```html 53 | 54 | 55 | 56 |
Success
57 | ``` 58 | 59 | ### Keyboard Navigation 60 | ```typescript 61 | function Modal({ onClose }: { onClose: () => void }) { 62 | useEffect(() => { 63 | const handleEscape = (e: KeyboardEvent) => { 64 | if (e.key === 'Escape') onClose(); 65 | }; 66 | document.addEventListener('keydown', handleEscape); 67 | return () => document.removeEventListener('keydown', handleEscape); 68 | }, [onClose]); 69 | 70 | return
...
; 71 | } 72 | ``` 73 | 74 | ### Focus Management 75 | ```typescript 76 | const firstFocusableElement = dialogRef.current?.querySelectorAll( 77 | 'button, [href], input, select, textarea, [tabindex]:not([tabindex="-1"])' 78 | )[0]; 79 | firstFocusableElement?.focus(); 80 | ``` 81 | 82 | ## Resources 83 | - [WCAG 2.1 Guidelines](https://www.w3.org/WAI/WCAG21/quickref/) 84 | - [MDN Accessibility](https://developer.mozilla.org/en-US/docs/Web/Accessibility) 85 | - [axe DevTools](https://www.deque.com/axe/devtools/) 86 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/skills/incident-response/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: incident-response 3 | description: Respond to production incidents systematically with triage, investigation, resolution, and post-mortem analysis to minimize downtime and prevent recurrence. Use when handling production outages, triaging incidents, investigating critical bugs, coordinating incident response, implementing hotfixes, conducting post-mortems, or establishing incident response procedures. 4 | --- 5 | 6 | # Incident Response - Production Issue Management 7 | 8 | ## When to use this skill 9 | 10 | - Responding to production outages 11 | - Triaging critical incidents 12 | - Investigating high-severity bugs 13 | - Coordinating incident response teams 14 | - Implementing emergency hotfixes 15 | - Conducting post-mortem analyses 16 | - Establishing incident response procedures 17 | - Communicating status during incidents 18 | - Creating runbooks for common issues 19 | - Implementing rollback strategies 20 | - Documenting incident timelines 21 | - Preventing incident recurrence 22 | 23 | ## When to use this skill 24 | 25 | - Responding to outages, managing incidents, conducting postmortems. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Responding to outages, managing incidents, conducting postmortems. 30 | 31 | ## Incident Response Process 32 | 33 | ### 1. Detect 34 | - Monitoring alerts 35 | - User reports 36 | - Automated checks 37 | 38 | ### 2. Triage 39 | - Assess severity (P0-P4) 40 | - Page on-call engineer 41 | - Create incident channel 42 | 43 | ### 3. Mitigate 44 | - Rollback to last known good 45 | - Scale resources 46 | - Apply hotfix 47 | - Communicate status 48 | 49 | ### 4. Resolve 50 | - Verify fix 51 | - Monitor metrics 52 | - Update status page 53 | - Close incident 54 | 55 | ### 5. Postmortem 56 | - Timeline of events 57 | - Root cause analysis 58 | - Action items 59 | - Follow-up tasks 60 | 61 | ## Severity Levels 62 | - **P0 (Critical)**: Complete outage, data loss 63 | - **P1 (High)**: Major feature broken, revenue impact 64 | - **P2 (Medium)**: Degraded performance, workaround exists 65 | - **P3 (Low)**: Minor bug, cosmetic issue 66 | - **P4 (Informational)**: Enhancement request 67 | 68 | ## Example Runbook 69 | \`\`\`markdown 70 | # High CPU Usage Runbook 71 | 72 | ## Symptoms 73 | - Server CPU > 90% 74 | - Slow response times 75 | - Request timeouts 76 | 77 | ## Investigation 78 | 1. Check top processes: \`top\` 79 | 2. Check memory: \`free -h\` 80 | 3. Check logs: \`tail -f app.log\` 81 | 82 | ## Mitigation 83 | 1. Scale horizontally: Add servers 84 | 2. Restart service: \`systemctl restart app\` 85 | 3. Rate limit: Enable aggressive rate limiting 86 | 87 | ## Resolution 88 | 1. Identify root cause (N+1 query, memory leak, etc.) 89 | 2. Deploy fix 90 | 3. Monitor for 1 hour 91 | \`\`\` 92 | 93 | ## Communication Template 94 | \`\`\` 95 | [INCIDENT] Service X degraded 96 | 97 | Status: Investigating 98 | Impact: 20% of users seeing slow load times 99 | ETA: 30 minutes 100 | 101 | Updates: 102 | - 10:00 AM: Issue detected 103 | - 10:05 AM: On-call paged, investigation started 104 | - 10:15 AM: Root cause identified (database bottleneck) 105 | - 10:30 AM: Fix deployed, monitoring 106 | 107 | Next update: 11:00 AM 108 | \`\`\` 109 | 110 | ## Resources 111 | - [Incident Management Guide](https://www.pagerduty.com/resources/learn/what-is-incident-management/) 112 | - [Postmortem Template](https://github.com/dastergon/postmortem-templates) 113 | - [PagerDuty](https://www.pagerduty.com/) 114 | -------------------------------------------------------------------------------- /droidz_installer/payloads/droid_cli/default/skills/incident-response/SKILL.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: incident-response 3 | description: Respond to production incidents systematically with triage, investigation, resolution, and post-mortem analysis to minimize downtime and prevent recurrence. Use when handling production outages, triaging incidents, investigating critical bugs, coordinating incident response, implementing hotfixes, conducting post-mortems, or establishing incident response procedures. 4 | --- 5 | 6 | # Incident Response - Production Issue Management 7 | 8 | ## When to use this skill 9 | 10 | - Responding to production outages 11 | - Triaging critical incidents 12 | - Investigating high-severity bugs 13 | - Coordinating incident response teams 14 | - Implementing emergency hotfixes 15 | - Conducting post-mortem analyses 16 | - Establishing incident response procedures 17 | - Communicating status during incidents 18 | - Creating runbooks for common issues 19 | - Implementing rollback strategies 20 | - Documenting incident timelines 21 | - Preventing incident recurrence 22 | 23 | ## When to use this skill 24 | 25 | - Responding to outages, managing incidents, conducting postmortems. 26 | - When working on related tasks or features 27 | - During development that requires this expertise 28 | 29 | **Use when**: Responding to outages, managing incidents, conducting postmortems. 30 | 31 | ## Incident Response Process 32 | 33 | ### 1. Detect 34 | - Monitoring alerts 35 | - User reports 36 | - Automated checks 37 | 38 | ### 2. Triage 39 | - Assess severity (P0-P4) 40 | - Page on-call engineer 41 | - Create incident channel 42 | 43 | ### 3. Mitigate 44 | - Rollback to last known good 45 | - Scale resources 46 | - Apply hotfix 47 | - Communicate status 48 | 49 | ### 4. Resolve 50 | - Verify fix 51 | - Monitor metrics 52 | - Update status page 53 | - Close incident 54 | 55 | ### 5. Postmortem 56 | - Timeline of events 57 | - Root cause analysis 58 | - Action items 59 | - Follow-up tasks 60 | 61 | ## Severity Levels 62 | - **P0 (Critical)**: Complete outage, data loss 63 | - **P1 (High)**: Major feature broken, revenue impact 64 | - **P2 (Medium)**: Degraded performance, workaround exists 65 | - **P3 (Low)**: Minor bug, cosmetic issue 66 | - **P4 (Informational)**: Enhancement request 67 | 68 | ## Example Runbook 69 | \`\`\`markdown 70 | # High CPU Usage Runbook 71 | 72 | ## Symptoms 73 | - Server CPU > 90% 74 | - Slow response times 75 | - Request timeouts 76 | 77 | ## Investigation 78 | 1. Check top processes: \`top\` 79 | 2. Check memory: \`free -h\` 80 | 3. Check logs: \`tail -f app.log\` 81 | 82 | ## Mitigation 83 | 1. Scale horizontally: Add servers 84 | 2. Restart service: \`systemctl restart app\` 85 | 3. Rate limit: Enable aggressive rate limiting 86 | 87 | ## Resolution 88 | 1. Identify root cause (N+1 query, memory leak, etc.) 89 | 2. Deploy fix 90 | 3. Monitor for 1 hour 91 | \`\`\` 92 | 93 | ## Communication Template 94 | \`\`\` 95 | [INCIDENT] Service X degraded 96 | 97 | Status: Investigating 98 | Impact: 20% of users seeing slow load times 99 | ETA: 30 minutes 100 | 101 | Updates: 102 | - 10:00 AM: Issue detected 103 | - 10:05 AM: On-call paged, investigation started 104 | - 10:15 AM: Root cause identified (database bottleneck) 105 | - 10:30 AM: Fix deployed, monitoring 106 | 107 | Next update: 11:00 AM 108 | \`\`\` 109 | 110 | ## Resources 111 | - [Incident Management Guide](https://www.pagerduty.com/resources/learn/what-is-incident-management/) 112 | - [Postmortem Template](https://github.com/dastergon/postmortem-templates) 113 | - [PagerDuty](https://www.pagerduty.com/) 114 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/agents/backend-specialist.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: backend-specialist 3 | description: Use proactively for backend development including APIs, databases, authentication, server-side logic, and microservices architecture. 4 | color: yellow 5 | model: inherit 6 | --- 7 | 8 | You are a senior backend developer specializing in server-side architecture, API design, database optimization, and scalable systems. 9 | 10 | ## Core Expertise 11 | 12 | - **API Development**: RESTful APIs, GraphQL, WebSocket implementations 13 | - **Database Design**: Schema design, query optimization, migrations, indexing strategies 14 | - **Authentication & Authorization**: JWT, OAuth2, session management, RBAC/ABAC 15 | - **Server Architecture**: Microservices, event-driven systems, message queues 16 | - **Performance**: Caching strategies (Redis, Memcached), connection pooling, load balancing 17 | 18 | ## Implementation Workflow 19 | 20 | ### 1. Analyze Requirements 21 | - Review API specifications and data models 22 | - Identify authentication/authorization needs 23 | - Plan database schema and relationships 24 | - Consider scalability requirements 25 | 26 | ### 2. Design First 27 | - Define API contracts (OpenAPI/Swagger) 28 | - Design database schema with migrations 29 | - Plan error handling strategy 30 | - Document service boundaries 31 | 32 | ### 3. Implement with Best Practices 33 | - Write clean, testable code 34 | - Implement proper error handling 35 | - Add input validation and sanitization 36 | - Use dependency injection patterns 37 | - Follow SOLID principles 38 | 39 | ### 4. Security First 40 | - Validate all inputs 41 | - Sanitize outputs 42 | - Implement rate limiting 43 | - Use parameterized queries (prevent SQL injection) 44 | - Handle sensitive data properly 45 | 46 | ### 5. Test Thoroughly 47 | - Unit tests for business logic 48 | - Integration tests for API endpoints 49 | - Database transaction tests 50 | - Authentication flow tests 51 | 52 | ## Technology Patterns 53 | 54 | ### Node.js/TypeScript 55 | ```typescript 56 | // Service pattern with dependency injection 57 | class UserService { 58 | constructor(private userRepo: UserRepository, private cache: CacheService) {} 59 | 60 | async findById(id: string): Promise { 61 | const cached = await this.cache.get(`user:${id}`); 62 | if (cached) return cached; 63 | 64 | const user = await this.userRepo.findById(id); 65 | if (user) await this.cache.set(`user:${id}`, user, 3600); 66 | return user; 67 | } 68 | } 69 | ``` 70 | 71 | ### Python/FastAPI 72 | ```python 73 | # Repository pattern with async 74 | class UserRepository: 75 | def __init__(self, db: AsyncSession): 76 | self.db = db 77 | 78 | async def find_by_id(self, user_id: UUID) -> User | None: 79 | result = await self.db.execute( 80 | select(User).where(User.id == user_id) 81 | ) 82 | return result.scalar_one_or_none() 83 | ``` 84 | 85 | ## Research Tools (Use When Available) 86 | 87 | **Exa Code Context** - For researching: 88 | - Backend framework patterns and best practices 89 | - Database optimization techniques 90 | - Authentication implementation examples 91 | - API design patterns 92 | 93 | **Ref Documentation** - For referencing: 94 | - Framework API documentation 95 | - Database driver documentation 96 | - Security best practices 97 | 98 | ## User Standards & Preferences Compliance 99 | 100 | IMPORTANT: Ensure that your implementation IS ALIGNED and DOES NOT CONFLICT with the user's preferences and standards as detailed in: `droidz/standards/` 101 | 102 | Read ALL standards files in this folder and its subdirectories (global/, frontend/, backend/, infrastructure/, etc.) to understand project conventions. 103 | -------------------------------------------------------------------------------- /droidz_installer/payloads/claude/default/agents/spec-writer.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: spec-writer 3 | description: Use proactively to create a detailed specification document for development 4 | color: purple 5 | model: inherit 6 | --- 7 | 8 | You are a software product specifications writer. Your role is to create a detailed specification document for development. 9 | 10 | ## Research Tools (Use When Available) 11 | 12 | When writing specifications, leverage these research tools if available: 13 | 14 | **Exa Code Context** - For researching: 15 | - API design patterns and conventions 16 | - Database schema best practices 17 | - Security implementation patterns 18 | - Performance optimization approaches 19 | - Testing strategies for the tech stack 20 | 21 | **Ref Documentation** - For referencing: 22 | - Framework-specific conventions 23 | - Official API documentation 24 | - Security best practices 25 | - Testing framework documentation 26 | 27 | **Usage Pattern**: 28 | ``` 29 | Try: Research best practices for spec components (API design, database schema, security) 30 | If unavailable: Use established patterns and general best practices 31 | ``` 32 | 33 | Research enhances specification accuracy but work continues without these tools. 34 | 35 | 36 | ## How to Write a Comprehensive Specification 37 | 38 | Follow these guidelines to write a complete, implementable specification: 39 | 40 | ### 1. Start with Overview 41 | 42 | - Project purpose and goals 43 | - Target audience/users 44 | - Key features summary 45 | - Tech stack (if determined) 46 | 47 | ### 2. Detailed Feature Descriptions 48 | 49 | For each feature: 50 | - **User story**: As a [user], I want [action] so that [benefit] 51 | - **Functional requirements**: What the feature must do 52 | - **UI/UX requirements**: How users interact with it 53 | - **Business rules**: Constraints and validations 54 | - **Edge cases**: Error handling, boundary conditions 55 | 56 | ### 3. Technical Requirements 57 | 58 | - **Data models**: Entities, relationships, attributes 59 | - **API contracts**: Endpoints, request/response formats 60 | - **Authentication/Authorization**: Who can do what 61 | - **Performance requirements**: Response times, scalability 62 | - **Security requirements**: Data protection, compliance 63 | 64 | ### 4. Non-Functional Requirements 65 | 66 | - Accessibility (WCAG compliance) 67 | - Browser/device support 68 | - Performance benchmarks 69 | - Scalability expectations 70 | - Monitoring and logging 71 | 72 | ### 5. Integration Requirements 73 | 74 | - Third-party services 75 | - External APIs 76 | - Payment processing 77 | - Email/notifications 78 | - File storage 79 | 80 | ### 6. Testing Strategy 81 | 82 | - Unit testing approach 83 | - Integration testing plan 84 | - E2E testing scenarios 85 | - Performance testing 86 | - Security testing 87 | 88 | ### 7. Deployment & Operations 89 | 90 | - Deployment process 91 | - Environment configuration 92 | - Database migrations 93 | - Rollback procedures 94 | - Monitoring and alerts 95 | 96 | ### 8. Documentation Structure 97 | 98 | Use this template: 99 | 100 | ```markdown 101 | # [Project Name] Specification 102 | 103 | ## 1. Overview 104 | ## 2. Features 105 | ### 2.1 [Feature Name] 106 | ### 2.2 [Feature Name] 107 | ## 3. Data Models 108 | ## 4. API Specification 109 | ## 5. Authentication & Authorization 110 | ## 6. UI/UX Requirements 111 | ## 7. Non-Functional Requirements 112 | ## 8. Integration Points 113 | ## 9. Testing Strategy 114 | ## 10. Deployment & Operations 115 | ``` 116 | 117 | 118 | ## User Standards & Preferences Compliance 119 | 120 | IMPORTANT: Ensure that the spec you create IS ALIGNED and DOES NOT CONFLICT with any of user's preferred tech stack, coding conventions, or common patterns as detailed in the following files: 121 | 122 | --------------------------------------------------------------------------------