@tekmidian/pai 0.5.7 → 0.6.0

package/templates/skills/CORE/SkillSystem.md

@@ -1,213 +0,0 @@
-# Custom Skill System
-
-**The MANDATORY configuration system for ALL PAI skills.**
-
----
-
-## THIS IS THE AUTHORITATIVE SOURCE
-
-This document defines the **required structure** for every skill in the PAI system.
-
-**ALL skill creation MUST follow this structure.**
-
-**"Canonicalize a skill"** = Restructure it to match this exact format, including TitleCase naming.
-
----
-
-## TitleCase Naming Convention (MANDATORY)
-
-**All naming in the skill system MUST use TitleCase (PascalCase).**
-
-| Component | Wrong | Correct |
-|-----------|-------|---------|
-| Skill directory | `createskill`, `create-skill` | `Createskill` |
-| Workflow files | `create.md`, `update-info.md` | `Create.md`, `UpdateInfo.md` |
-| Reference docs | `prosody-guide.md` | `ProsodyGuide.md` |
-| Tool files | `manage-server.ts` | `ManageServer.ts` |
-| YAML name | `name: create-skill` | `name: Createskill` |
-
-**Exception:** `SKILL.md` is always uppercase (convention for the main skill file).
-
----
-
-## The Required Structure
-
-Every SKILL.md has two parts:
-
-### 1. YAML Frontmatter (Single-Line Description)
-
-```yaml
----
-name: SkillName
-description: [What it does]. USE WHEN [intent triggers using OR]. [Additional capabilities].
----
-```
-
-**Rules:**
-- `name` uses **TitleCase**
-- `description` is a **single line** (not multi-line with `|`)
-- `USE WHEN` keyword is **MANDATORY** (Claude Code parses this for skill activation)
-- Use intent-based triggers with `OR` for multiple conditions
-- Max 1024 characters (Anthropic hard limit)
-
-### 2. Markdown Body
-
-```markdown
-# SkillName
-
-[Brief description]
-
-## Workflow Routing
-
-**When executing a workflow, do BOTH of these:**
-
-1. **Call the notification script** (for observability tracking):
-   ```bash
-   ~/.claude/Tools/SkillWorkflowNotification WORKFLOWNAME SKILLNAME
-   ```
-
-2. **Output the text notification** (for user visibility):
-   ```
-   Running the **WorkflowName** workflow from the **SKILLNAME** skill...
-   ```
-
-This ensures workflows appear in the observability dashboard AND the user sees the announcement.
-
-| Workflow | Trigger | File |
-|----------|---------|------|
-| **WorkflowOne** | "trigger phrase" | `workflows/WorkflowOne.md` |
-| **WorkflowTwo** | "another trigger" | `workflows/WorkflowTwo.md` |
-
-## Examples
-
-**Example 1: [Common use case]**
-```
-User: "[Typical user request]"
-→ Invokes WorkflowOne workflow
-→ [What skill does]
-→ [What user gets back]
-```
-
-## [Additional Sections]
-```
-
----
-
-## Examples Section (REQUIRED)
-
-**Every skill MUST have an `## Examples` section** showing 2-3 concrete usage patterns.
-
-**Why Examples Matter:**
-- Anthropic research shows examples improve tool selection accuracy from 72% to 90%
-- Descriptions tell Claude WHEN to activate; examples show HOW the skill works
-
-**Example Format:**
-```markdown
-## Examples
-
-**Example 1: [Use case name]**
-```
-User: "[Actual user request]"
-→ Invokes WorkflowName workflow
-→ [What the skill does]
-→ [What user receives back]
-```
-```
-
----
-
-## Intent Matching, Not String Matching
-
-We use **intent matching**, not exact phrase matching.
-
-**Example description:**
-```yaml
-description: Complete blog workflow. USE WHEN user mentions doing anything with their blog, website, site, including things like update, proofread, write, edit, publish, preview, blog posts, or website pages.
-```
-
-**Key Principles:**
-- Use intent language: "user mentions", "user wants to", "including things like"
-- Don't list exact phrases in quotes
-- Cover the domain conceptually
-- Use `OR` to combine multiple trigger conditions
-
----
-
-## Directory Structure
-
-Every skill follows this structure:
-
-```
-SkillName/                    # TitleCase directory name
-├── SKILL.md                  # Main skill file (always uppercase)
-├── ReferenceDoc.md           # Optional: Reference docs (TitleCase)
-├── tools/                    # CLI tools (ALWAYS present, even if empty)
-│   ├── ToolName.ts           # TypeScript CLI tool (TitleCase)
-│   └── ToolName.help.md      # Tool documentation (TitleCase)
-└── workflows/
-    ├── Create.md             # Work execution workflow (TitleCase)
-    └── Update.md             # Work execution workflow (TitleCase)
-```
-
----
-
-## Workflows vs Reference Documentation
-
-**CRITICAL DISTINCTION:**
-
-### Workflows (`workflows/` directory)
-- Operational procedures (create, update, delete, deploy)
-- Step-by-step execution instructions
-- Actions that change state or produce output
-- Things you "run" or "execute"
-
-### Reference Documentation (skill root)
-- Guides and how-to documentation
-- Specifications and schemas
-- Information you "read" or "reference"
-
----
-
-## Complete Checklist
-
-Before a skill is complete:
-
-### Naming (TitleCase)
-- [ ] Skill directory uses TitleCase
-- [ ] All workflow files use TitleCase
-- [ ] All reference docs use TitleCase
-- [ ] YAML `name:` uses TitleCase
-
-### YAML Frontmatter
-- [ ] Single-line description with embedded `USE WHEN` clause
-- [ ] No separate `triggers:` or `workflows:` arrays
-- [ ] Description under 1024 characters
-
-### Markdown Body
-- [ ] `## Workflow Routing` section with table format
-- [ ] `## Examples` section with 2-3 concrete patterns
-- [ ] All workflows have routing entries
-
-### Structure
-- [ ] `tools/` directory exists (even if empty)
-- [ ] No `backups/` directory inside skill
-- [ ] Workflows contain ONLY execution procedures
-- [ ] Reference docs live at skill root
-
----
-
-## Summary
-
-| Component | Purpose | Naming |
-|-----------|---------|--------|
-| **Skill directory** | Contains all skill files | TitleCase (e.g., `Blogging`) |
-| **SKILL.md** | Main skill file | Always uppercase |
-| **Workflow files** | Execution procedures | TitleCase (e.g., `Create.md`) |
-| **Reference docs** | Information to read | TitleCase (e.g., `ApiReference.md`) |
-| **Tool files** | CLI automation | TitleCase (e.g., `ManageServer.ts`) |
-
-This system ensures:
-1. Skills invoke properly based on intent (USE WHEN in description)
-2. Specific functionality executes accurately (Workflow Routing in body)
-3. All skills have consistent, predictable structure
-4. **All naming follows TitleCase convention**

package/templates/skills/CORE/TerminalTabs.md

@@ -1,119 +0,0 @@
-# Terminal Tab Title System
-
-## Overview
-
-The PAI system automatically updates your terminal tab title with a 4-word summary of what was done after each task completion. This provides instant visual feedback in your terminal tabs, making it easy to see what each Claude session accomplished.
-
-## How It Works
-
-The `stop-hook.ts` hook runs after every task completion and:
-
-1. **Extracts the task summary** from the COMPLETED line in responses
-2. **Generates a 4-word title** that summarizes what was accomplished
-3. **Updates your terminal tab** using ANSI escape sequences
-
-## Features
-
-### 4-Word Summary Format
-
-The system creates meaningful 4-word summaries by:
-- Using past-tense action verbs (Created, Updated, Fixed, etc.)
-- Extracting key nouns from the task
-- Prioritizing words from the COMPLETED line when available
-- Falling back to the user's original query if needed
-
-### Examples
-
-| User Query | Tab Title |
-|------------|-----------|
-| "Update the README documentation" | Updated Readme Documentation Done |
-| "Fix the stop-hook" | Fixed Stop Hook Successfully |
-| "Send email to Angela" | Sent Email Angela Done |
-| "Research AI trends" | Researched AI Trends Complete |
-
-## Terminal Compatibility
-
-The tab title system works with terminals that support OSC (Operating System Command) sequences:
-
-- **Kitty** - Full support
-- **iTerm2** - Full support
-- **Terminal.app** - Full support
-- **Alacritty** - Full support
-- **VS Code Terminal** - Full support
-
-## Implementation Details
-
-### Escape Sequences Used
-
-```bash
-# OSC 0 - Sets icon and window title
-printf '\033]0;Title Here\007'
-
-# OSC 2 - Sets window title
-printf '\033]2;Title Here\007'
-
-# OSC 30 - Kitty-specific tab title
-printf '\033]30;Title Here\007'
-```
-
-### Hook Location
-
-The terminal tab functionality is implemented in:
-```
-${PAI_DIR}/Hooks/stop-hook.ts
-```
-
-### Key Functions
-
-1. **generateTabTitle(prompt, completedLine)** - Creates the 4-word summary
-2. **setKittyTabTitle(title)** - Sends escape sequences to update the tab
-3. **Hook execution** - Runs automatically after every task
-
-## Debugging
-
-If tab titles aren't updating:
-
-1. **Check hook is executable:**
-   ```bash
-   ls -la ${PAI_DIR}/Hooks/stop-hook.ts
-   # Should show: -rwxr-xr-x
-   ```
-
-2. **Verify Claude Code settings:**
-   - Ensure stop-hook is configured in your Claude Code settings
-   - Path should be: `${PAI_DIR}/Hooks/stop-hook.ts`
-
-3. **Test manually:**
-   ```bash
-   printf '\033]0;Test Title\007' >&2
-   ```
-
-4. **Check stderr output:**
-   The hook logs to stderr with:
-   - 🏷️ Tab title changes
-   - 📝 User queries processed
-   - ✅ Completed text extracted
-
-## Customization
-
-To modify the tab title behavior, edit `${PAI_DIR}/Hooks/stop-hook.ts`:
-
-- Change word count (currently 4 words)
-- Modify verb tense (currently past tense)
-- Add custom prefixes or suffixes
-- Filter different stop words
-
-## Benefits
-
-- **Visual Task Tracking** - See what each tab accomplished at a glance
-- **Multi-Session Management** - Easily identify different Claude sessions
-- **Task History** - Tab titles persist as a record of completed work
-- **No Manual Updates** - Fully automatic, runs on every task completion
-
-## Integration with Voice System
-
-The terminal tab system works alongside the voice notification system:
-- Both extract information from the COMPLETED line
-- Tab gets a 4-word visual summary
-- Voice speaks the completion message
-- Both provide immediate feedback through different channels

package/templates/skills/CORE/VOICE.md

@@ -1,106 +0,0 @@
-# Voice System Reference
-
-**This file is a reference pointer to the canonical voice system documentation.**
-
----
-
-## 📍 Canonical Documentation Location
-
-**All voice system documentation is maintained in the voice-server directory:**
-
-`${PAI_DIR}/voice-server/`
-
----
-
-## 📚 Voice Server Documentation
-
-### Overview and Setup
-**Location:** `${PAI_DIR}/voice-server/README.md`
-
-**Contains:**
-- Voice server overview and features
-- Installation and setup instructions
-- Service management (start/stop/restart)
-- API usage and endpoints
-- Voice IDs for all agents
-- Menu bar indicator setup
-- Configuration options
-- Troubleshooting guide
-
-### Quick Start
-**Location:** `${PAI_DIR}/voice-server/QUICKSTART.md`
-
-**Contains:**
-- 5-minute setup guide
-- Minimal configuration steps
-- Basic testing commands
-
----
-
-## 🎯 Quick Reference
-
-**Start voice server:**
-```bash
-${PAI_DIR}/voice-server/start.sh
-```
-
-**Check status:**
-```bash
-${PAI_DIR}/voice-server/status.sh
-```
-
-**Restart server:**
-```bash
-${PAI_DIR}/voice-server/restart.sh
-```
-
-**Stop server:**
-```bash
-${PAI_DIR}/voice-server/stop.sh
-```
-
-**Test voice:**
-```bash
-curl -X POST http://localhost:8888/notify \
-  -H "Content-Type: application/json" \
-  -d '{"message":"Test message","voice_enabled":true}'
-```
-
----
-
-## 🎤 Available Voice IDs
-
-Voice IDs are ElevenLabs identifiers configured in hook files:
-
-| Agent | Voice ID | Description |
-|-------|----------|-------------|
-| PAI (Main) | s3TPKV1kjDlVtZbl4Ksh | UK Male - Professional |
-| Researcher | AXdMgz6evoL7OPd7eU12 | US Female - Analytical |
-| Engineer | fATgBRI8wg5KkDFg8vBd | US Female - Steady |
-| Architect | muZKMsIDGYtIkjjiUS82 | UK Female - Strategic |
-| Designer | ZF6FPAbjXT4488VcRRnw | Indian Female - Creative |
-| Pentester | xvHLFjaUEpx4BOf7EiDd | UK Male - Technical |
-
-See `${PAI_DIR}/voice-server/README.md` for complete voice list.
-
----
-
-## 🔗 Related Documentation
-
-- **Prosody Guide:** `${PAI_DIR}/Skills/CORE/prosody-guide.md` (voice parameter tuning)
-- **Agent Template:** `${PAI_DIR}/Skills/CORE/prosody-agent-template.md` (creating agent voices)
-
----
-
-## ⚠️ Important
-
-**DO NOT duplicate voice documentation in CORE.**
-
-- The voice-server directory is the **canonical source** for all voice system documentation
-- Duplicating documentation causes version conflicts and maintenance issues
-- Always refer to and update voice-server documentation directly
-- This reference file should only contain pointers, not duplicated content
-
----
-
-**Last Updated:** 2025-12-01

package/templates/skills/createskill-skill.template.md

@@ -1,78 +0,0 @@
-<!-- Generated by PAI Setup -->
----
-name: Createskill
-description: MANDATORY skill creation framework for ALL skill creation requests. USE WHEN user wants to create, validate, update, or canonicalize a skill, OR user mentions skill creation, skill development, new skill, build skill, OR user references skill compliance, skill structure, or skill architecture.
----
-
-# Createskill
-
-MANDATORY skill creation framework for ALL skill creation requests.
-
-## Authoritative Source
-
-**Before creating ANY skill, READ:** `${PAI_DIR}/skills/CORE/SkillSystem.md`
-
-**Canonical example to follow:** Look at existing skills in `~/.claude/skills/` for structure reference.
-
-## TitleCase Naming Convention
-
-**All naming must use TitleCase (PascalCase).**
-
-| Component | Format | Example |
-|-----------|--------|---------|
-| Skill directory | TitleCase | `Blogging`, `Daemon`, `CreateSkill` |
-| Workflow files | TitleCase.md | `Create.md`, `UpdateDaemonInfo.md` |
-| Reference docs | TitleCase.md | `ProsodyGuide.md`, `ApiReference.md` |
-| Tool files | TitleCase.ts | `ManageServer.ts` |
-| Help files | TitleCase.help.md | `ManageServer.help.md` |
-
-**Wrong (NEVER use):**
-- `createskill`, `create-skill`, `CREATE_SKILL`
-- `create.md`, `update-info.md`, `SYNC_REPO.md`
-
-## Workflow Routing
-
-**When executing a workflow, output this notification directly:**
-
-```
-Running the **WorkflowName** workflow from the **Createskill** skill...
-```
-
-| Workflow | Trigger | File |
-|----------|---------|------|
-| **CreateSkill** | "create a new skill" | `workflows/CreateSkill.md` |
-| **ValidateSkill** | "validate skill", "check skill" | `workflows/ValidateSkill.md` |
-| **UpdateSkill** | "update skill", "add workflow" | `workflows/UpdateSkill.md` |
-| **CanonicalizeSkill** | "canonicalize", "fix skill structure" | `workflows/CanonicalizeSkill.md` |
-
-## Examples
-
-**Example 1: Create a new skill from scratch**
-```
-User: "Create a skill for managing my recipes"
-→ Invokes CreateSkill workflow
-→ Reads SkillSystem.md for structure requirements
-→ Creates skill directory with TitleCase naming
-→ Creates SKILL.md, workflows/, tools/
-→ Generates USE WHEN triggers based on intent
-```
-
-**Example 2: Fix an existing skill that's not routing properly**
-```
-User: "The research skill isn't triggering - validate it"
-→ Invokes ValidateSkill workflow
-→ Checks SKILL.md against canonical format
-→ Verifies TitleCase naming throughout
-→ Verifies USE WHEN triggers are intent-based
-→ Reports compliance issues with fixes
-```
-
-**Example 3: Canonicalize a skill with old naming**
-```
-User: "Canonicalize the daemon skill"
-→ Invokes CanonicalizeSkill workflow
-→ Renames workflow files to TitleCase
-→ Updates routing table to match
-→ Ensures Examples section exists
-→ Verifies all checklist items
-```