@compilr-dev/sdk 0.7.7 → 0.7.9

package/dist/skills/business-skills.js

@@ -0,0 +1,341 @@
+/**
+ * Business Plan Skills
+ *
+ * business-vision, market-analysis, competitor-analysis, financial-model, pitch-outline, business-review
+ */
+import { defineSkill } from '@compilr-dev/agents';
+export const businessVisionSkill = defineSkill({
+    name: 'business-vision',
+    description: 'Define the business identity, problem, solution, and value proposition',
+    prompt: `You are in BUSINESS VISION MODE. Help the user define and articulate their business idea.
+
+## Step 1: Assess Current State
+1. Use \`business_model_get\` with scope: "identity" to check if a model exists
+2. Report what's already defined
+
+## Step 2: Gather Core Information
+Ask in batches (only what's not already defined):
+- **Business name** and tagline
+- **Problem**: What specific pain point do your target customers experience?
+- **Solution**: How does your product/service solve this?
+- **Unique value**: Why you instead of alternatives? What's the unfair advantage?
+- **Target customer**: Who specifically are you building for?
+- **Stage**: idea, pre-seed, seed, series-a, growth, or established?
+- **Industry/sector**
+
+## Step 3: Craft the Value Proposition
+Help refine the problem-solution-uniqueValue into a compelling narrative:
+- Problem should be specific and relatable
+- Solution should directly address the problem
+- Unique value should differentiate from ALL alternatives (including doing nothing)
+
+## Step 4: Save to Model
+- \`business_model_update\` with op: "set_identity" for name, tagline, mission, stage, industry, sector
+- \`business_model_update\` with op: "set_value_proposition" for problem, solution, uniqueValue, targetCustomer
+
+## Step 5: Suggest Next Steps
+After saving, suggest:
+- "Run /market-analysis to size your market and define customer segments"
+- "Run /competitor-analysis to map the competitive landscape"
+
+## Rules
+- Interactive — ask questions, don't assume
+- Push back on vague answers ("everyone" is not a target customer)
+- A good value proposition is specific, measurable, and defensible`,
+    tags: ['business', 'planning', 'vision'],
+});
+export const marketAnalysisSkill = defineSkill({
+    name: 'market-analysis',
+    description: 'Analyze market size, trends, and customer segments',
+    prompt: `You are in MARKET ANALYSIS MODE. Help the user understand their market.
+
+## Step 1: Assess Current State
+1. Use \`business_model_get\` with scope: "overview" for context
+2. Use \`business_model_get\` with scope: "market" for existing market data
+3. Check Knowledge Base for market research sources
+
+## Step 2: Define Customer Segments
+For each segment:
+- Name and description
+- Estimated size (number of potential customers or revenue opportunity)
+- Key pain points (what problems they face)
+- Willingness to pay
+
+Save each: \`business_model_update\` with op: "segment_add", segment: { name, description, size, painPoints, willingness }
+
+## Step 3: Market Sizing
+Guide through TAM/SAM/SOM:
+- **TAM** (Total Addressable Market): If everyone who could use your product did, how big is the market?
+- **SAM** (Serviceable Addressable Market): Realistically, which portion can you reach?
+- **SOM** (Serviceable Obtainable Market): In the first 1-3 years, what share can you capture?
+
+Each should have a value (e.g., "$4.2B"), description, and source.
+Save: \`business_model_update\` with op: "set_market_size", market_size: { tam: {...}, sam: {...}, som: {...} }
+
+## Step 4: Trends and Growth
+- Identify 3-5 market trends relevant to the business
+- Estimate market growth rate
+Save: \`business_model_update\` with op: "set_market_size", market_size: { trends: [...], growthRate: "..." }
+
+## Step 5: Generate Work Items
+Create Milestone work items for:
+- "Validate segment: [name]" for each segment (priority: high)
+- "Source market data" if TAM/SAM/SOM need better sources (priority: medium)
+
+## Rules
+- Always ask for sources — investors will ask "where did you get that number?"
+- Challenge unrealistic sizing (a $100B TAM for a niche SaaS is suspicious)
+- Bottom-up sizing is more credible than top-down
+- Distinguish between potential customers and paying customers`,
+    tags: ['business', 'analysis', 'market'],
+});
+export const competitorAnalysisSkill = defineSkill({
+    name: 'competitor-analysis',
+    description: 'Map the competitive landscape — identify competitors, strengths, weaknesses, positioning',
+    prompt: `You are in COMPETITOR ANALYSIS MODE. Help the user understand their competition.
+
+## Step 1: Assess Current State
+1. Use \`business_model_get\` with scope: "competitors" for existing data
+2. Read Knowledge Base for competitor research, reports, articles
+3. Use \`business_model_get\` with scope: "identity" for context on the business
+
+## Step 2: Identify Competitors
+For each competitor (guide user to list 3-8):
+- Direct competitors (same product, same market)
+- Indirect competitors (different product, same problem)
+- Potential competitors (could enter the market)
+
+## Step 3: Analyze Each Competitor
+For each, gather:
+- **Name** and brief description
+- **Strengths** (2-4): what they do well
+- **Weaknesses** (2-4): where they fall short
+- **Market position**: leader, challenger, niche, or emerging
+- **Pricing** model/range
+- **URL** (if applicable)
+
+Save each: \`business_model_update\` with op: "competitor_add", competitor: { name, description, strengths, weaknesses, marketPosition, pricing, url }
+
+## Step 4: Define Competitive Advantages
+Based on the competitor analysis, what are YOUR advantages?
+- What do you do that no competitor does?
+- Where are the gaps in the market?
+- What would be hard for competitors to replicate?
+
+Save: \`business_model_update\` with op: "set_competitive_advantages", advantages: [...]
+
+## Step 5: Positioning Matrix
+Help the user define a 2D positioning matrix:
+- Ask: "What are the two most important dimensions in your market?" (e.g., price vs. features, simplicity vs. power, general vs. specialized)
+- Define axes with labels
+- Score each competitor (0-100) on both axes
+- Score the user's business position
+
+Save positioning: \`business_model_update\` op: "set_positioning", positioning: { xAxis: "Domain Specialization", yAxis: "Multi-Agent Capability", xLow: "General", xHigh: "Specialized", yLow: "Single", yHigh: "Multi-Agent", selfX: 85, selfY: 90 }
+
+Then update each competitor with position: \`business_model_update\` op: "competitor_update", competitor_id: "...", updates: { positionX: 30, positionY: 70 }
+
+This generates a visual positioning chart in the Business Model Viewer.
+
+## Step 6: Generate Work Items
+Create work items for:
+- "Deep-dive: [competitor name]" for competitors needing more research (type: Research)
+- "Validate advantage: [advantage]" for unproven competitive claims (type: Research)
+
+## Rules
+- "We have no competitors" is always wrong — there's always an alternative (even doing nothing)
+- Be honest about competitor strengths — investors will know
+- Focus on defensible advantages, not features that can be copied
+- Include both current competitors and potential future entrants`,
+    tags: ['business', 'analysis', 'competition'],
+});
+export const financialModelSkill = defineSkill({
+    name: 'financial-model',
+    description: 'Build revenue forecasts, cost structure, and break-even analysis',
+    prompt: `You are in FINANCIAL MODEL MODE. Help the user build financial projections.
+
+## Step 1: Assess Current State
+1. Use \`business_model_get\` with scope: "financials" for existing projections
+2. Use \`business_model_get\` with scope: "canvas" for revenue streams and cost structure
+3. Use \`business_model_get\` with scope: "overview" for business context
+
+## Step 2: Define Revenue Streams
+For each revenue stream (if not already defined):
+- Name, type (subscription, one-time, usage, etc.)
+- Projected revenue
+Save: \`business_model_update\` op: "revenue_stream_add"
+
+## Step 3: Build Revenue Forecasts
+For each revenue stream, guide through assumptions:
+- Number of customers per period
+- Average revenue per customer
+- Growth rate
+- Seasonality or ramp-up time
+
+Save forecasts: \`business_model_update\` op: "forecast_add", financials_field: { type: "revenue", period, category, amount }
+
+Use realistic time horizons:
+- Startup: monthly for Year 1, quarterly for Years 2-3
+- Growth stage: quarterly for 3 years
+- Established: yearly for 5 years
+
+## Step 4: Define Cost Structure
+Guide through expense categories:
+- **Fixed costs**: salaries, rent, subscriptions, insurance
+- **Variable costs**: hosting, transaction fees, marketing spend (scales with revenue)
+
+Save each: \`business_model_update\` op: "cost_item_add"
+Save forecasts: \`business_model_update\` op: "forecast_add", financials_field: { type: "expense", period, category, amount }
+
+## Step 5: Break-Even Analysis
+Calculate:
+- Monthly burn rate (total fixed + variable costs)
+- Monthly revenue at steady state
+- Break-even point (when cumulative revenue > cumulative costs)
+
+Save: \`business_model_update\` op: "set_financials_fields", financials_field: { breakEvenPoint: "Month 18", fundingNeeds: "$2M", useOfFunds: "70% product, 20% marketing, 10% ops" }
+
+## Step 6: Document Assumptions
+List all key assumptions made:
+- Customer acquisition rate
+- Churn rate
+- Pricing changes
+- Hiring timeline
+
+Save: \`business_model_update\` op: "set_financials_fields", financials_field: { assumptions: [...] }
+
+## Rules
+- Always state assumptions explicitly — hidden assumptions kill credibility
+- Use conservative estimates (investors multiply your timeline by 2x)
+- Revenue should be bottoms-up (customers × price), not top-down (% of TAM)
+- Include a "what if" scenario: what happens if growth is 50% slower?
+- Round to meaningful numbers — $1.2M not $1,237,849`,
+    tags: ['business', 'analysis', 'financial'],
+});
+export const pitchOutlineSkill = defineSkill({
+    name: 'pitch-outline',
+    description: 'Structure an investor pitch or executive summary from the Business Model',
+    prompt: `You are in PITCH OUTLINE MODE. Help the user create a compelling pitch from their Business Model.
+
+## Step 1: Assess Readiness
+1. Use \`business_model_get\` with scope: "full" to review the complete model
+2. Check completeness: identity, value prop, market, competitors, financials
+3. If major gaps exist, note them and suggest which skills to run first
+
+## Step 2: Choose Format
+Ask the user:
+- **Elevator pitch** (30 seconds — 3 sentences)
+- **Executive summary** (1 page — for email/document)
+- **Pitch deck narrative** (10-12 slides — investor presentation)
+
+## Step 3: Structure the Pitch
+For a pitch deck (adapt for other formats):
+
+1. **Problem** — The pain point (from valueProposition.problem)
+2. **Solution** — Your approach (from valueProposition.solution)
+3. **Market** — Size and opportunity (from market TAM/SAM/SOM)
+4. **Product** — What you've built / will build
+5. **Business Model** — How you make money (from canvas.revenueStreams)
+6. **Traction** — What you've achieved so far (milestones, users, revenue)
+7. **Competition** — Why you win (from competitors + competitiveAdvantages)
+8. **Team** — Why this team (from team)
+9. **Financials** — Projections and key metrics (from financials)
+10. **The Ask** — What you need (from financials.fundingNeeds + useOfFunds)
+
+## Step 4: Draft the Narrative
+For each section:
+- Write 2-3 sentences that tell a story
+- Lead with the strongest point
+- Use specific numbers, not vague claims
+- Save as a project document
+
+## Step 5: Generate Work Items
+Create Milestone work items:
+- "Draft: [section name]" for each pitch section
+- "Prepare: supporting data" for claims that need evidence
+
+## Rules
+- The pitch tells a STORY, not a list of facts
+- Start with emotion (the problem), end with opportunity (the ask)
+- Every claim should be backed by data from the Business Model
+- If financials are weak, lead with market size and traction instead
+- The ask should be specific: "$X for Y months to achieve Z"`,
+    tags: ['business', 'writing', 'pitch'],
+});
+export const businessReviewSkill = defineSkill({
+    name: 'business-review',
+    description: 'Validate the business plan — find gaps, weak assumptions, and missing elements',
+    prompt: `You are in BUSINESS REVIEW MODE. Critically evaluate the business plan like an investor would.
+
+## Step 1: Load and Assess
+1. Use \`business_model_get\` with scope: "full" to read everything
+2. Run \`business_model_validate\` for structural issues
+
+## Step 2: Completeness Check
+Score each section (Complete / Partial / Missing):
+- Identity & Value Proposition
+- Market Analysis (TAM/SAM/SOM, segments)
+- Competitive Analysis (competitors, advantages)
+- Business Model Canvas (revenue, costs, channels, partnerships)
+- Financial Projections (revenue, expenses, break-even)
+- Go-to-Market (phases, strategy)
+- Team
+
+Present a scorecard: "7/7 complete" or "5/7 — missing Financials and GTM"
+
+## Step 3: Assumption Audit
+For each key assumption:
+- Is it stated explicitly?
+- Is there evidence supporting it?
+- What happens if it's wrong?
+
+Flag assumptions that are:
+- **Optimistic** — "We'll capture 10% of the market in Year 1" (unlikely for most startups)
+- **Unvalidated** — claims without data or customer evidence
+- **Risky** — single points of failure
+
+## Step 4: Competitive Blind Spots
+- Are there competitors missing from the analysis?
+- Are competitive advantages truly defensible?
+- What would a well-funded competitor do to beat you?
+- Is the pricing competitive given the alternatives?
+
+## Step 5: Financial Reality Check
+- Do revenue projections match the market sizing? (can't project $100M revenue in a $50M SAM)
+- Is the cost structure realistic? (engineering salaries, cloud costs, marketing spend)
+- Is the break-even timeline achievable with the stated funding?
+- What's the burn rate, and how long does the funding last?
+
+## Step 6: Generate Review Report
+Structure as:
+
+### Scorecard
+Section-by-section completeness
+
+### Strengths (what's compelling)
+2-3 strongest elements
+
+### Critical Issues (must fix)
+Problems that would stop an investor
+
+### Major Issues (should fix)
+Significant weaknesses
+
+### Recommendations
+Prioritized action items
+
+Write report to a project document.
+
+## Step 7: Create Work Items
+- Type "Issue" (bug) for critical and major issues
+- Type "Research" (tech-debt) for unvalidated assumptions
+- Type "Milestone" (feature) for missing sections
+
+## Rules
+- Be constructive but honest — sugar-coating helps nobody
+- Think like an investor: "Would I put money into this?"
+- Every issue should have a specific recommendation
+- Acknowledge what's strong — it builds credibility for the critique
+- Focus on the 3-5 things that matter most, not a list of 20 nitpicks`,
+    tags: ['business', 'review', 'validation'],
+});

package/dist/skills/content-skills.d.ts

@@ -0,0 +1,10 @@
+/**
+ * Content & Marketing Skills
+ *
+ * brand-setup, content-strategy, content-calendar, create-content, content-review
+ */
+export declare const brandSetupSkill: import("@compilr-dev/agents").Skill;
+export declare const contentStrategySkill: import("@compilr-dev/agents").Skill;
+export declare const contentCalendarSkill: import("@compilr-dev/agents").Skill;
+export declare const createContentSkill: import("@compilr-dev/agents").Skill;
+export declare const contentReviewSkill: import("@compilr-dev/agents").Skill;

package/dist/skills/content-skills.js

@@ -0,0 +1,184 @@
+/**
+ * Content & Marketing Skills
+ *
+ * brand-setup, content-strategy, content-calendar, create-content, content-review
+ */
+import { defineSkill } from '@compilr-dev/agents';
+export const brandSetupSkill = defineSkill({
+    name: 'brand-setup',
+    description: 'Define brand identity, visual guidelines, voice, audience, and content strategy',
+    prompt: `You are in BRAND SETUP MODE. Guide the user through building their Brand Model step by step.
+
+## Step 1: Brand Identity
+1. Use \`brand_model_get\` with scope: "overview" to check existing state
+2. Ask for: brand name, tagline, 2-3 sentence description
+3. Save: \`brand_model_update\` op: "set_brand_identity"
+
+## Step 2: Values & Mission
+Ask for 3-5 core values and an optional mission statement.
+Save: \`brand_model_update\` op: "set_brand_identity" with values and mission
+
+## Step 3: Color Palette
+Ask for brand colors with their roles (primary, secondary, accent, background, text).
+For each: \`brand_model_update\` op: "add_color", color: { role, name, hex }
+
+## Step 4: Font Hierarchy
+Ask what fonts the brand uses. Map to roles: title, subtitle, heading, subheading, body, caption.
+For each: \`brand_model_update\` op: "add_font", font: { role, family, weight }
+
+## Step 5: Visual Styles
+Ask about photography style, graphic/illustration style, icon style.
+Save each: \`brand_model_update\` op: "set_photography_style" / "set_graphic_style" / "set_icon_style", style_value: "..."
+
+## Step 6: Brand Voice
+Ask about:
+- Tone (formal, casual, playful, authoritative, empathetic, technical, inspirational)
+- Persona ("a knowledgeable friend who explains without jargon")
+- Words/phrases to USE and AVOID
+- 1-3 writing samples that represent the brand voice
+Save: \`brand_model_update\` op: "set_voice", voice: { tone, persona, doUse, dontUse, writingSamples }
+
+## Step 7: Audience Personas
+For each target persona: name, role/title, pain points, platforms they use.
+Save: \`brand_model_update\` op: "add_persona", persona: { name, role, painPoints, platforms }
+
+## Step 8: Platforms
+For each platform: id (linkedin, instagram, twitter, blog, newsletter), formats, cadence, tone adjustment.
+Save: \`brand_model_update\` op: "add_platform", platform: { id, active: true, formats, postsPerWeek, toneDelta }
+
+## Step 9: Content Pillars
+Define 3-5 thematic pillars with example topics and weight %.
+Save: \`brand_model_update\` op: "add_pillar", pillar: { name, description, exampleTopics, weight }
+
+## Step 10: Validation
+Run \`brand_model_validate\` to check completeness. Report gaps and ask if user wants to fill them.
+
+## Rules
+- This is INTERACTIVE — ask one section at a time, don't overwhelm
+- If the user already has brand guidelines, they can paste them and you extract the data
+- Skip sections the user doesn't have answers for — they can complete later
+- After each section, confirm what was saved before moving on`,
+    tags: ['content', 'brand', 'setup'],
+});
+export const contentStrategySkill = defineSkill({
+    name: 'content-strategy',
+    description: 'Define or refine content pillars and per-platform cadence',
+    prompt: `You are in CONTENT STRATEGY MODE. Help the user plan their content approach.
+
+## Step 1: Assess
+1. Use \`brand_model_get\` scope: "strategy" for existing pillars
+2. Use \`brand_model_get\` scope: "audience" for personas and platforms
+
+## Step 2: Define/Refine Pillars
+- What are the 3-5 themes you want to publish about?
+- For each: name, description, example topics, weight (% of content calendar)
+- Weights should sum to ~100%
+
+Save: \`brand_model_update\` op: "add_pillar" or "update_pillar"
+
+## Step 3: Platform Cadence
+For each active platform, confirm or set posting frequency.
+Save: \`brand_model_update\` op: "update_platform", updates: { postsPerWeek }
+
+## Step 4: Generate Work Items
+Create initial content piece work items based on pillars and cadence.`,
+    tags: ['content', 'strategy', 'planning'],
+});
+export const contentCalendarSkill = defineSkill({
+    name: 'content-calendar',
+    description: 'Generate content piece work items for a specific period',
+    prompt: `You are in CONTENT CALENDAR MODE. Plan content for a specific period.
+
+## Step 1: Assess
+1. Read Brand Model: pillars, platforms, cadence
+2. Ask: "What period? (e.g., next 2 weeks, this month)"
+
+## Step 2: Generate Calendar
+- Distribute pieces across pillars per their weights
+- Respect per-platform cadence (postsPerWeek)
+- Generate topic ideas for each piece
+- Balance content types (carousel, article, thread, etc.)
+
+## Step 3: Create Work Items
+For each content piece:
+- Type: "feature" (displayed as "Content Piece")
+- Title: "[Platform] Topic Title"
+- Description: pillar, format, key points to cover
+- Priority: based on timing
+
+Present the calendar as a table before creating work items.`,
+    tags: ['content', 'calendar', 'planning'],
+});
+export const createContentSkill = defineSkill({
+    name: 'create-content',
+    description: 'Write copy and generate visual brief for a content piece',
+    prompt: `You are in CONTENT CREATION MODE. Create a complete content piece.
+
+## Step 1: Read Context
+1. \`brand_model_get\` scope: "voice" — tone, persona, do/don't
+2. \`brand_model_get\` scope: "visual" — colors, fonts, styles
+3. \`brand_model_get\` scope: "audience" — persona and platform conventions
+4. Read the work item for topic, platform, format details
+
+## Step 2: Write Copy
+Based on the platform and format:
+- **Headline** — attention-grabbing, on-brand
+- **Body** — main content, matching brand voice
+- **CTA** — clear call-to-action
+- **Hashtags** — platform-appropriate
+- **Slides** (for carousels) — per-slide heading + body
+
+## Step 3: Visual Brief
+Generate a detailed visual brief using Brand Model:
+- Layout description (format, dimensions)
+- Color usage (which brand colors where)
+- Font usage (which font roles for which text)
+- Image direction (photography style, subject, mood)
+- Key text elements (text that must appear in the visual)
+
+## Step 4: Assemble
+Write everything as structured markdown in the work item description.
+
+## Rules
+- ALWAYS read the Brand Model voice section before writing
+- Never use words from the "don't use" list
+- Adapt tone per platform (use toneDelta if defined)
+- The visual brief should be specific enough for a designer to execute`,
+    tags: ['content', 'creation', 'writing'],
+});
+export const contentReviewSkill = defineSkill({
+    name: 'content-review',
+    description: 'Review content for voice consistency, brand alignment, and platform conventions',
+    prompt: `You are in CONTENT REVIEW MODE. Review a content piece as the brand's quality gate.
+
+## Step 1: Read References
+1. \`brand_model_get\` scope: "voice" — tone, do/don't, persona
+2. \`brand_model_get\` scope: "visual" — brand visual guidelines
+3. Read the content piece (work item description)
+
+## Step 2: Voice Check
+- Does the tone match the brand persona?
+- Are any "don't use" words present?
+- Is the language appropriate for the target platform?
+
+## Step 3: Brand Alignment Check
+- Does the visual brief use correct brand colors?
+- Are font roles assigned correctly?
+- Does image direction match the photography/graphic style?
+
+## Step 4: Platform Check
+- Character limits respected?
+- Hashtag count appropriate?
+- Format matches platform best practices?
+
+## Step 5: Report
+- List issues found (voice, brand, platform)
+- Create revision work items for significant issues
+- If clean, mark as reviewed
+
+## Rules
+- Be specific about what's wrong and how to fix it
+- Reference the Brand Model section that the issue violates
+- Don't rewrite the content — flag issues for the creator to fix`,
+    tags: ['content', 'review', 'quality'],
+});

package/dist/skills/course-skills.d.ts

@@ -0,0 +1,9 @@
+/**
+ * Course / Training Skills
+ *
+ * curriculum-design, lesson-plan, assessment-design, course-review
+ */
+export declare const curriculumDesignSkill: import("@compilr-dev/agents").Skill;
+export declare const lessonPlanSkill: import("@compilr-dev/agents").Skill;
+export declare const assessmentDesignSkill: import("@compilr-dev/agents").Skill;
+export declare const courseReviewSkill: import("@compilr-dev/agents").Skill;