devstack 0.1.0

package/vendor/skills/skills/perplexity/README.md

@@ -0,0 +1,212 @@
+# Perplexity Skill
+
+A comprehensive guide for using Perplexity AI tools effectively within Claude Code. This skill helps you choose the right search and research tool for your needs while avoiding context bloat and unnecessary API calls.
+
+## Purpose
+
+This skill provides clear guidelines for when and how to use Perplexity's search and conversational AI capabilities, ensuring you select the most appropriate tool for each task while respecting token budgets and avoiding overlaps with other specialized tools.
+
+## When to Use This Skill
+
+Use Perplexity tools ONLY when users explicitly request:
+
+- **Search queries**: "search", "find", "look up", "research"
+- **Current information**: "what's the latest", "recent trends"
+- **Generic questions**: Broad topics not covered by specialized tools
+
+## When NOT to Use This Skill
+
+Do NOT use Perplexity for:
+
+- **Library/framework documentation** → Use Context7 MCP instead
+- **Graphite `gt` CLI commands** → Use Graphite MCP instead
+- **Workspace-specific questions** → Use Nx MCP instead
+- **Specific URLs** → Use URL Crawler instead
+- **Deep research** → Use Researcher agent (`/research`) instead
+
+## Available Tools
+
+### 1. Perplexity Search
+
+**Best for**: Finding resources, URLs, and current best practices
+
+**When to use**:
+
+- Discovering tutorials, blog posts, or articles
+- Finding recent information about technologies
+- User says "search for...", "find...", "look up..."
+
+**Default usage** (always start with these limits):
+
+```typescript
+mcp__perplexity__perplexity_search({
+  query: "your search query",
+  max_results: 3, // Default is 10 - too many!
+  max_tokens_per_page: 512, // Reduce per-result content
+});
+```
+
+**When to increase limits**:
+Only increase limits if:
+
+- User explicitly needs comprehensive results
+- Initial search found nothing useful
+- Complex topic requires multiple sources
+
+```typescript
+// Increased limits (use sparingly)
+mcp__perplexity__perplexity_search({
+  query: "complex topic",
+  max_results: 5,
+  max_tokens_per_page: 1024,
+});
+```
+
+### 2. Perplexity Ask
+
+**Best for**: Getting conversational explanations synthesized from web sources
+
+**When to use**:
+
+- Need explanation, not just search results
+- Synthesize information from multiple web sources
+- Explain concepts with current context
+
+**Usage**:
+
+```typescript
+mcp__perplexity__perplexity_ask({
+  messages: [
+    {
+      role: "user",
+      content: "Explain how postgres advisory locks work",
+    },
+  ],
+});
+```
+
+**NOT for**:
+
+- Library documentation (use Context7)
+- Deep multi-source research (use researcher agent)
+
+### 3. Perplexity Research (PROHIBITED)
+
+**NEVER use**: `mcp__perplexity__perplexity_research`
+
+**Why**: Extremely high token cost (30-50k tokens)
+
+**Use instead**: Researcher agent (`/research <topic>`)
+
+- Provides multi-source synthesis with citations
+- Use sparingly for complex questions only
+
+## Tool Selection Chain
+
+When a user asks a question, follow this priority order:
+
+1. **Context7 MCP** - Library/framework documentation
+2. **Graphite MCP** - Any `gt` CLI mention
+3. **Nx MCP** - Questions about THIS workspace
+4. **Perplexity Search** - Generic searches
+5. **Perplexity Ask** - Conversational answers
+6. **Researcher agent** - Deep multi-source research
+7. **WebSearch** - Last resort (after Perplexity exhausted)
+
+## Usage Examples
+
+### Correct Usage
+
+**Use Perplexity Search:**
+
+```
+User: "Find postgres migration best practices"
+User: "Search for React testing tutorials"
+User: "Look up latest trends in microservices"
+```
+
+**Use Perplexity Ask:**
+
+```
+User: "Explain how postgres advisory locks work"
+User: "What are the trade-offs of microservices?"
+```
+
+### Incorrect Usage (Use Other Tools)
+
+**Use Context7 instead:**
+
+```
+❌ "Search for React hooks documentation"
+❌ "Find Next.js routing docs"
+❌ "Look up Temporal workflow API"
+```
+
+**Use Graphite MCP instead:**
+
+```
+❌ "Search for gt stack commands"
+❌ "Find gt branch workflow"
+```
+
+**Use Nx MCP instead:**
+
+```
+❌ "Search for build config" (in THIS workspace)
+❌ "Find project dependencies" (in THIS workspace)
+```
+
+## Key Features
+
+- **Token budget awareness**: Default to limited results to avoid context bloat
+- **Clear tool boundaries**: Know when to use Perplexity vs. specialized tools
+- **Fallback chain**: Search → Ask → WebSearch (last resort)
+- **Research delegation**: Use researcher agent for deep dives, not raw Perplexity API
+
+## Best Practices
+
+1. **Start conservative**: Always use `max_results: 3` and `max_tokens_per_page: 512`
+2. **Check alternatives first**: Try Context7, Graphite MCP, or Nx MCP before Perplexity
+3. **Know your trigger words**: "search", "find", "look up", "research", "latest"
+4. **Avoid research tool**: Never use `perplexity_research` - use researcher agent instead
+5. **Respect the chain**: Follow the tool selection priority order
+
+## Common Pitfalls
+
+- Using Perplexity for library docs (use Context7)
+- Using high limits by default (causes context bloat)
+- Using `perplexity_research` directly (use researcher agent)
+- Skipping the tool selection chain
+- Not checking if specialized tools apply first
+
+## Integration with Other Skills
+
+- **Context7**: For library/framework documentation
+- **Graphite MCP**: For `gt` CLI operations
+- **Nx MCP**: For workspace-specific queries
+- **Researcher agent**: For deep research tasks
+- **WebSearch**: As absolute last resort fallback
+
+## Quick Decision Matrix
+
+| User Request           | Tool to Use             |
+| ---------------------- | ----------------------- |
+| React hooks docs       | Context7 MCP            |
+| gt stack command       | Graphite MCP            |
+| Build config here      | Nx MCP                  |
+| Find migration guide   | Perplexity Search       |
+| Explain advisory locks | Perplexity Ask          |
+| Deep research report   | Researcher agent        |
+| Generic web search     | WebSearch (last resort) |
+
+## Summary
+
+The Perplexity skill ensures you use Perplexity AI tools effectively and appropriately:
+
+- Choose the right tool (Search vs. Ask)
+- Respect token budgets with conservative limits
+- Defer to specialized tools when appropriate
+- Avoid the expensive research tool
+- Follow the tool selection chain
+
+By following these guidelines, you'll provide better, faster, and more cost-effective responses to users.

package/vendor/skills/skills/perplexity/SKILL.md

@@ -0,0 +1,143 @@
+---
+name: perplexity
+description: Web search and research using Perplexity AI. Use when user says "search", "find", "look up", "ask", "research", or "what's the latest" for generic queries. NOT for library/framework docs (use Context7) or workspace questions.
+---
+
+# Perplexity Tools
+
+Use ONLY when user says "search", "find", "look up", "ask", "research", or "what's the latest" for generic queries. NOT for library/framework docs (use Context7), gt CLI (use Graphite MCP), or workspace questions (use Nx MCP).
+
+## Quick Reference
+
+**Which Perplexity tool?**
+
+- Need search results/URLs? → **Perplexity Search**
+- Need conversational answer? → **Perplexity Ask**
+- Need deep research? → **Researcher agent** (`/research <topic>`)
+
+**NOT Perplexity - use these instead:**
+
+- Library/framework docs → **Context7 MCP**
+- Graphite `gt` CLI → **Graphite MCP**
+- THIS workspace → **Nx MCP**
+- Specific URL → **URL Crawler**
+
+## Perplexity Search
+
+**When to use:**
+
+- Generic searches, finding resources
+- Current best practices, recent information
+- Tutorial/blog post discovery
+- User says "search for...", "find...", "look up..."
+
+**Default parameters (ALWAYS USE):**
+
+```typescript
+mcp__perplexity__perplexity_search({
+  query: "your search query",
+  max_results: 3, // Default is 10 - too many!
+  max_tokens_per_page: 512, // Reduce per-result content
+});
+```
+
+**When to increase limits:**
+Only if:
+
+- User explicitly needs comprehensive results
+- Initial search found nothing useful
+- Complex topic needs multiple sources
+
+```typescript
+// Increased limits (use sparingly)
+mcp__perplexity__perplexity_search({
+  query: "complex topic",
+  max_results: 5,
+  max_tokens_per_page: 1024,
+});
+```
+
+## Perplexity Ask
+
+**When to use:**
+
+- Need conversational explanation, not search results
+- Synthesize information from web
+- Explain concepts with current context
+
+**Usage:**
+
+```typescript
+mcp__perplexity__perplexity_ask({
+  messages: [
+    {
+      role: "user",
+      content: "Explain how postgres advisory locks work",
+    },
+  ],
+});
+```
+
+**NOT for:**
+
+- Library documentation (use Context7)
+- Deep multi-source research (use researcher agent)
+
+## Prohibited Tool
+
+**NEVER use:** `mcp__perplexity__perplexity_research`
+
+**Use instead:** Researcher agent (`/research <topic>`)
+
+- Token cost: 30-50k tokens
+- Provides multi-source synthesis with citations
+- Use sparingly for complex questions only
+
+## Tool Selection Chain
+
+**Priority order:**
+
+1. **Context7 MCP** - Library/framework docs
+2. **Graphite MCP** - Any `gt` CLI mention
+3. **Nx MCP** - THIS workspace questions
+4. **Perplexity Search** - Generic searches
+5. **Perplexity Ask** - Conversational answers
+6. **Researcher agent** - Deep multi-source research
+7. **WebSearch** - Last resort (after Perplexity exhausted)
+
+## Examples
+
+**✅ CORRECT - Use Perplexity Search:**
+
+- "Find postgres migration best practices"
+- "Search for React testing tutorials"
+- "Look up latest trends in microservices"
+
+**✅ CORRECT - Use Perplexity Ask:**
+
+- "Explain how postgres advisory locks work"
+- "What are the trade-offs of microservices?"
+
+**❌ WRONG - Use Context7 instead:**
+
+- "Search for React hooks documentation" → Context7 MCP
+- "Find Next.js routing docs" → Context7 MCP
+- "Look up Temporal workflow API" → Context7 MCP
+
+**❌ WRONG - Use Graphite MCP instead:**
+
+- "Search for gt stack commands" → Graphite MCP
+- "Find gt branch workflow" → Graphite MCP
+
+**❌ WRONG - Use Nx MCP instead:**
+
+- "Search for build config" (in THIS workspace) → Nx MCP
+- "Find project dependencies" (in THIS workspace) → Nx MCP
+
+## Key Points
+
+- **Default to limited results** - avoid context bloat
+- **Library docs = Context7** - ALWAYS try Context7 first
+- **"gt" = Graphite MCP** - ANY "gt" mention uses Graphite
+- **Deep research = /research** - NOT perplexity_research tool
+- **Fallback chain** - Search → Ask → WebSearch (last resort)

package/vendor/skills/skills/pitch-deck/SKILL.md

@@ -0,0 +1,259 @@
+---
+name: pitch-deck
+description: Generate professional PowerPoint pitch decks for startups and businesses. Use this skill when users request help creating investor pitch decks, sales presentations, or business pitch presentations. The skill follows standard 10-slide pitch deck structure and includes best practices for content and design.
+---
+
+# Pitch Deck Generator
+
+## Overview
+
+Generate professional PowerPoint pitch decks following industry best practices. This skill creates structured presentations for fundraising, sales, and business development using a proven 10-slide format.
+
+## When to Use This Skill
+
+Activate this skill when users request:
+
+- Investor pitch decks for fundraising
+- Sales or business development presentations
+- Product launch presentations
+- Startup pitch competition decks
+- Any structured business presentation following standard pitch deck format
+
+## Workflow
+
+### Step 1: Gather Information
+
+Collect necessary information from the user to populate the pitch deck. Use a conversational approach to gather details across the following categories:
+
+**Required information:**
+
+1. **Company basics**: Company name, tagline (one-liner describing what you do)
+2. **Problem**: What problem are you solving? Include data or statistics if available
+3. **Solution**: How does your product/service solve the problem? Key features and benefits
+4. **Business model**: How do you make money? Pricing, revenue streams
+
+**Recommended information** (include if available): 5. **Market opportunity**: Market size (TAM/SAM/SOM), growth rate, market trends 6. **Product details**: Product features, screenshots, technology highlights 7. **Traction**: Key metrics, revenue, users, growth rate, milestones, customer testimonials 8. **Competition**: Competitors, competitive advantages, differentiation 9. **Team**: Founders and key team members with relevant background 10. **Financials & Ask**: Funding amount, use of funds, financial projections, milestones
+
+**Approach:**
+
+- Ask open-ended questions to understand the business
+- Probe for specific metrics and data points when possible
+- For missing information, offer to create placeholder slides that can be updated later
+- Adapt the standard 10-slide structure based on available information
+
+### Step 2: Structure the Content
+
+Organize the gathered information into the standard pitch deck structure:
+
+1. **Title Slide**: Company name + tagline
+2. **Problem**: Pain point being addressed
+3. **Solution**: Product/service overview
+4. **Market Opportunity**: Market size and growth
+5. **Product**: Features and capabilities
+6. **Traction**: Metrics and achievements
+7. **Business Model**: Revenue and pricing
+8. **Competition**: Competitive landscape
+9. **Team**: Key people
+10. **Financials & Ask**: Funding request and projections
+
+**Reference best practices:** For detailed guidance on each slide's content and structure, consult `references/pitch_deck_best_practices.md`. Search for specific sections using grep:
+
+```bash
+grep -A 10 "### [Slide Number]. [Slide Name]" references/pitch_deck_best_practices.md
+```
+
+### Step 3: Create the JSON Data File
+
+Format the collected information as a JSON file that will be consumed by the pitch deck generation script. Create a file called `pitch_data.json` with the following structure:
+
+```json
+{
+  "company_name": "Company Name",
+  "tagline": "One-line description of what you do",
+  "problem": [
+    "Problem statement 1 with data/statistics",
+    "Problem statement 2 showing impact",
+    "Problem statement 3 demonstrating urgency"
+  ],
+  "solution": [
+    "How your product solves the problem",
+    "Key feature 1 and its benefit",
+    "Key feature 2 and its benefit",
+    "Unique value proposition"
+  ],
+  "market": [
+    "TAM: Total addressable market with $ figure",
+    "SAM: Serviceable available market",
+    "SOM: Serviceable obtainable market",
+    "Market growth rate and trends"
+  ],
+  "product": [
+    "Product feature 1",
+    "Product feature 2",
+    "Technology highlights",
+    "User experience benefits"
+  ],
+  "traction": [
+    "Revenue: $X (YY% growth)",
+    "Users: X,XXX active users",
+    "Key milestone 1",
+    "Customer testimonial or social proof"
+  ],
+  "business_model": [
+    "Revenue model (e.g., SaaS subscription)",
+    "Pricing: $XX/month per user",
+    "Unit economics: CAC, LTV, margins",
+    "Sales channels"
+  ],
+  "competition": {
+    "our_advantages": ["Advantage 1", "Advantage 2", "Unfair advantage/defensibility"],
+    "competitors": ["Competitor 1", "Competitor 2", "Alternative solutions"]
+  },
+  "team": [
+    "Founder 1: Name - Background and relevant experience",
+    "Founder 2: Name - Background and relevant experience",
+    "Key hire: Name - Background and why they matter",
+    "Notable advisors"
+  ],
+  "financials": [
+    "Raising: $X seed/Series A round",
+    "Use of funds: XX% engineering, XX% sales, XX% ops",
+    "Milestones with this funding",
+    "Runway: X-X months to next milestone"
+  ]
+}
+```
+
+**Notes:**
+
+- All fields are optional except `company_name`
+- Use arrays for bullet points (will be rendered as bullet lists)
+- Competition can be either an object with `our_advantages` and `competitors` keys (for two-column layout) or a simple array
+- Keep bullet points concise (1-2 lines each)
+- Include specific numbers and metrics where possible
+
+### Step 4: Generate the PowerPoint
+
+Execute the Python script to create the PowerPoint presentation:
+
+```bash
+python3 scripts/create_pitch_deck.py pitch_data.json output_filename.pptx
+```
+
+The script will:
+
+- Generate a professional PowerPoint file with proper formatting
+- Apply consistent color scheme and typography
+- Create slides based on available data (skipping sections if data not provided)
+- Output a `.pptx` file ready for presentation or further customization
+
+### Step 5: Review and Iterate
+
+Present the generated pitch deck location to the user and offer to:
+
+- Add missing sections if information becomes available
+- Refine bullet points for clarity and impact
+- Adjust structure based on specific audience (investor vs. sales pitch)
+- Provide guidance on presenting the deck
+
+**Iteration approach:**
+
+- User can update the JSON file with new information
+- Re-run the script to regenerate the updated presentation
+- For design customizations beyond the script's capabilities, advise manual editing in PowerPoint
+
+## Design Guidelines
+
+The generated pitch deck follows these design principles:
+
+**Color Scheme:**
+
+- Primary: Blue (#2962FF) for titles and emphasis
+- Secondary: Gray (#646464) for body text
+- Clean white background for readability
+
+**Typography:**
+
+- Title slides: 54pt bold
+- Section titles: 40pt bold
+- Body text: 18-20pt with appropriate line spacing
+
+**Layout:**
+
+- Consistent margins and spacing
+- One key message per slide
+- Bullet points limited to 3-5 items per slide
+- Two-column layouts for comparison slides
+
+**Visual Hierarchy:**
+
+- Clear title at top of each slide
+- Content organized with proper spacing
+- Emphasis on readability and professional appearance
+
+## Best Practices Reference
+
+For detailed guidance on pitch deck content, structure, and presentation tips, reference:
+
+- `references/pitch_deck_best_practices.md` - Comprehensive guide covering:
+  - Standard 10-slide structure with examples
+  - Content guidelines for each slide type
+  - Design best practices
+  - Common mistakes to avoid
+  - Tailoring for different audiences (investor, sales, product launch)
+  - Pre-pitch checklist
+
+Load this reference when providing detailed advice on pitch content or structure.
+
+## Example Usage Scenarios
+
+**Scenario 1: Early-stage startup seeking seed funding**
+
+- Focus on problem, solution, market opportunity, and team
+- Emphasize founder expertise and early traction
+- Include clear funding ask and use of funds
+
+**Scenario 2: Growth-stage company creating sales deck**
+
+- Emphasize product features and customer ROI
+- Include customer testimonials and case studies
+- De-emphasize fundraising, focus on value proposition
+
+**Scenario 3: Product launch presentation**
+
+- Focus on product features and market need
+- Include demo or product screenshots
+- Emphasize innovation and competitive positioning
+
+## Customization and Extensions
+
+After generating the base deck:
+
+- Users can manually add images, charts, and custom graphics in PowerPoint
+- Suggest creating appendix slides for detailed backup information
+- Recommend PDF export for sharing (File → Save As → PDF in PowerPoint)
+- Advise on presentation timing (typically 10-15 minutes for 10 slides)
+
+## Troubleshooting
+
+**Script errors:**
+
+- Ensure `python-pptx` library is installed: `pip3 install python-pptx`
+- Verify JSON file is properly formatted (use JSON validator if needed)
+- Check file paths are correct and user has write permissions
+
+**Content issues:**
+
+- If slides appear crowded, reduce bullet points to 3-5 per slide
+- For complex competition analysis, consider manually creating comparison tables in PowerPoint
+- For financial projections, consider creating charts in Excel and importing as images
+
+## Resources
+
+### scripts/
+
+- `create_pitch_deck.py`: Python script that generates PowerPoint presentations from structured JSON data
+
+### references/
+
+- `pitch_deck_best_practices.md`: Comprehensive guide on pitch deck content, structure, and design principles

package/vendor/skills/skills/pitch-deck/index.js

@@ -0,0 +1,9 @@
+export default async function pitch_deck(input) {
+  console.log("🧠 Running skill: pitch-deck");
+
+  // TODO: implement actual logic for this skill
+  return {
+    message: "Skill 'pitch-deck' executed successfully!",
+    input,
+  };
+}

package/vendor/skills/skills/pitch-deck/package.json

@@ -0,0 +1,11 @@
+{
+    "name": "@ai-labs-claude-skills/pitch-deck",
+    "version": "1.0.0",
+    "description": "Claude AI skill: pitch-deck",
+    "license": "MIT",
+    "author": "AI Labs",
+    "files": [
+        "."
+    ],
+    "main": "index.js"
+}