@compilr-dev/sdk 0.7.6 → 0.7.8

package/dist/skills/content-skills.js

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

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

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

package/dist/skills/course-skills.js

@@ -0,0 +1,164 @@
+/**
+ * Course / Training Skills
+ *
+ * curriculum-design, lesson-plan, assessment-design, course-review
+ */
+import { defineSkill } from '@compilr-dev/agents';
+export const curriculumDesignSkill = defineSkill({
+    name: 'curriculum-design',
+    description: 'Define course structure — modules, learning objectives, progression',
+    prompt: `You are in CURRICULUM DESIGN MODE. Help the user structure their course.
+
+## Step 1: Course Overview
+1. Use \`curriculum_model_get\` scope: "overview" to check existing state
+2. Ask for: course title, description, target audience, prerequisites, difficulty level
+3. Save: \`curriculum_model_update\` op: "set_course_info"
+
+## Step 2: Module Breakdown
+Ask: "What are the main topics/sections of your course?"
+Help organize into 3-8 modules with logical progression.
+For each module: \`curriculum_model_update\` op: "module_add"
+
+## Step 3: Learning Objectives
+For each module, ask: "After this module, what should the student be able to DO?"
+Use Bloom's taxonomy levels:
+- Remember (define, list, recall)
+- Understand (explain, describe, summarize)
+- Apply (use, implement, solve)
+- Analyze (compare, differentiate, examine)
+- Evaluate (assess, critique, judge)
+- Create (design, build, compose)
+
+Save: \`curriculum_model_update\` op: "module_update" with learningObjectives
+
+## Step 4: Time Estimates
+Ask about total course length, then distribute across modules.
+Save: \`curriculum_model_update\` op: "module_update" with estimatedMinutes
+
+## Step 5: Generate Work Items
+Create one "Lesson" work item per module: "Develop: [module title]"
+
+## Step 6: Validation
+Run \`curriculum_model_validate\` to check completeness.
+
+## Rules
+- Interactive — one section at a time
+- The user is the subject expert, you are the curriculum designer
+- Push for specific, measurable objectives (not "understand Python" but "write a function that takes arguments and returns a value")
+- Suggest KB uploads for existing materials`,
+    tags: ['education', 'planning', 'curriculum'],
+});
+export const lessonPlanSkill = defineSkill({
+    name: 'lesson-plan',
+    description: 'Break a module into detailed lessons with types and time estimates',
+    prompt: `You are in LESSON PLAN MODE. Break a module into detailed lessons.
+
+## Step 1: Read Context
+1. \`curriculum_model_get\` scope: "modules" for overview
+2. Ask which module to plan (or plan all)
+3. Read the module's learning objectives
+
+## Step 2: Propose Lessons
+For each learning objective, propose lessons:
+- **theory** — explain concepts, principles, background
+- **demo** — show how it works (live coding, walkthrough)
+- **hands-on** — student does it themselves
+- **discussion** — reflect, discuss implications, share experiences
+- **reading** — reference material, further study
+
+Balance: aim for at least 40% hands-on/demo.
+
+## Step 3: Sequence and Time
+- Order lessons logically (concept before practice)
+- Estimate minutes per lesson
+- Total should roughly match the module's estimated time
+
+Save each: \`curriculum_model_update\` op: "lesson_add"
+
+## Step 4: Suggest Assessments
+After lessons, suggest an assessment for the module.
+Save: \`curriculum_model_update\` op: "assessment_add"
+
+## Rules
+- Every learning objective should be addressed by at least one lesson
+- Don't create theory-only modules — students need practice
+- Keep individual lessons under 45 minutes
+- Suggest where KB materials could be used`,
+    tags: ['education', 'planning', 'lessons'],
+});
+export const assessmentDesignSkill = defineSkill({
+    name: 'assessment-design',
+    description: 'Create quizzes, exercises, and projects for a module',
+    prompt: `You are in ASSESSMENT DESIGN MODE. Create assessments linked to learning objectives.
+
+## Step 1: Read Context
+1. \`curriculum_model_get\` scope: "module" with the target module
+2. Review learning objectives and existing lessons
+
+## Step 2: Choose Assessment Types
+Match assessment to objective level:
+- **quiz** — for Remember/Understand (multiple choice, true/false, short answer)
+- **exercise** — for Apply/Analyze (hands-on practice, problem solving)
+- **project** — for Evaluate/Create (open-ended, multi-step)
+- **peer-review** — students review each other's work
+- **reflection** — self-assessment, learning journal
+
+## Step 3: Design Each Assessment
+For each: title, type, description, which objectives it tests.
+Save: \`curriculum_model_update\` op: "assessment_add"
+
+## Step 4: Coverage Check
+Verify every learning objective has at least one assessment.
+Flag untested objectives.
+
+## Rules
+- Every objective should be assessed
+- Mix assessment types for variety
+- Exercises should be doable within the lesson timeframe
+- Projects can span multiple objectives`,
+    tags: ['education', 'assessment'],
+});
+export const courseReviewSkill = defineSkill({
+    name: 'course-review',
+    description: 'Review course for pedagogical quality — balance, coverage, progression',
+    prompt: `You are in COURSE REVIEW MODE. Evaluate the curriculum as a pedagogical expert.
+
+## Step 1: Load
+1. \`curriculum_model_get\` scope: "full"
+2. Run \`curriculum_model_validate\` for structural issues
+
+## Step 2: Completeness
+Check each module has:
+- Learning objectives (specific, measurable)
+- Lessons (at least 2)
+- At least one assessment
+Score: Complete / Partial / Missing
+
+## Step 3: Balance Analysis
+- Theory vs practice ratio per module (flag if >70% theory)
+- Time distribution across modules (flag if one is >2x the average)
+- Lesson type variety (flag modules with only one type)
+
+## Step 4: Progression
+- Are prerequisites respected? (easier modules before harder ones)
+- Does difficulty increase progressively?
+- Are foundational concepts taught before they're needed?
+
+## Step 5: Assessment Coverage
+- Map objectives to assessments
+- Flag objectives with no assessment
+- Flag assessments testing nothing specific
+
+## Step 6: Report
+Generate a structured review:
+- Scorecard (modules: complete/partial/missing)
+- Strengths
+- Issues (critical + recommendations)
+- Create work items for issues found
+
+## Rules
+- Be constructive — suggest fixes, don't just flag problems
+- Focus on pedagogy, not domain accuracy (user is the expert)
+- 3-5 most impactful recommendations, not a list of 20 nitpicks`,
+    tags: ['education', 'review', 'quality'],
+});

package/dist/skills/index.d.ts

@@ -1,4 +1,4 @@
 /**
  * Platform Skills — barrel export
  */
-export { platformSkills, designSkill, sketchSkill, prdSkill, refineSkill, refineItemSkill, architectureSkill, sessionNotesSkill, buildSkill, scaffoldSkill, outlineSkill, literatureReviewSkill, draftSectionSkill, peerReviewSkill, researchScaffoldSkill, businessVisionSkill, marketAnalysisSkill, competitorAnalysisSkill, financialModelSkill, pitchOutlineSkill, businessReviewSkill, } from './platform-skills.js';
+export { platformSkills, designSkill, sketchSkill, prdSkill, refineSkill, refineItemSkill, architectureSkill, sessionNotesSkill, buildSkill, scaffoldSkill, outlineSkill, literatureReviewSkill, draftSectionSkill, peerReviewSkill, researchScaffoldSkill, businessVisionSkill, marketAnalysisSkill, competitorAnalysisSkill, financialModelSkill, pitchOutlineSkill, businessReviewSkill, brandSetupSkill, contentStrategySkill, contentCalendarSkill, createContentSkill, contentReviewSkill, curriculumDesignSkill, lessonPlanSkill, assessmentDesignSkill, courseReviewSkill, } from './platform-skills.js';

package/dist/skills/index.js

@@ -1,4 +1,4 @@
 /**
  * Platform Skills — barrel export
  */
-export { platformSkills, designSkill, sketchSkill, prdSkill, refineSkill, refineItemSkill, architectureSkill, sessionNotesSkill, buildSkill, scaffoldSkill, outlineSkill, literatureReviewSkill, draftSectionSkill, peerReviewSkill, researchScaffoldSkill, businessVisionSkill, marketAnalysisSkill, competitorAnalysisSkill, financialModelSkill, pitchOutlineSkill, businessReviewSkill, } from './platform-skills.js';
+export { platformSkills, designSkill, sketchSkill, prdSkill, refineSkill, refineItemSkill, architectureSkill, sessionNotesSkill, buildSkill, scaffoldSkill, outlineSkill, literatureReviewSkill, draftSectionSkill, peerReviewSkill, researchScaffoldSkill, businessVisionSkill, marketAnalysisSkill, competitorAnalysisSkill, financialModelSkill, pitchOutlineSkill, businessReviewSkill, brandSetupSkill, contentStrategySkill, contentCalendarSkill, createContentSkill, contentReviewSkill, curriculumDesignSkill, lessonPlanSkill, assessmentDesignSkill, courseReviewSkill, } from './platform-skills.js';

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

@@ -1,36 +1,16 @@
 /**
- * Platform Skills
+ * Platform Skills — Aggregate
  *
- * Skills that depend on platform-specific tools (backlog, workitems, documents, projects).
- * These were originally in @compilr-dev/agents and @compilr-dev/agents-coding-core
- * but belong in the SDK since they reference platform tools.
- *
- * Skills: design, sketch, prd, refine, refine-item, architecture, session-notes, build, scaffold
+ * Re-exports all domain-specific skills and provides the combined platformSkills array.
+ * Individual skill files: software-skills.ts, research-skills.ts, business-skills.ts, content-skills.ts
  */
-import { type Skill } from '@compilr-dev/agents';
-export declare const designSkill: Skill;
-export declare const refineSkill: Skill;
-export declare const sketchSkill: Skill;
-export declare const refineItemSkill: Skill;
-export declare const architectureSkill: Skill;
-export declare const prdSkill: Skill;
-export declare const sessionNotesSkill: Skill;
-export declare const buildSkill: Skill;
-export declare const scaffoldSkill: Skill;
-export declare const outlineSkill: Skill;
-export declare const literatureReviewSkill: Skill;
-export declare const draftSectionSkill: Skill;
-export declare const peerReviewSkill: Skill;
-export declare const researchScaffoldSkill: Skill;
-export declare const businessVisionSkill: Skill;
-export declare const marketAnalysisSkill: Skill;
-export declare const competitorAnalysisSkill: Skill;
-export declare const financialModelSkill: Skill;
-export declare const pitchOutlineSkill: Skill;
-export declare const businessReviewSkill: Skill;
+import type { Skill } from '@compilr-dev/agents';
+export { designSkill, sketchSkill, prdSkill, refineSkill, refineItemSkill, architectureSkill, sessionNotesSkill, buildSkill, scaffoldSkill, } from './software-skills.js';
+export { outlineSkill, literatureReviewSkill, draftSectionSkill, peerReviewSkill, researchScaffoldSkill, } from './research-skills.js';
+export { businessVisionSkill, marketAnalysisSkill, competitorAnalysisSkill, financialModelSkill, pitchOutlineSkill, businessReviewSkill, } from './business-skills.js';
+export { brandSetupSkill, contentStrategySkill, contentCalendarSkill, createContentSkill, contentReviewSkill, } from './content-skills.js';
+export { curriculumDesignSkill, lessonPlanSkill, assessmentDesignSkill, courseReviewSkill, } from './course-skills.js';
 /**
- * All platform-specific skills (20 total).
- * These skills reference platform tools (backlog, workitems, documents, projects)
- * and belong in the SDK rather than in generic agent/coding libraries.
+ * All platform-specific skills (29 total).
  */
 export declare const platformSkills: Skill[];