@boopkit/cap-product-design 0.3.1 → 0.4.0

package/README.md

@@ -12,10 +12,10 @@ A bundle of agent-facing skill files for requirements, design, feature docs, and
 
 Copied into `skills/` on install:
 
-- `reqs.feature-requirements.skill.md` — how to turn a brief or vague directive into real requirements: ask 3-5 focused trade-off questions, push back on ambiguity without interrogating, and know when enough clarity is enough to proceed.
-- `reqs.feature-documentation.skill.md` — how to write feature documentation aimed at a specific audience and activity, with the right tone and grounding for readers who haven't done this before.
-- `design.engineering-design.skill.md` — the engineering design doc structure (Goals, Non-Goals, Approach, Alternatives, Tradeoffs, Open Questions) with a stance: make the *decision* visible, not just the solution.
-- `docs.reference-integration.skill.md` — how to blend new knowledge into `reference/` after a feature lands, keeping it a living wiki of what the system actually is, not a pile of per-feature pages.
+- `boop-product-design-feature-requirements/SKILL.md` — how to turn a brief or vague directive into real requirements: ask 3-5 focused trade-off questions, push back on ambiguity without interrogating, and know when enough clarity is enough to proceed.
+- `boop-product-design-feature-documentation/SKILL.md` — how to write feature documentation aimed at a specific audience and activity, with the right tone and grounding for readers who haven't done this before.
+- `boop-product-design-engineering-design/SKILL.md` — the engineering design doc structure (Goals, Non-Goals, Approach, Alternatives, Tradeoffs, Open Questions) with a stance: make the *decision* visible, not just the solution.
+- `boop-product-design-reference-integration/SKILL.md` — how to blend new knowledge into `reference/` after a feature lands, keeping it a living wiki of what the system actually is, not a pile of per-feature pages.
 
 ## Requirements
 
@@ -33,10 +33,10 @@ Skills are meant to be read by AI agents, not humans (though humans are welcome)
 
 How agents find them depends on the harness:
 
-- Projects with a Claude Code `CLAUDE.md` typically instruct the agent to consult `skills/index.md` or the relevant `.skill.md` file before acting.
-- Harnesses with a native skill-discovery system (e.g. slash-command style skills) surface them by filename.
+- Projects with a Claude Code `CLAUDE.md` typically instruct the agent to list the `skills/` directory and read each folder's `SKILL.md` frontmatter before acting.
+- Harnesses with a native skill-discovery system (e.g. slash-command style skills) surface them by folder name.
 
-A typical flow: a founder gives the agent a two-sentence feature brief. The agent reads `reqs.feature-requirements.skill.md` and asks a few trade-off questions to fill the gaps. Once the shape is clear it reads `design.engineering-design.skill.md` and writes a design doc with an explicit Alternatives section. After the feature ships, it reads `docs.reference-integration.skill.md` and blends the new behaviour into the existing concept pages in `reference/` — not a new feature-specific page.
+A typical flow: a founder gives the agent a two-sentence feature brief. The agent reads `boop-product-design-feature-requirements/SKILL.md` and asks a few trade-off questions to fill the gaps. Once the shape is clear it reads `boop-product-design-engineering-design/SKILL.md` and writes a design doc with an explicit Alternatives section. After the feature ships, it reads `boop-product-design-reference-integration/SKILL.md` and blends the new behaviour into the existing concept pages in `reference/` — not a new feature-specific page.
 
 ## Added by
 

package/capability.json

@@ -5,5 +5,16 @@
   "dependencies": [],
   "devDependencies": [],
   "files": [],
-  "skills": ["design.engineering-design.skill.md", "reqs.feature-documentation.skill.md", "reqs.feature-requirements.skill.md"]
+  "skills": [
+    "boop-product-design-engineering-design",
+    "boop-product-design-feature-documentation",
+    "boop-product-design-feature-requirements",
+    "boop-product-design-reference-integration"
+  ],
+  "skill_migrations": {
+    "boop-product-design-engineering-design": "design.engineering-design.skill.md",
+    "boop-product-design-feature-documentation": "reqs.feature-documentation.skill.md",
+    "boop-product-design-feature-requirements": "reqs.feature-requirements.skill.md",
+    "boop-product-design-reference-integration": "docs.reference-integration.skill.md"
+  }
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@boopkit/cap-product-design",
-  "version": "0.3.1",
+  "version": "0.4.0",
   "description": "Product design skills for AI agents",
   "files": [
     "skills/",

package/skills/{design.engineering-design.skill.md → boop-product-design-engineering-design/SKILL.md}

@@ -1,5 +1,10 @@
+---
+name: boop-product-design-engineering-design
+description: "When you need to design a feature or system and communicate the technical decisions."
+metadata:
+  category: design
+---
 # Engineering Design
-When you need to design a feature or system and communicate the technical decisions.
 
 ## Goal
 **Make the decision visible, not just the solution.**
@@ -44,7 +49,7 @@ Well-designed systems separate concerns into layers with clear responsibilities
 - **Entry points are thin dispatch** — parse, call, format. No business rules, no direct data access.
 - **Logic owns the rules** — all domain validation, calculations, and orchestration live here. This layer is transport-agnostic and testable in isolation.
 - **Data access is encapsulated** — the logic layer calls data abstractions; it doesn't construct raw queries or import database clients directly.
-- **Each layer has its own design skill** — before writing code in a layer, check `skills/index.md` for the matching design skill (e.g., controller design, service design, data model design).
+- **Each layer has its own design skill** — before writing code in a layer, check the `skills/` directory for the matching design skill (e.g., controller design, service design, data model design).
 
 ### Why this matters for agents
 

package/skills/{reqs.feature-documentation.skill.md → boop-product-design-feature-documentation/SKILL.md}

@@ -1,5 +1,10 @@
+---
+name: boop-product-design-feature-documentation
+description: "When you need to document a complex feature, function or system"
+metadata:
+  category: reqs
+---
 # Feature Documentation
-When you need to document a complex feature, function or system
 - Identity the intended audience. For example, data engineers who may not have done this sort of exercise before.
 - Identify the audience's "group identity". For example, which company, team, or project they belong to.
 - Identify the activity to be explained. For example, designing or operating at scale.

package/skills/{reqs.feature-requirements.skill.md → boop-product-design-feature-requirements/SKILL.md}

@@ -1,3 +1,9 @@
+---
+name: boop-product-design-feature-requirements
+description: "When you need to define what a feature should accomplish before designing how to build it."
+metadata:
+  category: reqs
+---
 # Feature Requirements
 
 Be sure to read the [reference/tenets.ref.md](../reference/tenets.ref.md) for overarching principles that apply to all features. 

package/skills/{docs.reference-integration.skill.md → boop-product-design-reference-integration/SKILL.md}

@@ -1,5 +1,10 @@
+---
+name: boop-product-design-reference-integration
+description: "When you need to integrate new knowledge into the project's `reference/` directory after completing a feature, fixing a bug that changes behavior, or adding a capability."
+metadata:
+  category: docs
+---
 # Reference Integration
-When you need to integrate new knowledge into the project's `reference/` directory after completing a feature, fixing a bug that changes behavior, or adding a capability.
 
 ## Goal
 Keep `reference/` as a living wiki of **what the system actually is right now** — not a pile of per-feature pages. New knowledge is blended into existing concept pages; new pages are created only when a genuinely new concept has no home.