@polymorphism-tech/morph-spec 4.5.0 → 4.6.0

package/src/utils/skills-installer.js

@@ -2,11 +2,18 @@
  * Skills Installer
  *
  * Copies framework skills to .claude/skills/ during morph-spec init.
- * Installs level-0-meta, level-1-workflows, and level-2-domains skills using
- * the native Claude Code subdirectory format: .claude/skills/{skill-name}/SKILL.md
- * so Claude Code can discover them via /<skill-name> syntax.
- * Level-3 and level-4 only contain README.md placeholder files and
- * are intentionally skipped.
+ * Installs level-0-meta and level-1-workflows skills using the native Claude Code
+ * subdirectory format: .claude/skills/{skill-name}/SKILL.md (plus optional
+ * scripts/, references/, and assets/ subdirectories).
+ * Level-2 domain specialists are installed as native subagents via installDomainAgents().
+ * Level-3 and level-4 only contain README.md placeholder files and are skipped.
+ *
+ * Source skills can be either:
+ *   - Directory-based: framework/skills/{level}/{skill-name}/SKILL.md  (preferred)
+ *   - Flat file: framework/skills/{level}/{skill-name}.md               (legacy, still supported)
+ *
+ * Directory-based skills have their entire directory copied (scripts/, references/,
+ * assets/) so Claude Code can execute scripts and load references on demand.
  */
 
 import { mkdirSync, copyFileSync, existsSync, readdirSync, statSync } from 'fs';
@@ -26,15 +33,42 @@ const FRAMEWORK_SKILLS_DIR = join(__dirname, '..', '..', 'framework', 'skills');
 const SKILL_LEVELS_TO_INSTALL = ['level-0-meta', 'level-1-workflows'];
 
 /**
- * Recursively walk srcDir and install each .md skill file (excluding README.md)
- * into destDir using the native Claude Code subdirectory format:
- *   destDir/{skill-name}/SKILL.md
+ * Recursively copy a directory tree from src to dest.
+ * Creates dest if it doesn't exist. Skips README.md files.
+ *
+ * @param {string} src - Source directory path
+ * @param {string} dest - Destination directory path
+ */
+function copyDirectory(src, dest) {
+  mkdirSync(dest, { recursive: true });
+  for (const entry of readdirSync(src)) {
+    if (entry === 'README.md') continue;
+    const srcPath = join(src, entry);
+    const destPath = join(dest, entry);
+    if (statSync(srcPath).isDirectory()) {
+      copyDirectory(srcPath, destPath);
+    } else {
+      copyFileSync(srcPath, destPath);
+    }
+  }
+}
+
+/**
+ * Walk srcDir and install skills into destDir.
+ *
+ * Handles two source formats:
+ *   1. Directory-based skill: srcDir/{skill-name}/SKILL.md
+ *      → copies entire directory (SKILL.md + scripts/ + references/ + assets/)
+ *      → destDir/{skill-name}/
+ *
+ *   2. Flat .md skill (legacy): srcDir/{skill-name}.md
+ *      → destDir/{skill-name}/SKILL.md
  *
- * Each skill file must have a unique name across all subdirectories;
- * duplicate filenames would cause silent overwrites of the SKILL.md inside
- * the subdirectory.
+ * Level directories (level-0-meta, level-1-workflows, sub-categories) are
+ * traversed recursively. A directory is recognized as a skill directory when
+ * it contains a SKILL.md file.
  *
- * @param {string} srcDir - Source directory to walk recursively
+ * @param {string} srcDir - Source directory to walk
  * @param {string} destDir - Destination base directory (.claude/skills/)
  */
 function installSkillsFromDir(srcDir, destDir) {
@@ -44,9 +78,18 @@ function installSkillsFromDir(srcDir, destDir) {
     const stat = statSync(srcPath);
 
     if (stat.isDirectory()) {
-      installSkillsFromDir(srcPath, destDir);
+      const skillMdPath = join(srcPath, 'SKILL.md');
+      if (existsSync(skillMdPath)) {
+        // Directory-based skill — copy entire directory including scripts/, references/, assets/
+        const skillDestDir = join(destDir, entry);
+        copyDirectory(srcPath, skillDestDir);
+      } else {
+        // Level/category directory — recurse
+        installSkillsFromDir(srcPath, destDir);
+      }
     } else if (entry.endsWith('.md') && entry !== 'README.md') {
-      const skillName = entry.slice(0, -3); // strip .md
+      // Legacy flat .md skill — wrap in subdirectory as SKILL.md
+      const skillName = entry.slice(0, -3);
       const skillDir = join(destDir, skillName);
       mkdirSync(skillDir, { recursive: true });
       copyFileSync(srcPath, join(skillDir, 'SKILL.md'));
@@ -58,7 +101,8 @@ function installSkillsFromDir(srcDir, destDir) {
  * Install morph framework skills to .claude/skills/ in the target project.
  * Skills are copied into subdirectories as SKILL.md files so Claude Code can
  * discover them natively via /<skill-name> syntax (e.g., /phase-design,
- * /blazor-builder).
+ * /blazor-builder). Directory-based skills also get their scripts/,
+ * references/, and assets/ subdirectories copied for on-demand loading.
  *
  * @param {string} projectDir - Target project root directory
  */

package/.morph/context/README.md

@@ -1,17 +0,0 @@
-# morph-spec-framework - Project Context
-
-## Overview
-
-This file will be auto-updated by MORPH-SPEC detection system.
-
-## Stack
-
-Run `morph-spec detect` to analyze your project.
-
-## Technologies
-
-(To be detected)
-
-## Architecture
-
-(To be detected)

package/framework/skills/level-2-domains/backend/api-designer.md

@@ -1,66 +0,0 @@
----
-name: api-designer
-description: >
-  API Designer specialist for REST API design, OpenAPI specs, and endpoint architecture. Activates for keywords: api, endpoint, rest, openapi, swagger, http.
-allowed-tools: Read, Write, Edit, Bash, Glob, Grep
----
-
-# API Designer
-
-**Tier:** 3 (Specialist)
-**Always Active:** No
-**Keywords:** api, endpoint, controller, rest, http, route, dto, request, response
-**Reports to:** dotnet-senior
-
----
-
-## Role
-
-REST API design specialist for .NET Minimal API and controllers, focusing on clean endpoint design and DTO contracts.
-
----
-
-## Standards Applied
-
-```
-framework/standards/core/coding.md
-framework/standards/backend/dotnet/core.md
-framework/standards/backend/dotnet/async.md
-framework/standards/backend/api/rest.md
-framework/standards/backend/api/validation.md
-```
-
----
-
-## Responsibilities
-
-- Design REST API endpoints following conventions
-- Create request/response DTOs
-- Implement API controllers or Minimal API endpoints
-- Apply proper HTTP status codes (200, 201, 400, 404, etc.)
-- Implement input validation with FluentValidation
-- Design API versioning strategy
-- Create error response formats
-
----
-
-## When to Use
-
-- Creating new API endpoints
-- Designing DTO contracts
-- API refactoring
-- Implementing validation logic
-- Designing error responses
-
----
-
-## Collaborates With
-
-- **dotnet-senior** - Service layer consumed by endpoints
-- **ef-modeler** - Entity → DTO mapping
-- **blazor-builder** - Frontend consuming API
-- **testing-specialist** - API integration tests
-
----
-
-*MORPH-SPEC by Polymorphism Tech*

package/framework/skills/level-2-domains/backend/ef-modeler.md

@@ -1,65 +0,0 @@
----
-name: ef-modeler
-description: >
-  Entity Framework Modeler specialist for database schema, migrations, DbContext design, and ORM patterns. Activates for keywords: entity framework, migrations, dbcontext, ef core.
-allowed-tools: Read, Write, Edit, Bash, Glob, Grep
----
-
-# EF Modeler
-
-**Tier:** 3 (Specialist)
-**Always Active:** No
-**Keywords:** entity, database, migration, ef core, dbcontext, table, column, relationship, query
-**Reports to:** dotnet-senior
-
----
-
-## Role
-
-Entity Framework Core specialist for database modeling, entities, configurations, and migrations.
-
----
-
-## Standards Applied
-
-```
-framework/standards/core/coding.md
-framework/standards/backend/dotnet/core.md
-framework/standards/backend/database/ef-core.md
-framework/standards/backend/database/migrations.md
-framework/standards/backend/database/repository-patterns.md
-framework/standards/backend/database/performance.md
-```
-
----
-
-## Responsibilities
-
-- Design entity models with private setters and factory methods
-- Create IEntityTypeConfiguration for each entity
-- Configure relationships, indexes, and constraints
-- Generate and review EF Core migrations
-- Optimize database queries (avoid N+1, use proper includes)
-- Implement repository patterns with IDbContextFactory
-
----
-
-## When to Use
-
-- Creating/modifying entity classes
-- Database schema changes
-- Migration creation/review
-- Query optimization
-- DbContext configuration
-
----
-
-## Collaborates With
-
-- **dotnet-senior** - Service layer consuming repositories
-- **api-designer** - DTO mapping from entities
-- **azure-architect** - Database provisioning (Azure SQL, Cosmos DB)
-
----
-
-*MORPH-SPEC by Polymorphism Tech*

package/framework/skills/level-3-technologies/README.md

@@ -1,7 +0,0 @@
-# Level 3: Technologies
-
-Technology-specific implementation patterns.
-
-**Purpose:** Skills for specific technologies (EF Core, Blazor, Hangfire, SignalR, etc.).
-
-**To be populated in Phase 8/9.**

package/framework/skills/level-4-patterns/README.md

@@ -1,7 +0,0 @@
-# Level 4: Patterns
-
-Architectural and design patterns.
-
-**Purpose:** Skills for specific patterns (CQRS, Event Sourcing, DDD, Repository, etc.).
-
-**To be populated later.**