@compilr-dev/sdk 0.26.0 → 0.28.0

package/dist/project-types/{skill-meta.js → macro-meta.js}

@@ -1,16 +1,36 @@
 /**
- * Skill Metadata Registry
+ * Macro Metadata Registry — the single registry for every macro we ship.
  *
- * Maps skill IDs to UI metadata (label, icon, category).
- * This is the single source of truth — the desktop reads this via IPC.
+ * 55 entries: 42 platform macros, the 6 agents-library builtins they do not shadow, and the 7
+ * from agents-coding. Every id here is a MACRO — a named prompt the user invokes — never an
+ * installed Skill, which carries its own description in its SKILL.md.
+ *
+ * ⚠️ THERE USED TO BE THREE OF THESE. This one (unread, reachable only through an IPC channel
+ * nothing called), ACTION_META_REGISTRY (live, shorter labels), and a third inside Desktop
+ * (live, the slash menu). Each was missing what the others had: this one lacked all 8 canvas
+ * and 7 agents-coding macros, Desktop's lacked all 20 business/content/course/book ones. The
+ * failure mode was never an error — a macro with no entry renders as its raw id with a generic
+ * icon, so a business-plan project listed `business-vision`, `market-analysis`, … verbatim.
+ *
+ * `shortLabel` is why the merge is not lossy: ACTION_META's labels were shorter ON PURPOSE
+ * (a button in a row of six cannot say "Competitor Analysis"), so both survive here. Every one
+ * of its 35 labels is reproducible as `shortLabel ?? label`, asserted before it was deleted.
+ *
+ * Coverage is enforced, in both directions, by tests/skills/macro-meta-coverage.test.ts —
+ * derived from the macro sources themselves, never a hand-written list, because a hand-written
+ * list is precisely what produced three maps.
+ *
+ * Spec: project-docs/00-requirements/compilr-dev-sdk/macro-metadata-consolidation.md
  */
-/** All skill UI metadata — platform skills + builtin skills */
-export const SKILL_META_REGISTRY = {
-    // ── Platform Skills (SDK) ────────────────────────────────────────────────
+/** All macro UI metadata — platform macros + the agents library's builtins. */
+export const MACRO_META_REGISTRY = {
+    // ── Platform Macros (SDK) ────────────────────────────────────────────────
     design: {
         id: 'design',
         label: 'Design App',
+        shortLabel: 'Design',
         description: 'Guide through project design',
+        shortDescription: 'Design the app',
         icon: 'Wand2',
         category: 'design',
     },
@@ -24,21 +44,28 @@ export const SKILL_META_REGISTRY = {
     prd: {
         id: 'prd',
         label: 'Write PRD',
+        shortLabel: 'PRD',
         description: 'Product requirements document',
+        shortDescription: 'Write requirements',
         icon: 'FileText',
         category: 'planning',
     },
     refine: {
         id: 'refine',
         label: 'Refine Backlog',
+        shortLabel: 'Refine',
         description: 'Expand and refine requirements',
+        shortDescription: 'Refine backlog',
         icon: 'RefreshCw',
         category: 'planning',
     },
     'refine-item': {
         id: 'refine-item',
         label: 'Refine Item',
+        shortLabel: 'Refine',
         description: 'Add detail to a work item',
+        shortDescription: 'Add detail to this item',
+        suggestedRole: 'pm',
         icon: 'RefreshCw',
         category: 'planning',
     },
@@ -46,13 +73,16 @@ export const SKILL_META_REGISTRY = {
         id: 'architecture',
         label: 'Architecture',
         description: 'System architecture design',
+        shortDescription: 'System architecture',
         icon: 'Network',
         category: 'design',
     },
     'session-notes': {
         id: 'session-notes',
         label: 'Session Notes',
+        shortLabel: 'Notes',
         description: 'Summarize work done',
+        shortDescription: 'Session summary',
         icon: 'StickyNote',
         category: 'documentation',
     },
@@ -60,6 +90,8 @@ export const SKILL_META_REGISTRY = {
         id: 'build',
         label: 'Build',
         description: 'Implement a feature',
+        shortDescription: 'Implement this item',
+        suggestedRole: 'developer',
         icon: 'Hammer',
         category: 'development',
     },
@@ -67,6 +99,7 @@ export const SKILL_META_REGISTRY = {
         id: 'scaffold',
         label: 'Scaffold',
         description: 'Generate project code',
+        shortDescription: 'Generate code',
         icon: 'Layers',
         category: 'development',
     },
@@ -74,7 +107,9 @@ export const SKILL_META_REGISTRY = {
     outline: {
         id: 'outline',
         label: 'Paper Outline',
+        shortLabel: 'Outline',
         description: 'Build paper structure',
+        shortDescription: 'Build paper outline',
         icon: 'BookOpen',
         category: 'research',
     },
@@ -88,14 +123,18 @@ export const SKILL_META_REGISTRY = {
     'draft-section': {
         id: 'draft-section',
         label: 'Draft Section',
+        shortLabel: 'Draft',
         description: 'Write a paper section',
+        shortDescription: 'Write a section',
         icon: 'PenTool',
         category: 'research',
     },
     'peer-review': {
         id: 'peer-review',
         label: 'Peer Review',
+        shortLabel: 'Review',
         description: 'Validate argument structure',
+        shortDescription: 'Review the paper',
         icon: 'ShieldCheck',
         category: 'research',
     },
@@ -110,42 +149,54 @@ export const SKILL_META_REGISTRY = {
     'business-vision': {
         id: 'business-vision',
         label: 'Business Vision',
+        shortLabel: 'Vision',
         description: 'Define business identity and value proposition',
+        shortDescription: 'Define your business',
         icon: 'Target',
         category: 'planning',
     },
     'market-analysis': {
         id: 'market-analysis',
         label: 'Market Analysis',
+        shortLabel: 'Market',
         description: 'Analyze market size, trends, and segments',
+        shortDescription: 'Analyze the market',
         icon: 'TrendingUp',
         category: 'analysis',
     },
     'competitor-analysis': {
         id: 'competitor-analysis',
         label: 'Competitor Analysis',
+        shortLabel: 'Competitors',
         description: 'Map competitive landscape',
+        shortDescription: 'Map competition',
         icon: 'Swords',
         category: 'analysis',
     },
     'financial-model': {
         id: 'financial-model',
         label: 'Financial Model',
+        shortLabel: 'Financials',
         description: 'Build revenue and cost projections',
+        shortDescription: 'Build projections',
         icon: 'DollarSign',
         category: 'analysis',
     },
     'pitch-outline': {
         id: 'pitch-outline',
         label: 'Pitch Outline',
+        shortLabel: 'Pitch',
         description: 'Structure an investor pitch',
+        shortDescription: 'Structure a pitch',
         icon: 'Rocket',
         category: 'planning',
     },
     'business-review': {
         id: 'business-review',
         label: 'Business Review',
+        shortLabel: 'Review',
         description: 'Validate the business plan',
+        shortDescription: 'Validate the plan',
         icon: 'ShieldCheck',
         category: 'analysis',
     },
@@ -153,35 +204,45 @@ export const SKILL_META_REGISTRY = {
     'brand-setup': {
         id: 'brand-setup',
         label: 'Brand Setup',
+        shortLabel: 'Brand',
         description: 'Define brand identity, voice, and visual guidelines',
+        shortDescription: 'Set up brand identity',
         icon: 'Palette',
         category: 'planning',
     },
     'content-strategy': {
         id: 'content-strategy',
         label: 'Content Strategy',
+        shortLabel: 'Strategy',
         description: 'Define content pillars and cadence',
+        shortDescription: 'Define pillars',
         icon: 'Target',
         category: 'planning',
     },
     'content-calendar': {
         id: 'content-calendar',
         label: 'Content Calendar',
+        shortLabel: 'Calendar',
         description: 'Plan content for a period',
+        shortDescription: 'Plan content',
         icon: 'Calendar',
         category: 'planning',
     },
     'create-content': {
         id: 'create-content',
         label: 'Create Content',
+        shortLabel: 'Create',
         description: 'Write copy and visual brief',
+        shortDescription: 'Write content',
         icon: 'PenTool',
         category: 'development',
     },
     'content-review': {
         id: 'content-review',
         label: 'Content Review',
+        shortLabel: 'Review',
         description: 'Review for brand consistency',
+        shortDescription: 'Check quality',
         icon: 'CheckCircle',
         category: 'analysis',
     },
@@ -190,27 +251,34 @@ export const SKILL_META_REGISTRY = {
         id: 'curriculum-design',
         label: 'Curriculum',
         description: 'Define modules and learning objectives',
+        shortDescription: 'Define structure',
         icon: 'School',
         category: 'planning',
     },
     'lesson-plan': {
         id: 'lesson-plan',
         label: 'Lesson Plan',
+        shortLabel: 'Lessons',
         description: 'Break modules into lessons',
+        shortDescription: 'Plan lessons',
         icon: 'BookOpen',
         category: 'planning',
     },
     'assessment-design': {
         id: 'assessment-design',
         label: 'Assessment',
+        shortLabel: 'Assess',
         description: 'Create quizzes and exercises',
+        shortDescription: 'Create assessments',
         icon: 'ClipboardCheck',
         category: 'planning',
     },
     'course-review': {
         id: 'course-review',
         label: 'Course Review',
+        shortLabel: 'Review',
         description: 'Pedagogical quality check',
+        shortDescription: 'Quality check',
         icon: 'CheckCircle',
         category: 'analysis',
     },
@@ -218,7 +286,9 @@ export const SKILL_META_REGISTRY = {
     'book-outline': {
         id: 'book-outline',
         label: 'Book Outline',
+        shortLabel: 'Outline',
         description: 'Define structure, beats, and chapters',
+        shortDescription: 'Plan structure',
         icon: 'BookOpen',
         category: 'planning',
     },
@@ -226,13 +296,16 @@ export const SKILL_META_REGISTRY = {
         id: 'character-design',
         label: 'Characters',
         description: 'Build character profiles and relationships',
+        shortDescription: 'Build cast',
         icon: 'Users',
         category: 'planning',
     },
     'plot-threads': {
         id: 'plot-threads',
         label: 'Plot Threads',
+        shortLabel: 'Threads',
         description: 'Define and track narrative threads',
+        shortDescription: 'Map plot lines',
         icon: 'GitBranch',
         category: 'planning',
     },
@@ -240,13 +313,16 @@ export const SKILL_META_REGISTRY = {
         id: 'scene-breakdown',
         label: 'Scenes',
         description: 'Break chapters into scenes',
+        shortDescription: 'Detail scenes',
         icon: 'Layers',
         category: 'development',
     },
     'book-review': {
         id: 'book-review',
         label: 'Book Review',
+        shortLabel: 'Review',
         description: 'Structural review of the book',
+        shortDescription: 'Structure check',
         icon: 'CheckCircle',
         category: 'analysis',
     },
@@ -254,7 +330,10 @@ export const SKILL_META_REGISTRY = {
     'code-review': {
         id: 'code-review',
         label: 'Code Review',
+        shortLabel: 'Review',
         description: 'Review code quality',
+        shortDescription: 'Review code for this item',
+        suggestedRole: 'qa',
         icon: 'Search',
         category: 'development',
     },
@@ -269,6 +348,7 @@ export const SKILL_META_REGISTRY = {
         id: 'explain',
         label: 'Explain',
         description: 'Explain code or concept',
+        shortDescription: 'Explain this item',
         icon: 'BookOpen',
         category: 'documentation',
     },
@@ -293,16 +373,127 @@ export const SKILL_META_REGISTRY = {
         icon: 'ListTodo',
         category: 'planning',
     },
+    // ── Canvas (Desktop renders these; the CLI filters them by the `canvas` tag) ──
+    canvas: {
+        id: 'canvas',
+        label: 'Visual Canvas',
+        description: 'Author or edit a visual canvas',
+        icon: 'Image',
+        category: 'design',
+    },
+    infographic: {
+        id: 'infographic',
+        label: 'Infographic',
+        description: 'Author an infographic canvas',
+        icon: 'Image',
+        category: 'design',
+    },
+    carousel: {
+        id: 'carousel',
+        label: 'Carousel Deck',
+        description: 'Author a slide carousel',
+        icon: 'Images',
+        category: 'design',
+    },
+    board: {
+        id: 'board',
+        label: 'Infinite Board',
+        description: 'Author an infinite board',
+        icon: 'LayoutDashboard',
+        category: 'design',
+    },
+    'canvas-styles': {
+        id: 'canvas-styles',
+        label: 'Canvas Styles',
+        description: 'Pick a canvas aesthetic',
+        icon: 'Palette',
+        category: 'design',
+    },
+    'canvas-exemplar-infographic': {
+        id: 'canvas-exemplar-infographic',
+        label: 'Example: Infographic',
+        description: 'Worked infographic to read first',
+        icon: 'Image',
+        category: 'design',
+    },
+    'canvas-exemplar-app-screen': {
+        id: 'canvas-exemplar-app-screen',
+        label: 'Example: App Screen',
+        description: 'Worked app-screen mock to read first',
+        icon: 'LayoutDashboard',
+        category: 'design',
+    },
+    'canvas-icons': {
+        id: 'canvas-icons',
+        label: 'Canvas Icons',
+        description: 'The canvas icon set',
+        icon: 'Shapes',
+        category: 'design',
+    },
+    // ── agents-coding ────────────────────────────────────────────────────────
+    'git-workflow': {
+        id: 'git-workflow',
+        label: 'Git Workflow',
+        description: 'Git operations with safety checks',
+        icon: 'GitBranch',
+        category: 'development',
+    },
+    'test-driven': {
+        id: 'test-driven',
+        label: 'Test-Driven',
+        description: 'Test-driven development workflow',
+        icon: 'TestTube',
+        category: 'development',
+    },
+    'code-navigation': {
+        id: 'code-navigation',
+        label: 'Code Navigation',
+        description: 'Navigate and understand a codebase',
+        icon: 'Compass',
+        category: 'analysis',
+    },
+    'pr-workflow': {
+        id: 'pr-workflow',
+        label: 'PR Workflow',
+        description: 'Create and review pull requests',
+        icon: 'GitPullRequest',
+        category: 'development',
+    },
+    'project-onboarding': {
+        id: 'project-onboarding',
+        label: 'Onboard Project',
+        description: 'Get oriented in a new project',
+        icon: 'BookOpen',
+        category: 'analysis',
+    },
+    'code-optimization': {
+        id: 'code-optimization',
+        label: 'Optimize',
+        description: 'Performance optimization workflow',
+        icon: 'Zap',
+        category: 'development',
+    },
+    'dependency-management': {
+        id: 'dependency-management',
+        label: 'Dependencies',
+        description: 'Maintain project dependencies',
+        icon: 'Package',
+        category: 'development',
+    },
 };
 /**
- * Get skill metadata by ID.
+ * Get macro metadata by ID.
+ *
+ * No internal caller: `buildMacroList` and `resolveActionMeta` read the registry directly.
+ * Kept as public API of a published package — but do not read its existence as evidence that
+ * something depends on it. The IPC channel that used to was deleted for being dead.
  */
-export function getSkillMeta(skillId) {
-    return SKILL_META_REGISTRY[skillId];
+export function getMacroMeta(macroId) {
+    return MACRO_META_REGISTRY[macroId];
 }
 /**
- * Get all skill metadata entries.
+ * Get all macro metadata entries.
  */
-export function getAllSkillMeta() {
-    return Object.values(SKILL_META_REGISTRY);
+export function getAllMacroMeta() {
+    return Object.values(MACRO_META_REGISTRY);
 }

package/dist/project-types/macro-relevance.d.ts

@@ -0,0 +1,47 @@
+/**
+ * Which macros matter for a project type.
+ *
+ * ⚠️ THIS REPLACES A HAND-WRITTEN COPY, AND THE COPY HAD DRIFTED BADLY. Desktop kept a
+ * `TYPE_RELEVANT_SKILLS` table listing macro ids per project type — a second copy of
+ * `ProjectTypeConfig.projectActions`, which the SDK already declares. By the time it was found:
+ *
+ *   - business-plan, content and course promoted NONE of their own domain macros. A business
+ *     plan offered canvas, explain and session-notes; its six business macros were not promoted
+ *     and, having no metadata entry either, listed below as raw ids.
+ *   - `book` had no entry at all, so a book project fell through to an unordered list.
+ *   - it keyed `cli`, `api` and `library`, which are not project types and never matched.
+ *
+ * None of that was reachable by a compiler. The list is derived here instead, and the guard in
+ * tests/project-types/macro-relevance.test.ts asserts every id it can emit is a real macro with
+ * metadata, and that every project type is covered.
+ *
+ * Spec: project-docs/00-requirements/compilr-dev-sdk/macro-metadata-consolidation.md
+ */
+/**
+ * What the HOST can do, not what the user wants.
+ *
+ * A terminal cannot draw a canvas, so the CLI passes `canvas: false` and the canvas macros are
+ * never promoted there. This is the one thing that legitimately differs between the two hosts,
+ * so it is a parameter rather than a per-host list — neither host gets to re-decide the rest.
+ */
+export interface MacroCapabilities {
+    /**
+     * The host can render a canvas.
+     *
+     * Three states, and they differ in MEMBERSHIP, not just ordering:
+     *   `true`      — Desktop. Canvas macros are listed and promoted.
+     *   `false`     — the CLI. Canvas macros are EXCLUDED. A terminal cannot draw one, and the
+     *                 CLI's resolver already refuses them, so listing them offers something that
+     *                 then answers "Unknown command" — the exact bug the CLI had fixed for
+     *                 disabled skills and still had here.
+     *   `undefined` — no opinion: listed, not promoted. What a plain `buildMacroList()` does.
+     */
+    canvas?: boolean;
+}
+/**
+ * Macro ids relevant to a project type, most relevant first.
+ *
+ * Returns `[]` for an unknown or absent type, which callers should read as "no opinion about
+ * ordering" rather than "nothing is relevant".
+ */
+export declare function getRelevantMacros(projectTypeId?: string, capabilities?: MacroCapabilities): string[];

package/dist/project-types/macro-relevance.js

@@ -0,0 +1,58 @@
+/**
+ * Which macros matter for a project type.
+ *
+ * ⚠️ THIS REPLACES A HAND-WRITTEN COPY, AND THE COPY HAD DRIFTED BADLY. Desktop kept a
+ * `TYPE_RELEVANT_SKILLS` table listing macro ids per project type — a second copy of
+ * `ProjectTypeConfig.projectActions`, which the SDK already declares. By the time it was found:
+ *
+ *   - business-plan, content and course promoted NONE of their own domain macros. A business
+ *     plan offered canvas, explain and session-notes; its six business macros were not promoted
+ *     and, having no metadata entry either, listed below as raw ids.
+ *   - `book` had no entry at all, so a book project fell through to an unordered list.
+ *   - it keyed `cli`, `api` and `library`, which are not project types and never matched.
+ *
+ * None of that was reachable by a compiler. The list is derived here instead, and the guard in
+ * tests/project-types/macro-relevance.test.ts asserts every id it can emit is a real macro with
+ * metadata, and that every project type is covered.
+ *
+ * Spec: project-docs/00-requirements/compilr-dev-sdk/macro-metadata-consolidation.md
+ */
+import { PROJECT_TYPES } from './index.js';
+import { platformMacros } from '../skills/platform-macros.js';
+/** Macros that apply to any project where code is involved. */
+const SOFTWARE_MACROS = ['build', 'code-review', 'debug'];
+/** Applies everywhere: explaining something is not domain-specific. */
+const UNIVERSAL_MACROS = ['explain'];
+/**
+ * The canvas macros a user would reach for, derived from tags rather than named.
+ *
+ * `canvas` minus `reference`: the exemplars and the icon set are material the AGENT reads via
+ * canvas_guide, and nobody opens "canvas icons" from a slash menu. Desktop expressed that by
+ * omitting three names from a hand-written list and explaining it in a comment — which is not a
+ * rule a new canvas macro can inherit. The tag is.
+ */
+function promotableCanvasMacros() {
+    return platformMacros
+        .filter((m) => (m.tags ?? []).includes('canvas') && !(m.tags ?? []).includes('reference'))
+        .map((m) => m.name);
+}
+/**
+ * Macro ids relevant to a project type, most relevant first.
+ *
+ * Returns `[]` for an unknown or absent type, which callers should read as "no opinion about
+ * ordering" rather than "nothing is relevant".
+ */
+export function getRelevantMacros(projectTypeId, capabilities = {}) {
+    if (!projectTypeId)
+        return [];
+    const config = PROJECT_TYPES.find((t) => t.id === projectTypeId);
+    if (!config)
+        return [];
+    const ordered = [...config.projectActions];
+    if (config.category === 'software')
+        ordered.push(...SOFTWARE_MACROS);
+    if (capabilities.canvas)
+        ordered.push(...promotableCanvasMacros());
+    ordered.push(...UNIVERSAL_MACROS);
+    return [...new Set(ordered)];
+}

package/dist/project-types/types.d.ts

@@ -66,16 +66,35 @@ export interface ActionMeta {
     suggestedRole?: string;
 }
 /**
- * UI metadata for a skill.
+ * UI metadata for a macro.
  */
-export interface SkillMeta {
+export interface MacroMeta {
     id: string;
+    /** Full name, for menus and lists: "Business Vision". */
     label: string;
+    /**
+     * Short name for an action button sitting in a row of six: "Vision".
+     * Falls back to `label`. This is why merging the old ACTION_META_REGISTRY into this one
+     * could not simply drop its labels — they were shorter ON PURPOSE, not drifted.
+     */
+    shortLabel?: string;
+    /** Full sentence, for menus and lists: "Analyze market size, trends, and segments". */
     description: string;
-    /** Lucide icon name */
+    /**
+     * Terse, imperative phrasing for an action button: "Analyze the market". For a work-item
+     * action it is scoped to the item — "Implement this item", not "Implement a feature".
+     * Falls back to `description`. Like `shortLabel`, this was a deliberate second phrasing in
+     * the registry this one absorbed, not drift: 33 of its 35 entries differed.
+     */
+    shortDescription?: string;
+    /** Lucide icon name. The CLI ignores it; that is the only per-host difference here. */
     icon: string;
-    category: 'design' | 'development' | 'planning' | 'documentation' | 'analysis' | 'research';
+    category: MacroCategory;
+    /** Agent role suggested to own this when it is offered as a work-item action. */
+    suggestedRole?: string;
 }
+/** The categories a macro can be filed under. Shared, so a host cannot be missing one. */
+export type MacroCategory = 'design' | 'development' | 'planning' | 'documentation' | 'analysis' | 'research';
 /**
  * Full project type configuration.
  */

package/dist/skills/book-macros.d.ts

@@ -0,0 +1,10 @@
+/**
+ * Book Macros
+ *
+ * book-outline, character-design, plot-threads, scene-breakdown, book-review
+ */
+export declare const bookOutlineMacro: import("@compilr-dev/agents").Skill;
+export declare const characterDesignMacro: import("@compilr-dev/agents").Skill;
+export declare const plotThreadsMacro: import("@compilr-dev/agents").Skill;
+export declare const sceneBreakdownMacro: import("@compilr-dev/agents").Skill;
+export declare const bookReviewMacro: import("@compilr-dev/agents").Skill;

package/dist/skills/{book-skills.js → book-macros.js}

@@ -1,10 +1,10 @@
 /**
- * Book Skills
+ * Book Macros
  *
  * book-outline, character-design, plot-threads, scene-breakdown, book-review
  */
 import { defineSkill } from '@compilr-dev/agents';
-export const bookOutlineSkill = defineSkill({
+export const bookOutlineMacro = defineSkill({
     name: 'book-outline',
     description: 'Define the book structure — story template selection, beat sheet, chapter breakdown, and narrative arc. Use when starting a new book or restructuring an existing one. Produces a BookModel outline stored in the project database.',
     prompt: `You are in BOOK OUTLINE MODE. Help the user structure their book.
@@ -45,7 +45,7 @@ Create one "Chapter" work item per chapter.
 - Beat percentages are guidelines, not rigid rules`,
     tags: ['book', 'planning', 'structure'],
 });
-export const characterDesignSkill = defineSkill({
+export const characterDesignMacro = defineSkill({
     name: 'character-design',
     description: 'Build detailed character profiles including backstory, traits, motivations, arcs, and relationship maps. Use after the outline exists. Creates or updates character entries in the BookModel with connections between characters.',
     prompt: `You are in CHARACTER DESIGN MODE. Help the user build their cast.
@@ -82,7 +82,7 @@ This feeds the Character Map visualization.
 - For non-fiction: "characters" are key concepts with relationships`,
     tags: ['book', 'characters'],
 });
-export const plotThreadsSkill = defineSkill({
+export const plotThreadsMacro = defineSkill({
     name: 'plot-threads',
     description: 'Define and track plot threads across chapters — main plot, subplots, and thematic threads. Use when the outline and characters exist but narrative threads need explicit tracking. Maps each thread to the chapters where it appears.',
     prompt: `You are in PLOT THREADS MODE. Map the story's narrative threads.
@@ -118,7 +118,7 @@ Report issues and suggest fixes.
 - For non-fiction: threads are argument lines`,
     tags: ['book', 'plotting'],
 });
-export const sceneBreakdownSkill = defineSkill({
+export const sceneBreakdownMacro = defineSkill({
     name: 'scene-breakdown',
     description: 'Break a chapter into detailed scenes with setting, characters present, POV, conflict, and beats. Use when a chapter outline exists but needs scene-level granularity before drafting. Produces scene entries linked to the chapter in the BookModel.',
     prompt: `You are in SCENE BREAKDOWN MODE. Detail a chapter's scenes.
@@ -151,7 +151,7 @@ Save: \`book_model_update\` op: "scene_add"
 - End chapters on moments of tension or decision`,
     tags: ['book', 'scenes'],
 });
-export const bookReviewSkill = defineSkill({
+export const bookReviewMacro = defineSkill({
     name: 'book-review',
     description: 'Structural review of the entire book — validates beat sheet completeness, character arc consistency, thread coverage across chapters, and pacing balance. Use after substantial content exists to find structural gaps before drafting or revision.',
     prompt: `You are in BOOK REVIEW MODE. Evaluate the book's structure.