[#1] ✨ - Multiple AI providers

.agents/skills/find-skills/SKILL.md

@@ -0,0 +1,142 @@
+---
+name: find-skills
+description: Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
+---
+
+# Find Skills
+
+This skill helps you discover and install skills from the open agent skills ecosystem.
+
+## When to Use This Skill
+
+Use this skill when the user:
+
+- Asks "how do I do X" where X might be a common task with an existing skill
+- Says "find a skill for X" or "is there a skill for X"
+- Asks "can you do X" where X is a specialized capability
+- Expresses interest in extending agent capabilities
+- Wants to search for tools, templates, or workflows
+- Mentions they wish they had help with a specific domain (design, testing, deployment, etc.)
+
+## What is the Skills CLI?
+
+The Skills CLI (`npx skills`) is the package manager for the open agent skills ecosystem. Skills are modular packages that extend agent capabilities with specialized knowledge, workflows, and tools.
+
+**Key commands:**
+
+- `npx skills find [query]` - Search for skills interactively or by keyword
+- `npx skills add <package>` - Install a skill from GitHub or other sources
+- `npx skills check` - Check for skill updates
+- `npx skills update` - Update all installed skills
+
+**Browse skills at:** https://skills.sh/
+
+## How to Help Users Find Skills
+
+### Step 1: Understand What They Need
+
+When a user asks for help with something, identify:
+
+1. The domain (e.g., React, testing, design, deployment)
+2. The specific task (e.g., writing tests, creating animations, reviewing PRs)
+3. Whether this is a common enough task that a skill likely exists
+
+### Step 2: Check the Leaderboard First
+
+Before running a CLI search, check the [skills.sh leaderboard](https://skills.sh/) to see if a well-known skill already exists for the domain. The leaderboard ranks skills by total installs, surfacing the most popular and battle-tested options.
+
+For example, top skills for web development include:
+- `vercel-labs/agent-skills` — React, Next.js, web design (100K+ installs each)
+- `anthropics/skills` — Frontend design, document processing (100K+ installs)
+
+### Step 3: Search for Skills
+
+If the leaderboard doesn't cover the user's need, run the find command:
+
+```bash
+npx skills find [query]
+```
+
+For example:
+
+- User asks "how do I make my React app faster?" → `npx skills find react performance`
+- User asks "can you help me with PR reviews?" → `npx skills find pr review`
+- User asks "I need to create a changelog" → `npx skills find changelog`
+
+### Step 4: Verify Quality Before Recommending
+
+**Do not recommend a skill based solely on search results.** Always verify:
+
+1. **Install count** — Prefer skills with 1K+ installs. Be cautious with anything under 100.
+2. **Source reputation** — Official sources (`vercel-labs`, `anthropics`, `microsoft`) are more trustworthy than unknown authors.
+3. **GitHub stars** — Check the source repository. A skill from a repo with <100 stars should be treated with skepticism.
+
+### Step 5: Present Options to the User
+
+When you find relevant skills, present them to the user with:
+
+1. The skill name and what it does
+2. The install count and source
+3. The install command they can run
+4. A link to learn more at skills.sh
+
+Example response:
+
+```
+I found a skill that might help! The "react-best-practices" skill provides
+React and Next.js performance optimization guidelines from Vercel Engineering.
+(185K installs)
+
+To install it:
+npx skills add vercel-labs/agent-skills@react-best-practices
+
+Learn more: https://skills.sh/vercel-labs/agent-skills/react-best-practices
+```
+
+### Step 6: Offer to Install
+
+If the user wants to proceed, you can install the skill for them:
+
+```bash
+npx skills add <owner/repo@skill> -g -y
+```
+
+The `-g` flag installs globally (user-level) and `-y` skips confirmation prompts.
+
+## Common Skill Categories
+
+When searching, consider these common categories:
+
+| Category        | Example Queries                          |
+| --------------- | ---------------------------------------- |
+| Web Development | react, nextjs, typescript, css, tailwind |
+| Testing         | testing, jest, playwright, e2e           |
+| DevOps          | deploy, docker, kubernetes, ci-cd        |
+| Documentation   | docs, readme, changelog, api-docs        |
+| Code Quality    | review, lint, refactor, best-practices   |
+| Design          | ui, ux, design-system, accessibility     |
+| Productivity    | workflow, automation, git                |
+
+## Tips for Effective Searches
+
+1. **Use specific keywords**: "react testing" is better than just "testing"
+2. **Try alternative terms**: If "deploy" doesn't work, try "deployment" or "ci-cd"
+3. **Check popular sources**: Many skills come from `vercel-labs/agent-skills` or `ComposioHQ/awesome-claude-skills`
+
+## When No Skills Are Found
+
+If no relevant skills exist:
+
+1. Acknowledge that no existing skill was found
+2. Offer to help with the task directly using your general capabilities
+3. Suggest the user could create their own skill with `npx skills init`
+
+Example:
+
+```
+I searched for skills related to "xyz" but didn't find any matches.
+I can still help you with this task directly! Would you like me to proceed?
+
+If this is something you do often, you could create your own skill:
+npx skills init my-xyz-skill
+```

.eslintrc.js

@@ -29,5 +29,16 @@ module.exports = {
     'eqeqeq': ['error', 'always'],
     'prettier/prettier': 'error'
   },
-  ignorePatterns: ['out', 'node_modules', '**/*.d.ts', 'webpack.config.js', '.eslintrc.js']
+  ignorePatterns: [
+    'out',
+    'node_modules',
+    'coverage',
+    '**/*.d.ts',
+    'webpack.config.js',
+    'jest.config.js',
+    '.eslintrc.js',
+    '__tests__/**',
+    'src/__tests__/**',
+    '**/*.test.ts',
+  ],
 };

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -1,5 +1,5 @@
 name: 🐛 Bug Report
-description: Report a bug on cursor whisper
+description: Report a bug on promptimize
 title: '<YOUR TITLE HERE>'
 labels: ['bug', 'bugfix', 'priority: high']
 body:
@@ -23,9 +23,14 @@ body:
       label: Which actions are affected?
       multiple: true
       options:
-        - Issue
-        - Pull Request
-        - Commits
+        - Audio recording / microphone
+        - Transcription (Whisper)
+        - Prompt optimization
+        - Text insertion (editor / chat)
+        - Configuration / setup wizard
+        - Configuration panel (webview)
+        - Keyboard shortcuts / commands
+        - Other
 
   - type: dropdown
     id: platforms
@@ -36,6 +41,8 @@ body:
         - macOS
         - Windows
         - Linux
+        - VS Code
+        - Cursor
 
   - type: markdown
     attributes:
@@ -68,8 +75,8 @@ body:
 
   - type: input
     attributes:
-      label: cursor whisper version
-      description: What version of cursor whisper is being used?
+      label: promptimize version
+      description: What version of promptimize is being used?
       placeholder: 'master'
     validations:
       required: true

.github/ISSUE_TEMPLATE/chore_task.yml

@@ -25,8 +25,10 @@ body:
       options:
         - CI/CD
         - Dependencies
-        - Code Refactoring
-        - Repository Configuration
+        - Code refactoring
+        - Tests
+        - Documentation maintenance
+        - Repository configuration
         - Other
 
   - type: markdown

.github/ISSUE_TEMPLATE/doc_update.yml

@@ -24,9 +24,12 @@ body:
       multiple: false
       options:
         - README.md
-        - Wiki
-        - API Documentation
-        - Inline Code Comments
+        - Quick start (docs/quickstart.md)
+        - User guide (recording, shortcuts, troubleshooting)
+        - Configuration docs
+        - Architecture / ADRs
+        - Developer docs (testing, standards, release)
+        - Inline code comments
         - Other
 
   - type: markdown

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -1,5 +1,5 @@
 name: ✨ Feature Request
-description: Propose an idea or improvement for cursor whisper
+description: Propose an idea or improvement for promptimize
 title: '<YOUR TITLE HERE>'
 labels: ['enhancement', 'feature', 'priority: low']
 body:
@@ -23,9 +23,13 @@ body:
       label: What area does this improvement affect?
       multiple: false
       options:
-        - User Interface
+        - Audio recording / microphone
+        - Transcription (Whisper)
+        - Prompt optimization
+        - Text insertion (editor / chat)
+        - Configuration / setup
+        - User interface (status bar, webview, notifications)
         - Performance
-        - New Feature
         - Documentation
         - Other
 
@@ -35,9 +39,13 @@ body:
       label: What actions does this improvement affect?
       multiple: true
       options:
-        - Issue
-        - Pull Request
-        - Commit
+        - Transcribe recording
+        - Promptimize recording
+        - Setup wizard
+        - Configure API key / provider
+        - Open configuration panel
+        - Test transformation
+        - Other
 
   - type: markdown
     attributes:
@@ -92,9 +100,9 @@ body:
 
   - type: input
     attributes:
-      label: Version of cursor whisper
+      label: Version of promptimize
       description: |
-        What version of cursor whisper are you using, or does this proposal apply to all versions?
+        What version of promptimize are you using, or does this proposal apply to all versions?
       placeholder: 'master'
     validations:
       required: false

.github/ISSUE_TEMPLATE/help_request.yml

@@ -23,8 +23,12 @@ body:
       label: What area do you need help with?
       multiple: false
       options:
-        - Code or implementation
-        - Build or setup
+        - Setup and configuration (API keys, wizard)
+        - Recording (microphone, permissions)
+        - Transcription (Whisper)
+        - Prompt optimization / providers
+        - Text insertion (editor / Cursor chat)
+        - Build from source / development
         - Documentation or usage
         - Workflow or CI/CD
         - Other

.github/ISSUE_TEMPLATE/hotfix.yml

@@ -1,14 +1,14 @@
 name: 🔥 Hotfix Issue
 
-description: Request a new hotfix for copilot (only team members)
+description: Request a new hotfix for promptimize (only team members)
 title: '<YOUR TITLE HERE>'
 labels: ['hotfix', 'branched', 'priority: high']
 body:
   - type: markdown
     attributes:
       value: |
         ### ⚠️ Disclaimer
-        > **Only members of the copilot team can create hotfix issues.**
+        > **Only members of the promptimize team can create hotfix issues.**
         > Any hotfix issue created by someone outside the team will be closed automatically.
 
         ---

.github/ISSUE_TEMPLATE/release.yml

@@ -1,13 +1,13 @@
 name: 🚀 Release Issue
-description: Request a new release for copilot (only team members)
+description: Request a new release for promptimize (only team members)
 title: "<YOUR TITLE HERE>"
 labels: ["release", "branched", "priority: medium"]
 body:
   - type: markdown
     attributes:
       value: |
         ### ⚠️ Disclaimer
-        > **Only members of the copilot team can create release issues.**
+        > **Only members of the promptimize team can create release issues.**
         > Any release issue created by someone outside the team will be closed automatically.
 
         ---

.vscodeignore

@@ -9,8 +9,12 @@ webpack.config.js
 **/*.map
 **/*.ts
 !out/**/*.js
-node_modules/**
-!node_modules/@kstonekuan/**
+!out/presentation/webview/**
+node_modules/**/test/**
+node_modules/**/tests/**
+node_modules/**/*.md
+node_modules/**/.*.yml
+node_modules/**/.*.yaml
 coverage/**
 **/__tests__/**
 **/*.test.ts