@robosoft/skillhub-cli 0.3.2 → 0.3.3

package/CHANGELOG.md

@@ -1,5 +1,12 @@
 # Changelog
 
+## 0.3.3
+
+- Changed skill attach output so skill packages do not copy internal `rules/` folders into `.cursor/skills/<name>` or other target skill folders.
+- Kept rules as explicit top-level artifacts installed by `skillhub rule <category/name>`.
+- Updated local skill creation so `skillhub create skill <name>` creates `SKILL.md`, `skill.json`, and `templates/`, but not `rules/`.
+
+
 ## 0.3.2
 
 - Changed Cursor rule attachment path from `.cursor/rules/skillhub/<name>.md` to `.cursor/rules/<name>.md`.

package/README.md

@@ -4,7 +4,7 @@ Fetch reusable SkillHub knowledge from a web app or registry and attach it to an
 
 SkillHub has three knowledge sections:
 
-- **Skills**: capability/workflow packages, usually folders with `SKILL.md`, templates, examples, and supporting rules.
+- **Skills**: capability/workflow packages, usually folders with `SKILL.md`, `skill.json`, templates, and examples. Rules are attached separately with `skillhub rule ...`.
 - **Rules**: focused `.md` rule files such as `frontend/antipattern.md` or `backend/security.md`.
 - **Domain**: product, business, architecture, or platform knowledge in `.md` files.
 
@@ -44,7 +44,6 @@ Cursor output uses only `.md` files. Registry/category prefixes like `frontend/`
     app/
       SKILL.md
       skill.json
-      rules/
       templates/
   rules/
     skillhub.md
@@ -165,7 +164,6 @@ skillhub-registry/
       app/
         skill.json
         SKILL.md
-        rules/
         templates/
   rules/
     frontend/

package/bin/skillhub.mjs

@@ -622,7 +622,17 @@ async function writeArtifactFiles(projectRoot, config, section, artifactName, fi
     const targetDir = path.join(projectRoot, baseDir, artifactName);
     await fs.rm(targetDir, { recursive: true, force: true });
     await ensureDir(targetDir);
-    for (const file of files) {
+
+    // Skills are capability packages. Project rules must be attached explicitly with
+    // `skillhub rule ...`, so we do not copy a skill package's internal rules folder
+    // into the IDE skill folder. This keeps .cursor/skills/app focused on the skill
+    // itself while .cursor/rules remains the single place for rules.
+    const skillFiles = files.filter((file) => {
+      const relativePath = normalizeSlashes(file.path);
+      return relativePath !== "rules" && !relativePath.startsWith("rules/");
+    });
+
+    for (const file of skillFiles) {
       const targetPath = safeJoin(targetDir, file.path);
       await ensureDir(path.dirname(targetPath));
       await fs.writeFile(targetPath, file.content, "utf8");
@@ -982,7 +992,6 @@ async function commandCreate(projectRoot, positional, flags = {}) {
   if (section === "skills") {
     const packageDir = path.join(sectionDir, name);
     if (await exists(packageDir)) throw new Error(`Skill already exists: ${packageDir}`);
-    await ensureDir(path.join(packageDir, "rules"));
     await ensureDir(path.join(packageDir, "templates"));
     await writeJson(path.join(packageDir, "skill.json"), {
       name,
@@ -996,7 +1005,6 @@ async function commandCreate(projectRoot, positional, flags = {}) {
       compatibleWith: ["cursor", "claude", "codex", "gemini", "opencode"],
     });
     await fs.writeFile(path.join(packageDir, "SKILL.md"), `# ${titleFromName(name)}\n\n## Description\n\n${description}\n\n## When to Use\n\nUse this skill when the user asks for ${titleFromName(name).toLowerCase()} work.\n\n## Workflow\n\n1. Understand the requirement and constraints.\n2. Inspect the existing project structure before changing code.\n3. Propose the smallest safe implementation plan.\n4. Implement using project conventions.\n5. Validate with build, lint, tests, or manual checks.\n\n## Rules\n\n- Follow installed project rules first.\n- Use installed domain knowledge when relevant.\n- Do not invent APIs, paths, or product behavior.\n- Keep changes scoped to the user request.\n\n## Output\n\nExplain changed files, validation performed, and any remaining risks.\n`, "utf8");
-    await fs.writeFile(path.join(packageDir, "rules/main.md"), `# ${titleFromName(name)} Rules\n\n- Add skill-specific rules here.\n`, "utf8");
     ok(`Created skill ${name}@${version}`);
     info(`Location: ${packageDir}`);
     return;

package/docs/skillhub-cli-logic.md

@@ -22,7 +22,6 @@ A skill is a reusable workflow/capability package.
 skills/frontend/app/
   skill.json
   SKILL.md
-  rules/
   templates/
   examples/
 ```

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@robosoft/skillhub-cli",
-  "version": "0.3.2",
+  "version": "0.3.3",
   "description": "SkillHub CLI for fetching SkillHub web-app knowledge packages into IDE projects: skills, rules, and domain knowledge.",
   "type": "module",
   "bin": {

package/skillhub-registry/skills/frontend/app/rules/main.md

@@ -1,6 +0,0 @@
-# Frontend App Skill Rules
-
-- Follow the installed frontend anti-pattern rules.
-- Keep components focused and typed.
-- Respect existing project architecture.
-- Add accessible labels and keyboard-friendly interactions.

package/skillhub-registry/skills/frontend-app/rules/main.md

@@ -1,6 +0,0 @@
-# Frontend App Skill Rules
-
-- Read installed rules before writing code.
-- Read installed domain knowledge if the feature touches business behavior.
-- Prefer small composable components over giant screen files.
-- Keep mutation and data fetching logic easy to test.