@pigcloud/skills 1.0.10 → 1.1.2

package/skills/03-implementation/database-change/skill-spec.json

@@ -0,0 +1,25 @@
+{
+  "group": "03-implementation",
+  "name": "database-change",
+  "description": "Apply schema, index, or data migration changes with care for compatibility.",
+  "title": "Database Change",
+  "purpose": "Execute database modifications safely and keep compatibility, rollback, and validation in view.",
+  "whenToUse": [
+    "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."
+  ],
+  "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": "database-migration-safety",
+  "source": "bootstrap-from-skill-md"
+}

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

@@ -0,0 +1,29 @@
+---
+name: frontend-development
+description: Implement UI behavior, components, and client-side data flow changes.
+---
+
+# Frontend Development
+
+## Purpose
+
+Build frontend code that follows the approved UX, contract, and repository conventions.
+
+## When to Use
+
+- You need to change a UI, client-side workflow, or view-level state.
+- The interface shape is already known.
+- Accessibility, responsiveness, or client-side validation matters.
+
+## How
+
+- Implement the component or view change with the smallest safe UI surface area.
+- Keep state, effects, and data fetching close to the feature boundary.
+- Preserve layout, keyboard, and accessibility behavior unless the change requires otherwise.
+- Validate the path in a browser or UI test before handing off.
+
+## 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/frontend-development/assets/golden-prompt-suite.current.js

@@ -0,0 +1,22 @@
+#!/usr/bin/env node
+
+module.exports = {
+  "name": "frontend-development.golden-prompt-suite.current",
+  "skill": "frontend-development",
+  "description": "Implement UI behavior, components, and client-side data flow changes.",
+  "cases": [
+    {
+      "id": "frontend-implementation-plan",
+      "prompt": "This frontend page or component needs implementation. Outline the key steps and constraints.",
+      "expectedFirstSkill": "frontend-development",
+      "expectedOutput": [
+        "component changes",
+        "state handling",
+        "validation"
+      ],
+      "expectedStop": "Do not change unrelated UI.",
+      "expectedHandoff": "unit-test"
+    }
+  ]
+};
+

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

@@ -0,0 +1,17 @@
+# frontend-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 UI behavior, components, and client-side data flow changes.

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

@@ -0,0 +1,26 @@
+# frontend-development
+
+## Replay Case
+
+- Case: `frontend-implementation-plan`
+- First skill: `frontend-development`
+
+### Prompt
+
+```text
+This frontend page or component needs implementation. Outline the key steps and constraints.
+```
+
+### Expected Output
+
+- component changes
+- state handling
+- validation
+
+### Stop Rule
+
+- Do not change unrelated UI.
+
+### Handoff
+
+- unit-test

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

@@ -0,0 +1,18 @@
+# frontend-development
+
+## Prompt Template
+
+```text
+You are handling the frontend-development skill.
+Goal: Implement UI behavior, components, and client-side data flow changes
+Inputs: the request, supporting evidence, constraints, and existing repository facts.
+Output contract: component changes, state handling, validation.
+Stop rule: Do not change unrelated UI.
+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/frontend-development/skill-spec.json

@@ -0,0 +1,25 @@
+{
+  "group": "03-implementation",
+  "name": "frontend-development",
+  "description": "Implement UI behavior, components, and client-side data flow changes.",
+  "title": "Frontend Development",
+  "purpose": "Build frontend code that follows the approved UX, contract, and repository conventions.",
+  "whenToUse": [
+    "You need to change a UI, client-side workflow, or view-level state.",
+    "The interface shape is already known.",
+    "Accessibility, responsiveness, or client-side validation matters."
+  ],
+  "how": [
+    "Implement the component or view change with the smallest safe UI surface area.",
+    "Keep state, effects, and data fetching close to the feature boundary.",
+    "Preserve layout, keyboard, and accessibility behavior unless the change requires otherwise.",
+    "Validate the path in a browser or UI test before handing off."
+  ],
+  "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": "frontend-implementation-plan",
+  "source": "bootstrap-from-skill-md"
+}

package/skills/04-validation/code-review/SKILL.md

@@ -0,0 +1,29 @@
+---
+name: code-review
+description: Review a diff or pull request for correctness, maintainability, and risk.
+---
+
+# Code Review
+
+## Purpose
+
+Assess the change for bugs, regressions, clarity, and maintainability before merge.
+
+## When to Use
+
+- You need review findings for a completed diff.
+- The task is to judge quality, not implement code.
+- You need findings that are tied to evidence in the patch.
+
+## How
+
+- Inspect the diff for correctness, maintainability, and regression risk, then report actionable findings.
+- Anchor each finding to a concrete location, impact, and fix path.
+- Rank findings by severity and keep the report focused on the submitted change.
+- If evidence is weak, collect more proof before calling it a finding.
+
+## When to Avoid
+
+- You still need design or implementation work.
+- The task is about a different validation subtype.
+- You need to rewrite code instead of reviewing it.

package/skills/04-validation/code-review/assets/golden-prompt-suite.current.js

@@ -0,0 +1,22 @@
+#!/usr/bin/env node
+
+module.exports = {
+  "name": "code-review.golden-prompt-suite.current",
+  "skill": "code-review",
+  "description": "Review a diff or pull request for correctness, maintainability, and risk.",
+  "cases": [
+    {
+      "id": "review-diff-correctness",
+      "prompt": "Review this diff for correctness, maintainability, and regression risk.",
+      "expectedFirstSkill": "code-review",
+      "expectedOutput": [
+        "findings",
+        "severity",
+        "fix recommendations"
+      ],
+      "expectedStop": "Do not refactor the code inside the review step.",
+      "expectedHandoff": "evidence-collector"
+    }
+  ]
+};
+

package/skills/04-validation/code-review/references/README.md

@@ -0,0 +1,17 @@
+# code-review 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: Review a diff or pull request for correctness, maintainability, and risk.

package/skills/04-validation/code-review/references/cases.md

@@ -0,0 +1,26 @@
+# code-review
+
+## Replay Case
+
+- Case: `review-diff-correctness`
+- First skill: `code-review`
+
+### Prompt
+
+```text
+Review this diff for correctness, maintainability, and regression risk.
+```
+
+### Expected Output
+
+- findings
+- severity
+- fix recommendations
+
+### Stop Rule
+
+- Do not refactor the code inside the review step.
+
+### Handoff
+
+- evidence-collector

package/skills/04-validation/code-review/references/prompt-template.md

@@ -0,0 +1,18 @@
+# code-review
+
+## Prompt Template
+
+```text
+You are handling the code-review skill.
+Goal: Review a diff or pull request for correctness, maintainability, and risk
+Inputs: the request, supporting evidence, constraints, and existing repository facts.
+Output contract: findings, severity, fix recommendations.
+Stop rule: Do not refactor the code inside the review step.
+Handoff: evidence-collector.
+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/04-validation/code-review/skill-spec.json

@@ -0,0 +1,25 @@
+{
+  "group": "04-validation",
+  "name": "code-review",
+  "description": "Review a diff or pull request for correctness, maintainability, and risk.",
+  "title": "Code Review",
+  "purpose": "Assess the change for bugs, regressions, clarity, and maintainability before merge.",
+  "whenToUse": [
+    "You need review findings for a completed diff.",
+    "The task is to judge quality, not implement code.",
+    "You need findings that are tied to evidence in the patch."
+  ],
+  "how": [
+    "Inspect the diff for correctness, maintainability, and regression risk, then report actionable findings.",
+    "Anchor each finding to a concrete location, impact, and fix path.",
+    "Rank findings by severity and keep the report focused on the submitted change.",
+    "If evidence is weak, collect more proof before calling it a finding."
+  ],
+  "whenToAvoid": [
+    "You still need design or implementation work.",
+    "The task is about a different validation subtype.",
+    "You need to rewrite code instead of reviewing it."
+  ],
+  "caseId": "review-diff-correctness",
+  "source": "bootstrap-from-skill-md"
+}

package/skills/04-validation/performance-review/SKILL.md

@@ -0,0 +1,29 @@
+---
+name: performance-review
+description: Review changes for latency, throughput, memory, and load risk.
+---
+
+# Performance Review
+
+## Purpose
+
+Assess whether the change introduces a measurable performance problem or hot path risk.
+
+## When to Use
+
+- The change may affect response time or resource usage.
+- You need performance-oriented findings.
+- The task mentions latency, throughput, memory, load, or hot paths.
+
+## How
+
+- Trace hot paths, expensive calls, and resource pressure before recommending optimizations.
+- Name the concrete bottleneck path and what resource it stresses.
+- Estimate the likely impact and keep the fix suggestion small.
+- Avoid vague "might be slow" comments without a measurable path.
+
+## When to Avoid
+
+- You still need design or implementation work.
+- The task is about a different validation subtype.
+- You need to rewrite code instead of reviewing it.

package/skills/04-validation/performance-review/assets/golden-prompt-suite.current.js

@@ -0,0 +1,22 @@
+#!/usr/bin/env node
+
+module.exports = {
+  "name": "performance-review.golden-prompt-suite.current",
+  "skill": "performance-review",
+  "description": "Review changes for latency, throughput, memory, and load risk.",
+  "cases": [
+    {
+      "id": "performance-bottleneck-check",
+      "prompt": "Check whether this change introduces latency, throughput, or resource pressure risks.",
+      "expectedFirstSkill": "performance-review",
+      "expectedOutput": [
+        "performance findings",
+        "bottleneck map",
+        "optimization advice"
+      ],
+      "expectedStop": "Do not rewrite code.",
+      "expectedHandoff": "regression-check"
+    }
+  ]
+};
+

package/skills/04-validation/performance-review/references/README.md

@@ -0,0 +1,17 @@
+# performance-review 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: Review changes for latency, throughput, memory, and load risk.

package/skills/04-validation/performance-review/references/cases.md

@@ -0,0 +1,26 @@
+# performance-review
+
+## Replay Case
+
+- Case: `performance-bottleneck-check`
+- First skill: `performance-review`
+
+### Prompt
+
+```text
+Check whether this change introduces latency, throughput, or resource pressure risks.
+```
+
+### Expected Output
+
+- performance findings
+- bottleneck map
+- optimization advice
+
+### Stop Rule
+
+- Do not rewrite code.
+
+### Handoff
+
+- regression-check

package/skills/04-validation/performance-review/references/prompt-template.md

@@ -0,0 +1,18 @@
+# performance-review
+
+## Prompt Template
+
+```text
+You are handling the performance-review skill.
+Goal: Review changes for latency, throughput, memory, and load risk
+Inputs: the request, supporting evidence, constraints, and existing repository facts.
+Output contract: performance findings, bottleneck map, optimization advice.
+Stop rule: Do not rewrite code.
+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/04-validation/performance-review/skill-spec.json

@@ -0,0 +1,25 @@
+{
+  "group": "04-validation",
+  "name": "performance-review",
+  "description": "Review changes for latency, throughput, memory, and load risk.",
+  "title": "Performance Review",
+  "purpose": "Assess whether the change introduces a measurable performance problem or hot path risk.",
+  "whenToUse": [
+    "The change may affect response time or resource usage.",
+    "You need performance-oriented findings.",
+    "The task mentions latency, throughput, memory, load, or hot paths."
+  ],
+  "how": [
+    "Trace hot paths, expensive calls, and resource pressure before recommending optimizations.",
+    "Name the concrete bottleneck path and what resource it stresses.",
+    "Estimate the likely impact and keep the fix suggestion small.",
+    "Avoid vague \"might be slow\" comments without a measurable path."
+  ],
+  "whenToAvoid": [
+    "You still need design or implementation work.",
+    "The task is about a different validation subtype.",
+    "You need to rewrite code instead of reviewing it."
+  ],
+  "caseId": "performance-bottleneck-check",
+  "source": "bootstrap-from-skill-md"
+}

package/skills/04-validation/regression-check/SKILL.md

@@ -0,0 +1,29 @@
+---
+name: regression-check
+description: Verify that the change does not break existing behavior or release assumptions.
+---
+
+# Regression Check
+
+## Purpose
+
+Confirm the change is safe for surrounding behaviors, flows, and release expectations.
+
+## When to Use
+
+- You need a final safety pass after implementation.
+- The change could affect unrelated paths.
+- Nearby flows, defaults, or release assumptions could change.
+
+## How
+
+- Compare the change against nearby behaviors, then confirm the surrounding flows still hold.
+- Check the happy path, the fallback path, and the failure path around the change.
+- Confirm any shared contract, flag, or default still behaves as expected.
+- Note anything that should be monitored after release.
+
+## When to Avoid
+
+- You still need design or implementation work.
+- The task is about a different validation subtype.
+- You need to rewrite code instead of reviewing it.

package/skills/04-validation/regression-check/assets/golden-prompt-suite.current.js

@@ -0,0 +1,22 @@
+#!/usr/bin/env node
+
+module.exports = {
+  "name": "regression-check.golden-prompt-suite.current",
+  "skill": "regression-check",
+  "description": "Verify that the change does not break existing behavior or release assumptions.",
+  "cases": [
+    {
+      "id": "regression-behavior-scan",
+      "prompt": "The change is complete. Check whether related behavior broke.",
+      "expectedFirstSkill": "regression-check",
+      "expectedOutput": [
+        "regression matrix",
+        "safety check",
+        "remaining risk"
+      ],
+      "expectedStop": "Do not change production code.",
+      "expectedHandoff": "release-check"
+    }
+  ]
+};
+

package/skills/04-validation/regression-check/references/README.md

@@ -0,0 +1,17 @@
+# regression-check 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: Verify that the change does not break existing behavior or release assumptions.

package/skills/04-validation/regression-check/references/cases.md

@@ -0,0 +1,26 @@
+# regression-check
+
+## Replay Case
+
+- Case: `regression-behavior-scan`
+- First skill: `regression-check`
+
+### Prompt
+
+```text
+The change is complete. Check whether related behavior broke.
+```
+
+### Expected Output
+
+- regression matrix
+- safety check
+- remaining risk
+
+### Stop Rule
+
+- Do not change production code.
+
+### Handoff
+
+- release-check

package/skills/04-validation/regression-check/references/prompt-template.md

@@ -0,0 +1,18 @@
+# regression-check
+
+## Prompt Template
+
+```text
+You are handling the regression-check skill.
+Goal: Verify that the change does not break existing behavior or release assumptions
+Inputs: the request, supporting evidence, constraints, and existing repository facts.
+Output contract: regression matrix, safety check, remaining risk.
+Stop rule: Do not change production code.
+Handoff: release-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/04-validation/regression-check/skill-spec.json

@@ -0,0 +1,25 @@
+{
+  "group": "04-validation",
+  "name": "regression-check",
+  "description": "Verify that the change does not break existing behavior or release assumptions.",
+  "title": "Regression Check",
+  "purpose": "Confirm the change is safe for surrounding behaviors, flows, and release expectations.",
+  "whenToUse": [
+    "You need a final safety pass after implementation.",
+    "The change could affect unrelated paths.",
+    "Nearby flows, defaults, or release assumptions could change."
+  ],
+  "how": [
+    "Compare the change against nearby behaviors, then confirm the surrounding flows still hold.",
+    "Check the happy path, the fallback path, and the failure path around the change.",
+    "Confirm any shared contract, flag, or default still behaves as expected.",
+    "Note anything that should be monitored after release."
+  ],
+  "whenToAvoid": [
+    "You still need design or implementation work.",
+    "The task is about a different validation subtype.",
+    "You need to rewrite code instead of reviewing it."
+  ],
+  "caseId": "regression-behavior-scan",
+  "source": "bootstrap-from-skill-md"
+}

package/skills/04-validation/security-review/SKILL.md

@@ -0,0 +1,29 @@
+---
+name: security-review
+description: Review changes for authorization, data exposure, secrets, and abuse risk.
+---
+
+# Security Review
+
+## Purpose
+
+Find security weaknesses and recommend the smallest safe mitigation.
+
+## When to Use
+
+- The change touches auth, secrets, data access, user input, or trust boundaries.
+- You need a security-specific review.
+- The risk is about exposure, privilege, or abuse rather than correctness alone.
+
+## How
+
+- Check auth, data exposure, input handling, and trust boundaries before merge.
+- Trace how untrusted input reaches sensitive operations or secrets.
+- State the attack path, impacted asset, and minimum fix needed to close it.
+- Keep findings focused on concrete exploitability or exposure.
+
+## When to Avoid
+
+- You still need design or implementation work.
+- The task is about a different validation subtype.
+- You need to rewrite code instead of reviewing it.

package/skills/04-validation/security-review/assets/golden-prompt-suite.current.js

@@ -0,0 +1,22 @@
+#!/usr/bin/env node
+
+module.exports = {
+  "name": "security-review.golden-prompt-suite.current",
+  "skill": "security-review",
+  "description": "Review changes for authorization, data exposure, secrets, and abuse risk.",
+  "cases": [
+    {
+      "id": "security-risk-check",
+      "prompt": "Check whether this change introduces auth, injection, or data exposure risks.",
+      "expectedFirstSkill": "security-review",
+      "expectedOutput": [
+        "security findings",
+        "risk level",
+        "mitigation"
+      ],
+      "expectedStop": "Do not rewrite code.",
+      "expectedHandoff": "regression-check"
+    }
+  ]
+};
+