@pigcloud/skills 1.0.10 → 1.1.2

package/skills/02-design/database-design/assets/golden-prompt-suite.current.js

@@ -0,0 +1,22 @@
+#!/usr/bin/env node
+
+module.exports = {
+  "name": "database-design.golden-prompt-suite.current",
+  "skill": "database-design",
+  "description": "Design schemas, indexes, query shapes, and data ownership before database work.",
+  "cases": [
+    {
+      "id": "database-schema-plan",
+      "prompt": "This feature needs persistence. Design the schema and query shape.",
+      "expectedFirstSkill": "database-design",
+      "expectedOutput": [
+        "schema",
+        "indexes",
+        "query plan"
+      ],
+      "expectedStop": "Do not write migration code yet.",
+      "expectedHandoff": "task-breakdown"
+    }
+  ]
+};
+

package/skills/02-design/database-design/references/README.md

@@ -0,0 +1,17 @@
+# database-design References
+
+This directory is local to the skill and is the only reference entry point for this skill.
+
+## Contents
+
+- `../skill-spec.json`: design source for regenerating this skill
+- `prompt-template.md`: reusable prompt wording for this skill
+- `cases.md`: human-readable replay case for this skill
+- `../assets/golden-prompt-suite.current.js`: machine-readable local case fixture
+
+## Guidance
+
+- Keep skill-specific explanation here instead of pushing it into a stage-level shared library.
+- Keep shared hard constraints in `../../../rules/index.md`.
+- Keep canonical names unchanged.
+- Skill summary: Design schemas, indexes, query shapes, and data ownership before database work.

package/skills/02-design/database-design/references/cases.md

@@ -0,0 +1,26 @@
+# database-design
+
+## Replay Case
+
+- Case: `database-schema-plan`
+- First skill: `database-design`
+
+### Prompt
+
+```text
+This feature needs persistence. Design the schema and query shape.
+```
+
+### Expected Output
+
+- schema
+- indexes
+- query plan
+
+### Stop Rule
+
+- Do not write migration code yet.
+
+### Handoff
+
+- task-breakdown

package/skills/02-design/database-design/references/prompt-template.md

@@ -0,0 +1,18 @@
+# database-design
+
+## Prompt Template
+
+```text
+You are handling the database-design skill.
+Goal: Design schemas, indexes, query shapes, and data ownership before database work
+Inputs: the request, supporting evidence, constraints, and existing repository facts.
+Output contract: schema, indexes, query plan.
+Stop rule: Do not write migration code yet.
+Handoff: task-breakdown.
+Keep the response scoped to this stage and do not absorb the work of the next stage.
+```
+
+## Notes
+
+- Keep the template aligned with the local replay case and local assets.
+- Read `cases.md` for the matching replay example.

package/skills/02-design/database-design/skill-spec.json

@@ -0,0 +1,25 @@
+{
+  "group": "02-design",
+  "name": "database-design",
+  "description": "Design schemas, indexes, query shapes, and data ownership before database work.",
+  "title": "Database Design",
+  "purpose": "Plan table structure, relationships, indexing, and data access patterns with low risk.",
+  "whenToUse": [
+    "A new table, column, index, or schema change is needed.",
+    "Query performance or data consistency matters.",
+    "Data ownership, cardinality, or retention rules are still unclear."
+  ],
+  "how": [
+    "Define tables, keys, indexes, and the queries the schema must support.",
+    "Match the schema to the access pattern instead of forcing the app to compensate.",
+    "Capture migration, backfill, and rollback expectations before implementation.",
+    "Note the locking, transaction, and compatibility risks that matter during rollout."
+  ],
+  "whenToAvoid": [
+    "The change is already small and local.",
+    "The system shape is already settled.",
+    "You only need request-level clarification or implementation detail."
+  ],
+  "caseId": "database-schema-plan",
+  "source": "bootstrap-from-skill-md"
+}

package/skills/02-design/task-breakdown/SKILL.md

@@ -0,0 +1,29 @@
+---
+name: task-breakdown
+description: Split an approved change into ordered, testable work items.
+---
+
+# Task Breakdown
+
+## Purpose
+
+Turn a design or request into a concrete execution sequence with clear boundaries.
+
+## When to Use
+
+- The work is too large to do in one pass.
+- You need to organize implementation, validation, and handoff steps.
+- Dependencies or risky steps need an explicit order.
+
+## How
+
+- Break the approved change into ordered work items with clear validation points.
+- Keep each item small enough to finish, validate, and hand off on its own.
+- Call out prerequisites, blockers, and the evidence each step should produce.
+- Separate design cleanup from implementation execution.
+
+## When to Avoid
+
+- The change is already small and local.
+- The system shape is already settled.
+- You only need request-level clarification or implementation detail.

package/skills/02-design/task-breakdown/assets/golden-prompt-suite.current.js

@@ -0,0 +1,22 @@
+#!/usr/bin/env node
+
+module.exports = {
+  "name": "task-breakdown.golden-prompt-suite.current",
+  "skill": "task-breakdown",
+  "description": "Split an approved change into ordered, testable work items.",
+  "cases": [
+    {
+      "id": "breakdown-executable-work",
+      "prompt": "The plan is fixed. Break it into executable and verifiable tasks.",
+      "expectedFirstSkill": "task-breakdown",
+      "expectedOutput": [
+        "task list",
+        "ordering",
+        "acceptance points"
+      ],
+      "expectedStop": "Do not start implementation.",
+      "expectedHandoff": "backend-development"
+    }
+  ]
+};
+

package/skills/02-design/task-breakdown/references/README.md

@@ -0,0 +1,17 @@
+# task-breakdown References
+
+This directory is local to the skill and is the only reference entry point for this skill.
+
+## Contents
+
+- `../skill-spec.json`: design source for regenerating this skill
+- `prompt-template.md`: reusable prompt wording for this skill
+- `cases.md`: human-readable replay case for this skill
+- `../assets/golden-prompt-suite.current.js`: machine-readable local case fixture
+
+## Guidance
+
+- Keep skill-specific explanation here instead of pushing it into a stage-level shared library.
+- Keep shared hard constraints in `../../../rules/index.md`.
+- Keep canonical names unchanged.
+- Skill summary: Split an approved change into ordered, testable work items.

package/skills/02-design/task-breakdown/references/cases.md

@@ -0,0 +1,26 @@
+# task-breakdown
+
+## Replay Case
+
+- Case: `breakdown-executable-work`
+- First skill: `task-breakdown`
+
+### Prompt
+
+```text
+The plan is fixed. Break it into executable and verifiable tasks.
+```
+
+### Expected Output
+
+- task list
+- ordering
+- acceptance points
+
+### Stop Rule
+
+- Do not start implementation.
+
+### Handoff
+
+- backend-development

package/skills/02-design/task-breakdown/references/prompt-template.md

@@ -0,0 +1,18 @@
+# task-breakdown
+
+## Prompt Template
+
+```text
+You are handling the task-breakdown skill.
+Goal: Split an approved change into ordered, testable work items
+Inputs: the request, supporting evidence, constraints, and existing repository facts.
+Output contract: task list, ordering, acceptance points.
+Stop rule: Do not start implementation.
+Handoff: backend-development.
+Keep the response scoped to this stage and do not absorb the work of the next stage.
+```
+
+## Notes
+
+- Keep the template aligned with the local replay case and local assets.
+- Read `cases.md` for the matching replay example.

package/skills/02-design/task-breakdown/skill-spec.json

@@ -0,0 +1,25 @@
+{
+  "group": "02-design",
+  "name": "task-breakdown",
+  "description": "Split an approved change into ordered, testable work items.",
+  "title": "Task Breakdown",
+  "purpose": "Turn a design or request into a concrete execution sequence with clear boundaries.",
+  "whenToUse": [
+    "The work is too large to do in one pass.",
+    "You need to organize implementation, validation, and handoff steps.",
+    "Dependencies or risky steps need an explicit order."
+  ],
+  "how": [
+    "Break the approved change into ordered work items with clear validation points.",
+    "Keep each item small enough to finish, validate, and hand off on its own.",
+    "Call out prerequisites, blockers, and the evidence each step should produce.",
+    "Separate design cleanup from implementation execution."
+  ],
+  "whenToAvoid": [
+    "The change is already small and local.",
+    "The system shape is already settled.",
+    "You only need request-level clarification or implementation detail."
+  ],
+  "caseId": "breakdown-executable-work",
+  "source": "bootstrap-from-skill-md"
+}

package/skills/03-implementation/backend-development/SKILL.md

@@ -0,0 +1,29 @@
+---
+name: backend-development
+description: Implement server-side features, services, APIs, and data flow changes.
+---
+
+# Backend Development
+
+## Purpose
+
+Build backend code that matches the approved design and respects repository constraints.
+
+## When to Use
+
+- You need to write or refactor backend code.
+- The implementation boundary is already approved.
+- The work affects services, controllers, repositories, or server-side data flow.
+
+## How
+
+- Make the smallest code change that fits the approved scope and keep validation close by.
+- Preserve existing contracts unless the design explicitly changes them.
+- Keep service, mapper, repository, and controller changes aligned with the same path.
+- Add the closest useful test or smoke check for the changed behavior.
+
+## When to Avoid
+
+- The requirements are still unclear or incomplete.
+- The task belongs to planning or validation instead of coding.
+- You only need documentation or evidence collection.

package/skills/03-implementation/backend-development/assets/golden-prompt-suite.current.js

@@ -0,0 +1,22 @@
+#!/usr/bin/env node
+
+module.exports = {
+  "name": "backend-development.golden-prompt-suite.current",
+  "skill": "backend-development",
+  "description": "Implement server-side features, services, APIs, and data flow changes.",
+  "cases": [
+    {
+      "id": "backend-implementation-plan",
+      "prompt": "This backend capability needs implementation. Give the smallest viable approach and code changes.",
+      "expectedFirstSkill": "backend-development",
+      "expectedOutput": [
+        "implementation notes",
+        "code changes",
+        "validation"
+      ],
+      "expectedStop": "Do not expand scope.",
+      "expectedHandoff": "unit-test"
+    }
+  ]
+};
+

package/skills/03-implementation/backend-development/references/README.md

@@ -0,0 +1,17 @@
+# backend-development References
+
+This directory is local to the skill and is the only reference entry point for this skill.
+
+## Contents
+
+- `../skill-spec.json`: design source for regenerating this skill
+- `prompt-template.md`: reusable prompt wording for this skill
+- `cases.md`: human-readable replay case for this skill
+- `../assets/golden-prompt-suite.current.js`: machine-readable local case fixture
+
+## Guidance
+
+- Keep skill-specific explanation here instead of pushing it into a stage-level shared library.
+- Keep shared hard constraints in `../../../rules/index.md`.
+- Keep canonical names unchanged.
+- Skill summary: Implement server-side features, services, APIs, and data flow changes.

package/skills/03-implementation/backend-development/references/cases.md

@@ -0,0 +1,26 @@
+# backend-development
+
+## Replay Case
+
+- Case: `backend-implementation-plan`
+- First skill: `backend-development`
+
+### Prompt
+
+```text
+This backend capability needs implementation. Give the smallest viable approach and code changes.
+```
+
+### Expected Output
+
+- implementation notes
+- code changes
+- validation
+
+### Stop Rule
+
+- Do not expand scope.
+
+### Handoff
+
+- unit-test

package/skills/03-implementation/backend-development/references/prompt-template.md

@@ -0,0 +1,18 @@
+# backend-development
+
+## Prompt Template
+
+```text
+You are handling the backend-development skill.
+Goal: Implement server-side features, services, APIs, and data flow changes
+Inputs: the request, supporting evidence, constraints, and existing repository facts.
+Output contract: implementation notes, code changes, validation.
+Stop rule: Do not expand scope.
+Handoff: unit-test.
+Keep the response scoped to this stage and do not absorb the work of the next stage.
+```
+
+## Notes
+
+- Keep the template aligned with the local replay case and local assets.
+- Read `cases.md` for the matching replay example.

package/skills/03-implementation/backend-development/skill-spec.json

@@ -0,0 +1,25 @@
+{
+  "group": "03-implementation",
+  "name": "backend-development",
+  "description": "Implement server-side features, services, APIs, and data flow changes.",
+  "title": "Backend Development",
+  "purpose": "Build backend code that matches the approved design and respects repository constraints.",
+  "whenToUse": [
+    "You need to write or refactor backend code.",
+    "The implementation boundary is already approved.",
+    "The work affects services, controllers, repositories, or server-side data flow."
+  ],
+  "how": [
+    "Make the smallest code change that fits the approved scope and keep validation close by.",
+    "Preserve existing contracts unless the design explicitly changes them.",
+    "Keep service, mapper, repository, and controller changes aligned with the same path.",
+    "Add the closest useful test or smoke check for the changed behavior."
+  ],
+  "whenToAvoid": [
+    "The requirements are still unclear or incomplete.",
+    "The task belongs to planning or validation instead of coding.",
+    "You only need documentation or evidence collection."
+  ],
+  "caseId": "backend-implementation-plan",
+  "source": "bootstrap-from-skill-md"
+}

package/skills/03-implementation/bug-fix/SKILL.md

@@ -0,0 +1,29 @@
+---
+name: bug-fix
+description: Diagnose and fix an observed defect without expanding the scope.
+---
+
+# Bug Fix
+
+## Purpose
+
+Resolve a verified defect with the smallest safe change and enough validation.
+
+## When to Use
+
+- A bug is reproducible or clearly evidenced.
+- The fix should stay within the current problem scope.
+- You need to repair behavior without widening the feature request.
+
+## How
+
+- Reproduce the defect, isolate the root cause, and patch only the affected path.
+- Keep the fix narrow enough that the new behavior is easy to reason about.
+- Add a regression check that fails before the fix and passes after it.
+- Avoid opportunistic cleanup unless it is necessary to close the defect.
+
+## When to Avoid
+
+- The requirements are still unclear or incomplete.
+- The task belongs to planning or validation instead of coding.
+- You only need documentation or evidence collection.

package/skills/03-implementation/bug-fix/assets/golden-prompt-suite.current.js

@@ -0,0 +1,22 @@
+#!/usr/bin/env node
+
+module.exports = {
+  "name": "bug-fix.golden-prompt-suite.current",
+  "skill": "bug-fix",
+  "description": "Diagnose and fix an observed defect without expanding the scope.",
+  "cases": [
+    {
+      "id": "bugfix-minimal-root-cause",
+      "prompt": "This bug already reproduced. Identify the root cause and give the smallest fix.",
+      "expectedFirstSkill": "bug-fix",
+      "expectedOutput": [
+        "root cause",
+        "fix",
+        "verification"
+      ],
+      "expectedStop": "Do not broaden the scope.",
+      "expectedHandoff": "regression-check"
+    }
+  ]
+};
+

package/skills/03-implementation/bug-fix/references/README.md

@@ -0,0 +1,17 @@
+# bug-fix References
+
+This directory is local to the skill and is the only reference entry point for this skill.
+
+## Contents
+
+- `../skill-spec.json`: design source for regenerating this skill
+- `prompt-template.md`: reusable prompt wording for this skill
+- `cases.md`: human-readable replay case for this skill
+- `../assets/golden-prompt-suite.current.js`: machine-readable local case fixture
+
+## Guidance
+
+- Keep skill-specific explanation here instead of pushing it into a stage-level shared library.
+- Keep shared hard constraints in `../../../rules/index.md`.
+- Keep canonical names unchanged.
+- Skill summary: Diagnose and fix an observed defect without expanding the scope.

package/skills/03-implementation/bug-fix/references/cases.md

@@ -0,0 +1,26 @@
+# bug-fix
+
+## Replay Case
+
+- Case: `bugfix-minimal-root-cause`
+- First skill: `bug-fix`
+
+### Prompt
+
+```text
+This bug already reproduced. Identify the root cause and give the smallest fix.
+```
+
+### Expected Output
+
+- root cause
+- fix
+- verification
+
+### Stop Rule
+
+- Do not broaden the scope.
+
+### Handoff
+
+- regression-check

package/skills/03-implementation/bug-fix/references/prompt-template.md

@@ -0,0 +1,18 @@
+# bug-fix
+
+## Prompt Template
+
+```text
+You are handling the bug-fix skill.
+Goal: Diagnose and fix an observed defect without expanding the scope
+Inputs: the request, supporting evidence, constraints, and existing repository facts.
+Output contract: root cause, fix, verification.
+Stop rule: Do not broaden the scope.
+Handoff: regression-check.
+Keep the response scoped to this stage and do not absorb the work of the next stage.
+```
+
+## Notes
+
+- Keep the template aligned with the local replay case and local assets.
+- Read `cases.md` for the matching replay example.

package/skills/03-implementation/bug-fix/skill-spec.json

@@ -0,0 +1,25 @@
+{
+  "group": "03-implementation",
+  "name": "bug-fix",
+  "description": "Diagnose and fix an observed defect without expanding the scope.",
+  "title": "Bug Fix",
+  "purpose": "Resolve a verified defect with the smallest safe change and enough validation.",
+  "whenToUse": [
+    "A bug is reproducible or clearly evidenced.",
+    "The fix should stay within the current problem scope.",
+    "You need to repair behavior without widening the feature request."
+  ],
+  "how": [
+    "Reproduce the defect, isolate the root cause, and patch only the affected path.",
+    "Keep the fix narrow enough that the new behavior is easy to reason about.",
+    "Add a regression check that fails before the fix and passes after it.",
+    "Avoid opportunistic cleanup unless it is necessary to close the defect."
+  ],
+  "whenToAvoid": [
+    "The requirements are still unclear or incomplete.",
+    "The task belongs to planning or validation instead of coding.",
+    "You only need documentation or evidence collection."
+  ],
+  "caseId": "bugfix-minimal-root-cause",
+  "source": "bootstrap-from-skill-md"
+}

package/skills/03-implementation/database-change/SKILL.md

@@ -0,0 +1,29 @@
+---
+name: database-change
+description: Apply schema, index, or data migration changes with care for compatibility.
+---
+
+# Database Change
+
+## Purpose
+
+Execute database modifications safely and keep compatibility, rollback, and validation in view.
+
+## When to Use
+
+- A migration, schema change, index change, or data correction is required.
+- Data risk matters and must be controlled.
+- Backfill, rollout, or rollback planning is part of the work.
+
+## How
+
+- Plan the migration, backfill, and rollback path before touching persistent data.
+- Preserve forward and backward compatibility when the release path depends on it.
+- Validate the data shape, row counts, and any critical invariants after the change.
+- Keep application code changes separate unless the migration depends on them.
+
+## When to Avoid
+
+- The requirements are still unclear or incomplete.
+- The task belongs to planning or validation instead of coding.
+- You only need documentation or evidence collection.

package/skills/03-implementation/database-change/assets/golden-prompt-suite.current.js

@@ -0,0 +1,22 @@
+#!/usr/bin/env node
+
+module.exports = {
+  "name": "database-change.golden-prompt-suite.current",
+  "skill": "database-change",
+  "description": "Apply schema, index, or data migration changes with care for compatibility.",
+  "cases": [
+    {
+      "id": "database-migration-safety",
+      "prompt": "This change needs a database schema update. Confirm migration and rollback safety.",
+      "expectedFirstSkill": "database-change",
+      "expectedOutput": [
+        "migration steps",
+        "safety checks",
+        "rollback"
+      ],
+      "expectedStop": "Do not skip rollback planning.",
+      "expectedHandoff": "regression-check"
+    }
+  ]
+};
+

package/skills/03-implementation/database-change/references/README.md

@@ -0,0 +1,17 @@
+# database-change References
+
+This directory is local to the skill and is the only reference entry point for this skill.
+
+## Contents
+
+- `../skill-spec.json`: design source for regenerating this skill
+- `prompt-template.md`: reusable prompt wording for this skill
+- `cases.md`: human-readable replay case for this skill
+- `../assets/golden-prompt-suite.current.js`: machine-readable local case fixture
+
+## Guidance
+
+- Keep skill-specific explanation here instead of pushing it into a stage-level shared library.
+- Keep shared hard constraints in `../../../rules/index.md`.
+- Keep canonical names unchanged.
+- Skill summary: Apply schema, index, or data migration changes with care for compatibility.

package/skills/03-implementation/database-change/references/cases.md

@@ -0,0 +1,26 @@
+# database-change
+
+## Replay Case
+
+- Case: `database-migration-safety`
+- First skill: `database-change`
+
+### Prompt
+
+```text
+This change needs a database schema update. Confirm migration and rollback safety.
+```
+
+### Expected Output
+
+- migration steps
+- safety checks
+- rollback
+
+### Stop Rule
+
+- Do not skip rollback planning.
+
+### Handoff
+
+- regression-check

package/skills/03-implementation/database-change/references/prompt-template.md

@@ -0,0 +1,18 @@
+# database-change
+
+## Prompt Template
+
+```text
+You are handling the database-change skill.
+Goal: Apply schema, index, or data migration changes with care for compatibility
+Inputs: the request, supporting evidence, constraints, and existing repository facts.
+Output contract: migration steps, safety checks, rollback.
+Stop rule: Do not skip rollback planning.
+Handoff: regression-check.
+Keep the response scoped to this stage and do not absorb the work of the next stage.
+```
+
+## Notes
+
+- Keep the template aligned with the local replay case and local assets.
+- Read `cases.md` for the matching replay example.