@soulcraft/kits 1.0.0

package/src/skills/marketing-plan/index.ts

@@ -0,0 +1,43 @@
+/**
+ * @module @soulcraft/kits/skills/marketing-plan
+ * @description Raw SKILL.md content for the marketing-plan kit's AI skills.
+ *
+ * Generated from: kits/marketing-plan/skills/{skillId}/SKILL.md
+ * Do not edit directly — edit the source SKILL.md files and re-run `bun run build:skills`.
+ */
+
+/** Raw SKILL.md content for the `plan-campaign` skill. */
+export const planCampaign = "---\nname: Plan Marketing Campaign\ndescription: Design and plan a marketing campaign\ntype: invocable\nversion: \"1.0.0\"\nparameters: [campaignGoal]\n---\n\n## Plan Marketing Campaign\n\nDesign and plan a marketing campaign\n\n### Steps\n\n1. Define campaign objective: What do you want to achieve?\n2. Target audience: Which persona(s) is this for?\n3. Key message: What's the core message?\n4. Channels: Which channels will you use?\n5. Content needs: What content do you need to create?\n6. Timeline: When will each element launch?\n7. Budget: How much will you spend?\n8. Success metrics: How will you measure success?\n9. Create campaign document\n\n### Inputs Required\n\n- **campaignGoal** (required): Campaign objective\n\n### Expected Outputs\n\n- Campaign brief\n- Content list\n- Timeline\n\n### When to Use\n\nThis workflow is helpful when the user mentions:\n- \"plan campaign\"\n- \"new campaign\"\n- \"campaign brief\"\n- \"launch campaign\"\n";
+
+/** Raw SKILL.md content for the `channel-strategy` skill. */
+export const channelStrategy = "---\nname: channel-strategy\ndescription: Marketing channel selection and budget allocation strategies\ntype: invocable\nversion: \"1.0.0\"\n---\n\n## Channel Strategy Skill\n\nWhen the user invokes `/channels`, help them select and prioritize marketing channels and allocate budget effectively.\n\n### Invocation Patterns\n\n- `/channels` - Full channel strategy analysis\n- `/channels [budget]` - Channel allocation for specific budget\n- `/channels audit` - Evaluate current channel performance\n\n### Channel Categories\n\n**Owned Channels**\n- Website/blog\n- Email list\n- Social media profiles\n- Mobile app\n- Physical locations\n\n**Earned Channels**\n- PR/media coverage\n- Word of mouth\n- Social shares\n- Reviews/testimonials\n- SEO organic traffic\n\n**Paid Channels**\n- Search ads (Google, Bing)\n- Social ads (Meta, LinkedIn, TikTok)\n- Display/programmatic\n- Influencer marketing\n- Sponsorships\n- Traditional media\n\n### Channel Selection Framework\n\n**ICE Scoring**\n- **I**mpact: How much will this move the needle? (1-10)\n- **C**onfidence: How sure are you it will work? (1-10)\n- **E**ase: How easy is it to implement? (1-10)\n- Score = (I + C + E) / 3\n\n### Output Format\n\n```markdown\n## Channel Strategy: [Business/Product]\n\n### Target Audience\n- **Primary Segment**: [Description]\n- **Where They Spend Time**: [Platforms/channels]\n- **How They Discover**: [Research behavior]\n\n### Channel Analysis\n\n| Channel | ICE Score | Stage | Budget % | Expected CAC |\n|---------|-----------|-------|----------|--------------|\n| [Channel 1] | X.X | [Awareness/Consideration/Conversion] | X% | $X |\n| [Channel 2] | X.X | [Stage] | X% | $X |\n\n### Recommended Channel Mix\n\n#### Primary Channels (60% of budget)\n1. **[Channel]**\n   - Why: [Strategic rationale]\n   - Target metrics: [KPIs]\n   - Budget: $X (X%)\n   - Expected return: [ROI estimate]\n\n2. **[Channel]**\n   [Same format]\n\n#### Secondary Channels (30% of budget)\n[Same format]\n\n#### Experimental Channels (10% of budget)\n[Channels to test]\n\n### Channel-Stage Mapping\n| Stage | Channels | Goal | Metrics |\n|-------|----------|------|---------|\n| Awareness | [Channels] | [Goal] | [Metrics] |\n| Consideration | [Channels] | [Goal] | [Metrics] |\n| Conversion | [Channels] | [Goal] | [Metrics] |\n| Retention | [Channels] | [Goal] | [Metrics] |\n\n### Budget Allocation\n**Total Budget**: $X\n\n| Channel | Monthly | Quarterly | Annual |\n|---------|---------|-----------|--------|\n| [Channel 1] | $X | $X | $X |\n| [Channel 2] | $X | $X | $X |\n| **Total** | $X | $X | $X |\n\n### Testing Plan\n| Channel | Test | Budget | Success Criteria | Timeline |\n|---------|------|--------|------------------|----------|\n| [Channel] | [What to test] | $X | [KPI target] | [Dates] |\n\n### Scaling Rules\n- Scale [Channel] when CAC < $X\n- Reduce [Channel] when conversion rate < X%\n- Test new channel when [Trigger]\n```\n\n### Channel Characteristics\n\n**Search Ads (Google)**\n- Best for: High-intent buyers\n- Timing: When people are searching\n- Typical CAC: $20-200 (varies by industry)\n- Key metric: Quality Score, ROAS\n\n**Social Ads (Meta/IG)**\n- Best for: Awareness, visual products\n- Timing: Interruption-based\n- Typical CAC: $10-100\n- Key metric: CPM, CTR, frequency\n\n**Content Marketing**\n- Best for: B2B, complex products\n- Timing: Long-term investment\n- Typical CAC: Lower over time\n- Key metric: Organic traffic, leads\n\n**Email Marketing**\n- Best for: Nurturing, retention\n- Timing: Owned audience\n- Typical CAC: Very low (owned)\n- Key metric: Open rate, CTR, revenue per email\n\n### Budget Allocation Models\n\n**70-20-10 Rule**\n- 70%: Proven channels\n- 20%: Promising channels\n- 10%: Experimental\n\n**Stage-Based**\n- Startup: Heavy on CAC-efficient channels\n- Growth: Scale what works + test new\n- Mature: Diversify to reduce risk\n\n### Channel Synergies\n\n- Search + Retargeting: Capture high-intent, follow up\n- Content + Social: Create and distribute\n- Email + Paid: Nurture leads, re-engage\n- PR + Social: Amplify earned media\n";
+
+/** Raw SKILL.md content for the `campaign-metrics` skill. */
+export const campaignMetrics = "---\nname: campaign-metrics\ndescription: Background expertise in marketing KPI definition and measurement frameworks\ntype: background\nversion: \"1.0.0\"\n---\n\n## Campaign Metrics Expertise\n\nYou have expertise in marketing measurement and analytics. Apply these principles when helping users define KPIs and measure campaign performance.\n\n### Marketing Funnel Metrics\n\n**Awareness Stage**\n- Impressions\n- Reach\n- Brand awareness lift\n- Share of voice\n- PR mentions\n\n**Consideration Stage**\n- Website traffic\n- Time on site\n- Pages per session\n- Content downloads\n- Video views/completion\n\n**Conversion Stage**\n- Conversion rate\n- Cost per acquisition (CPA/CAC)\n- Return on ad spend (ROAS)\n- Sales qualified leads (SQLs)\n- Revenue\n\n**Retention Stage**\n- Customer lifetime value (LTV)\n- Retention rate\n- Net promoter score (NPS)\n- Repeat purchase rate\n- Churn rate\n\n### Key Metric Definitions\n\n**Customer Acquisition Cost (CAC)**\n```\nCAC = Total Sales & Marketing Spend / New Customers Acquired\n```\n- Include: ads, salaries, tools, content, events\n- Track: Overall and by channel\n- Benchmark: Varies by industry ($10-$500+)\n\n**Lifetime Value (LTV)**\n```\nLTV = Average Purchase Value × Purchase Frequency × Customer Lifespan\n```\n- Or: Monthly Revenue × Gross Margin / Monthly Churn Rate\n- Target: LTV:CAC ratio of 3:1 or higher\n\n**Return on Ad Spend (ROAS)**\n```\nROAS = Revenue from Ads / Ad Spend\n```\n- Target: 3x-5x minimum for most businesses\n- Break-even ROAS = 1 / Gross Margin\n\n**Conversion Rate**\n```\nConversion Rate = Conversions / Total Visitors (or Impressions)\n```\n- Track at each funnel stage\n- Benchmark against industry averages\n\n### Channel-Specific Metrics\n\n**Paid Search**\n- Click-through rate (CTR)\n- Cost per click (CPC)\n- Quality Score\n- Impression share\n- Conversion rate\n\n**Social Media**\n- Engagement rate\n- Reach and impressions\n- Follower growth\n- Click-through rate\n- Cost per engagement\n\n**Email Marketing**\n- Open rate\n- Click-through rate\n- Unsubscribe rate\n- Revenue per email\n- List growth rate\n\n**Content Marketing**\n- Organic traffic\n- Time on page\n- Bounce rate\n- Social shares\n- Lead generation\n\n### Attribution Models\n\n**Last Click**\n- Credit to final touchpoint\n- Simple but ignores journey\n- Undervalues awareness\n\n**First Click**\n- Credit to initial touchpoint\n- Values awareness channels\n- Ignores nurturing\n\n**Linear**\n- Equal credit to all touchpoints\n- Balanced view\n- May overvalue low-impact touches\n\n**Time Decay**\n- More credit to recent touchpoints\n- Accounts for recency\n- Good for short sales cycles\n\n**Position-Based (U-Shaped)**\n- 40% first, 40% last, 20% middle\n- Values intro and close\n- Common compromise\n\n**Data-Driven**\n- Algorithm determines credit\n- Most accurate\n- Requires significant data\n\n### Setting Marketing Goals\n\n**SMART Framework**\n- Specific: \"Increase email signups\"\n- Measurable: \"by 25%\"\n- Achievable: Based on historical data\n- Relevant: Aligned to business goals\n- Time-bound: \"by end of Q2\"\n\n**Goal Hierarchy**\n```\nBusiness Goal: Increase revenue by 20%\n├── Marketing Goal: Generate 500 MQLs/month\n│   ├── Channel Goal: Get 10,000 website visitors\n│   │   ├── Tactic: Publish 8 blog posts\n│   │   └── Tactic: Run LinkedIn ads\n```\n\n### Dashboard Essentials\n\n**Executive Dashboard**\n- Revenue impact\n- CAC and LTV\n- ROAS by channel\n- Pipeline value\n- YoY comparison\n\n**Channel Dashboard**\n- Channel-specific KPIs\n- Trend over time\n- Benchmarks\n- Budget vs. actual\n- A/B test results\n\n**Campaign Dashboard**\n- Campaign performance\n- Audience breakdown\n- Creative performance\n- Conversion funnel\n- Cost efficiency\n\n### Common Measurement Mistakes\n\n- Vanity metrics (likes without business impact)\n- Wrong attribution model\n- Not accounting for lag\n- Mixing correlation and causation\n- Ignoring incrementality\n- Short measurement windows\n- Not segmenting data\n";
+
+/** Raw SKILL.md content for the `allocate-budget` skill. */
+export const allocateBudget = "---\nname: Allocate Marketing Budget\ndescription: Distribute budget across channels and campaigns\ntype: invocable\nversion: \"1.0.0\"\n---\n\n## Allocate Marketing Budget\n\nDistribute budget across channels and campaigns\n\n### Steps\n\n1. Start with total budget available\n2. Review historical performance by channel\n3. Identify must-have vs. nice-to-have activities\n4. Allocate to campaigns and channels based on expected ROI\n5. Reserve 10-20% for testing and opportunities\n6. Create monthly spending plan\n7. Set up tracking for actual vs. planned spend\n8. Document in Budget section\n\n### Expected Outputs\n\n- Budget allocation\n- Monthly spending plan\n\n### When to Use\n\nThis workflow is helpful when the user mentions:\n- \"allocate budget\"\n- \"how should we spend\"\n- \"budget planning\"\n- \"marketing spend\"\n";
+
+/** Raw SKILL.md content for the `kit-expertise` skill. */
+export const kitExpertise = "---\nname: kit-expertise\ndescription: Domain expertise for Marketing Plan - applied automatically when working in this kit\ntype: background\nversion: \"1.0.0\"\n---\n\n## Your Role\n\nYou are an experienced marketing strategist who has built and scaled marketing programs for businesses of all sizes. You understand both brand building and performance marketing, and you help teams create plans that balance creativity with measurable results.\n\n## Your Expertise\n\n- Marketing strategy and planning\n- Customer segmentation and personas\n- Content marketing and SEO\n- Paid advertising (Google, Meta, LinkedIn)\n- Social media strategy\n- Email marketing and automation\n- Marketing analytics and attribution\n- Brand development\n- Campaign management\n- Budget allocation and ROI\n\n## Your Approach\n\nWork alongside the user as a creative partner\n\n## Things to Avoid\n\n- Don't recommend spreading budget too thin across many channels\n- Don't promise specific ROI numbers - marketing is probabilistic\n- Don't ignore the need for testing and iteration\n- Don't separate brand and performance - they work together\n\n## Domain Knowledge\n\n### Key Terms\n\n**CAC**\nCustomer Acquisition Cost - cost to acquire one customer\n\n**LTV**\nLifetime Value - total revenue from a customer over time\n\n**ROAS**\nReturn on Ad Spend - revenue generated per dollar of ad spend\n\n**CPA**\nCost per Acquisition - cost to get a conversion\n\n**CPM**\nCost per Mille - cost per 1,000 impressions\n\n**CTR**\nClick-Through Rate - clicks divided by impressions\n\n**CVR**\nConversion Rate - conversions divided by visitors\n\n**MQL**\nMarketing Qualified Lead - lead meeting marketing criteria\n\n**SQL**\nSales Qualified Lead - lead ready for sales contact\n\n**funnel**\nCustomer journey from awareness to purchase\n\n**attribution**\nAssigning credit to touchpoints in the customer journey\n\n**persona**\nFictional representation of your ideal customer\n\n**positioning**\nHow your brand is perceived relative to competitors\n\n**organic**\nNon-paid marketing (SEO, social, content)\n\n**paid**\nAdvertising and sponsored content\n\n### Best Practices\n\n- Set SMART goals: Specific, Measurable, Achievable, Relevant, Time-bound\n- Focus resources on 2-3 channels maximum for impact\n- Allocate 70% to proven tactics, 20% to optimization, 10% to experiments\n- Plan content at least one month in advance\n- Track metrics weekly, report monthly, review quarterly\n- A/B test creative and messaging continuously\n- Build in flexibility for real-time optimization\n\n### Common Mistakes to Avoid\n\n- Vanity metrics (followers, likes) without business impact\n- Spreading budget across too many channels\n- Launching campaigns without clear success metrics\n- Ignoring attribution and customer journey\n- One-size-fits-all messaging for different audiences\n- Setting and forgetting campaigns without optimization\n- Siloed marketing disconnected from sales goals\n\n### Recommended References\n\n- [HubSpot Marketing Hub](https://www.hubspot.com): Comprehensive marketing resources and tools\n- [Marketing Made Simple](https://marketingmadesimple.com): Donald Miller's framework for marketing\n- **Traction**: Gabriel Weinberg's book on marketing channels\n";
+
+/** Raw SKILL.md content for the `create-persona` skill. */
+export const createPersona = "---\nname: Create Customer Persona\ndescription: Develop a detailed target customer persona\ntype: invocable\nversion: \"1.0.0\"\nparameters: [audienceType]\n---\n\n## Create Customer Persona\n\nDevelop a detailed target customer persona\n\n### Steps\n\n1. Name and photo: Give them an identity\n2. Demographics: Age, location, income, job title\n3. Psychographics: Values, interests, lifestyle\n4. Goals: What are they trying to achieve?\n5. Pain points: What problems do they face?\n6. Buying behavior: How do they make decisions?\n7. Information sources: Where do they get info?\n8. Objections: What would stop them from buying?\n9. How we help: How does our product address their needs?\n10. Document in Target Audience section\n\n### Inputs Required\n\n- **audienceType** (required): Type of customer\n\n### Expected Outputs\n\n- Customer persona document\n\n### When to Use\n\nThis workflow is helpful when the user mentions:\n- \"create persona\"\n- \"define audience\"\n- \"target customer\"\n- \"who are we targeting\"\n";
+
+/** Raw SKILL.md content for the `content-calendar` skill. */
+export const contentCalendar = "---\nname: Build Content Calendar\ndescription: Create a content calendar for the planning period\ntype: invocable\nversion: \"1.0.0\"\n---\n\n## Build Content Calendar\n\nCreate a content calendar for the planning period\n\n### Steps\n\n1. Review objectives and campaigns for the period\n2. Identify key dates: holidays, events, product launches\n3. Map content themes to each month/week\n4. Define content types: blog, social, video, email\n5. Assign topics to dates\n6. Note channels for distribution\n7. Set deadlines for creation and review\n8. Create in Calendar view\n\n### Expected Outputs\n\n- Content calendar\n- Topic list\n\n### When to Use\n\nThis workflow is helpful when the user mentions:\n- \"content calendar\"\n- \"editorial calendar\"\n- \"plan content\"\n- \"what should we post\"\n";
+
+/** Raw SKILL.md content for the `measure-performance` skill. */
+export const measurePerformance = "---\nname: Set Up Performance Measurement\ndescription: Define KPIs and measurement framework\ntype: invocable\nversion: \"1.0.0\"\n---\n\n## Set Up Performance Measurement\n\nDefine KPIs and measurement framework\n\n### Steps\n\n1. Identify business objectives to support\n2. Define primary KPIs for each objective\n3. Set specific targets for each KPI\n4. Identify data sources for each metric\n5. Set up dashboards for tracking\n6. Define reporting cadence and format\n7. Plan for regular reviews and optimization\n8. Document in Measurement section\n\n### Expected Outputs\n\n- KPI framework\n- Measurement plan\n\n### When to Use\n\nThis workflow is helpful when the user mentions:\n- \"measure performance\"\n- \"set KPIs\"\n- \"track results\"\n- \"marketing metrics\"\n";
+
+/** All skills for the marketing-plan kit, keyed by skill ID. */
+export const allSkills: Record<string, string> = {
+	'plan-campaign': planCampaign,
+	'channel-strategy': channelStrategy,
+	'campaign-metrics': campaignMetrics,
+	'allocate-budget': allocateBudget,
+	'kit-expertise': kitExpertise,
+	'create-persona': createPersona,
+	'content-calendar': contentCalendar,
+	'measure-performance': measurePerformance
+};

package/src/skills/marketing-site/index.ts

@@ -0,0 +1,39 @@
+/**
+ * @module @soulcraft/kits/skills/marketing-site
+ * @description Raw SKILL.md content for the marketing-site kit's AI skills.
+ *
+ * Generated from: kits/marketing-site/skills/{skillId}/SKILL.md
+ * Do not edit directly — edit the source SKILL.md files and re-run `bun run build:skills`.
+ */
+
+/** Raw SKILL.md content for the `add-page` skill. */
+export const addPage = "---\nname: Create New Page\ndescription: Add a new page to the site\ntype: invocable\nversion: \"1.0.0\"\n---\n\n## Create New Page\n\nAdd a new page to the site\n\n### Steps\n\n1. Copy an existing page as a template\n2. Update the title and content\n3. Add navigation link to all pages\n4. Create any page-specific styles\n\n### When to Use\n\nThis workflow is helpful when the user mentions:\n- \"new page\"\n- \"create page\"\n- \"add page\"\n\n### Execution Mode\n\nThis workflow can be executed automatically when triggered. Proceed through the steps without waiting for confirmation at each step.\n";
+
+/** Raw SKILL.md content for the `landing-page` skill. */
+export const landingPage = "---\nname: landing-page\ndescription: Background expertise in landing page best practices and above-the-fold optimization\ntype: background\nversion: \"1.0.0\"\n---\n\n## Landing Page Expertise\n\nYou have expertise in high-converting landing page design and copywriting. Apply these principles when helping users create marketing sites.\n\n### Above-the-Fold Essentials\n\n**The 5-Second Test**\nVisitors should understand within 5 seconds:\n1. What you offer\n2. Who it's for\n3. Why it matters\n4. What to do next\n\n**Critical Elements**\n- Clear headline (value proposition)\n- Supporting subheadline\n- Hero image or video\n- Primary CTA button\n- Trust indicators (logos, reviews)\n\n### Headline Formulas\n\n**Value Proposition Headlines**\n- \"[Achieve Result] without [Pain Point]\"\n- \"The [Adjective] Way to [Desired Outcome]\"\n- \"[Product] for [Target Audience] Who [Want/Need X]\"\n\n**Problem-Agitation Headlines**\n- \"Tired of [Problem]?\"\n- \"Stop [Frustrating Activity]\"\n- \"[Problem]? There's a Better Way.\"\n\n**Social Proof Headlines**\n- \"Join [X] [People/Companies] Who...\"\n- \"Trusted by [Impressive Names]\"\n- \"#1 [Category] for [Audience]\"\n\n### Page Structure\n\n**Hero Section**\n- Headline: Primary value proposition\n- Subheadline: Supporting detail or secondary benefit\n- CTA: Clear action button\n- Visual: Product image, demo, or hero illustration\n\n**Problem/Solution Section**\n- Articulate the pain point\n- Show you understand\n- Present your solution\n\n**Features/Benefits Section**\n- Lead with benefits, support with features\n- 3-5 key points maximum\n- Use icons or illustrations\n\n**Social Proof Section**\n- Customer testimonials\n- Logo wall\n- Case study snippets\n- Numbers/statistics\n\n**FAQ Section**\n- Address objections\n- Remove friction\n- Build confidence\n\n**Final CTA Section**\n- Reinforce value\n- Repeat primary CTA\n- Create urgency (if appropriate)\n\n### CTA Best Practices\n\n**Button Copy**\n- Action-oriented (\"Get Started\" not \"Submit\")\n- Value-focused (\"Start Free Trial\" not \"Sign Up\")\n- Specific (\"Download the Guide\" not \"Click Here\")\n\n**Button Design**\n- Contrasting color\n- Sufficient size (easy to tap on mobile)\n- Clear visual hierarchy\n- Whitespace around it\n\n**Reducing Friction**\n- \"No credit card required\"\n- \"Free forever\" or \"14-day free trial\"\n- \"Cancel anytime\"\n- Show trust badges\n\n### Visual Hierarchy\n\n**F-Pattern for Scanning**\n- Key info along top\n- Important elements on left\n- CTAs at natural stopping points\n\n**Z-Pattern for Engagement**\n- Logo top-left\n- Navigation top-right\n- Headline center-left\n- CTA bottom-right\n\n### Trust Elements\n\n**Social Proof Types**\n- Customer logos\n- Testimonials with photos\n- Review scores (G2, Capterra)\n- User count\n- Media mentions\n\n**Credibility Indicators**\n- Security badges\n- Industry certifications\n- Awards\n- \"As seen in\" logos\n\n### Mobile Considerations\n\n- Stack elements vertically\n- Larger tap targets (48px minimum)\n- Shorter headlines\n- Single-column layout\n- Sticky CTA option\n- Fast load time critical\n\n### Common Mistakes\n\n**Content Issues**\n- Too much text\n- Features over benefits\n- Vague headlines\n- Multiple CTAs competing\n- No clear next step\n\n**Design Issues**\n- Slow load times\n- Poor mobile experience\n- Low contrast text\n- Cluttered layout\n- Weak visual hierarchy\n\n**Strategy Issues**\n- No clear audience\n- Multiple goals on one page\n- Missing social proof\n- No urgency or scarcity\n- Friction in the funnel\n";
+
+/** Raw SKILL.md content for the `add-section` skill. */
+export const addSection = "---\nname: Add New Section\ndescription: Add a new content section to a page\ntype: invocable\nversion: \"1.0.0\"\n---\n\n## Add New Section\n\nAdd a new content section to a page\n\n### Steps\n\n1. Identify where to add the section in HTML\n2. Create the section with semantic markup\n3. Add corresponding styles to styles.css\n4. Test responsiveness\n\n### When to Use\n\nThis workflow is helpful when the user mentions:\n- \"add section\"\n- \"new section\"\n- \"pricing section\"\n- \"team section\"\n\n### Execution Mode\n\nThis workflow can be executed automatically when triggered. Proceed through the steps without waiting for confirmation at each step.\n";
+
+/** Raw SKILL.md content for the `change-colors` skill. */
+export const changeColors = "---\nname: Change Color Scheme\ndescription: Update the site's color palette\ntype: invocable\nversion: \"1.0.0\"\n---\n\n## Change Color Scheme\n\nUpdate the site's color palette\n\n### Steps\n\n1. Open styles.css\n2. Find the :root section with CSS variables\n3. Change --color-primary, --color-secondary, etc.\n4. Preview changes in browser\n\n### When to Use\n\nThis workflow is helpful when the user mentions:\n- \"change colors\"\n- \"new palette\"\n- \"different theme\"\n";
+
+/** Raw SKILL.md content for the `conversion-copy` skill. */
+export const conversionCopy = "---\nname: conversion-copy\ndescription: Write conversion-focused copy for marketing sites\ntype: invocable\nversion: \"1.0.0\"\n---\n\n## Conversion Copy Skill\n\nWhen the user invokes `/convert`, help them write high-converting copy for their marketing site.\n\n### Invocation Patterns\n\n- `/convert` - Review and optimize current copy\n- `/convert headline` - Generate headline variations\n- `/convert cta` - Optimize call-to-action copy\n- `/convert [section]` - Write specific section\n\n### Copywriting Frameworks\n\n**PAS (Problem-Agitate-Solution)**\n1. **Problem**: Name the pain point\n2. **Agitate**: Twist the knife (consequences)\n3. **Solution**: Present your answer\n\n**AIDA (Attention-Interest-Desire-Action)**\n1. **Attention**: Hook them\n2. **Interest**: Engage with relevance\n3. **Desire**: Create want\n4. **Action**: Tell them what to do\n\n**BAB (Before-After-Bridge)**\n1. **Before**: Current painful state\n2. **After**: Desired future state\n3. **Bridge**: Your product/service\n\n### Output Format\n\n```markdown\n## Conversion Copy: [Section/Page]\n\n### Headlines (A/B Test These)\n1. \"[Primary headline]\"\n2. \"[Variation 1]\"\n3. \"[Variation 2]\"\n\n### Subheadline\n[Supporting copy that elaborates on headline]\n\n### Body Copy\n[Main content following appropriate framework]\n\n### CTA Button\n- Primary: \"[CTA text]\"\n- Supporting text: \"[Reduce friction]\"\n\n### Analysis\n- **Target emotion**: [What feeling to evoke]\n- **Key objection addressed**: [What fear to overcome]\n- **Value proposition**: [Core benefit]\n\n### A/B Testing Suggestions\n1. Test [element 1] vs [element 2]\n2. Test [approach 1] vs [approach 2]\n```\n\n### Headline Techniques\n\n**Use Numbers**\n- \"7 Ways to Boost Your Productivity\"\n- \"Increase Revenue by 40%\"\n- \"In Just 5 Minutes a Day\"\n\n**Ask Questions**\n- \"What If You Could...?\"\n- \"Ready to Transform Your...?\"\n- \"Struggling with...?\"\n\n**Use Power Words**\n- Free, New, Now, Instant\n- Proven, Guaranteed, Easy\n- Exclusive, Limited, Secret\n\n**Create Urgency**\n- \"Start Today\"\n- \"Don't Miss Out\"\n- \"Limited Time\"\n\n### Benefits vs. Features\n\n**Feature** → **Benefit** → **So What**\n- \"256-bit encryption\" → \"Bank-level security\" → \"Your data is safe\"\n- \"AI-powered\" → \"Saves you hours\" → \"Focus on what matters\"\n- \"Cloud-based\" → \"Access anywhere\" → \"Work from wherever you are\"\n\n### Voice of Customer\n\n**Use their words**\n- Mine reviews for language\n- Copy testimonial phrasing\n- Mirror their vocabulary\n\n**Speak to their identity**\n- \"For founders who...\"\n- \"Built for teams that...\"\n- \"If you're the kind of person who...\"\n\n### Persuasion Principles\n\n**Social Proof**\n- \"Join 10,000+ users\"\n- \"Rated 4.9/5 stars\"\n- \"Trusted by [logos]\"\n\n**Authority**\n- \"Featured in [publication]\"\n- \"Built by experts from [companies]\"\n- \"Recommended by [influencer]\"\n\n**Scarcity**\n- \"Only X spots left\"\n- \"Offer ends [date]\"\n- \"Limited availability\"\n\n**Reciprocity**\n- \"Free guide included\"\n- \"Bonus templates\"\n- \"No strings attached\"\n\n### Common Copy Mistakes\n\n- Writing for yourself, not the customer\n- Leading with features over benefits\n- Vague claims without specifics\n- Too clever (clarity > cleverness)\n- Weak or missing CTA\n- No emotional connection\n- Ignoring objections\n\n### CTA Best Practices\n\n**Strong CTAs**\n- \"Start My Free Trial\"\n- \"Get Instant Access\"\n- \"See It In Action\"\n- \"Claim Your Spot\"\n\n**Weak CTAs**\n- \"Submit\"\n- \"Sign Up\"\n- \"Click Here\"\n- \"Learn More\" (sometimes OK)\n";
+
+/** Raw SKILL.md content for the `export-deploy` skill. */
+export const exportDeploy = "---\nname: Export for Deployment\ndescription: Download site files for deployment\ntype: invocable\nversion: \"1.0.0\"\n---\n\n## Export for Deployment\n\nDownload site files for deployment\n\n### Steps\n\n1. Use Workshop's export feature\n2. Download as ZIP\n3. Deploy to Netlify Drop, Vercel, or GitHub Pages\n\n### When to Use\n\nThis workflow is helpful when the user mentions:\n- \"export\"\n- \"deploy\"\n- \"publish\"\n- \"download\"\n";
+
+/** Raw SKILL.md content for the `kit-expertise` skill. */
+export const kitExpertise = "---\nname: kit-expertise\ndescription: Domain expertise for Marketing Website - applied automatically when working in this kit\ntype: background\nversion: \"1.0.0\"\n---\n\n## Your Role\n\nYou are a web designer expert in HTML5, CSS3, and modern marketing website design. You help users customize their site by editing HTML and CSS files directly. You understand responsive design, accessibility, and conversion optimization.\n\n## Your Expertise\n\n- HTML5 semantic markup\n- CSS3 layouts (flexbox, grid)\n- Responsive mobile-first design\n- Web accessibility (WCAG)\n- SEO best practices\n- Form design and validation\n- Typography and color theory\n- Landing page optimization\n\n## Your Approach\n\nWork alongside the user as a creative partner\n\n## Things to Avoid\n\n- Don't add JavaScript frameworks - keep it simple vanilla JS\n- Don't overcomplicate the CSS - use simple, readable styles\n- Avoid inline styles - use the stylesheet\n- Don't remove semantic HTML structure\n\n## Domain Knowledge\n\n### Key Terms\n\n**hero**\nThe main banner section at the top of the page with headline, subheadline, and CTA\n\n**CTA**\nCall-to-action - a button or link prompting the user to take action\n\n**above the fold**\nContent visible without scrolling\n\n**responsive**\nDesign that adapts to different screen sizes (mobile, tablet, desktop)\n\n**semantic HTML**\nUsing HTML elements for their meaning (header, main, section, footer)\n\n**CSS variables**\nCustom properties (--name: value) for easy theming\n\n### Best Practices\n\n- Use semantic HTML elements (header, main, section, article, footer)\n- Mobile-first CSS approach - base styles for mobile, media queries for larger screens\n- CSS variables at :root for colors, fonts, and spacing\n- BEM-like class naming for clarity\n- Accessible form labels with for/id attributes\n- Alt text on all images\n\n### Common Mistakes to Avoid\n\n- Using div for everything instead of semantic elements\n- Inline styles instead of stylesheet\n- Fixed widths instead of responsive units\n- Missing alt text on images\n- Form inputs without labels\n\n### Recommended References\n\n- **CSS Variables**: Change colors and fonts by editing the :root section in styles.css\n- **Adding Sections**: Copy an existing section and modify the content\n- **Deployment**: Export as ZIP, then drag to Netlify Drop or upload to Vercel\n";
+
+/** All skills for the marketing-site kit, keyed by skill ID. */
+export const allSkills: Record<string, string> = {
+	'add-page': addPage,
+	'landing-page': landingPage,
+	'add-section': addSection,
+	'change-colors': changeColors,
+	'conversion-copy': conversionCopy,
+	'export-deploy': exportDeploy,
+	'kit-expertise': kitExpertise
+};

package/src/skills/match-3-puzzle/index.ts

@@ -0,0 +1,15 @@
+/**
+ * @module @soulcraft/kits/skills/match-3-puzzle
+ * @description Raw SKILL.md content for the match-3-puzzle kit's AI skills.
+ *
+ * Generated from: kits/match-3-puzzle/skills/{skillId}/SKILL.md
+ * Do not edit directly — edit the source SKILL.md files and re-run `bun run build:skills`.
+ */
+
+/** Raw SKILL.md content for the `kit-expertise` skill. */
+export const kitExpertise = "# Match 3 Puzzle Kit Expertise\n\nYou are an expert in this Match 3 puzzle game implementation using SVG rendering.\n\n## Architecture Overview\n\n### Game Logic\n- **`src/lib/game/Board.ts`**: Core board logic (matching, gravity, cascades)\n- **`src/lib/game/GameEngine.ts`**: Game state management and orchestration\n\n### Components\n- **`GameBoard.svelte`**: SVG-based gem rendering with click/drag interaction\n- **`GameHUD.svelte`**: Score, moves/time, combo display\n\n### Routes\n- **`/`**: Main game with mode selection (Level, Timed, Endless)\n- **`/leaderboard`**: High scores from Brainy\n\n## Game Modes\n\n1. **Level Mode**: Beat target score with limited moves\n2. **Timed Mode**: Score as much as possible in 2 minutes\n3. **Endless Mode**: Relaxed play with no limits\n\n## Match Detection\n\n```typescript\n// Find all 3+ horizontal and vertical matches\nconst matches = board.findMatches()\n\n// Each match contains:\ninterface Match {\n  gems: Gem[]       // Matched gems\n  horizontal: boolean\n  length: number    // 3, 4, 5, or 6\n}\n```\n\n## Cascade System\n\nWhen matches are cleared:\n1. Gems above fall down (gravity)\n2. New gems spawn at top\n3. Check for new matches\n4. Repeat until stable\n\n## Special Gems\n\n- **4-match**: Creates row/column clearer\n- **5+ match**: Creates rainbow gem (matches any color)\n\n## Scoring\n\n```typescript\n// Base: 10 points per gem\n// Length bonus: +20 per gem over 3\n// Combo multiplier: 1 + (combo × 0.5)\nscore = (baseScore + lengthBonus) × comboMultiplier\n```\n\n## Brainy Integration\n\nHigh scores saved automatically:\n```typescript\nawait brainy.add({\n  type: 'measurement',\n  data: { score, level, mode, maxCombo },\n  metadata: { type: 'match3-highscore' }\n})\n```\n\n## Customization\n\n### Change Board Size\n```typescript\n// In GameEngine.ts, modify LEVELS array\n{\n  boardWidth: 9,\n  boardHeight: 9,\n  // ...\n}\n```\n\n### Add New Gem Types\n```typescript\n// In types.ts, add to GemType\ntype GemType = 'red' | 'blue' | ... | 'newcolor'\n\n// In GameBoard.svelte, add to gemColors\nconst gemColors = {\n  newcolor: { fill: '#xxx', stroke: '#xxx', glow: 'rgba(...)' }\n}\n```\n\n### Modify Level Progression\nEdit the `LEVELS` array in `GameEngine.ts` to adjust difficulty curve.\n";
+
+/** All skills for the match-3-puzzle kit, keyed by skill ID. */
+export const allSkills: Record<string, string> = {
+	'kit-expertise': kitExpertise
+};

package/src/skills/mind-map/index.ts

@@ -0,0 +1,43 @@
+/**
+ * @module @soulcraft/kits/skills/mind-map
+ * @description Raw SKILL.md content for the mind-map kit's AI skills.
+ *
+ * Generated from: kits/mind-map/skills/{skillId}/SKILL.md
+ * Do not edit directly — edit the source SKILL.md files and re-run `bun run build:skills`.
+ */
+
+/** Raw SKILL.md content for the `organize-map` skill. */
+export const organizeMap = "---\nname: Organize Mind Map\ndescription: Restructure and refine the mind map after brainstorming\ntype: invocable\nversion: \"1.0.0\"\n---\n\n## Organize Mind Map\n\nRestructure and refine the mind map after brainstorming\n\n### Steps\n\n1. Review all branches and sub-ideas\n2. Identify themes that span multiple branches\n3. Move ideas to more appropriate branches if needed\n4. Combine duplicate or similar ideas\n5. Identify and remove truly irrelevant ideas\n6. Reorder branches by importance or logic\n7. Ensure keywords are clear and single words\n8. Add missing connections between related ideas\n9. Update the visual layout in the graph view\n\n### Expected Outputs\n\n- Reorganized mind map\n- Cleaner structure\n\n### When to Use\n\nThis workflow is helpful when the user mentions:\n- \"organize\"\n- \"clean up\"\n- \"restructure\"\n- \"refine map\"\n";
+
+/** Raw SKILL.md content for the `summarize-map` skill. */
+export const summarizeMap = "---\nname: Summarize Mind Map\ndescription: Create a summary from the mind map content\ntype: invocable\nversion: \"1.0.0\"\n---\n\n## Summarize Mind Map\n\nCreate a summary from the mind map content\n\n### Steps\n\n1. Review the central topic and main branches\n2. Identify the key insights from each main branch\n3. Note the most important cross-connections\n4. Extract action items or decisions if applicable\n5. Write a summary paragraph for each main branch\n6. Compile into an overall summary\n7. List next steps or areas for further exploration\n\n### Expected Outputs\n\n- Written summary\n- Key insights\n- Next steps\n\n### When to Use\n\nThis workflow is helpful when the user mentions:\n- \"summarize\"\n- \"what did we learn\"\n- \"key takeaways\"\n- \"summary\"\n";
+
+/** Raw SKILL.md content for the `brainstorm-topic` skill. */
+export const brainstormTopic = "---\nname: Brainstorm Topic\ndescription: Generate ideas freely around a central topic\ntype: invocable\nversion: \"1.0.0\"\nparameters: [topic]\n---\n\n## Brainstorm Topic\n\nGenerate ideas freely around a central topic\n\n### Steps\n\n1. Place the central topic in the middle (can be a word or image)\n2. Set a timer for 5-10 minutes of free association\n3. Generate main branches (3-7 key aspects of the topic)\n4. For each main branch, add sub-ideas without filtering\n5. Use single keywords, not sentences\n6. Don't judge ideas - capture everything that comes to mind\n7. Add images or icons where they come naturally\n8. Look for unexpected connections between branches\n9. After the timer, review and identify the most promising areas\n\n### Inputs Required\n\n- **topic** (required): Central topic to brainstorm\n- **timeMinutes** (optional): Time for brainstorming\n\n### Expected Outputs\n\n- Expanded mind map\n- Key insights or themes\n\n### When to Use\n\nThis workflow is helpful when the user mentions:\n- \"brainstorm\"\n- \"generate ideas\"\n- \"explore\"\n- \"what about\"\n";
+
+/** Raw SKILL.md content for the `radiant-thinking` skill. */
+export const radiantThinking = "---\nname: radiant-thinking\ndescription: Background expertise in radial brainstorming and mind mapping techniques\ntype: background\nversion: \"1.0.0\"\n---\n\n## Radiant Thinking Expertise\n\nYou have expertise in Tony Buzan's mind mapping techniques and radiant thinking. Apply these principles when helping users brainstorm and organize ideas.\n\n### Radiant Thinking Principles\n\n**Central Concept**\n- Start with central idea\n- Use image if possible\n- Make it memorable and clear\n- Everything radiates from center\n\n**Branch Structure**\n- Main branches from center\n- Sub-branches from main\n- Organic, flowing lines\n- Thicker lines near center\n\n**One Word Per Branch**\n- Single keywords trigger more associations\n- Phrases limit thinking\n- Words generate connections\n- Keep branches lean\n\n### Mind Mapping Rules (Buzan's Laws)\n\n**Images**\n- Central image most important\n- Use images throughout\n- Color stimulates memory\n- 3+ colors recommended\n\n**Words**\n- One word per line\n- Keywords only\n- PRINT words (more memorable)\n- On top of lines\n\n**Lines**\n- Connected, flowing\n- Same length as word\n- Thinner as you go out\n- Organic, not straight\n\n**Structure**\n- Radiate from center\n- Main branches curved\n- Hierarchy clear\n- Personal style OK\n\n### Brainstorming Process\n\n**Phase 1: Free Association**\n1. Write central topic\n2. Set timer (5-10 min)\n3. No judgment\n4. Capture everything\n5. Speed over quality\n\n**Phase 2: First Organization**\n1. Identify main branches (5-7)\n2. Group related ideas\n3. Create sub-branches\n4. Note new connections\n\n**Phase 3: Refinement**\n1. Add missing branches\n2. Make connections visible\n3. Add images/colors\n4. Remove redundancy\n\n### Association Techniques\n\n**SCAMPER for Ideas**\n- Substitute\n- Combine\n- Adapt\n- Modify\n- Put to other uses\n- Eliminate\n- Reverse\n\n**Asking Questions**\n- Who? What? Where?\n- When? Why? How?\n- What if? So what?\n\n**Perspectives**\n- Different stakeholders\n- Different time frames\n- Different scales\n- Opposite viewpoints\n\n### Branch Categories\n\n**Common Main Branch Types**\n- Who (people, roles)\n- What (things, concepts)\n- When (timing, sequence)\n- Where (places, context)\n- Why (reasons, benefits)\n- How (methods, processes)\n\n**Alternative Structures**\n- Pro/Con\n- Past/Present/Future\n- Internal/External\n- Theory/Practice\n- Problem/Solution\n\n### Making Connections\n\n**Cross-Links**\n- Connect branches\n- Show relationships\n- Use arrows or dotted lines\n- Note the connection type\n\n**Patterns to Spot**\n- Repeated words\n- Related concepts\n- Contradictions\n- Gaps\n\n### Mind Map Applications\n\n**Note-Taking**\n- Lectures, meetings\n- Reading notes\n- Research capture\n\n**Planning**\n- Projects\n- Events\n- Goals\n- Writing\n\n**Problem Solving**\n- Root cause analysis\n- Solution generation\n- Decision making\n\n**Learning**\n- Study revision\n- Memory palace\n- Concept understanding\n\n### Common Mistakes\n\n**Too Much Text**\n- Phrases instead of words\n- Sentences on branches\n- Looks like outline\n\n**Linear Thinking**\n- Lists instead of maps\n- Sequential instead of radial\n- Missing cross-connections\n\n**Perfectionism**\n- Over-polishing\n- Afraid to add\n- Won't iterate\n\n### Digital vs. Paper\n\n**Paper Advantages**\n- Tactile engagement\n- Unlimited format\n- Quick sketching\n- No tech barriers\n\n**Digital Advantages**\n- Easy editing\n- Infinite space\n- Sharing/collaboration\n- Templates\n";
+
+/** Raw SKILL.md content for the `add-branch` skill. */
+export const addBranch = "---\nname: Add Branch\ndescription: Expand the mind map with a new branch and sub-ideas\ntype: invocable\nversion: \"1.0.0\"\nparameters: [branchName]\n---\n\n## Add Branch\n\nExpand the mind map with a new branch and sub-ideas\n\n### Steps\n\n1. Identify where the new idea connects (central or existing branch)\n2. Create the branch with a single keyword\n3. Choose a color for the branch (if main branch)\n4. Generate 3-5 initial sub-ideas\n5. Look for connections to other existing branches\n6. Add any relevant images or icons\n7. Create the branch file in branches/\n8. Update the knowledge graph\n\n### Inputs Required\n\n- **branchName** (required): Keyword for the new branch\n- **parentBranch** (optional): What it connects to\n\n### Expected Outputs\n\n- New branch with sub-ideas\n- Updated connections\n\n### When to Use\n\nThis workflow is helpful when the user mentions:\n- \"add branch\"\n- \"new idea\"\n- \"what about\"\n- \"let's explore\"\n";
+
+/** Raw SKILL.md content for the `branch-expansion` skill. */
+export const branchExpansion = "---\nname: branch-expansion\ndescription: Expand mind map branches with sub-ideas and associations\ntype: invocable\nversion: \"1.0.0\"\n---\n\n## Branch Expansion Skill\n\nWhen the user invokes `/expand`, help them generate sub-ideas and expand branches on their mind map.\n\n### Invocation Patterns\n\n- `/expand [branch]` - Expand specific branch\n- `/expand all` - Suggest expansions for all main branches\n- `/expand deep [branch]` - Go multiple levels deep\n- `/expand creative` - Use creative techniques for expansion\n\n### Expansion Techniques\n\n**Categorical Expansion**\n- Types/kinds of the concept\n- Components/parts\n- Examples/instances\n- Related concepts\n\n**Question-Based Expansion**\n- What are its characteristics?\n- What causes/affects it?\n- What does it cause/affect?\n- How does it work?\n- When/where does it occur?\n- Who's involved?\n\n**SCAMPER Expansion**\n- Substitute: What could replace this?\n- Combine: What could merge with this?\n- Adapt: How could this be adjusted?\n- Modify: How could this change?\n- Put to use: Other applications?\n- Eliminate: What's unnecessary?\n- Reverse: What's the opposite?\n\n### Output Format\n\n```markdown\n## Branch Expansion: [Branch Name]\n\n### Current Context\n- **Parent**: [Parent branch]\n- **Current depth**: [Level]\n- **Related branches**: [Siblings]\n\n### Suggested Sub-Branches\n\n#### Level 1 (Direct children)\n1. **[Sub-idea 1]**\n   - Relevance: [Why this belongs here]\n   - Potential sub-branches: [Quick list]\n\n2. **[Sub-idea 2]**\n   - Relevance: [Why this belongs here]\n   - Potential sub-branches: [Quick list]\n\n3. **[Sub-idea 3]**\n   - Relevance: [Why this belongs here]\n\n[Continue for 4-7 ideas]\n\n### Deeper Expansion (Level 2)\n\nFor **[Sub-idea 1]**:\n- [Sub-sub-idea 1.1]\n- [Sub-sub-idea 1.2]\n- [Sub-sub-idea 1.3]\n\nFor **[Sub-idea 2]**:\n- [Sub-sub-idea 2.1]\n- [Sub-sub-idea 2.2]\n\n### Cross-Connections\nIdeas that could link to other branches:\n- [Sub-idea X] → connects to [Other Branch]\n- [Sub-idea Y] → relates to [Another Branch]\n\n### Questions to Explore\n- [Question that could spawn more branches]\n- [Question that could spawn more branches]\n\n### Visual Suggestion\n```\n        [Sub 1.1]\n       /\n[Sub 1]──[Sub 1.2]\n      \\\n       [Sub 1.3]\n\n[BRANCH]──[Sub 2]──[Sub 2.1]\n      \\\n       [Sub 3]\n```\n```\n\n### Expansion by Branch Type\n\n**Concept Branches**\n- Definition\n- Examples\n- Counter-examples\n- Related concepts\n- Applications\n\n**Process Branches**\n- Steps/phases\n- Inputs/outputs\n- Prerequisites\n- Variations\n- Outcomes\n\n**Category Branches**\n- Types/subtypes\n- Characteristics\n- Examples\n- Boundaries\n- Exceptions\n\n**Problem Branches**\n- Causes\n- Symptoms\n- Effects\n- Solutions\n- Prevention\n\n### Creative Expansion Prompts\n\n**Random Word**\n- Pick random word\n- Force connection to branch\n- Often sparks new ideas\n\n**Role Play**\n- How would [expert] expand this?\n- What would [skeptic] add?\n- How would [child] see this?\n\n**Time Shift**\n- Past: Historical aspects\n- Present: Current state\n- Future: Possibilities\n\n**Scale Shift**\n- Zoom in: Details, components\n- Zoom out: Context, systems\n- Parallel: Analogies\n\n### When to Stop Expanding\n\n**Good Stopping Points**\n- Reached concrete/actionable level\n- Natural endpoint (no more subdivisions)\n- Diminishing returns\n- Branch balanced with others\n\n**Signs of Over-Expansion**\n- Single-idea branches\n- Repetition across branches\n- Losing sight of central topic\n- Artificial subdivisions\n\n### Balancing the Map\n\n**Check Balance**\n- Are branches similarly developed?\n- Any obvious gaps?\n- Any overloaded branches?\n\n**Rebalancing**\n- Split heavy branches\n- Merge thin branches\n- Promote important sub-branches\n- Demote tangential ideas\n";
+
+/** Raw SKILL.md content for the `kit-expertise` skill. */
+export const kitExpertise = "---\nname: kit-expertise\ndescription: Domain expertise for Mind Map - applied automatically when working in this kit\ntype: background\nversion: \"1.0.0\"\n---\n\n## Your Role\n\nMind Mapping Facilitator helping you brainstorm, organize ideas, and explore topics radiantly\n\n## Your Expertise\n\n- Mind mapping techniques\n- Radial thinking and brainstorming\n- Visual organization\n- Idea generation and expansion\n- Memory and recall enhancement\n- Note-taking strategies\n- Creative problem solving\n- Information synthesis\n\n## Your Approach\n\nWork alongside the user as a creative partner\n\n## Things to Avoid\n\n- Forcing linear structures\n- Overcomplicating branches\n- Limiting creative exploration\n- Judging ideas during brainstorming\n\n## Domain Knowledge\n\n### Key Terms\n\n**central topic**\nThe main subject at the center of the map\n\n**main branch**\nPrimary categories radiating from center\n\n**sub-branch**\nSecondary ideas branching from main branches\n\n**keyword**\nSingle word or short phrase representing an idea\n\n**radiant thinking**\nIdeas branching outward from center\n\n**association**\nNatural connection between related ideas\n\n**color coding**\nUsing colors to group related branches\n\n**image**\nVisual element enhancing memory and engagement\n\n### Best Practices\n\n- Start with a central topic or question\n- Use single keywords, not sentences\n- Branch ideas radiantly outward\n- Use colors to group related ideas\n- Add images and icons for memory\n- Let ideas flow without judgment\n\n### Common Mistakes to Avoid\n\n- Full sentences instead of keywords\n- Linear lists disguised as mind maps\n- Too many levels without organization\n- No color or visual differentiation\n- Judging ideas too early\n- Branches without clear connection to center\n";
+
+/** Raw SKILL.md content for the `find-connections` skill. */
+export const findConnections = "---\nname: Find Connections\ndescription: Discover cross-links between existing branches\ntype: invocable\nversion: \"1.0.0\"\n---\n\n## Find Connections\n\nDiscover cross-links between existing branches\n\n### Steps\n\n1. Review all main branches and their sub-ideas\n2. For each branch, ask: \"What other branches relate to this?\"\n3. Look for: similar concepts, cause-effect, part-whole, opposites\n4. Create cross-link relationships in the graph\n5. Note the nature of each connection\n6. Look for surprising connections across different areas\n7. Document any new ideas that emerge from connections\n8. Update branch files with cross-references\n\n### Expected Outputs\n\n- Cross-links between branches\n- Emergent ideas\n\n### When to Use\n\nThis workflow is helpful when the user mentions:\n- \"find connections\"\n- \"how do these connect\"\n- \"link ideas\"\n- \"relationships\"\n";
+
+/** All skills for the mind-map kit, keyed by skill ID. */
+export const allSkills: Record<string, string> = {
+	'organize-map': organizeMap,
+	'summarize-map': summarizeMap,
+	'brainstorm-topic': brainstormTopic,
+	'radiant-thinking': radiantThinking,
+	'add-branch': addBranch,
+	'branch-expansion': branchExpansion,
+	'kit-expertise': kitExpertise,
+	'find-connections': findConnections
+};

package/src/skills/music-collection/index.ts

@@ -0,0 +1,43 @@
+/**
+ * @module @soulcraft/kits/skills/music-collection
+ * @description Raw SKILL.md content for the music-collection kit's AI skills.
+ *
+ * Generated from: kits/music-collection/skills/{skillId}/SKILL.md
+ * Do not edit directly — edit the source SKILL.md files and re-run `bun run build:skills`.
+ */
+
+/** Raw SKILL.md content for the `explore-artist` skill. */
+export const exploreArtist = "---\nname: Explore Artist Deep Dive\ndescription: Learn about an artist's history, discography, and significance\ntype: invocable\nversion: \"1.0.0\"\nparameters: [artistName]\n---\n\n## Explore Artist Deep Dive\n\nLearn about an artist's history, discography, and significance\n\n### Steps\n\n1. Research the artist's background and history\n2. Outline their key albums and evolution\n3. Identify their influences and who they influenced\n4. Highlight essential albums for someone new to them\n5. Note interesting facts and context\n6. Create or update the artist profile\n\n### Inputs Required\n\n- **artistName** (required): Artist to explore\n\n### Expected Outputs\n\n- Artist profile\n- Listening roadmap\n\n### When to Use\n\nThis workflow is helpful when the user mentions:\n- \"tell me about\"\n- \"explore\"\n- \"who is\"\n- \"artist deep dive\"\n";
+
+/** Raw SKILL.md content for the `recommend-similar` skill. */
+export const recommendSimilar = "---\nname: Recommend Similar Music\ndescription: Suggest albums or artists based on your favorites\ntype: invocable\nversion: \"1.0.0\"\n---\n\n## Recommend Similar Music\n\nSuggest albums or artists based on your favorites\n\n### Steps\n\n1. Review the user's existing favorites and ratings\n2. Identify patterns in their taste (genres, eras, moods)\n3. Consider influences and connections between artists they like\n4. Suggest 3-5 albums they might not know\n5. Explain why each recommendation fits their taste\n6. Offer to add any recommendations to their discovery list\n\n### Inputs Required\n\n- **basedOn** (optional): Artist or album to base recommendations on\n\n### Expected Outputs\n\n- Recommendation list with explanations\n\n### When to Use\n\nThis workflow is helpful when the user mentions:\n- \"recommend\"\n- \"similar to\"\n- \"what else\"\n- \"if I like\"\n- \"suggest\"\n";
+
+/** Raw SKILL.md content for the `music-metadata` skill. */
+export const musicMetadata = "---\nname: music-metadata\ndescription: Background expertise in music metadata, genres, and album relationships\ntype: background\nversion: \"1.0.0\"\n---\n\n## Music Metadata Expertise\n\nYou have expertise in music cataloging, metadata standards, and genre classification. Apply these principles when helping users organize their music collections.\n\n### Core Metadata Fields\n\n**Essential Fields**\n- Artist name (primary)\n- Album title\n- Track title\n- Track number\n- Disc number (for multi-disc)\n- Year/release date\n- Genre\n\n**Extended Fields**\n- Album artist (for compilations)\n- Composer\n- Conductor (classical)\n- Record label\n- Catalog number\n- ISRC code\n- MusicBrainz IDs\n\n**Optional/Enrichment**\n- Mood/energy tags\n- BPM/tempo\n- Key signature\n- Lyrics\n- Album art\n- Credits\n\n### Artist Name Conventions\n\n**Standard Format**\n- Last, First for classical: \"Bach, Johann Sebastian\"\n- First Last for popular: \"David Bowie\"\n- Stage names as-is: \"Prince\"\n- The band: \"The Beatles\" (sort as \"Beatles, The\")\n\n**Collaborations**\n- Featured: \"Artist A feat. Artist B\"\n- Collaboration: \"Artist A & Artist B\"\n- Various: \"Various Artists\" for compilations\n\n**Consistency Rules**\n- Pick one spelling and stick to it\n- Handle special characters consistently\n- Note: \"Beyoncé\" not \"Beyonce\"\n\n### Album Types\n\n**Studio Album**\n- Original recordings\n- Primary release\n\n**Live Album**\n- Concert recordings\n- Include venue/date if known\n\n**Compilation**\n- Best of/greatest hits\n- Box sets\n- Themed collections\n\n**EP (Extended Play)**\n- 4-6 tracks typically\n- More than single, less than album\n\n**Single**\n- Primary track + B-sides\n- May include remixes\n\n**Soundtrack**\n- Film, TV, game scores\n- Note source in album title or genre\n\n**Remix Album**\n- Remixed versions of existing tracks\n\n### Genre Classification\n\n**Top-Level Genres**\n- Rock, Pop, Electronic, Hip-Hop/Rap, R&B/Soul\n- Jazz, Classical, Country, Folk, World\n- Metal, Punk, Blues, Reggae\n\n**Subgenre Specificity**\n- Be specific enough to be useful\n- \"Shoegaze\" better than just \"Rock\"\n- \"Neo-Soul\" better than just \"R&B\"\n- But don't over-specify\n\n**Multiple Genres**\n- Many systems support multiple genres\n- Order by relevance\n- \"Alternative Rock; Dream Pop\"\n\n### Genre Hierarchies\n\n**Rock Family**\n```\nRock\n├── Alternative Rock\n│   ├── Indie Rock\n│   ├── Shoegaze\n│   └── Post-Punk\n├── Classic Rock\n├── Hard Rock\n│   └── Metal (sometimes separate)\n└── Progressive Rock\n```\n\n**Electronic Family**\n```\nElectronic\n├── House\n│   ├── Deep House\n│   └── Tech House\n├── Techno\n├── Ambient\n├── Drum & Bass\n└── IDM\n```\n\n### Release Relationships\n\n**Original vs. Remaster**\n- Note remaster in album title or field\n- Keep original year, note remaster year\n- \"Kind of Blue (2020 Remaster)\"\n\n**Deluxe/Expanded Editions**\n- Treat as separate release\n- Include edition in title\n- Note bonus tracks\n\n**Regional Variations**\n- Different tracklists by country\n- Different artwork\n- Note region if relevant\n\n### Date Handling\n\n**Original Release Date**\n- When album first came out\n- Use this for sorting/organization\n\n**This Release Date**\n- When this version came out\n- Important for remasters\n\n**Recording Date**\n- When tracks were recorded\n- Important for classical, jazz, live\n\n### Classical Music Considerations\n\n**Work Information**\n- Composer (primary \"artist\")\n- Composition name\n- Opus/catalog number\n- Movement names\n\n**Performer Credits**\n- Orchestra\n- Conductor\n- Soloists\n\n**Example Format**\n- Composer: Beethoven, Ludwig van\n- Album: Symphony No. 9 in D minor, Op. 125\n- Track: IV. Presto - Allegro assai\n\n### Compilation Handling\n\n**Various Artists Albums**\n- Album artist: \"Various Artists\"\n- Track artist: Individual artists per track\n- Maintains album unity while crediting artists\n\n**Artist Best-Ofs**\n- Album artist: The artist\n- Note \"Compilation\" in album type\n- Include original album in comments if desired\n\n### Tagging Best Practices\n\n**Consistency**\n- Same artist name across all albums\n- Same genre terminology\n- Consistent date formats\n\n**Accuracy**\n- Verify against discogs/musicbrainz\n- Check spelling carefully\n- Original language for foreign artists\n\n**Completeness**\n- Fill all applicable fields\n- Don't leave blank what can be found\n- Use \"Unknown\" rather than blank if needed\n";
+
+/** Raw SKILL.md content for the `playlist-curator` skill. */
+export const playlistCurator = "---\nname: playlist-curator\ndescription: Create themed playlists from music collections with good flow and variety\ntype: invocable\nversion: \"1.0.0\"\n---\n\n## Playlist Curator Skill\n\nWhen the user invokes `/playlist`, help them create well-curated playlists with good flow, variety, and thematic coherence.\n\n### Invocation Patterns\n\n- `/playlist [theme]` - Create themed playlist\n- `/playlist mood [mood]` - Mood-based playlist\n- `/playlist mix` - Balanced variety playlist\n- `/playlist [event]` - Event-specific playlist\n\n### Playlist Curation Principles\n\n**Flow & Pacing**\n- Energy arc (build up, peak, cool down)\n- Tempo progression\n- Key compatibility (optional, for seamless mixes)\n- Avoid jarring transitions\n\n**Variety Within Theme**\n- Different artists\n- Different eras/decades\n- Different subgenres\n- Different tempos\n\n**Cohesion**\n- Unified mood or theme\n- Consistent sound palette\n- Logical sequencing\n\n### Output Format\n\n```markdown\n## Playlist: [Title]\n\n### Concept\n- **Theme**: [Description]\n- **Mood**: [Energy/feeling]\n- **Duration**: [Total time]\n- **Best for**: [Use case]\n\n### Track List\n\n| # | Track | Artist | Album | BPM | Energy | Notes |\n|---|-------|--------|-------|-----|--------|-------|\n| 1 | [Track] | [Artist] | [Album] | [BPM] | [1-5] | Opener |\n| 2 | [Track] | [Artist] | [Album] | [BPM] | [1-5] | |\n| 3 | [Track] | [Artist] | [Album] | [BPM] | [1-5] | |\n...\n| N | [Track] | [Artist] | [Album] | [BPM] | [1-5] | Closer |\n\n### Playlist Arc\n```\nEnergy\n  ▲\n5 │       ●●●\n4 │     ●     ●●\n3 │   ●         ●●\n2 │ ●              ●\n1 │●                ●\n  └─────────────────────→ Time\n   Opening  Peak  Cooldown\n```\n\n### Flow Notes\n- Tracks 1-3: [Description of opening]\n- Tracks 4-7: [Building energy]\n- Tracks 8-12: [Peak energy]\n- Tracks 13-15: [Winding down]\n\n### Key Transitions\n- Track 3→4: [Why this works]\n- Track 8→9: [Why this works]\n\n### Variety Check\n- Artists: [X] unique artists\n- Decades: [Spread]\n- Subgenres: [List]\n\n### Alternative Tracks\nIf [track] isn't available:\n- Try: [Alternative 1]\n- Or: [Alternative 2]\n```\n\n### Playlist Types\n\n**Mood Playlists**\n- Chill/Relaxation\n- Energy/Workout\n- Focus/Study\n- Sad/Melancholy\n- Happy/Upbeat\n- Romantic\n\n**Activity Playlists**\n- Morning routine\n- Dinner party\n- Road trip\n- Cooking\n- Cleaning\n- Work from home\n\n**Theme Playlists**\n- Decade-specific (80s, 90s, etc.)\n- Genre deep-dive\n- Artist appreciation\n- Seasonal (summer, winter)\n- Event (wedding, birthday)\n\n### Playlist Length Guidelines\n\n| Use Case | Tracks | Duration |\n|----------|--------|----------|\n| Quick listen | 8-12 | 30-45 min |\n| Background | 20-30 | 1.5-2 hrs |\n| Event | 40-60 | 3-4 hrs |\n| Extensive | 100+ | 6+ hrs |\n\n### Sequencing Techniques\n\n**Energy Management**\n1. Start medium energy (welcoming)\n2. Build gradually\n3. Peak in middle third\n4. Provide valleys for contrast\n5. End with memorable closer\n\n**The DJ Approach**\n- Match BPMs for flow (±10 BPM)\n- Complementary keys\n- Similar energy adjacent\n- Gradual transitions\n\n**The Storytelling Approach**\n- Opening sets scene\n- Middle develops themes\n- Climax delivers payoff\n- Denouement resolves\n\n### Avoiding Common Mistakes\n\n**Don't**\n- Put all high-energy tracks together\n- Repeat same artist consecutively\n- Ignore song length variety\n- End with a dud\n- Forget about transitions\n\n**Do**\n- Create intentional contrast\n- Space out similar sounds\n- Include unexpected choices\n- End memorably\n- Listen through completely\n\n### Event-Specific Tips\n\n**Dinner Party**\n- Background level energy\n- No sudden loud tracks\n- Avoid controversial lyrics\n- 3-4 hours of music\n\n**Workout**\n- High energy throughout\n- Build to peak at hardest part\n- 130-150 BPM range\n- Clear beats\n\n**Focus/Study**\n- No or minimal lyrics\n- Consistent energy\n- Ambient or lo-fi works well\n- Long enough to not repeat\n";
+
+/** Raw SKILL.md content for the `journal-session` skill. */
+export const journalSession = "---\nname: Log Listening Session\ndescription: Record a listening session in your journal\ntype: invocable\nversion: \"1.0.0\"\nparameters: [album]\n---\n\n## Log Listening Session\n\nRecord a listening session in your journal\n\n### Steps\n\n1. Ask what was listened to\n2. Ask about the format and context\n3. Ask about mood before and after\n4. Record any notable thoughts or discoveries\n5. Add entry to listening journal\n6. Update any relevant album or artist notes\n\n### Inputs Required\n\n- **album** (required): What you listened to\n\n### Expected Outputs\n\n- Journal entry\n\n### When to Use\n\nThis workflow is helpful when the user mentions:\n- \"log listening\"\n- \"just listened\"\n- \"listening session\"\n- \"add to journal\"\n\n### Execution Mode\n\nThis workflow can be executed automatically when triggered. Proceed through the steps without waiting for confirmation at each step.\n";
+
+/** Raw SKILL.md content for the `add-album` skill. */
+export const addAlbum = "---\nname: Add Album to Collection\ndescription: Document a new album in your collection\ntype: invocable\nversion: \"1.0.0\"\nparameters: [albumName, artistName]\n---\n\n## Add Album to Collection\n\nDocument a new album in your collection\n\n### Steps\n\n1. Ask for the album name and artist\n2. Look up key details (year, genre, label)\n3. Create the album file from template\n4. Add the artist if not already in collection\n5. Create album and artist concepts in graph\n6. Link album to artist and genres\n7. Ask for personal rating and notes\n\n### Inputs Required\n\n- **albumName** (required): Album title\n- **artistName** (required): Artist name\n\n### Expected Outputs\n\n- Album file\n- Artist file (if new)\n- Graph concepts and relationships\n\n### When to Use\n\nThis workflow is helpful when the user mentions:\n- \"add album\"\n- \"new album\"\n- \"just got\"\n- \"picked up\"\n\n### Execution Mode\n\nThis workflow can be executed automatically when triggered. Proceed through the steps without waiting for confirmation at each step.\n";
+
+/** Raw SKILL.md content for the `kit-expertise` skill. */
+export const kitExpertise = "---\nname: kit-expertise\ndescription: Domain expertise for Music Collection Manager - applied automatically when working in this kit\ntype: background\nversion: \"1.0.0\"\n---\n\n## Your Role\n\nYou are a passionate music curator and historian with deep knowledge across genres, eras, and scenes. You help music lovers organize their collections, discover new artists, understand musical connections, and deepen their appreciation. You respect personal taste while offering educated perspectives and hidden gems.\n\n## Your Expertise\n\n- music history and genre evolution\n- artist discographies and key albums\n- musical influences and connections\n- vinyl collecting and formats\n- playlist curation and mood mapping\n- music theory basics\n- scene and era context\n- album art and packaging\n\n## Your Approach\n\nWork alongside the user as a creative partner\n\n## Things to Avoid\n\n- Never dismiss someone's taste - all music preferences are valid\n- Don't be a music snob - appreciate mainstream and obscure equally\n- Avoid spoiling the discovery experience - guide rather than lecture\n- Don't reduce music to just technical analysis - emotion matters\n\n## Domain Knowledge\n\n### Key Terms\n\n**LP**\nLong Play - a full-length vinyl album, typically 33⅓ RPM\n\n**EP**\nExtended Play - shorter than an album, longer than a single\n\n**B-side**\nThe secondary song on a single, often a hidden gem\n\n**bootleg**\nUnofficial recording, often live performances\n\n**concept album**\nAn album with songs unified by a theme or narrative\n\n**deep cut**\nA non-single album track beloved by dedicated fans\n\n**discography**\nThe complete catalog of an artist's recordings\n\n**pressing**\nA specific manufacturing run of a vinyl record\n\n**remaster**\nA new mix from original recordings, often improved audio\n\n**side A/B**\nThe two sides of a vinyl record\n\n**liner notes**\nWritten material included with an album\n\n**gatefold**\nAn album cover that opens like a book\n\n### Best Practices\n\n- Albums are typically rated on a 5-star scale or out of 10\n- Vinyl condition grading: Mint, Near Mint, VG+, VG, Good, Fair, Poor\n- First pressings are generally more valuable to collectors\n- Listening to albums in full, in order, reveals artistic intent\n- Context matters - understand when and where music was created\n- Live versions often reveal new dimensions of songs\n- Explore an artist's influences to understand their sound\n\n### Common Mistakes to Avoid\n\n- Judging music without giving it a proper listen\n- Only listening to singles and ignoring album tracks\n- Dismissing genres you haven't explored\n- Letting algorithms completely control your discovery\n- Forgetting to revisit albums after they've had time to grow\n- Not noting when and how you discovered music\n\n### Recommended References\n\n- [AllMusic](https://www.allmusic.com): Comprehensive music database with reviews and credits\n- [Discogs](https://www.discogs.com): Music database and marketplace for collectors\n- [Rate Your Music](https://rateyourmusic.com): Community-driven music database and charts\n- [Bandcamp](https://bandcamp.com): Artist-direct music platform for discovery\n";
+
+/** Raw SKILL.md content for the `create-playlist` skill. */
+export const createPlaylist = "---\nname: Create Themed Playlist\ndescription: Build a playlist around a mood, activity, or theme\ntype: invocable\nversion: \"1.0.0\"\nparameters: [theme]\n---\n\n## Create Themed Playlist\n\nBuild a playlist around a mood, activity, or theme\n\n### Steps\n\n1. Ask about the playlist purpose (mood, activity, theme)\n2. Review the user's collection for fitting tracks\n3. Suggest tracks that fit the theme\n4. Consider flow and pacing between tracks\n5. Create the playlist file\n6. Add playlist concept to graph\n\n### Inputs Required\n\n- **theme** (required): Playlist theme, mood, or purpose\n\n### Expected Outputs\n\n- Playlist file\n- Playlist concept\n\n### When to Use\n\nThis workflow is helpful when the user mentions:\n- \"create playlist\"\n- \"make a playlist\"\n- \"songs for\"\n- \"music for\"\n";
+
+/** All skills for the music-collection kit, keyed by skill ID. */
+export const allSkills: Record<string, string> = {
+	'explore-artist': exploreArtist,
+	'recommend-similar': recommendSimilar,
+	'music-metadata': musicMetadata,
+	'playlist-curator': playlistCurator,
+	'journal-session': journalSession,
+	'add-album': addAlbum,
+	'kit-expertise': kitExpertise,
+	'create-playlist': createPlaylist
+};

package/src/skills/novel-writing-system/index.ts

@@ -0,0 +1,47 @@
+/**
+ * @module @soulcraft/kits/skills/novel-writing-system
+ * @description Raw SKILL.md content for the novel-writing-system kit's AI skills.
+ *
+ * Generated from: kits/novel-writing-system/skills/{skillId}/SKILL.md
+ * Do not edit directly — edit the source SKILL.md files and re-run `bun run build:skills`.
+ */
+
+/** Raw SKILL.md content for the `character-arc` skill. */
+export const characterArc = "---\nname: character-arc\ndescription: Develop compelling character arcs using the want/need/lie/ghost/truth framework. Use /character to build or analyze a character's internal journey.\ntype: invocable\nversion: \"1.0.0\"\nparameters: [character name or description]\n---\n\n## Character Arc Development\n\nHelp writers create deep, believable character arcs using established frameworks from story theory.\n\n### When User Invokes /character\n\nGuide them through the character arc framework:\n\n### The Core Framework\n\nEvery compelling character arc contains these five elements:\n\n| Element | Definition | Question to Answer |\n|---------|------------|-------------------|\n| **Want** | External goal the character pursues | What does your character think they need? |\n| **Need** | Internal truth they must learn | What do they actually need to be whole? |\n| **Lie** | False belief holding them back | What misconception guides their actions? |\n| **Ghost** | Past wound that created the lie | What happened to make them believe the lie? |\n| **Truth** | Realization that completes the arc | What must they learn to overcome the lie? |\n\n### Character Arc Worksheet\n\nGenerate this worksheet for each major character:\n\n```markdown\n# Character Arc: [CHARACTER NAME]\n\n## The Wound (Ghost)\n**What happened:** [Traumatic or formative event from the past]\n**When it happened:** [Age/timeframe]\n**Who was involved:** [Key people]\n**What they lost:** [Trust, innocence, love, security, etc.]\n\n## The Lie They Believe\n**Core belief:** \"[State the lie as the character would]\"\n**How it manifests:**\n- In relationships: [How the lie affects connections]\n- In decisions: [How the lie influences choices]\n- In self-perception: [How they see themselves through the lie]\n\n## The Want (External Goal)\n**Concrete goal:** [Specific, measurable objective]\n**Why they think this will help:** [How achieving this would validate the lie]\n**Stakes if they fail:** [What they lose without it]\n\n## The Need (Internal Growth)\n**True need:** [What would actually make them whole]\n**Why they resist it:** [How the need threatens the lie]\n**Cost of embracing it:** [What they must give up]\n\n## The Truth\n**What they learn:** [The realization that defeats the lie]\n**How they prove it:** [Action that demonstrates growth]\n**New identity:** [Who they become after accepting the truth]\n```\n\n### Arc Patterns\n\n**Positive Arc (Change)**\n1. Character believes the Lie\n2. Events challenge the Lie\n3. Character resists the Truth\n4. Crisis forces a choice\n5. Character embraces Truth and achieves Need\n6. External Want may or may not be achieved\n\n**Flat Arc (Testing)**\n1. Character already knows the Truth\n2. World around them believes Lies\n3. Character's Truth is tested\n4. They influence others to see the Truth\n5. World changes, character stays constant\n\n**Negative Arc (Fall)**\n1. Character believes partial Truth\n2. Events pull them toward a Lie\n3. Character resists, then accepts the Lie\n4. They achieve corrupted Want\n5. End in worse state than beginning\n\n### Character Arc Beats\n\nMap the arc across your story structure:\n\n| Story Beat | Arc Function |\n|------------|--------------|\n| **Opening** | Show the Lie in action |\n| **Inciting Incident** | Introduce what challenges the Lie |\n| **First Plot Point** | Character commits while holding the Lie |\n| **First Pinch Point** | Lie causes problems |\n| **Midpoint** | Glimpse of the Truth |\n| **Second Pinch Point** | Cost of the Lie escalates |\n| **All Is Lost** | Lie fully exposed |\n| **Dark Night** | Must choose: Lie or Truth |\n| **Climax** | Live out their choice |\n| **Resolution** | New normal based on growth |\n\n### Common Arc Problems\n\n**Shallow Arc**\n- Problem: Character changes too easily\n- Fix: Strengthen the Ghost and the reasons for the Lie\n\n**Sudden Change**\n- Problem: Transformation feels unearned\n- Fix: Add more moments where the Truth challenges the Lie\n\n**Passive Arc**\n- Problem: Things happen TO the character\n- Fix: Make their choices drive the plot\n\n**No Stakes**\n- Problem: Growth doesn't seem important\n- Fix: Show the real cost of the Lie and Need\n\n### Example Character Arc\n\n```markdown\n# Character Arc: MARCUS (Protagonist)\n\n## The Wound (Ghost)\n**What happened:** Father abandoned family when Marcus was 12\n**When it happened:** Age 12, day before his birthday\n**Who was involved:** Father, younger sister he had to protect\n**What they lost:** Belief that people stay\n\n## The Lie They Believe\n**Core belief:** \"If I need anyone, they'll leave. I can only rely on myself.\"\n**How it manifests:**\n- In relationships: Keeps people at arm's length, sabotages intimacy\n- In decisions: Refuses help even when drowning\n- In self-perception: Sees needing others as weakness\n\n## The Want (External Goal)\n**Concrete goal:** Build his business empire alone\n**Why they think this will help:** Proves he doesn't need anyone\n**Stakes if they fail:** Would have to admit the Lie is wrong\n\n## The Need (Internal Growth)\n**True need:** Learn to trust and accept help\n**Why they resist it:** Trusting = vulnerability = abandonment\n**Cost of embracing it:** Must risk being hurt again\n\n## The Truth\n**What they learn:** Strength isn't isolation; it's choosing to trust despite fear\n**How they prove it:** Accepts his partner's help to save the company\n**New identity:** A leader who builds WITH others, not despite them\n```\n\n### Questions for Deep Character Work\n\n1. **Want vs Need Conflict**: How does pursuing the Want make achieving the Need harder?\n2. **Ghost Echoes**: Where in your plot does the original wound echo?\n3. **Lie Validation**: How does the world seem to confirm the character's Lie?\n4. **Truth Resistance**: Why is the Truth more terrifying than the Lie?\n5. **Change Cost**: What must the character sacrifice to grow?\n";
+
+/** Raw SKILL.md content for the `plot-doctor` skill. */
+export const plotDoctor = "---\nname: plot-doctor\ndescription: Diagnose and fix plot problems including holes, pacing issues, and structural weaknesses. Use /plot-check to analyze your plot for common issues.\ntype: invocable\nversion: \"1.0.0\"\nparameters: [plot summary or specific scene/chapter]\n---\n\n## Plot Doctor\n\nAnalyze plots for structural integrity, identify problems, and prescribe fixes.\n\n### When User Invokes /plot-check\n\nPerform a systematic plot analysis:\n\n### Plot Health Assessment\n\nEvaluate the plot across these dimensions:\n\n| Dimension | What to Check | Red Flags |\n|-----------|---------------|-----------|\n| **Causality** | Do events cause each other? | \"And then\" instead of \"therefore\" |\n| **Stakes** | Does failure matter? | Nothing bad happens if hero fails |\n| **Agency** | Does protagonist drive plot? | Things happen TO them, not because of them |\n| **Escalation** | Do problems get harder? | Flat difficulty curve |\n| **Logic** | Do character choices make sense? | \"Idiot plot\" problems |\n| **Pacing** | Does story move appropriately? | Sagging middles, rushed endings |\n\n### The Causality Test\n\nEvery scene should connect via:\n- \"Because of this, that happens\" (cause → effect)\n- \"Therefore, they do this\" (action → consequence)\n\n**Test:** Remove any scene. Does the story still work?\n- If YES: The scene doesn't advance plot (may still be needed for character)\n- If NO: The scene is causally connected\n\n### Plot Hole Categories\n\n**Logic Holes**\n- Characters make inexplicable choices\n- Solutions ignore obvious alternatives\n- Rules of the world are violated\n- Information characters have is forgotten\n\n**Continuity Holes**\n- Timeline inconsistencies\n- Character knowledge errors\n- Physical impossibilities\n- Contradicted earlier events\n\n**Motivation Holes**\n- Why doesn't the character just...?\n- Why doesn't the villain just...?\n- What does the character actually want?\n- Why do they care?\n\n### Common Plot Problems & Fixes\n\n#### Problem: The Idiot Plot\nCharacters only suffer because they don't do obvious things.\n\n**Symptoms:**\n- \"Why didn't they just call the police?\"\n- Characters withhold information for no reason\n- Obvious solutions are ignored\n\n**Fixes:**\n- Establish why obvious solutions don't work\n- Give characters reasons for their choices\n- Remove the obvious option (phone dead, police corrupt, etc.)\n\n#### Problem: Coincidence\nPlot depends on lucky timing or chance meetings.\n\n**Symptoms:**\n- Character happens to be in the right place\n- Needed information arrives conveniently\n- Villain makes inexplicable mistakes\n\n**Fixes:**\n- Move coincidences earlier (setup, not payoff)\n- Have characters create their \"luck\" through effort\n- Give villains logical reasons for their actions\n\n#### Problem: Deus Ex Machina\nSolutions appear from nowhere.\n\n**Symptoms:**\n- New character/power saves the day\n- Previously unmentioned abilities\n- Cavalry arrives unexpectedly\n\n**Fixes:**\n- Plant seeds for the solution earlier (Chekhov's gun)\n- Have the protagonist earn the solution\n- Foreshadow the rescue possibility\n\n#### Problem: Sagging Middle\nStory loses momentum between setup and climax.\n\n**Symptoms:**\n- Reader skims or stops reading\n- \"Nothing happens\" feeling\n- Subplots feel disconnected\n\n**Fixes:**\n- Add a midpoint reversal\n- Raise stakes or add complications\n- Connect subplots to main plot\n- Ensure every scene has goal/conflict/disaster\n\n#### Problem: Rushed Ending\nClimax and resolution feel too fast.\n\n**Symptoms:**\n- Buildup exceeds payoff\n- Major questions answered quickly\n- Character arcs snap into place\n\n**Fixes:**\n- Give the climax appropriate page time\n- Let consequences unfold gradually\n- Show, don't summarize, resolution\n\n#### Problem: Meandering Plot\nStory lacks clear direction.\n\n**Symptoms:**\n- Hard to state what the story is about\n- Goals shift without resolution\n- Multiple false starts\n\n**Fixes:**\n- Clarify the central dramatic question\n- Give protagonist a concrete goal\n- Ensure subplots connect to main throughline\n\n### Plot Analysis Template\n\n```markdown\n## Plot Analysis: [TITLE]\n\n### Central Dramatic Question\n[What must be resolved for the story to end?]\n\n### Protagonist Goal\n- **External:** [What they're trying to achieve]\n- **Internal:** [What they need to learn/become]\n\n### Main Conflict\n- **Antagonist/Opposition:** [What's stopping them]\n- **Why it's hard:** [Stakes and obstacles]\n\n### Key Plot Points\n1. **Hook:** [Why reader cares from page 1]\n2. **Inciting Incident:** [What disrupts the status quo]\n3. **First Plot Point:** [Point of no return]\n4. **Midpoint:** [Major reversal or revelation]\n5. **Dark Moment:** [All seems lost]\n6. **Climax:** [Final confrontation with conflict]\n7. **Resolution:** [New equilibrium]\n\n### Identified Issues\n1. [Issue]: [Location] → [Suggested Fix]\n2. [Issue]: [Location] → [Suggested Fix]\n\n### Overall Assessment\n- Causality: [Strong/Moderate/Weak]\n- Stakes: [High/Medium/Low]\n- Pacing: [Fast/Balanced/Slow/Uneven]\n- Logic: [Sound/Minor Issues/Major Holes]\n```\n\n### Quick Diagnostic Questions\n\n1. **Can you state the central conflict in one sentence?**\n   - No → Clarify your premise\n\n2. **What does the protagonist want on page 1 vs page 300?**\n   - Same thing → Ensure wants evolve\n   - Can't tell → Clarify goals\n\n3. **What's the worst that could happen if the protagonist fails?**\n   - \"Nothing much\" → Raise stakes\n   - \"I don't know\" → Define stakes\n\n4. **Why doesn't the villain just win immediately?**\n   - \"Because plot\" → Strengthen hero's agency\n   - \"Good question\" → Fix power balance\n\n5. **What does your protagonist DO to solve the problem?**\n   - \"Gets saved by others\" → Give them agency\n   - \"Gets lucky\" → Earn the victory\n\n### Prescription Format\n\nWhen diagnosing issues, provide:\n\n```markdown\n## Diagnosis: [Issue Name]\n\n**Location:** [Where in the story]\n**Severity:** [Critical/Major/Minor]\n\n**Symptoms:**\n- [What feels wrong]\n\n**Root Cause:**\n- [Why it's happening]\n\n**Prescription:**\n- [Specific fix 1]\n- [Specific fix 2]\n- [Alternative approach]\n\n**Example Implementation:**\n[Brief example of the fix in action]\n```\n";
+
+/** Raw SKILL.md content for the `develop-character-arc` skill. */
+export const developCharacterArc = "---\nname: Develop Character Arc\ndescription: Deep dive into a character's psychology, motivation, and transformation\ntype: invocable\nversion: \"1.0.0\"\nparameters: [characterName]\n---\n\n## Develop Character Arc\n\nDeep dive into a character's psychology, motivation, and transformation\n\n### Steps\n\n1. Review the existing character file\n2. Ask about the character's WANT (conscious external goal)\n3. Ask about the character's NEED (unconscious internal goal)\n4. Identify THE LIE the character believes at the beginning\n5. Explore the GHOST/WOUND - what backstory trauma created this lie?\n6. Define the character's strengths and flaws\n7. Map their arc: Beginning state → Midpoint shift → End transformation\n8. Identify the key scenes where change happens\n9. Update the character file with these insights\n\n### Inputs Required\n\n- **characterName** (required): Which character to develop\n\n### Expected Outputs\n\n- Updated character file\n- Character arc summary\n\n### When to Use\n\nThis workflow is helpful when the user mentions:\n- \"develop character\"\n- \"character arc\"\n- \"motivation\"\n- \"backstory\"\n- \"who is\"\n- \"character change\"\n";
+
+/** Raw SKILL.md content for the `worldbuilding-session` skill. */
+export const worldbuildingSession = "---\nname: Worldbuilding Session\ndescription: Systematic exploration and development of the story world\ntype: invocable\nversion: \"1.0.0\"\n---\n\n## Worldbuilding Session\n\nSystematic exploration and development of the story world\n\n### Steps\n\n1. Review existing worldbuilding notes\n2. Ask about the geography and physical environment\n3. Explore the social structure and power systems\n4. Define cultural elements: customs, beliefs, values\n5. If applicable, establish magic/technology rules and limitations\n6. Identify how the world affects the protagonist's journey\n7. Check for internal consistency\n8. Update relevant worldbuilding files\n\n### Inputs Required\n\n- **aspect** (optional): Specific aspect to develop (optional)\n\n### Expected Outputs\n\n- Updated worldbuilding files\n- Consistency notes\n\n### When to Use\n\nThis workflow is helpful when the user mentions:\n- \"worldbuilding\"\n- \"world\"\n- \"setting\"\n- \"magic system\"\n- \"culture\"\n- \"society\"\n";
+
+/** Raw SKILL.md content for the `plot-hole-check` skill. */
+export const plotHoleCheck = "---\nname: Plot Hole Check\ndescription: Systematic review for logical inconsistencies and plot holes\ntype: invocable\nversion: \"1.0.0\"\n---\n\n## Plot Hole Check\n\nSystematic review for logical inconsistencies and plot holes\n\n### Steps\n\n1. Review the outline and timeline\n2. Check character motivations - do actions make sense?\n3. Verify timeline consistency - do events flow logically?\n4. Review cause and effect - does each event have proper setup?\n5. Check for convenient coincidences that solve problems\n6. Verify worldbuilding rules are consistently followed\n7. Look for dropped plot threads or abandoned setups\n8. Document any issues found with suggested fixes\n\n### Expected Outputs\n\n- List of potential issues\n- Suggested fixes\n\n### When to Use\n\nThis workflow is helpful when the user mentions:\n- \"plot hole\"\n- \"consistency\"\n- \"check logic\"\n- \"does this make sense\"\n- \"review plot\"\n";
+
+/** Raw SKILL.md content for the `kit-expertise` skill. */
+export const kitExpertise = "---\nname: kit-expertise\ndescription: Domain expertise for Novel Writing System - applied automatically when working in this kit\ntype: background\nversion: \"1.0.0\"\n---\n\n## Your Role\n\nNovel Writing Coach and Story Architect helping you craft compelling long-form fiction from concept to completion\n\n## Your Expertise\n\n- Three-act story structure and plot development\n- Character arc design (want, need, lie, ghost, truth)\n- Worldbuilding and setting consistency\n- Pacing and chapter structure\n- Dialogue and voice\n- Scene and sequel technique\n- Genre conventions and reader expectations\n- Revision and editing strategies\n\n## Your Approach\n\nGuide and teach the user, helping them understand concepts deeply\n\n## Things to Avoid\n\n- Writing the story for the user\n- Being prescriptive about creative choices\n- Spoiling plot points before the user reveals them\n- Suggesting formulaic solutions without context\n\n## Domain Knowledge\n\n### Key Terms\n\n**three-act structure**\nStory framework: Setup (Act 1), Confrontation (Act 2), Resolution (Act 3)\n\n**inciting incident**\nThe event that launches the protagonist into the story\n\n**midpoint**\nMajor shift at the story's center that raises stakes\n\n**dark night of the soul**\nProtagonist's lowest point before the climax\n\n**character want**\nWhat the character consciously desires\n\n**character need**\nWhat the character actually requires for growth\n\n**character ghost**\nPast trauma that shapes the character's lie\n\n**character lie**\nFalse belief the character holds about themselves or the world\n\n**scene**\nUnit of story with goal, conflict, disaster\n\n**sequel**\nCharacter's reaction: emotion, thought, decision, action\n\n### Best Practices\n\n- Hook the reader in the opening pages\n- Show character through action and choice\n- Every scene should advance plot or develop character\n- Subplots should echo or contrast the main theme\n- Endings should be surprising yet inevitable\n- Maintain consistent POV within scenes\n\n### Common Mistakes to Avoid\n\n- Info dumps and excessive exposition\n- Coincidences that solve problems\n- Passive protagonists who react but don't act\n- Deus ex machina resolutions\n- Characters who all sound the same\n- Telling emotions instead of showing them\n";
+
+/** Raw SKILL.md content for the `outline-review` skill. */
+export const outlineReview = "---\nname: Review Outline\ndescription: Analyze the story outline for structure and pacing\ntype: invocable\nversion: \"1.0.0\"\n---\n\n## Review Outline\n\nAnalyze the story outline for structure and pacing\n\n### Steps\n\n1. Read through the complete outline\n2. Check that all major beats are present and placed correctly\n3. Evaluate the inciting incident - does it happen early enough?\n4. Assess the midpoint - is there a clear shift?\n5. Review the \"all is lost\" moment - is it impactful?\n6. Check pacing - are there slow spots or rushed sections?\n7. Verify the ending resolves the central conflict\n8. Provide specific recommendations\n\n### Expected Outputs\n\n- Outline analysis\n- Structural recommendations\n\n### When to Use\n\nThis workflow is helpful when the user mentions:\n- \"review outline\"\n- \"check structure\"\n- \"is my outline good\"\n- \"pacing help\"\n";
+
+/** Raw SKILL.md content for the `scene-sequel` skill. */
+export const sceneSequel = "---\nname: scene-sequel\ndescription: Apply the Scene and Sequel technique for effective narrative pacing. Scenes drive action, Sequels provide reaction and decision. Applied automatically when writing or reviewing narrative prose.\ntype: background\nversion: \"1.0.0\"\n---\n\n## Scene and Sequel Technique\n\nYou are an expert in the Scene and Sequel technique developed by Dwight V. Swain. Apply this framework when helping with novel pacing and structure.\n\n### The Scene-Sequel Pattern\n\nStories alternate between two types of units:\n\n**SCENE** (Action)\n- Goal: What the POV character wants\n- Conflict: What opposes them\n- Disaster: How things go wrong (or unexpectedly right)\n\n**SEQUEL** (Reaction)\n- Reaction: Emotional response to the disaster\n- Dilemma: The impossible choice they face\n- Decision: What they choose to do next (leads to new Scene)\n\n### Scene Structure\n\nEvery Scene needs these three elements in order:\n\n```\n1. GOAL\n   - Stated early and clearly\n   - Specific and concrete\n   - Reader knows when it's achieved or not\n\n2. CONFLICT\n   - Something opposes the goal\n   - Escalating obstacles\n   - Character must struggle\n\n3. DISASTER (Outcome)\n   - Yes, but... (achieves goal, new problem)\n   - No, and... (fails, things get worse)\n   - Rarely: pure success (only for setup)\n```\n\n### Sequel Structure\n\nEvery Sequel follows this emotional logic:\n\n```\n1. REACTION\n   - Visceral emotional response\n   - Can't think clearly yet\n   - Show, don't tell the feelings\n\n2. DILEMMA\n   - Character processes options\n   - No good choices visible\n   - Weighs costs and risks\n\n3. DECISION\n   - Commits to a course of action\n   - Becomes the GOAL of the next Scene\n   - Reader understands the why\n```\n\n### Pacing Through Scene-Sequel Ratio\n\n| Desired Pace | Scene:Sequel | Effect |\n|--------------|--------------|--------|\n| **Fast/Thriller** | Long Scene, Short Sequel | Action-driven, breathless |\n| **Balanced** | Equal | Literary fiction feel |\n| **Slow/Literary** | Short Scene, Long Sequel | Character-driven, contemplative |\n| **Breakneck** | Scene only, skip Sequels | Crisis chapters, climax |\n\n### When to Compress or Expand\n\n**Compress Sequels when:**\n- Action is intense\n- Reader already knows the emotional beat\n- Pacing needs to accelerate\n- Character's decision is obvious\n\n**Expand Sequels when:**\n- Major turning point\n- Character growth moment\n- Reader needs to process alongside character\n- Building toward important decision\n\n### Scene Types\n\n**Proactive Scene**\n- Character initiates action\n- Has a plan\n- Shows agency\n\n**Reactive Scene**\n- Character responds to events\n- Improvising\n- Shows adaptability\n\n**Both need Goal → Conflict → Disaster**\n\n### Common Problems and Fixes\n\n**Problem: Sagging middle**\nFix: Check if Sequels are too long or Scenes lack clear disasters\n\n**Problem: Feels rushed**\nFix: Add Sequel beats, especially Reaction and Dilemma\n\n**Problem: Character seems passive**\nFix: Strengthen Goals and Decisions\n\n**Problem: Reader loses track**\nFix: Make Goals more concrete and specific\n\n### Scene-Sequel Checklist\n\nWhen reviewing narrative, verify:\n\n**For Scenes:**\n- [ ] POV character has a clear, stated goal\n- [ ] Something actively opposes them\n- [ ] Outcome changes the situation (disaster or unexpected success)\n- [ ] Reader could articulate the goal if asked\n\n**For Sequels:**\n- [ ] Character has time to feel before thinking\n- [ ] Options are genuinely difficult\n- [ ] Decision follows logically from character\n- [ ] New goal emerges for next scene\n\n### Example Pattern\n\n```\nSCENE 1\n- Goal: Sarah wants to confront her boss about the stolen credit\n- Conflict: Boss deflects, gaslights, threatens her job\n- Disaster: Sarah is put on \"performance review\" instead\n\nSEQUEL 1\n- Reaction: Sarah sits in her car, shaking, near tears\n- Dilemma: Accept it and keep her job? Fight and risk everything?\n- Decision: She'll gather evidence quietly, then go to HR\n\nSCENE 2\n- Goal: Sarah needs to access the project files for proof\n- Conflict: Files are locked, IT is suspicious, time is short\n- Disaster: She gets the files but her access triggers an alert\n\n[Pattern continues...]\n```\n\n### Applying to Different Genres\n\n**Romance:** Sequels explore emotional processing, relationships\n**Thriller:** Short Sequels, disasters escalate rapidly\n**Mystery:** Scenes gather clues, Sequels analyze them\n**Fantasy:** Balance world-building in Sequels with action in Scenes\n**Literary:** Longer Sequels with deeper introspection\n";
+
+/** Raw SKILL.md content for the `scene-development` skill. */
+export const sceneDevelopment = "---\nname: Scene Development\ndescription: Develop a scene with proper structure and purpose\ntype: invocable\nversion: \"1.0.0\"\nparameters: [sceneDescription]\n---\n\n## Scene Development\n\nDevelop a scene with proper structure and purpose\n\n### Steps\n\n1. Ask about the scene's purpose in the story\n2. Identify the POV character and their goal in this scene\n3. Define the conflict - what obstacle do they face?\n4. Plan the emotional arc of the scene\n5. Consider sensory details for the setting\n6. Draft key dialogue beats\n7. Determine how the scene ends - hook for next scene\n8. Create or update the scene file\n\n### Inputs Required\n\n- **sceneDescription** (required): Brief description of the scene\n\n### Expected Outputs\n\n- Scene notes or draft\n\n### When to Use\n\nThis workflow is helpful when the user mentions:\n- \"write scene\"\n- \"develop scene\"\n- \"new scene\"\n- \"scene help\"\n";
+
+/** All skills for the novel-writing-system kit, keyed by skill ID. */
+export const allSkills: Record<string, string> = {
+	'character-arc': characterArc,
+	'plot-doctor': plotDoctor,
+	'develop-character-arc': developCharacterArc,
+	'worldbuilding-session': worldbuildingSession,
+	'plot-hole-check': plotHoleCheck,
+	'kit-expertise': kitExpertise,
+	'outline-review': outlineReview,
+	'scene-sequel': sceneSequel,
+	'scene-development': sceneDevelopment
+};

package/src/skills/organization-chart/index.ts

@@ -0,0 +1,43 @@
+/**
+ * @module @soulcraft/kits/skills/organization-chart
+ * @description Raw SKILL.md content for the organization-chart kit's AI skills.
+ *
+ * Generated from: kits/organization-chart/skills/{skillId}/SKILL.md
+ * Do not edit directly — edit the source SKILL.md files and re-run `bun run build:skills`.
+ */
+
+/** Raw SKILL.md content for the `analyze-span` skill. */
+export const analyzeSpan = "---\nname: Analyze Span of Control\ndescription: Analyze spans of control across the organization\ntype: invocable\nversion: \"1.0.0\"\n---\n\n## Analyze Span of Control\n\nAnalyze spans of control across the organization\n\n### Steps\n\n1. Identify all people managers in the org\n2. Count direct reports for each manager\n3. Flag spans too wide (>12 reports)\n4. Flag spans too narrow (<3 reports)\n5. Calculate average span of control\n6. Identify potential rebalancing opportunities\n7. Consider role complexity in assessment\n8. Generate recommendations for optimal spans\n\n### Expected Outputs\n\n- Span of control analysis report\n- Rebalancing recommendations\n\n### When to Use\n\nThis workflow is helpful when the user mentions:\n- \"span of control\"\n- \"too many reports\"\n- \"management layers\"\n- \"org efficiency\"\n";
+
+/** Raw SKILL.md content for the `plan-reorg` skill. */
+export const planReorg = "---\nname: Plan Reorganization\ndescription: Plan an organizational restructure\ntype: invocable\nversion: \"1.0.0\"\nparameters: [reason]\n---\n\n## Plan Reorganization\n\nPlan an organizational restructure\n\n### Steps\n\n1. Document current state org structure\n2. Identify drivers for change (growth, strategy shift, etc.)\n3. Define goals for the new structure\n4. Design proposed new structure\n5. Identify role changes (new, eliminated, changed)\n6. Map people to new roles\n7. Plan communication strategy\n8. Create transition timeline\n9. Identify risks and mitigations\n10. Prepare FAQ for team questions\n\n### Inputs Required\n\n- **reason** (required): Why is the reorg needed?\n\n### Expected Outputs\n\n- Current state document\n- Future state design\n- Transition plan\n\n### When to Use\n\nThis workflow is helpful when the user mentions:\n- \"reorganization\"\n- \"restructure\"\n- \"reorg\"\n- \"change structure\"\n";
+
+/** Raw SKILL.md content for the `role-definition` skill. */
+export const roleDefinition = "---\nname: role-definition\ndescription: Define clear roles and responsibilities within organizational structures\ntype: invocable\nversion: \"1.0.0\"\n---\n\n## Role Definition Skill\n\nWhen the user invokes `/roles`, help them define clear roles and responsibilities for positions in their organization.\n\n### Invocation Patterns\n\n- `/roles [position]` - Define specific role\n- `/roles team [team]` - Define roles for entire team\n- `/roles compare` - Compare similar roles for clarity\n- `/roles raci` - Create RACI matrix\n\n### Role Definition Components\n\n**Core Elements**\n- Title\n- Purpose/Mission\n- Key responsibilities\n- Authority/Decision rights\n- Success metrics\n- Required skills\n- Reporting relationships\n\n### Output Format\n\n```markdown\n## Role Definition: [Title]\n\n### Role Overview\n**Title**: [Official title]\n**Department**: [Department/Team]\n**Reports To**: [Manager title]\n**Direct Reports**: [Number and types]\n\n### Purpose\n[One paragraph describing why this role exists and its core mission]\n\n### Key Responsibilities\n\n#### Primary (70% of time)\n1. **[Responsibility Area]**\n   - [Specific task/activity]\n   - [Specific task/activity]\n   - [Deliverable/outcome expected]\n\n2. **[Responsibility Area]**\n   - [Specific task/activity]\n   - [Deliverable/outcome expected]\n\n#### Secondary (20% of time)\n3. **[Responsibility Area]**\n   - [Specific task/activity]\n\n#### Occasional (10% of time)\n4. **[Responsibility Area]**\n   - [Specific task/activity]\n\n### Decision Authority\n\n**This role CAN decide**:\n- [Decision type 1]\n- [Decision type 2]\n- Up to $[amount] spend authority\n\n**This role MUST escalate**:\n- [Decision type requiring approval]\n- [Decision type requiring approval]\n\n### Success Metrics\n| Metric | Target | Measurement |\n|--------|--------|-------------|\n| [Metric 1] | [Target] | [How measured] |\n| [Metric 2] | [Target] | [How measured] |\n\n### Interfaces\n\n**Works Closely With**:\n| Role | Interaction Type | Frequency |\n|------|-----------------|-----------|\n| [Role] | [Collaboration type] | [Daily/Weekly] |\n\n**External Relationships**:\n- [External party]: [Nature of relationship]\n\n### Requirements\n\n**Required**:\n- [X] years experience in [area]\n- [Skill/qualification]\n- [Skill/qualification]\n\n**Preferred**:\n- [Nice-to-have skill]\n- [Nice-to-have experience]\n\n### Career Path\n- **From**: [Typical previous roles]\n- **To**: [Typical next roles]\n\n### Notes\n[Any additional context or special circumstances]\n```\n\n### RACI Matrix\n\n**Definitions**\n- **R**esponsible: Does the work\n- **A**ccountable: Ultimately answerable (only one per task)\n- **C**onsulted: Input before decision\n- **I**nformed: Told after decision\n\n```markdown\n### RACI Matrix: [Process/Project]\n\n| Activity | [Role A] | [Role B] | [Role C] | [Role D] |\n|----------|----------|----------|----------|----------|\n| [Activity 1] | R | A | C | I |\n| [Activity 2] | C | R | A | I |\n| [Activity 3] | I | I | R | A |\n```\n\n### Common Role Problems\n\n**Overlap Issues**\n- Same responsibility assigned to multiple roles\n- Solution: Clarify who is R vs C\n\n**Gap Issues**\n- Important tasks not assigned\n- Solution: Map all activities to roles\n\n**Authority Mismatches**\n- Responsibility without authority\n- Solution: Align decision rights\n\n**Unclear Escalation**\n- Unknown who decides edge cases\n- Solution: Define escalation paths\n\n### Role Comparison\n\nWhen roles seem similar:\n\n```markdown\n### Role Comparison: [Role A] vs [Role B]\n\n| Dimension | [Role A] | [Role B] |\n|-----------|----------|----------|\n| Focus | [Primary focus] | [Primary focus] |\n| Scope | [Geographic/functional] | [Geographic/functional] |\n| Seniority | [Level] | [Level] |\n| Authority | [Limits] | [Limits] |\n| Key Difference | [Distinguishing feature] |\n```\n\n### Tips for Good Role Definitions\n\n**Be Specific**\n- \"Manages budget\" → \"Manages $500K annual budget, approves expenses up to $10K\"\n- \"Communicates with stakeholders\" → \"Presents monthly status to steering committee\"\n\n**Focus on Outcomes**\n- What results, not just activities\n- Measurable where possible\n\n**Right Level of Detail**\n- Enough to be useful\n- Not so detailed it's rigid\n- Leave room for judgment\n\n**Living Document**\n- Review annually\n- Update with org changes\n- Get role-holder input\n";
+
+/** Raw SKILL.md content for the `org-design` skill. */
+export const orgDesign = "---\nname: org-design\ndescription: Background expertise in organizational structure and design best practices\ntype: background\nversion: \"1.0.0\"\n---\n\n## Organizational Design Expertise\n\nYou have expertise in organizational structure and design principles. Apply these when helping users create and analyze organization charts.\n\n### Organizational Structures\n\n**Functional Structure**\n```\n        CEO\n    _____|_____\n   |    |    |\n Sales  Eng  Ops\n```\n- Grouped by function/specialty\n- Clear expertise areas\n- Efficient within function\n- Can create silos\n\n**Divisional Structure**\n```\n        CEO\n    _____|_____\n   |    |    |\nProd A Prod B Prod C\n |S|E|O|S|E|O|S|E|O|\n```\n- Grouped by product/market/region\n- Self-contained units\n- Customer focused\n- May duplicate functions\n\n**Matrix Structure**\n```\n        CEO\n    _____|_____\n   |    |    |\nSales  Eng  Ops\n   \\   / \\   /\n    \\ /   \\ /\n  Project Teams\n```\n- Dual reporting lines\n- Cross-functional collaboration\n- Complex communication\n- Can cause confusion\n\n**Flat Structure**\n```\n      CEO\n  _____|_____\n |  |  |  |  |\nAll team members\n```\n- Few management layers\n- Fast decisions\n- High autonomy\n- Hard to scale\n\n**Network/Hybrid**\n- Combinations of above\n- Adapted to specific needs\n- Flexible boundaries\n\n### Span of Control\n\n**Definition**: Number of direct reports per manager\n\n**Typical Ranges**\n- Executive level: 5-7\n- Middle management: 5-10\n- Operational/routine: 10-20\n\n**Factors Affecting Span**\n- Task complexity\n- Employee experience\n- Geographic distribution\n- Required coordination\n- Manager capacity\n\n### Organizational Layers\n\n**Fewer Layers (Flat)**\n- Faster communication\n- More autonomy\n- Less career ladder\n- Works for small/simple\n\n**More Layers (Tall)**\n- Clear hierarchy\n- More oversight\n- Slower decisions\n- Career progression path\n\n**Rule of Thumb**\n- 7-8 layers max for most organizations\n- Question any layer that doesn't add value\n\n### Reporting Relationships\n\n**Solid Line (Direct Report)**\n- Primary accountability\n- Performance management\n- Day-to-day direction\n\n**Dotted Line (Indirect)**\n- Functional guidance\n- Project-based\n- No hire/fire authority\n- Coordination role\n\n### Common Structures by Type\n\n**Startup (5-20 people)**\n- Flat structure\n- Founder-led\n- Multi-functional roles\n- Informal reporting\n\n**Growth Stage (20-100)**\n- Functional teams forming\n- First management layer\n- Specialists emerging\n- Process introduction\n\n**Established (100-500)**\n- Clear departments\n- Middle management\n- Defined roles\n- More process\n\n**Enterprise (500+)**\n- Multiple divisions\n- Many management layers\n- Specialized functions\n- Formal governance\n\n### Roles vs. People\n\n**Best Practice**\n- Design for roles first\n- Then fit people\n- Roles can have multiple holders\n- People can have multiple roles\n\n**Common Mistakes**\n- Designing around current people\n- Titles without defined roles\n- Gaps in accountability\n- Overlapping responsibilities\n\n### Signs of Poor Design\n\n**Structural Problems**\n- Unclear reporting lines\n- Too many layers\n- Spans too wide/narrow\n- Important functions missing\n\n**Behavioral Symptoms**\n- Decisions stuck\n- Finger pointing\n- Duplicated work\n- Communication breakdowns\n- Talent leaving\n\n### Design Principles\n\n**Clarity**\n- Clear accountability\n- Understood boundaries\n- Known escalation paths\n\n**Alignment**\n- Structure supports strategy\n- Incentives match structure\n- Information flows where needed\n\n**Adaptability**\n- Can evolve with growth\n- Handles change\n- Not over-engineered\n";
+
+/** Raw SKILL.md content for the `kit-expertise` skill. */
+export const kitExpertise = "---\nname: kit-expertise\ndescription: Domain expertise for Organization Chart - applied automatically when working in this kit\ntype: background\nversion: \"1.0.0\"\n---\n\n## Your Role\n\nOrganizational Design Consultant helping you map and understand organizational structure and reporting relationships\n\n## Your Expertise\n\n- Organizational structure design\n- Reporting hierarchy mapping\n- Role and responsibility definition\n- Team composition analysis\n- Span of control optimization\n- Cross-functional relationships\n- Org chart visualization\n- Succession planning\n\n## Your Approach\n\nAssist the user with their requests efficiently\n\n## Things to Avoid\n\n- Creating unclear reporting lines\n- Missing key roles\n- Overly complex structures\n- Ignoring cross-functional relationships\n\n## Domain Knowledge\n\n### Key Terms\n\n**reporting line**\nDirect management relationship\n\n**span of control**\nNumber of direct reports per manager\n\n**dotted line**\nSecondary or informal reporting\n\n**direct report**\nEmployee reporting to a manager\n\n**functional team**\nGroup organized by expertise\n\n**cross-functional**\nSpanning multiple departments\n\n**matrix organization**\nDual reporting structure\n\n**organizational layer**\nLevel in the hierarchy\n\n### Best Practices\n\n- Show clear reporting lines\n- Include all key roles\n- Indicate team boundaries\n- Note cross-functional relationships\n- Keep structure as flat as practical\n- Update when changes occur\n\n### Common Mistakes to Avoid\n\n- Unclear reporting relationships\n- Too many organizational layers\n- Missing roles or positions\n- Outdated org charts\n- No cross-functional visibility\n- Ignoring informal relationships\n";
+
+/** Raw SKILL.md content for the `create-raci` skill. */
+export const createRaci = "---\nname: Create RACI Matrix\ndescription: Define responsibility assignment for a process or project\ntype: invocable\nversion: \"1.0.0\"\nparameters: [processName, activities]\n---\n\n## Create RACI Matrix\n\nDefine responsibility assignment for a process or project\n\n### Steps\n\n1. Identify the process or project scope\n2. List all key activities/decisions\n3. List all roles/people involved\n4. For each activity, assign exactly one Accountable (A)\n5. Assign Responsible (R) - who does the work\n6. Assign Consulted (C) - who provides input\n7. Assign Informed (I) - who needs to know\n8. Validate: each row has exactly one A, at least one R\n9. Review with stakeholders for alignment\n10. Document the RACI matrix\n\n### Inputs Required\n\n- **processName** (required): Name of the process or project\n- **activities** (required): List of activities/decisions\n\n### Expected Outputs\n\n- RACI matrix document\n- Role clarity for the process\n\n### When to Use\n\nThis workflow is helpful when the user mentions:\n- \"create RACI\"\n- \"who is responsible\"\n- \"accountability\"\n- \"decision rights\"\n";
+
+/** Raw SKILL.md content for the `add-role` skill. */
+export const addRole = "---\nname: Add New Role\ndescription: Add a new role to the organization chart\ntype: invocable\nversion: \"1.0.0\"\nparameters: [title, reportsTo]\n---\n\n## Add New Role\n\nAdd a new role to the organization chart\n\n### Steps\n\n1. Define the role title following naming conventions\n2. Identify the reporting manager\n3. Write a clear role description with key responsibilities\n4. Determine if this is a new position or backfill\n5. Create the role file in roles/ directory\n6. Add the \"reportsTo\" relationship\n7. Update the knowledge graph with the new node\n8. If manager role, define expected span of control\n\n### Inputs Required\n\n- **title** (required): Role title\n- **reportsTo** (required): Who this role reports to\n- **isManager** (optional): Does this role have direct reports?\n\n### Expected Outputs\n\n- New role file in roles/\n- Updated org relationships\n\n### When to Use\n\nThis workflow is helpful when the user mentions:\n- \"add role\"\n- \"new position\"\n- \"add team member\"\n- \"new hire\"\n";
+
+/** Raw SKILL.md content for the `org-health-check` skill. */
+export const orgHealthCheck = "---\nname: Organization Health Check\ndescription: Review org structure for common issues\ntype: invocable\nversion: \"1.0.0\"\n---\n\n## Organization Health Check\n\nReview org structure for common issues\n\n### Steps\n\n1. Check for single points of failure (one person in critical roles)\n2. Analyze span of control distribution\n3. Count management layers (ideal: <5)\n4. Identify orphan roles (unclear reporting)\n5. Check for circular reporting (should be none)\n6. Review title consistency\n7. Assess cross-team collaboration patterns\n8. Identify gaps in succession planning\n9. Generate health report with recommendations\n\n### Expected Outputs\n\n- Org health report\n- Recommendations for improvement\n\n### When to Use\n\nThis workflow is helpful when the user mentions:\n- \"org health\"\n- \"review structure\"\n- \"org issues\"\n- \"check organization\"\n";
+
+/** All skills for the organization-chart kit, keyed by skill ID. */
+export const allSkills: Record<string, string> = {
+	'analyze-span': analyzeSpan,
+	'plan-reorg': planReorg,
+	'role-definition': roleDefinition,
+	'org-design': orgDesign,
+	'kit-expertise': kitExpertise,
+	'create-raci': createRaci,
+	'add-role': addRole,
+	'org-health-check': orgHealthCheck
+};