@orderful/droid 0.10.5 → 0.11.1

package/src/lib/types.ts

@@ -1,8 +1,14 @@
-export enum AITool {
+export enum Platform {
   ClaudeCode = 'claude-code',
   OpenCode = 'opencode',
 }
 
+// Backwards compatibility alias - using different names to avoid redeclare error
+// eslint-disable-next-line @typescript-eslint/no-unused-vars
+const AIToolValue = Platform;
+export { AIToolValue as AITool };
+export type AITool = Platform;
+
 /**
  * Get the AI's mention tag
  * Always @droid - consistent branding regardless of underlying AI tool
@@ -32,14 +38,44 @@ export enum ConfigOptionType {
   Select = 'select',
 }
 
+export interface PlatformConfig {
+  tools: Record<string, InstalledSkill>;
+}
+
 export interface DroidConfig {
-  ai_tool: AITool;
+  platform: Platform;
+  user_mention: string;
+  output_preference: OutputPreference;
+  git_username: string;
+  platforms: Record<string, PlatformConfig>;
+}
+
+// Legacy config structure for migration
+export interface LegacyDroidConfig {
+  ai_tool: Platform;
   user_mention: string;
   output_preference: OutputPreference;
   git_username: string;
   skills: Record<string, InstalledSkill>;
 }
 
+/**
+ * Get installed tools for the current platform
+ */
+export function getPlatformTools(config: DroidConfig): Record<string, InstalledSkill> {
+  return config.platforms[config.platform]?.tools ?? {};
+}
+
+/**
+ * Set installed tools for the current platform
+ */
+export function setPlatformTools(config: DroidConfig, tools: Record<string, InstalledSkill>): void {
+  if (!config.platforms[config.platform]) {
+    config.platforms[config.platform] = { tools: {} };
+  }
+  config.platforms[config.platform].tools = tools;
+}
+
 export interface InstalledSkill {
   version: string;
   installed_at: string;
@@ -77,3 +113,28 @@ export interface ConfigOption {
 export interface SkillOverrides {
   [key: string]: string | boolean | number;
 }
+
+/**
+ * Tool manifest structure (TOOL.yaml)
+ */
+export interface ToolSkillInclude {
+  name: string;
+  required: boolean;
+  description?: string;
+}
+
+export interface ToolIncludes {
+  skills: ToolSkillInclude[];
+  commands: string[];
+  agents: string[];
+}
+
+export interface ToolManifest {
+  name: string;
+  description: string;
+  version: string;
+  status?: SkillStatus;
+  includes: ToolIncludes;
+  dependencies?: string[];
+  config_schema?: Record<string, ConfigOption>;
+}

package/src/tools/brain/TOOL.yaml

@@ -0,0 +1,27 @@
+name: brain
+description: "Collaborative scratchpad for planning and research. Create docs with /brain plan, /brain research, or /brain review. Use @mentions for async discussion. Docs persist across sessions."
+version: 0.2.0
+status: beta
+
+includes:
+  skills:
+    - name: brain
+      required: true
+    - name: brain-obsidian
+      required: false
+      description: "Obsidian vault integration with YAML frontmatter and wikilinks"
+  commands:
+    - brain
+    - scratchpad
+  agents: []
+
+dependencies: []
+
+config_schema:
+  brain_dir:
+    type: string
+    description: Directory for brain docs (default varies by platform)
+  inbox_folder:
+    type: string
+    description: Subfolder for new docs (empty = flat structure)
+    default: ""

package/src/tools/coach/TOOL.yaml

@@ -0,0 +1,21 @@
+name: coach
+description: "Learning-mode AI assistance - AI as coach, not crutch. Use /coach plan for co-authored planning, /coach scaffold for structure with hints, /coach review for Socratic questions."
+version: 0.1.0
+status: beta
+
+includes:
+  skills:
+    - name: coach
+      required: true
+  commands:
+    - coach
+  agents: []
+
+dependencies:
+  - comments
+
+config_schema:
+  scaffold_verbosity:
+    type: string
+    description: "How detailed scaffold hints should be: minimal, medium, detailed"
+    default: "medium"

package/src/tools/code-review/TOOL.yaml

@@ -0,0 +1,18 @@
+name: code-review
+description: "Comprehensive code review using specialized agents. Reviews PRs, staged changes, branches, or specific files with confidence scoring."
+version: 0.1.0
+status: alpha
+
+includes:
+  skills:
+    - name: code-review
+      required: true
+  commands:
+    - code-review
+  agents:
+    - edi-standards-reviewer
+    - error-handling-reviewer
+    - test-coverage-analyzer
+    - type-reviewer
+
+dependencies: []

package/src/tools/comments/TOOL.yaml

@@ -0,0 +1,27 @@
+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."
+version: 0.2.3
+status: beta
+
+includes:
+  skills:
+    - name: comments
+      required: true
+  commands:
+    - comments
+  agents: []
+
+dependencies: []
+
+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)
+    default: ""
+  preserve_comments:
+    type: boolean
+    description: Keep original comments after addressing (vs removing them)
+    default: true

package/src/{skills → tools/comments/skills}/comments/SKILL.md

@@ -79,13 +79,22 @@ When you find a `@droid` marker:
 
 ### On `/comments check`:
 
+**Use a two-pass approach for coherent responses:**
+
+#### Pass 1: Read & Analyse
 1. **Read config first:** Check `~/.droid/skills/comments/overrides.yaml` for `preserve_comments` setting (default: `true`)
-2. Search for `> @droid` (and any configured `ai_mentions`) in the specified scope
+2. Search for ALL `> @droid` comments (and any configured `ai_mentions`) in the specified scope
 3. If there's a `git diff`, check those files first for relevant context
-4. For each comment, determine intent:
+4. **Read all comments before responding** - understand the full picture
+5. Look for connections between comments (one may inform another)
+6. Note any contradictions or tensions to address
+
+#### Pass 2: Respond & Write
+1. For each comment, determine intent:
    - **Action request** ("do X", "add Y", "fix Z") → Execute the action
    - **Question** ("what do you think", "should we") → Respond with `> @{user_mention}`
-5. **Handle original comment based on `preserve_comments`:**
+2. Ensure responses are coherent across all comments (don't contradict yourself)
+3. **Handle original comment based on `preserve_comments`:**
    - If `preserve_comments: true` → Keep the original `@droid` comment (add response below it)
    - If `preserve_comments: false` → Remove the original comment after addressing
 

package/src/{skills → tools/comments/skills}/comments/SKILL.yaml

@@ -1,6 +1,6 @@
 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.2
+version: 0.2.3
 status: beta
 dependencies: []
 provides_output: false

package/src/tools/project/TOOL.yaml

@@ -0,0 +1,26 @@
+name: project
+description: "Manage project context files for persistent AI memory across sessions. Load, update, or create project context before working on multi-session features."
+version: 0.1.2
+status: beta
+
+includes:
+  skills:
+    - name: project
+      required: true
+  commands:
+    - project
+  agents: []
+
+dependencies: []
+
+config_schema:
+  projects_dir:
+    type: string
+    description: Path to projects directory (default varies by platform)
+  preset:
+    type: select
+    description: Output format for templates
+    default: "markdown"
+    options:
+      - markdown
+      - obsidian

package/dist/agents/README.md

@@ -1,137 +0,0 @@
-# Contributing Agents
-
-Agents are specialized AI personas with specific expertise or roles. They augment the AI's capabilities for particular tasks.
-
-## Directory Structure
-
-Each agent is a directory containing:
-
-```
-agents/
-└── my-agent/
-    ├── AGENT.yaml      # Required: Manifest with metadata and persona
-    └── AGENT.md        # Required: Documentation for users
-```
-
-## AGENT.yaml (Manifest)
-
-```yaml
-name: my-agent                          # Must match directory name
-description: Short description          # Shown in TUI and listings
-version: 1.0.0                          # Semver
-status: alpha                           # alpha | beta | stable (optional)
-
-# Agent type (required)
-mode: subagent                          # primary | subagent | all
-
-# Tools this agent can use (optional)
-tools:
-  - Read
-  - Glob
-  - Grep
-  - Bash
-
-# Suggested triggers - phrases that might invoke this agent
-triggers:
-  - "review my code"
-  - "check for bugs"
-
-# Persona - system prompt additions for this agent (used if AGENT.md is minimal)
-persona: |
-  You are a specialized assistant focused on...
-
-  Your priorities are:
-  1. First priority
-  2. Second priority
-
-  Always be specific and constructive.
-```
-
-### Agent Modes
-
-- **`primary`** - Main agents you interact with directly. Cycle through them with Tab key.
-- **`subagent`** - Specialized helpers invoked via @mention (e.g., `@code-reviewer check this`) or by primary agents.
-- **`all`** - Agent works as both primary and subagent.
-
-## AGENT.md (Documentation)
-
-The AGENT.md file documents the agent for users:
-
-```markdown
----
-name: my-agent
-description: Short description (must match AGENT.yaml)
----
-
-# My Agent
-
-Description of what this agent does and when to use it.
-
-## What It Does
-
-- Bullet points of capabilities
-- What it focuses on
-- What it ignores
-
-## Usage
-
-Examples of how to invoke or use this agent.
-
-## Output Format
-
-Description of how the agent formats its responses.
-```
-
-## Example Agent
-
-See `code-reviewer/` for a complete example:
-
-- Reviews code for bugs, security issues, style
-- Categorizes issues by severity (critical/warning/suggestion)
-- References specific file and line numbers
-
-## Ideas for Agents
-
-- **test-writer** - Generates unit tests for code
-- **doc-writer** - Writes documentation and comments
-- **refactorer** - Suggests and applies refactoring patterns
-- **security-auditor** - Deep security analysis
-- **performance-optimizer** - Identifies performance bottlenecks
-
-## Installation
-
-When you install an agent via the TUI, droid:
-
-1. Reads `AGENT.yaml` for metadata (name, description, tools)
-2. Reads `AGENT.md` for the agent's instructions/persona
-3. Combines them into a single `.md` file with frontmatter
-4. Writes to `~/.claude/agents/{name}.md`
-
-The installed format matches what Claude Code expects:
-
-```markdown
----
-name: my-agent
-description: Short description
-tools: Read, Glob, Grep, Bash
----
-
-[Content from AGENT.md]
-```
-
-## Testing Your Agent
-
-1. Run `npm run build` to compile
-2. Run `droid` to open the TUI
-3. Navigate to Agents tab
-4. Verify your agent appears with correct metadata
-5. Install and verify it appears in `~/.claude/agents/`
-
-## Checklist
-
-- [ ] `AGENT.yaml` has all required fields (name, description, version, mode)
-- [ ] `AGENT.md` contains the agent's instructions/persona
-- [ ] Name matches directory name
-- [ ] Description is clear and concise
-- [ ] Mode is appropriate (subagent for specialized tasks, primary for main assistants)
-- [ ] Tools list only includes what the agent needs

package/src/agents/README.md

@@ -1,137 +0,0 @@
-# Contributing Agents
-
-Agents are specialized AI personas with specific expertise or roles. They augment the AI's capabilities for particular tasks.
-
-## Directory Structure
-
-Each agent is a directory containing:
-
-```
-agents/
-└── my-agent/
-    ├── AGENT.yaml      # Required: Manifest with metadata and persona
-    └── AGENT.md        # Required: Documentation for users
-```
-
-## AGENT.yaml (Manifest)
-
-```yaml
-name: my-agent                          # Must match directory name
-description: Short description          # Shown in TUI and listings
-version: 1.0.0                          # Semver
-status: alpha                           # alpha | beta | stable (optional)
-
-# Agent type (required)
-mode: subagent                          # primary | subagent | all
-
-# Tools this agent can use (optional)
-tools:
-  - Read
-  - Glob
-  - Grep
-  - Bash
-
-# Suggested triggers - phrases that might invoke this agent
-triggers:
-  - "review my code"
-  - "check for bugs"
-
-# Persona - system prompt additions for this agent (used if AGENT.md is minimal)
-persona: |
-  You are a specialized assistant focused on...
-
-  Your priorities are:
-  1. First priority
-  2. Second priority
-
-  Always be specific and constructive.
-```
-
-### Agent Modes
-
-- **`primary`** - Main agents you interact with directly. Cycle through them with Tab key.
-- **`subagent`** - Specialized helpers invoked via @mention (e.g., `@code-reviewer check this`) or by primary agents.
-- **`all`** - Agent works as both primary and subagent.
-
-## AGENT.md (Documentation)
-
-The AGENT.md file documents the agent for users:
-
-```markdown
----
-name: my-agent
-description: Short description (must match AGENT.yaml)
----
-
-# My Agent
-
-Description of what this agent does and when to use it.
-
-## What It Does
-
-- Bullet points of capabilities
-- What it focuses on
-- What it ignores
-
-## Usage
-
-Examples of how to invoke or use this agent.
-
-## Output Format
-
-Description of how the agent formats its responses.
-```
-
-## Example Agent
-
-See `code-reviewer/` for a complete example:
-
-- Reviews code for bugs, security issues, style
-- Categorizes issues by severity (critical/warning/suggestion)
-- References specific file and line numbers
-
-## Ideas for Agents
-
-- **test-writer** - Generates unit tests for code
-- **doc-writer** - Writes documentation and comments
-- **refactorer** - Suggests and applies refactoring patterns
-- **security-auditor** - Deep security analysis
-- **performance-optimizer** - Identifies performance bottlenecks
-
-## Installation
-
-When you install an agent via the TUI, droid:
-
-1. Reads `AGENT.yaml` for metadata (name, description, tools)
-2. Reads `AGENT.md` for the agent's instructions/persona
-3. Combines them into a single `.md` file with frontmatter
-4. Writes to `~/.claude/agents/{name}.md`
-
-The installed format matches what Claude Code expects:
-
-```markdown
----
-name: my-agent
-description: Short description
-tools: Read, Glob, Grep, Bash
----
-
-[Content from AGENT.md]
-```
-
-## Testing Your Agent
-
-1. Run `npm run build` to compile
-2. Run `droid` to open the TUI
-3. Navigate to Agents tab
-4. Verify your agent appears with correct metadata
-5. Install and verify it appears in `~/.claude/agents/`
-
-## Checklist
-
-- [ ] `AGENT.yaml` has all required fields (name, description, version, mode)
-- [ ] `AGENT.md` contains the agent's instructions/persona
-- [ ] Name matches directory name
-- [ ] Description is clear and concise
-- [ ] Mode is appropriate (subagent for specialized tasks, primary for main assistants)
-- [ ] Tools list only includes what the agent needs