@compilr-dev/sdk 0.26.0 → 0.28.0

package/dist/skills/prompt-resolver.d.ts

@@ -1,11 +1,17 @@
 /**
- * Unified skill prompt resolver — used by both CLI and Desktop.
+ * Unified slash-command prompt resolver — used by both CLI and Desktop.
  *
- * Resolves a slash command name to a skill prompt using:
+ * Resolves a slash command name to a prompt using:
  * 1. Binding resolution (config.json slashCommands)
  * 2. 5-layer priority: project → user → SDK platform → agents builtin → agents-coding
  *
  * Also provides getAllAvailableSkills() for autocomplete/picker display.
+ *
+ * ⚠️ DELIBERATELY NOT RENAMED YET. This module spans BOTH populations: layer 4 is platform
+ * macros, but layers 2–3 read the user's and project's `SKILL.md` directories, so today an
+ * installed skill is also reachable by typing its name. That conflation is what M5 removes, by
+ * moving user-authored macros to `commands/` and leaving `skills/` to skills alone. Naming this
+ * module before that split would name the wrong shape; the rename follows M5, not this group.
  */
 import type { ForkedFromMarker } from './types.js';
 /** Result of resolving a skill prompt */

package/dist/skills/prompt-resolver.js

@@ -1,17 +1,23 @@
 /**
- * Unified skill prompt resolver — used by both CLI and Desktop.
+ * Unified slash-command prompt resolver — used by both CLI and Desktop.
  *
- * Resolves a slash command name to a skill prompt using:
+ * Resolves a slash command name to a prompt using:
  * 1. Binding resolution (config.json slashCommands)
  * 2. 5-layer priority: project → user → SDK platform → agents builtin → agents-coding
  *
  * Also provides getAllAvailableSkills() for autocomplete/picker display.
+ *
+ * ⚠️ DELIBERATELY NOT RENAMED YET. This module spans BOTH populations: layer 4 is platform
+ * macros, but layers 2–3 read the user's and project's `SKILL.md` directories, so today an
+ * installed skill is also reachable by typing its name. That conflation is what M5 removes, by
+ * moving user-authored macros to `commands/` and leaving `skills/` to skills alone. Naming this
+ * module before that split would name the wrong shape; the rename follows M5, not this group.
  */
 import { readFileSync, existsSync, readdirSync } from 'node:fs';
 import { join } from 'node:path';
 import { parseSkillMarkdown } from './loader.js';
 import { resolveBinding, getSkillsDir, readScopeConfigSync } from './paths.js';
-import { platformSkills } from './platform-skills.js';
+import { platformMacros } from './platform-macros.js';
 // Re-export builtinSkills from agents (available via SDK re-export)
 // The SDK re-exports builtinSkills from @compilr-dev/agents
 import { builtinSkills } from '@compilr-dev/agents';
@@ -99,10 +105,10 @@ export function resolveSkillPrompt(name, projectDir, sources) {
             return { prompt, skillName: name, isBound: false, source: 'user' };
         }
     }
-    // 4. SDK platform skills
-    const sdkSkill = platformSkills.find((s) => s.name === name);
-    if (sdkSkill) {
-        return { prompt: sdkSkill.prompt, skillName: name, isBound: false, source: 'sdk' };
+    // 4. SDK platform macros
+    const sdkMacro = platformMacros.find((s) => s.name === name);
+    if (sdkMacro) {
+        return { prompt: sdkMacro.prompt, skillName: name, isBound: false, source: 'sdk' };
     }
     // 5. Additional sources
     if (sources?.factorySkills) {
@@ -178,7 +184,7 @@ export function getAllAvailableSkills(projectDir, sources) {
         }
     }
     // 2. SDK platform skills
-    for (const skill of platformSkills) {
+    for (const skill of platformMacros) {
         if (!seen.has(skill.name)) {
             seen.add(skill.name);
             entries.push({ name: skill.name, description: skill.description, source: 'sdk' });

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

@@ -0,0 +1,10 @@
+/**
+ * Research Paper Macros
+ *
+ * outline, literature-review, draft-section, peer-review, research-scaffold
+ */
+export declare const outlineMacro: import("@compilr-dev/agents").Skill;
+export declare const literatureReviewMacro: import("@compilr-dev/agents").Skill;
+export declare const draftSectionMacro: import("@compilr-dev/agents").Skill;
+export declare const peerReviewMacro: import("@compilr-dev/agents").Skill;
+export declare const researchScaffoldMacro: import("@compilr-dev/agents").Skill;

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

@@ -1,10 +1,10 @@
 /**
- * Research Paper Skills
+ * Research Paper Macros
  *
  * outline, literature-review, draft-section, peer-review, research-scaffold
  */
 import { defineSkill } from '@compilr-dev/agents';
-export const outlineSkill = defineSkill({
+export const outlineMacro = defineSkill({
     name: 'outline',
     description: 'Build or refine the research paper structure — define sections, formulate claims with evidence requirements, and map sources to claims. Use when starting a new paper or restructuring an existing one. Produces a ResearchModel outline stored in the project database.',
     prompt: `You are in OUTLINE MODE. Your goal is to help the user build or refine a structured outline for their research paper using the Research Model.
@@ -148,7 +148,7 @@ Create one work item per section:
 ✓ User has reviewed and approved the outline`,
     tags: ['research', 'planning', 'outline'],
 });
-export const literatureReviewSkill = defineSkill({
+export const literatureReviewMacro = defineSkill({
     name: 'literature-review',
     description: 'Systematically analyze sources from the Knowledge Base — extract key findings, link evidence to claims in the outline, assess source quality, and identify coverage gaps. Use after the outline exists and sources have been added to the Knowledge Base.',
     prompt: `You are in LITERATURE REVIEW MODE. Your goal is to systematically analyze the sources in the Knowledge Base and connect them to the Research Model's sections and claims.
@@ -252,7 +252,7 @@ If multiple sources have been analyzed, provide a thematic synthesis:
 ✓ User has reviewed the source-claim mappings`,
     tags: ['research', 'analysis', 'sources'],
 });
-export const draftSectionSkill = defineSkill({
+export const draftSectionMacro = defineSkill({
     name: 'draft-section',
     description: 'Draft a specific paper section using the outline structure, claims, and linked sources. Use when the outline and literature review are complete for the target section. Produces academic prose with inline citations following the selected citation style.',
     prompt: `You are in DRAFT SECTION MODE. Your goal is to write or revise a section of the research paper, guided by the Research Model's outline, claims, and linked sources.
@@ -364,7 +364,7 @@ Report to the user:
 ✓ User has reviewed the draft`,
     tags: ['research', 'writing', 'drafting'],
 });
-export const peerReviewSkill = defineSkill({
+export const peerReviewMacro = defineSkill({
     name: 'peer-review',
     description: 'Peer review the research paper — validate argument structure, find logical gaps, check claim-evidence consistency, assess citation coverage, and verify cross-section coherence. Use before submission to identify weaknesses. Produces a structured review report with actionable issues.',
     prompt: `You are in PEER REVIEW MODE. Your goal is to critically evaluate the research paper's argument structure, identify gaps, and check consistency — like an academic peer reviewer.
@@ -513,7 +513,7 @@ For issues that affect the Research Model:
 ✓ User has received the review summary`,
     tags: ['research', 'review', 'quality'],
 });
-export const researchScaffoldSkill = defineSkill({
+export const researchScaffoldMacro = defineSkill({
     name: 'research-scaffold',
     description: 'Scaffold a new research paper project from a template — APA journal article, IEEE conference paper, thesis/dissertation, literature review, or lab report. Use when starting a fresh research project. Creates the ResearchModel with template-appropriate sections, citation style, and document structure.',
     prompt: `You are in RESEARCH SCAFFOLD MODE. Your goal is to help the user set up a new research paper project using a template.

package/dist/skills/resolver.d.ts

@@ -6,7 +6,7 @@
  * 5-layer priority (first match by name wins):
  *   1. project (<projectDir>/.compilr/skills/)
  *   2. user    (~/.compilr-dev/skills/)
- *   3. sdk     (platformSkills)
+ *   3. sdk     (platformMacros)
  *   4. agents  (builtinSkills)
  *   5. agents-coding (codingSkills)
  *
@@ -28,8 +28,14 @@ export interface SkillEligibilityContext {
     agentId?: string;
     /** Tool names this agent has access to. */
     toolNames?: ReadonlySet<string> | readonly string[];
-    /** Explicit skill allowlist on the agent (legacy enabledSkills). */
-    enabledSkills?: readonly string[];
+    /**
+     * Skills this agent may choose. `undefined` = no allowlist, `[]` = none.
+     *
+     * ⚠️ NAMED FOR WHAT IT HOLDS. This was called `enabledSkills` and documented "legacy", while
+     * every caller fed it `grantedSkills` — the exact field-name reuse that inverted the contract
+     * and stripped every custom agent's skills in 0.25.0, preserved in the type that caused it.
+     */
+    grantedSkills?: readonly string[];
     /** Active project category ('software', 'research', 'business', ...). */
     projectType?: string;
 }
@@ -62,11 +68,11 @@ export declare function resolveSkillsForAgent(skills: CustomSkill[], context: Sk
  * than once. Every judgement lives here: which fields of the agent matter, and what an absent
  * allowlist means.
  *
- * ⚠️ READS `grantedSkills`, NOT `enabledSkills`. Those are different fields for different things.
- * `enabledSkills` holds COMMANDS — the 13 its picker offers are `code-review`, `debug`, `design`,
- * `prd` and friends, all slash commands a user types — and 0.25.0 wired Skills enforcement onto
- * it, so ticking "Code Review" wrote a name no installed skill has and the agent silently got
- * zero skills.
+ * ⚠️ READS `grantedSkills`. There used to be a second field, `enabledSkills`, holding MACRO ids —
+ * the 13 its picker offered were `code-review`, `debug`, `design`, `prd` and friends, all things
+ * a user types — and 0.25.0 wired Skills enforcement onto it, so ticking "Code Review" wrote a
+ * name no installed skill has and the agent silently got zero skills. That field is deleted, and
+ * the reason it must never come back in another guise is the whole point of this comment.
  *
  * `grantedSkills` follows the MCP contract: `undefined` = never asked, reaches everything
  * eligible; `[]` = granted nothing. That reading is legitimate here precisely because the field
@@ -79,7 +85,7 @@ export declare function resolveSkillsForAgent(skills: CustomSkill[], context: Sk
 export declare function resolveSkillsForTeamAgent(pool: CustomSkill[], agent: {
     id: string;
     role?: string;
-    /** Skills this agent may choose. NOT `enabledSkills`, which holds Commands. */
+    /** Skills this agent may choose. undefined = never asked, [] = none. */
     grantedSkills?: readonly string[];
 }, opts?: {
     projectType?: string;

package/dist/skills/resolver.js

@@ -6,7 +6,7 @@
  * 5-layer priority (first match by name wins):
  *   1. project (<projectDir>/.compilr/skills/)
  *   2. user    (~/.compilr-dev/skills/)
- *   3. sdk     (platformSkills)
+ *   3. sdk     (platformMacros)
  *   4. agents  (builtinSkills)
  *   5. agents-coding (codingSkills)
  *
@@ -48,12 +48,12 @@ export function resolveSkillsForAgent(skills, context) {
     const toolSet = context.toolNames instanceof Set ? context.toolNames : new Set(context.toolNames ?? []);
     /*
       ⚠️ THIS SET COMES FROM `grantedSkills`, WHICH IS NEW — so `[]` correctly means "granted
-      nothing", the MCP contract. It does NOT come from `enabledSkills`, which holds Commands and
-      has always documented empty as "all skills"; 0.25.0 conflated the two and every custom agent
-      silently lost its skills. `resolveSkillsForTeamAgent` is the only caller that maps a field
-      onto this context, which is where that distinction is kept.
+      nothing", the MCP contract. It must NEVER be fed `enabledSkills`, which holds MACRO ids and
+      has always documented empty as "all"; 0.25.0 conflated the two and every custom agent
+      silently lost its skills. The field is now named `grantedSkills` on both sides, so the two
+      cannot be mixed up by a caller that does not read this comment.
     */
-    const allowlist = context.enabledSkills ? new Set(context.enabledSkills) : null;
+    const allowlist = context.grantedSkills ? new Set(context.grantedSkills) : null;
     return skills.filter((skill) => {
         if (skill.enabled === false)
             return false;
@@ -79,7 +79,7 @@ export function resolveSkillsForAgent(skills, context) {
                     return false;
             }
         }
-        // Stage 1.4 — Agent's explicit enabledSkills allowlist (legacy mechanism).
+        // Stage 1.4 — the agent's explicit grant.
         if (allowlist && !allowlist.has(skill.name))
             return false;
         return true;
@@ -94,11 +94,11 @@ export function resolveSkillsForAgent(skills, context) {
  * than once. Every judgement lives here: which fields of the agent matter, and what an absent
  * allowlist means.
  *
- * ⚠️ READS `grantedSkills`, NOT `enabledSkills`. Those are different fields for different things.
- * `enabledSkills` holds COMMANDS — the 13 its picker offers are `code-review`, `debug`, `design`,
- * `prd` and friends, all slash commands a user types — and 0.25.0 wired Skills enforcement onto
- * it, so ticking "Code Review" wrote a name no installed skill has and the agent silently got
- * zero skills.
+ * ⚠️ READS `grantedSkills`. There used to be a second field, `enabledSkills`, holding MACRO ids —
+ * the 13 its picker offered were `code-review`, `debug`, `design`, `prd` and friends, all things
+ * a user types — and 0.25.0 wired Skills enforcement onto it, so ticking "Code Review" wrote a
+ * name no installed skill has and the agent silently got zero skills. That field is deleted, and
+ * the reason it must never come back in another guise is the whole point of this comment.
  *
  * `grantedSkills` follows the MCP contract: `undefined` = never asked, reaches everything
  * eligible; `[]` = granted nothing. That reading is legitimate here precisely because the field
@@ -112,7 +112,7 @@ export function resolveSkillsForTeamAgent(pool, agent, opts = {}) {
     return resolveSkillsForAgent(pool, {
         role: agent.role,
         agentId: agent.id,
-        enabledSkills: agent.grantedSkills,
+        grantedSkills: agent.grantedSkills,
         projectType: opts.projectType,
         toolNames: opts.toolNames,
     });

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

@@ -0,0 +1,14 @@
+/**
+ * Software Development Macros
+ *
+ * design, sketch, prd, refine, refine-item, architecture, session-notes, build, scaffold
+ */
+export declare const designMacro: import("@compilr-dev/agents").Skill;
+export declare const refineMacro: import("@compilr-dev/agents").Skill;
+export declare const sketchMacro: import("@compilr-dev/agents").Skill;
+export declare const refineItemMacro: import("@compilr-dev/agents").Skill;
+export declare const architectureMacro: import("@compilr-dev/agents").Skill;
+export declare const prdMacro: import("@compilr-dev/agents").Skill;
+export declare const sessionNotesMacro: import("@compilr-dev/agents").Skill;
+export declare const buildMacro: import("@compilr-dev/agents").Skill;
+export declare const scaffoldMacro: import("@compilr-dev/agents").Skill;

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

@@ -1,5 +1,5 @@
 /**
- * Software Development Skills
+ * Software Development Macros
  *
  * design, sketch, prd, refine, refine-item, architecture, session-notes, build, scaffold
  */
@@ -7,7 +7,7 @@ import { defineSkill } from '@compilr-dev/agents';
 // =============================================================================
 // From @compilr-dev/agents (7 skills)
 // =============================================================================
-export const designSkill = defineSkill({
+export const designMacro = defineSkill({
     name: 'design',
     description: 'Interactive requirements gathering session that produces 5-15 actionable backlog items. Use when starting a new project from scratch or when the user has an idea but no clear requirements. Asks structured questions about goals, users, features, and constraints.',
     prompt: `You are in DESIGN MODE. Your goal is to gather enough information to populate the project backlog with 5-15 actionable items.
@@ -18,9 +18,9 @@ export const designSkill = defineSkill({
 - Need to create initial backlog
 
 ## When NOT to Use
-- Project already has requirements → use refine skill
-- Quick project outline needed → use sketch skill
-- Just need to update PRD → use prd skill
+- Project already has requirements → tell the user to run /refine
+- Quick project outline needed → tell the user to run /sketch
+- Just need to update PRD → tell the user to run /prd
 
 ## PHASES
 
@@ -92,7 +92,7 @@ When you have enough information:
 ✓ User has approved the backlog`,
     tags: ['planning', 'requirements'],
 });
-export const refineSkill = defineSkill({
+export const refineMacro = defineSkill({
     name: 'refine',
     description: 'Iteratively refine and expand existing project requirements. Use when the project already has an initial design or backlog but needs deeper detail, edge cases, or new features explored. Walks through each area asking targeted follow-up questions.',
     prompt: `You are in REFINE MODE. Your goal is to deepen and expand existing requirements based on user feedback.
@@ -104,9 +104,9 @@ export const refineSkill = defineSkill({
 - Adding missing items to backlog
 
 ## When NOT to Use
-- No backlog exists yet → use design skill
-- Quick outline needed → use sketch skill
-- Refining single item → use refine-item skill
+- No backlog exists yet → tell the user to run /design
+- Quick outline needed → tell the user to run /sketch
+- Refining single item → tell the user to run /refine-item
 
 ## STARTUP
 
@@ -171,7 +171,7 @@ For complex features:
 ✓ No open questions remain`,
     tags: ['planning', 'requirements'],
 });
-export const sketchSkill = defineSkill({
+export const sketchMacro = defineSkill({
     name: 'sketch',
     description: 'Quick lightweight project outline using a few simple questions. Use for rapid brainstorming or when the user wants a fast first pass before committing to a full design session. Produces a high-level summary, not detailed backlog items.',
     prompt: `You are in SKETCH MODE. Ask 6 quick questions, then create backlog items.
@@ -182,9 +182,9 @@ export const sketchSkill = defineSkill({
 - Initial brainstorming session
 
 ## When NOT to Use
-- Detailed requirements needed → use design skill
-- Project already has backlog → use refine skill
-- Single item focus → use refine-item skill
+- Detailed requirements needed → tell the user to run /design
+- Project already has backlog → tell the user to run /refine
+- Single item focus → tell the user to run /refine-item
 
 STEPS:
 1. Use todo_write with 6 tasks (one per question)
@@ -210,7 +210,7 @@ RULES:
 - For fresh projects, ALWAYS add CHORE-001 scaffolding as first item`,
     tags: ['planning', 'requirements'],
 });
-export const refineItemSkill = defineSkill({
+export const refineItemMacro = defineSkill({
     name: 'refine-item',
     description: 'Deep-dive refinement of a single backlog work item. Use when an item needs more detail — acceptance criteria, implementation notes, subtask breakdown, or dependency analysis. Reads the item from the database and produces an updated version.',
     prompt: `You are in FOCUSED REFINE MODE. Your goal is to refine a specific backlog item.
@@ -221,9 +221,9 @@ export const refineItemSkill = defineSkill({
 - Changing priority of specific item
 
 ## When NOT to Use
-- Multiple items need refinement → use refine skill
-- No items exist yet → use design or sketch skill
-- Ready to implement → use build skill
+- Multiple items need refinement → tell the user to run /refine
+- No items exist yet → tell the user to run /design or /sketch
+- Ready to implement → tell the user to run /build
 
 ## STARTUP
 
@@ -278,7 +278,7 @@ Based on user's choice:
 ✓ Changes are summarized`,
     tags: ['planning', 'requirements'],
 });
-export const architectureSkill = defineSkill({
+export const architectureMacro = defineSkill({
     name: 'architecture',
     description: 'Create or update architecture documentation including ADRs, system diagrams, data models, and API designs. Use after requirements are defined. Reads the current backlog and project documents to produce architecture artifacts stored as project documents.',
     prompt: `You are in ARCHITECTURE MODE. Your goal is to create architecture documentation.
@@ -290,9 +290,9 @@ export const architectureSkill = defineSkill({
 - Recording technical decisions
 
 ## When NOT to Use
-- Need product requirements → use design or prd skill
-- Need to implement features → use build skill
-- Just want to understand existing code → use explain skill
+- Need product requirements → tell the user to run /design or /prd
+- Need to implement features → tell the user to run /build
+- Just want to understand existing code → tell the user to run /explain
 
 ## DOCUMENT TYPE: {{doc_type}}
 {{#if custom_topic}}Custom Topic: {{custom_topic}}{{/if}}
@@ -423,7 +423,7 @@ Generate appropriate documentation.
 ✓ User has reviewed the output`,
     tags: ['architecture', 'documentation'],
 });
-export const prdSkill = defineSkill({
+export const prdMacro = defineSkill({
     name: 'prd',
     description: 'Create, amend, or enhance the Product Requirements Document. Use when formalizing requirements into a structured PRD with sections for overview, user personas, functional requirements, non-functional requirements, and success metrics. Stored as a project document.',
     prompt: `You are in PRD MODE. Your goal is to update or enhance the existing Product Requirements Document.
@@ -434,9 +434,9 @@ export const prdSkill = defineSkill({
 - Refining vision or scope
 
 ## When NOT to Use
-- No PRD exists yet → use design skill first
-- Need architecture docs → use architecture skill
-- Need session summary → use session-notes skill
+- No PRD exists yet → tell the user to run /design first
+- Need architecture docs → tell the user to run /architecture
+- Need session summary → tell the user to run /session-notes
 
 ## STARTUP
 
@@ -508,7 +508,7 @@ Based on section selected:
 ✓ Related backlog updates are suggested if needed`,
     tags: ['planning', 'requirements'],
 });
-export const sessionNotesSkill = defineSkill({
+export const sessionNotesMacro = defineSkill({
     name: 'session-notes',
     description: 'Create structured session notes capturing work done, decisions made, and open questions. Use at the end of a work session to document progress. Reviews conversation history and produces a formatted summary stored as a project document.',
     prompt: `You are in SESSION NOTES MODE. Your goal is to create a structured summary of the current session.
@@ -519,8 +519,8 @@ export const sessionNotesSkill = defineSkill({
 - Need to capture decisions for future reference
 
 ## When NOT to Use
-- Need product requirements → use prd skill
-- Need architecture docs → use architecture skill
+- Need product requirements → tell the user to run /prd
+- Need architecture docs → tell the user to run /architecture
 - In the middle of active work
 
 ## STARTUP
@@ -602,7 +602,7 @@ CRITICAL: session notes are database documents. NEVER write a .md file (no write
 ✓ User has reviewed the note`,
     tags: ['documentation', 'session'],
 });
-export const buildSkill = defineSkill({
+export const buildMacro = defineSkill({
     name: 'build',
     description: 'Implement a backlog work item end-to-end — read requirements, write code, run tests, and update the item status. Use when an item is ready to build. Follows a structured workflow: understand → plan → implement → verify → mark complete.',
     tags: ['implementation', 'coding'],
@@ -614,10 +614,10 @@ export const buildSkill = defineSkill({
 - Ready to write code for a feature
 
 ## When NOT to Use
-- Item is too vague → use refine-item skill first
-- No backlog exists → use design or sketch skill
-- Just exploring code → use code-navigation skill
-- Need to fix a bug → use debug skill
+- Item is too vague → tell the user to run /refine-item first
+- No backlog exists → tell the user to run /design or /sketch
+- Just exploring code → tell the user to run /code-navigation
+- Need to fix a bug → tell the user to run /debug
 
 ## CRITICAL: PROJECT DIRECTORY
 
@@ -699,7 +699,7 @@ Before implementing, read these files for context:
 - Always run tests before marking complete`,
     version: '1.0.0',
 });
-export const scaffoldSkill = defineSkill({
+export const scaffoldMacro = defineSkill({
     name: 'scaffold',
     description: 'Generate a complete project scaffold from the Application Model or tech stack selection. Use after the design phase to create the initial codebase — directory structure, configuration, boilerplate, and starter components. Supports multiple toolkits (React+Node, Next+Prisma, FastAPI, Go, static landing).',
     tags: ['setup', 'foundation', 'scaffolding'],
@@ -711,9 +711,9 @@ export const scaffoldSkill = defineSkill({
 - Need basic project structure
 
 ## When NOT to Use
-- Project already has structure → use build skill
-- Need requirements first → use design skill
-- Modifying existing project → use appropriate skill
+- Project already has structure → tell the user to run /build
+- Need requirements first → tell the user to run /design
+- Modifying existing project → tell the user to run /appropriate
 
 ## FACTORY CHECK (TRY THIS FIRST)
 

package/dist/skills/types.d.ts

@@ -86,5 +86,5 @@ export interface CustomSkill {
  * A second copy of a list is a list that will disagree with the first. Deriving it costs one
  * import and cannot go stale.
  */
-export declare const RESERVED_SKILL_NAMES: readonly string[];
-export declare function isReservedSkillName(name: string): boolean;
+export declare const RESERVED_MACRO_NAMES: readonly string[];
+export declare function isReservedMacroName(name: string): boolean;

package/dist/skills/types.js

@@ -9,7 +9,7 @@
  * extensions live under the optional `compilr:` block, which
  * Anthropic-compatible runtimes ignore.
  */
-import { platformSkills } from './platform-skills.js';
+import { platformMacros } from './platform-macros.js';
 /**
  * SDK skill names that are reserved — user/project skills cannot use these.
  *
@@ -27,7 +27,7 @@ import { platformSkills } from './platform-skills.js';
  * A second copy of a list is a list that will disagree with the first. Deriving it costs one
  * import and cannot go stale.
  */
-export const RESERVED_SKILL_NAMES = platformSkills.map((s) => s.name);
-export function isReservedSkillName(name) {
-    return RESERVED_SKILL_NAMES.includes(name);
+export const RESERVED_MACRO_NAMES = platformMacros.map((s) => s.name);
+export function isReservedMacroName(name) {
+    return RESERVED_MACRO_NAMES.includes(name);
 }

package/dist/team/agent-templates.d.ts

@@ -21,7 +21,6 @@ export interface AgentTemplate {
     personality?: string;
     systemPromptAddition?: string;
     toolProfile?: string;
-    enabledSkills?: string[];
     modelTier?: string;
 }
 /** List all saved templates */

package/dist/team/agent-templates.js

@@ -60,7 +60,6 @@ export function saveTemplate(name, agent, description) {
         personality: agent.personality,
         systemPromptAddition: agent.systemPromptAddition,
         toolProfile: agent.toolConfig?.profile,
-        enabledSkills: agent.enabledSkills,
         modelTier: agent.modelTier,
     };
     templates.push(template);
@@ -101,7 +100,6 @@ export function createAgentFromTemplate(template, agentId, existingAgents) {
         mascot: assignMascot(existingAgents),
         createdAt: new Date().toISOString(),
         toolConfig: template.toolProfile ? { profile: template.toolProfile } : undefined,
-        enabledSkills: template.enabledSkills,
         modelTier: template.modelTier,
     };
 }

package/dist/team/custom-agents.d.ts

@@ -17,7 +17,6 @@ export interface CustomAgentDefinition {
     mascot: string;
     createdAt: string;
     toolConfig?: ToolConfig;
-    enabledSkills?: string[];
     modelTier?: ModelTier;
     /** Custom instructions appended to the agent's system prompt (max 2000 chars) */
     systemPromptAddition?: string;
@@ -97,4 +96,4 @@ export declare function isAgentIdTaken(id: string, existingCustomAgents: CustomA
 /**
  * Create a new CustomAgentDefinition with auto-assigned mascot.
  */
-export declare function createCustomAgentDefinition(id: string, displayName: string, specialty: string, personality: string | undefined, existingAgents: CustomAgentDefinition[], toolConfig?: ToolConfig, enabledSkills?: string[], modelTier?: ModelTier, systemPromptAddition?: string): CustomAgentDefinition;
+export declare function createCustomAgentDefinition(id: string, displayName: string, specialty: string, personality: string | undefined, existingAgents: CustomAgentDefinition[], toolConfig?: ToolConfig, modelTier?: ModelTier, systemPromptAddition?: string): CustomAgentDefinition;

package/dist/team/custom-agents.js

@@ -191,7 +191,7 @@ export function isAgentIdTaken(id, existingCustomAgents, teamAgentIds, predefine
 /**
  * Create a new CustomAgentDefinition with auto-assigned mascot.
  */
-export function createCustomAgentDefinition(id, displayName, specialty, personality, existingAgents, toolConfig, enabledSkills, modelTier, systemPromptAddition) {
+export function createCustomAgentDefinition(id, displayName, specialty, personality, existingAgents, toolConfig, modelTier, systemPromptAddition) {
     return {
         id,
         displayName,
@@ -200,7 +200,6 @@ export function createCustomAgentDefinition(id, displayName, specialty, personal
         mascot: assignMascot(existingAgents),
         createdAt: new Date().toISOString(),
         toolConfig: toolConfig ?? createDefaultToolConfig(),
-        enabledSkills: enabledSkills ?? [], // Empty = all skills
         modelTier: modelTier ?? 'balanced', // Default tier
         systemPromptAddition: systemPromptAddition?.trim() || undefined,
     };

package/dist/team/index.d.ts

@@ -26,7 +26,7 @@ export type { AgentTemplate } from './agent-templates.js';
 export { listTemplates, getTemplate, saveTemplate, updateTemplate, deleteTemplate, createAgentFromTemplate, } from './agent-templates.js';
 export type { PlanSubmitInfo, PlanSubmitResult, PlanModeExitInfo, PlanModeCallbacks, } from './plan-mode.js';
 export { PLAN_MODE_BLOCKED_TOOLS, PLAN_MODE_DENIAL_MESSAGE, PLAN_MODE_PROMPT, isToolAllowedInPlanMode, getPlanModePrompt, } from './plan-mode.js';
-export type { AgentWorkshopData, WorkshopRoleDef, WorkshopToolProfile, WorkshopModelTier, WorkshopSkillDef, } from './workshop-data.js';
+export type { AgentWorkshopData, WorkshopRoleDef, WorkshopToolProfile, WorkshopModelTier, WorkshopMacroDef, } from './workshop-data.js';
 export { buildAgentWorkshopData, buildSuggestedRolesMap } from './workshop-data.js';
 export type { ITeamPersistence, IArtifactStorage, ISessionRegistry } from './interfaces.js';
 export type { ParsedMention, ParsedInput } from './mention-parser.js';
@@ -39,8 +39,8 @@ export { wouldCreateLoop, recordAssignment, getAssignmentHistory, clearAssignmen
 export { DelegationTracker } from './delegation-tracker.js';
 export type { Delegation, DelegationStatus, DelegationResult, CompletionEvent, CreateDelegationOptions, DelegationStats, DelegationTrackerEvents, } from './delegation-tracker.js';
 export { setActiveSharedContext, getActiveSharedContext, recordTeamActivity } from './activity.js';
-export type { SkillToolRequirement } from './skill-requirements.js';
-export { SKILL_REQUIREMENTS, getDefinedSkillNames, getSkillRequirements, checkSkillCompatibility, getCompatibleSkills, getAllRequiredTools, getSkillsByCategory, } from './skill-requirements.js';
+export type { MacroToolRequirement } from './macro-requirements.js';
+export { MACRO_REQUIREMENTS, getDefinedMacroNames, getMacroRequirements, checkMacroCompatibility, getCompatibleMacros, getAllRequiredTools, getMacrosByCategory, } from './macro-requirements.js';
 export { resolveAgentIdCollision } from './collision-utils.js';
 export { createDelegationStatusTool, createHandoffTool, createDelegateTool, createDelegateBackgroundTool, } from './delegation-tools.js';
 export type { HandoffResult, HandoffToolConfig, DelegateResult, DelegateToolConfig, DelegateBackgroundResult, DelegateBackgroundToolConfig, } from './delegation-tools.js';

package/dist/team/index.js

@@ -30,7 +30,7 @@ export { wouldCreateLoop, recordAssignment, getAssignmentHistory, clearAssignmen
 export { DelegationTracker } from './delegation-tracker.js';
 // Activity recording
 export { setActiveSharedContext, getActiveSharedContext, recordTeamActivity } from './activity.js';
-export { SKILL_REQUIREMENTS, getDefinedSkillNames, getSkillRequirements, checkSkillCompatibility, getCompatibleSkills, getAllRequiredTools, getSkillsByCategory, } from './skill-requirements.js';
+export { MACRO_REQUIREMENTS, getDefinedMacroNames, getMacroRequirements, checkMacroCompatibility, getCompatibleMacros, getAllRequiredTools, getMacrosByCategory, } from './macro-requirements.js';
 // Collision utils
 export { resolveAgentIdCollision } from './collision-utils.js';
 // Delegation & Handoff tools (factory functions)