@orderful/droid 0.14.0 → 0.15.0

package/src/tools/comments/TOOL.yaml

@@ -1,5 +1,5 @@
 name: comments
-description: "Enable inline conversations using @droid/@user markers. Tag @droid to ask the AI, AI responds with @{your-name}. Ideal for code review notes and async collaboration."
+description: "Enable inline conversations using @droid/@user markers. Tag @droid to ask the AI, AI responds with @{your-name}. Use /comments check to address markers, /comments cleanup to remove resolved threads. Ideal for code review notes and async collaboration."
 version: 0.2.3
 status: beta
 
@@ -19,7 +19,7 @@ config_schema:
     description: Override the global user mention for this skill
   ai_mentions:
     type: string
-    description: Additional AI mentions to recognize (comma-separated)
+    description: Additional AI mentions to recognize (comma-separated, e.g., "@claude,@ai")
     default: ""
   preserve_comments:
     type: boolean

package/src/tools/comments/skills/comments/SKILL.md

@@ -4,6 +4,7 @@ description: "Enable inline conversations using @droid/@user markers. Tag @droid
 globs:
   - "**/*"
 alwaysApply: false
+allowed-tools: Read, Grep, Glob, Edit
 ---
 
 # Comments Skill

package/src/tools/droid/skills/droid/SKILL.md

@@ -4,6 +4,7 @@ description: "Core droid meta-skill for update awareness and tool discovery. Che
 globs:
   - "**/*"
 alwaysApply: false
+allowed-tools: Bash
 ---
 
 # Droid

package/src/tools/project/skills/project/SKILL.md

@@ -4,6 +4,7 @@ description: "Manage project context files for persistent AI memory across sessi
 globs:
   - "**/PROJECT.md"
 alwaysApply: false
+allowed-tools: Read, Write, Glob, Grep
 ---
 
 # Project Skill

package/dist/tools/brain/skills/brain/SKILL.yaml

@@ -1,29 +0,0 @@
-name: brain
-description: "Your scratchpad (or brain) - a collaborative space for planning and research. Triggers on phrases like 'let's use our brain', 'open a scratchpad', or 'plan this out' to capture AI output into a persistent doc. Create docs with /brain plan (or /scratchpad plan), /brain research, or /brain review. Use @mentions for async discussion. Docs persist across sessions."
-version: 0.2.0
-status: beta
-dependencies: []
-provides_output: false
-command_aliases:
-  scratchpad: brain
-config_schema:
-  brain_dir:
-    type: string
-    description: Directory for brain docs (default varies by AI tool)
-  inbox_folder:
-    type: string
-    description: Subfolder for new docs (empty = flat structure)
-    default: ""
-examples:
-  - title: "Start a planning doc"
-    code: |
-      /brain plan auth refactor
-      # Creates planning doc, becomes active for session
-  - title: "Quick note capture"
-    code: |
-      /brain note Remember to check rate limits on the API
-      # Fire-and-forget to inbox
-  - title: "Check for comments"
-    code: |
-      /brain check
-      # Find and address @mentions in active doc

package/dist/tools/brain/skills/brain-obsidian/SKILL.yaml

@@ -1,42 +0,0 @@
-name: brain-obsidian
-description: "Obsidian extension for brain skill. Adds YAML frontmatter, wikilinks, and folder organization. Requires brain skill. Install this to use brain docs with your Obsidian vault."
-version: 0.1.0
-status: beta
-dependencies:
-  - brain
-  # Optional: project skill enables linking features
-provides_output: false
-config_schema:
-  inbox_folder:
-    type: string
-    description: Folder for new brain docs
-    default: "0-Inbox"
-  archive_folder:
-    type: string
-    description: Folder for archived/stale docs
-    default: "4-Archives"
-  para_structure:
-    type: boolean
-    description: Enable full PARA folder organization
-    default: false
-  projects_folder:
-    type: string
-    description: Folder for active project docs (when para_structure is true)
-    default: "1-Projects"
-  areas_folder:
-    type: string
-    description: Folder for area docs (when para_structure is true)
-    default: "1-Areas"
-  resources_folder:
-    type: string
-    description: Folder for reference material (when para_structure is true)
-    default: "3-Resources"
-examples:
-  - title: "Create planning doc in vault"
-    code: |
-      /brain plan auth refactor
-      # Creates in vault's 0-Inbox/ with YAML frontmatter
-  - title: "Link to project"
-    code: |
-      /brain plan feature-x
-      # Frontmatter includes project: "[[feature-x]]"

package/dist/tools/coach/skills/coach/SKILL.yaml

@@ -1,25 +0,0 @@
-name: coach
-description: "Learning-mode AI assistance - AI as coach, not crutch. Triggers on phrases like 'help me think through', 'coach me on', 'I want to learn how to', or 'don't just give me the answer'. Use /coach plan for co-authored planning, /coach scaffold for structure with hints, /coach review for Socratic questions on your code."
-version: 0.1.0
-status: beta
-dependencies:
-  - comments
-provides_output: false
-config_schema:
-  scaffold_verbosity:
-    type: string
-    description: "How detailed scaffold hints should be: minimal (signatures only), medium (hints), detailed (pseudocode)"
-    default: "medium"
-examples:
-  - title: "Start co-authored planning"
-    code: |
-      /coach plan add user authentication
-      # AI asks questions, proposes structure, offers to create brain doc
-  - title: "Get scaffold for implementation"
-    code: |
-      /coach scaffold
-      # AI generates types/signatures with hint comments, you fill in logic
-  - title: "Review your implementation"
-    code: |
-      /coach review src/auth/login.ts
-      # AI adds inline // @you questions via comments skill

package/dist/tools/code-review/agents/edi-standards-reviewer/AGENT.yaml

@@ -1,14 +0,0 @@
-name: edi-standards-reviewer
-description: >-
-  Review code for EDI integration patterns, partnership handling, and billing
-  system concerns. Use PROACTIVELY when changes touch trading partners,
-  transactions, or billing.
-version: 0.1.0
-status: alpha
-mode: subagent
-model: sonnet
-color: blue
-tools:
-  - Read
-  - Grep
-  - Glob

package/dist/tools/code-review/agents/error-handling-reviewer/AGENT.yaml

@@ -1,14 +0,0 @@
-name: error-handling-reviewer
-description: >-
-  Hunt for silent failures and missing error handling. Use PROACTIVELY to find
-  try/catch blocks that swallow errors, promises without rejection handling,
-  and missing validation.
-version: 0.1.0
-status: alpha
-mode: subagent
-model: sonnet
-color: orange
-tools:
-  - Read
-  - Grep
-  - Glob

package/dist/tools/code-review/agents/test-coverage-analyzer/AGENT.yaml

@@ -1,14 +0,0 @@
-name: test-coverage-analyzer
-description: >-
-  Analyze test coverage for code changes. Use PROACTIVELY when reviewing PRs
-  or before merging to ensure adequate test coverage.
-version: 0.1.0
-status: alpha
-mode: subagent
-model: sonnet
-color: green
-tools:
-  - Read
-  - Grep
-  - Glob
-  - Bash

package/dist/tools/code-review/agents/type-reviewer/AGENT.yaml

@@ -1,13 +0,0 @@
-name: type-reviewer
-description: >-
-  Review TypeScript type design and interface contracts. Check for proper
-  typing, avoid `any`, ensure domain types are used correctly.
-version: 0.1.0
-status: alpha
-mode: subagent
-model: sonnet
-color: purple
-tools:
-  - Read
-  - Grep
-  - Glob

package/dist/tools/code-review/skills/code-review/SKILL.yaml

@@ -1,19 +0,0 @@
-name: code-review
-description: "Comprehensive code review using specialized agents. Reviews PRs, staged changes, branches, or specific files. Includes EDI/partnership analysis, test coverage, error handling, and type safety checks with confidence scoring."
-version: 0.1.0
-status: alpha
-dependencies: []
-provides_output: false
-examples:
-  - title: "Review a PR"
-    code: |
-      /code-review #123
-  - title: "Review staged changes"
-    code: |
-      /code-review staged
-  - title: "Review current branch vs main"
-    code: |
-      /code-review branch
-  - title: "Review a specific file"
-    code: |
-      /code-review src/billing/BillingService.ts

package/dist/tools/comments/skills/comments/SKILL.yaml

@@ -1,50 +0,0 @@
-name: comments
-description: "Enable inline conversations using @droid/@user markers. Tag @droid to ask the AI, AI responds with @{your-name}. Use /comments check to address markers, /comments cleanup to remove resolved threads. Ideal for code review notes and async collaboration."
-version: 0.2.3
-status: beta
-dependencies: []
-provides_output: false
-config_schema:
-  user_mention:
-    type: string
-    description: Override the global user mention for this skill
-  ai_mentions:
-    type: string
-    description: Additional AI mentions to recognize (comma-separated, e.g., "@claude,@ai")
-    default: ""
-  preserve_comments:
-    type: boolean
-    description: Keep original comments after addressing (vs removing them)
-    default: true
-examples:
-  - title: "Action request"
-    code: |
-      // @droid use PascalCase for enum keys
-      enum Status {
-        PENDING = 'pending'
-      }
-  - title: "Ask a question"
-    code: |
-      > @droid Should we cache this?
-
-      > @fry Yes, add Redis caching here...
-  - title: "TODO with context"
-    code: |
-      // @droid TODO: refactor to async/await
-      // The callback pattern is unwieldy
-      function fetchData(callback) {
-        api.get('/data', callback);
-      }
-  - title: "Code review note"
-    code: |
-      // @droid potential memory leak here
-      // Clear interval on unmount?
-      useEffect(() => {
-        setInterval(poll, 1000);
-      }, []);
-  - title: "Multi-line discussion"
-    code: |
-      > @droid Best approach for pagination?
-      > We have ~10k records.
-
-      > @fry Use cursor-based, limit 50.

package/dist/tools/droid/skills/droid/SKILL.yaml

@@ -1,7 +0,0 @@
-name: droid
-description: "Core droid meta-skill for update awareness and tool discovery. Checks for updates and helps users find the right tools."
-version: 0.2.0
-status: beta
-dependencies: []
-provides_output: false
-config_schema: {}

package/dist/tools/project/skills/project/SKILL.yaml

@@ -1,30 +0,0 @@
-name: project
-description: "Manage project context files for persistent AI memory across sessions. Load project context before working (/project {name}), update with new learnings (/project update), or create new projects (/project create). Use when working on multi-session features, refactors, or any work that benefits from accumulated context."
-version: 0.1.2
-status: beta
-dependencies: []
-provides_output: false
-config_schema:
-  projects_dir:
-    type: string
-    description: Path to projects directory (default varies by AI tool)
-  preset:
-    type: select
-    description: Output format for templates
-    default: "markdown"
-    options:
-      - markdown
-      - obsidian
-examples:
-  - title: "Load project by name"
-    code: |
-      /project transaction templates
-      # Fuzzy matches "transaction-templates" folder
-  - title: "Update after work session"
-    code: |
-      /project update
-      # Analyzes conversation, proposes PROJECT.md updates
-  - title: "Create new project"
-    code: |
-      /project create billing-refactor
-      # Creates folder with PROJECT.md and CHANGELOG.md

package/src/tools/brain/skills/brain/SKILL.yaml

@@ -1,29 +0,0 @@
-name: brain
-description: "Your scratchpad (or brain) - a collaborative space for planning and research. Triggers on phrases like 'let's use our brain', 'open a scratchpad', or 'plan this out' to capture AI output into a persistent doc. Create docs with /brain plan (or /scratchpad plan), /brain research, or /brain review. Use @mentions for async discussion. Docs persist across sessions."
-version: 0.2.0
-status: beta
-dependencies: []
-provides_output: false
-command_aliases:
-  scratchpad: brain
-config_schema:
-  brain_dir:
-    type: string
-    description: Directory for brain docs (default varies by AI tool)
-  inbox_folder:
-    type: string
-    description: Subfolder for new docs (empty = flat structure)
-    default: ""
-examples:
-  - title: "Start a planning doc"
-    code: |
-      /brain plan auth refactor
-      # Creates planning doc, becomes active for session
-  - title: "Quick note capture"
-    code: |
-      /brain note Remember to check rate limits on the API
-      # Fire-and-forget to inbox
-  - title: "Check for comments"
-    code: |
-      /brain check
-      # Find and address @mentions in active doc

package/src/tools/brain/skills/brain-obsidian/SKILL.yaml

@@ -1,42 +0,0 @@
-name: brain-obsidian
-description: "Obsidian extension for brain skill. Adds YAML frontmatter, wikilinks, and folder organization. Requires brain skill. Install this to use brain docs with your Obsidian vault."
-version: 0.1.0
-status: beta
-dependencies:
-  - brain
-  # Optional: project skill enables linking features
-provides_output: false
-config_schema:
-  inbox_folder:
-    type: string
-    description: Folder for new brain docs
-    default: "0-Inbox"
-  archive_folder:
-    type: string
-    description: Folder for archived/stale docs
-    default: "4-Archives"
-  para_structure:
-    type: boolean
-    description: Enable full PARA folder organization
-    default: false
-  projects_folder:
-    type: string
-    description: Folder for active project docs (when para_structure is true)
-    default: "1-Projects"
-  areas_folder:
-    type: string
-    description: Folder for area docs (when para_structure is true)
-    default: "1-Areas"
-  resources_folder:
-    type: string
-    description: Folder for reference material (when para_structure is true)
-    default: "3-Resources"
-examples:
-  - title: "Create planning doc in vault"
-    code: |
-      /brain plan auth refactor
-      # Creates in vault's 0-Inbox/ with YAML frontmatter
-  - title: "Link to project"
-    code: |
-      /brain plan feature-x
-      # Frontmatter includes project: "[[feature-x]]"

package/src/tools/coach/skills/coach/SKILL.yaml

@@ -1,25 +0,0 @@
-name: coach
-description: "Learning-mode AI assistance - AI as coach, not crutch. Triggers on phrases like 'help me think through', 'coach me on', 'I want to learn how to', or 'don't just give me the answer'. Use /coach plan for co-authored planning, /coach scaffold for structure with hints, /coach review for Socratic questions on your code."
-version: 0.1.0
-status: beta
-dependencies:
-  - comments
-provides_output: false
-config_schema:
-  scaffold_verbosity:
-    type: string
-    description: "How detailed scaffold hints should be: minimal (signatures only), medium (hints), detailed (pseudocode)"
-    default: "medium"
-examples:
-  - title: "Start co-authored planning"
-    code: |
-      /coach plan add user authentication
-      # AI asks questions, proposes structure, offers to create brain doc
-  - title: "Get scaffold for implementation"
-    code: |
-      /coach scaffold
-      # AI generates types/signatures with hint comments, you fill in logic
-  - title: "Review your implementation"
-    code: |
-      /coach review src/auth/login.ts
-      # AI adds inline // @you questions via comments skill

package/src/tools/code-review/agents/edi-standards-reviewer/AGENT.yaml

@@ -1,14 +0,0 @@
-name: edi-standards-reviewer
-description: >-
-  Review code for EDI integration patterns, partnership handling, and billing
-  system concerns. Use PROACTIVELY when changes touch trading partners,
-  transactions, or billing.
-version: 0.1.0
-status: alpha
-mode: subagent
-model: sonnet
-color: blue
-tools:
-  - Read
-  - Grep
-  - Glob

package/src/tools/code-review/agents/error-handling-reviewer/AGENT.yaml

@@ -1,14 +0,0 @@
-name: error-handling-reviewer
-description: >-
-  Hunt for silent failures and missing error handling. Use PROACTIVELY to find
-  try/catch blocks that swallow errors, promises without rejection handling,
-  and missing validation.
-version: 0.1.0
-status: alpha
-mode: subagent
-model: sonnet
-color: orange
-tools:
-  - Read
-  - Grep
-  - Glob

package/src/tools/code-review/agents/test-coverage-analyzer/AGENT.yaml

@@ -1,14 +0,0 @@
-name: test-coverage-analyzer
-description: >-
-  Analyze test coverage for code changes. Use PROACTIVELY when reviewing PRs
-  or before merging to ensure adequate test coverage.
-version: 0.1.0
-status: alpha
-mode: subagent
-model: sonnet
-color: green
-tools:
-  - Read
-  - Grep
-  - Glob
-  - Bash

package/src/tools/code-review/agents/type-reviewer/AGENT.yaml

@@ -1,13 +0,0 @@
-name: type-reviewer
-description: >-
-  Review TypeScript type design and interface contracts. Check for proper
-  typing, avoid `any`, ensure domain types are used correctly.
-version: 0.1.0
-status: alpha
-mode: subagent
-model: sonnet
-color: purple
-tools:
-  - Read
-  - Grep
-  - Glob

package/src/tools/code-review/skills/code-review/SKILL.yaml

@@ -1,19 +0,0 @@
-name: code-review
-description: "Comprehensive code review using specialized agents. Reviews PRs, staged changes, branches, or specific files. Includes EDI/partnership analysis, test coverage, error handling, and type safety checks with confidence scoring."
-version: 0.1.0
-status: alpha
-dependencies: []
-provides_output: false
-examples:
-  - title: "Review a PR"
-    code: |
-      /code-review #123
-  - title: "Review staged changes"
-    code: |
-      /code-review staged
-  - title: "Review current branch vs main"
-    code: |
-      /code-review branch
-  - title: "Review a specific file"
-    code: |
-      /code-review src/billing/BillingService.ts

package/src/tools/comments/skills/comments/SKILL.yaml

@@ -1,50 +0,0 @@
-name: comments
-description: "Enable inline conversations using @droid/@user markers. Tag @droid to ask the AI, AI responds with @{your-name}. Use /comments check to address markers, /comments cleanup to remove resolved threads. Ideal for code review notes and async collaboration."
-version: 0.2.3
-status: beta
-dependencies: []
-provides_output: false
-config_schema:
-  user_mention:
-    type: string
-    description: Override the global user mention for this skill
-  ai_mentions:
-    type: string
-    description: Additional AI mentions to recognize (comma-separated, e.g., "@claude,@ai")
-    default: ""
-  preserve_comments:
-    type: boolean
-    description: Keep original comments after addressing (vs removing them)
-    default: true
-examples:
-  - title: "Action request"
-    code: |
-      // @droid use PascalCase for enum keys
-      enum Status {
-        PENDING = 'pending'
-      }
-  - title: "Ask a question"
-    code: |
-      > @droid Should we cache this?
-
-      > @fry Yes, add Redis caching here...
-  - title: "TODO with context"
-    code: |
-      // @droid TODO: refactor to async/await
-      // The callback pattern is unwieldy
-      function fetchData(callback) {
-        api.get('/data', callback);
-      }
-  - title: "Code review note"
-    code: |
-      // @droid potential memory leak here
-      // Clear interval on unmount?
-      useEffect(() => {
-        setInterval(poll, 1000);
-      }, []);
-  - title: "Multi-line discussion"
-    code: |
-      > @droid Best approach for pagination?
-      > We have ~10k records.
-
-      > @fry Use cursor-based, limit 50.

package/src/tools/droid/skills/droid/SKILL.yaml

@@ -1,7 +0,0 @@
-name: droid
-description: "Core droid meta-skill for update awareness and tool discovery. Checks for updates and helps users find the right tools."
-version: 0.2.0
-status: beta
-dependencies: []
-provides_output: false
-config_schema: {}

package/src/tools/project/skills/project/SKILL.yaml

@@ -1,30 +0,0 @@
-name: project
-description: "Manage project context files for persistent AI memory across sessions. Load project context before working (/project {name}), update with new learnings (/project update), or create new projects (/project create). Use when working on multi-session features, refactors, or any work that benefits from accumulated context."
-version: 0.1.2
-status: beta
-dependencies: []
-provides_output: false
-config_schema:
-  projects_dir:
-    type: string
-    description: Path to projects directory (default varies by AI tool)
-  preset:
-    type: select
-    description: Output format for templates
-    default: "markdown"
-    options:
-      - markdown
-      - obsidian
-examples:
-  - title: "Load project by name"
-    code: |
-      /project transaction templates
-      # Fuzzy matches "transaction-templates" folder
-  - title: "Update after work session"
-    code: |
-      /project update
-      # Analyzes conversation, proposes PROJECT.md updates
-  - title: "Create new project"
-    code: |
-      /project create billing-refactor
-      # Creates folder with PROJECT.md and CHANGELOG.md