@pigcloud/skills 1.0.11 → 1.1.2

package/skills/references/golden-prompt-suite.js

@@ -1,436 +0,0 @@
-function makeCase(skill, id, prompt, expectedOutput, expectedStop, expectedHandoff) {
-  return {
-    id,
-    prompt,
-    expectedFirstSkill: skill,
-    expectedOutput,
-    expectedStop,
-    expectedHandoff,
-  };
-}
-
-const cases = [
-  makeCase(
-    'workflow-router',
-    'router-unclear-stage',
-    'We have a new request but I am not sure which stage should handle it.',
-    ['next skill', 'stage decision', 'handoff note'],
-    'Do not perform the target skill\'s work.',
-    'spec-refinement',
-  ),
-  makeCase(
-    'workflow-router',
-    'router-approved-brief',
-    'The brief is ready. Which stage should receive it next?',
-    ['next skill', 'stage decision', 'handoff note'],
-    'Do not perform the target skill\'s work.',
-    'spec-refinement',
-  ),
-  makeCase(
-    'workflow-router',
-    'router-before-coding',
-    'This needs architecture help before coding. Route it.',
-    ['next skill', 'stage decision', 'handoff note'],
-    'Do not perform the target skill\'s work.',
-    'technical-design',
-  ),
-
-  makeCase(
-    'spec-refinement',
-    'product-reminder-feature',
-    'We need a reminder feature for inactive users.',
-    ['product brief', 'scope', 'acceptance outline', 'open questions'],
-    'Do not jump into design or code.',
-    'spec-refinement',
-  ),
-  makeCase(
-    'spec-refinement',
-    'product-retention-gap',
-    'Users keep missing renewal emails; help me define the product scope.',
-    ['product objective', 'scope', 'acceptance outline', 'open questions'],
-    'Do not decide implementation details.',
-    'spec-refinement',
-  ),
-  makeCase(
-    'spec-refinement',
-    'product-unclear-opportunity',
-    'We think there is a retention problem, but the exact feature is unclear.',
-    ['product objective', 'scope', 'acceptance outline', 'open questions'],
-    'Do not write technical design.',
-    'spec-refinement',
-  ),
-
-  makeCase(
-    'spec-refinement',
-    'spec-approved-brief',
-    'The brief is approved; turn it into an executable spec-refinement and task breakdown.',
-    ['executable spec-refinement', 'task breakdown plan', 'acceptance criteria', 'confirmation package'],
-    'Do not generate code or reopen discovery.',
-    'feature-build',
-  ),
-  makeCase(
-    'spec-refinement',
-    'spec-code-alignment',
-    'Compare the PRD with current project facts and implementation evidence, then produce the engineering spec-refinement.',
-    ['execution direction plan', 'impact scope', 'implementation inputs', 'conflict map'],
-    'Do not jump into implementation.',
-    'technical-design',
-  ),
-  makeCase(
-    'spec-refinement',
-    'spec-confirmation-pack',
-    'I need a confirmation package with the spec-refinement, tasks, and acceptance criteria before coding.',
-    ['executable spec-refinement', 'task breakdown plan', 'confirmation package'],
-    'Do not write code.',
-    'feature-build',
-  ),
-
-  makeCase(
-    'spec-refinement',
-    'spec-approved-brief',
-    'The brief is approved; turn it into an executable spec-refinement.',
-    ['executable spec-refinement', 'acceptance criteria', 'impact scope', 'implementation inputs'],
-    'Do not rewrite the PRD or code the change.',
-    'feature-build',
-  ),
-  makeCase(
-    'spec-refinement',
-    'spec-code-gap',
-    'Compare the PRD with the current code and identify gaps.',
-    ['executable spec-refinement', 'impact scope', 'implementation inputs'],
-    'Do not jump into implementation.',
-    'feature-build',
-  ),
-  makeCase(
-    'spec-refinement',
-    'spec-align-with-code',
-    'The requirement is messy; align it with existing behavior and make it engineer-ready.',
-    ['executable spec-refinement', 'acceptance criteria', 'implementation input summary'],
-    'Do not rewrite the PRD.',
-    'technical-design',
-  ),
-
-  makeCase(
-    'technical-design',
-    'design-cross-module',
-    'This change touches multiple modules, cache behavior, and compatibility; help me plan it.',
-    ['design decisions', 'dependency map', 'interface contract', 'implementation constraints'],
-    'Do not start implementation.',
-    'feature-build',
-  ),
-  makeCase(
-    'technical-design',
-    'design-boundaries',
-    'Design the module boundaries, dependencies, and rollback path.',
-    ['design decisions', 'dependency map', 'interface contract', 'implementation constraints'],
-    'Do not reopen product discovery.',
-    'feature-build',
-  ),
-  makeCase(
-    'technical-design',
-    'design-interface-contract',
-    'I need an interface contract before anyone starts coding.',
-    ['interface contract', 'implementation constraints'],
-    'Do not produce full code.',
-    'feature-build',
-  ),
-
-  makeCase(
-    'feature-build',
-    'build-approved-spec',
-    'Implement the approved spec-refinement in the controller and service.',
-    ['code changes', 'implementation notes', 'validation evidence'],
-    'Do not expand scope or rewrite requirements.',
-    'test-design',
-  ),
-  makeCase(
-    'feature-build',
-    'build-scope-stable',
-    'Make the local code changes but keep the scope stable.',
-    ['code changes', 'implementation notes', 'validation evidence'],
-    'Do not change the agreed boundaries.',
-    'test-design',
-  ),
-  makeCase(
-    'feature-build',
-    'build-simple-refactor',
-    'This controller needs a simple refactor that does not change behavior.',
-    ['code changes', 'implementation notes', 'validation evidence'],
-    'Do not rewrite the spec-refinement.',
-    'test-design',
-  ),
-
-  makeCase(
-    'test-design',
-    'test-coverage',
-    'Design test coverage and validate the change.',
-    ['test strategy', 'test cases', 'regression matrix', 'validation result'],
-    'Do not modify production code.',
-    'code-review',
-  ),
-  makeCase(
-    'test-design',
-    'test-regression-matrix',
-    'The feature is implemented; give me a regression matrix.',
-    ['test strategy', 'regression matrix', 'validation result'],
-    'Do not rewrite the PRD.',
-    'code-review',
-  ),
-  makeCase(
-    'test-design',
-    'test-edge-cases',
-    'I need edge cases and validation paths for this change.',
-    ['test cases', 'validation result'],
-    'Do not replace code review.',
-    'code-review',
-  ),
-
-  makeCase(
-    'code-review',
-    'review-correctness',
-    'Review this diff for correctness and safety.',
-    ['findings with severity', 'fix recommendations'],
-    'Do not refactor the code inside the review step.',
-    'knowledge-capture',
-  ),
-  makeCase(
-    'code-review',
-    'review-maintainability',
-    'Find maintainability issues in this PR.',
-    ['findings', 'severity', 'fix recommendations'],
-    'Do not perform implementation refactors.',
-    'knowledge-capture',
-  ),
-  makeCase(
-    'code-review',
-    'review-regression',
-    'Check whether this change introduces regressions.',
-    ['findings', 'severity', 'fix recommendations'],
-    'Do not turn review into a design task.',
-    'knowledge-capture',
-  ),
-
-  makeCase(
-    'knowledge-capture',
-    'capture-decisions',
-    'Capture the reusable decisions and pitfalls from this task.',
-    ['reusable note', 'handoff summary'],
-    'Do not redo upstream analysis.',
-    null,
-  ),
-  makeCase(
-    'knowledge-capture',
-    'capture-summary',
-    'Summarize the decisions, pitfalls, and reusable notes from this task.',
-    ['reusable note', 'knowledge page', 'handoff summary'],
-    'Do not generate new requirements or code.',
-    null,
-  ),
-  makeCase(
-    'knowledge-capture',
-    'capture-decision-log',
-    'Turn these findings into a reusable note for future work.',
-    ['reusable note', 'handoff summary'],
-    'Do not reopen the design or implementation debate.',
-    null,
-  ),
-
-  makeCase(
-    'api-contract-docs',
-    'api-profile-docs',
-    'Document the user profile endpoints with request and response shapes.',
-    ['API document', 'contract notes', 'examples'],
-    'Do not change implementation.',
-    'knowledge-capture',
-  ),
-  makeCase(
-    'api-contract-docs',
-    'api-payment-contract',
-    'Write the contract for this payment endpoint with examples.',
-    ['API document', 'contract notes', 'examples'],
-    'Do not rewrite product scope.',
-    'knowledge-capture',
-  ),
-  makeCase(
-    'api-contract-docs',
-    'api-openapi-notes',
-    'Capture the OpenAPI notes for a new endpoint.',
-    ['API document', 'contract notes', 'examples'],
-    'Do not change implementation or product scope.',
-    'knowledge-capture',
-  ),
-
-  makeCase(
-    'domain-modeling',
-    'domain-reverse-engineer',
-    'Reverse engineer the customer order domain from this codebase and docs.',
-    ['domain map', 'core concepts', 'boundary notes'],
-    'Do not implement code.',
-    'technical-design',
-  ),
-  makeCase(
-    'domain-modeling',
-    'domain-boundary-split',
-    'Split the billing and account concepts into boundaries.',
-    ['domain map', 'core concepts', 'boundary notes'],
-    'Do not write PRD text.',
-    'technical-design',
-  ),
-  makeCase(
-    'domain-modeling',
-    'domain-language-extraction',
-    'Extract ubiquitous language from the current product notes.',
-    ['domain map', 'core concepts', 'boundary notes'],
-    'Do not write implementation code.',
-    'spec-refinement',
-  ),
-
-  makeCase(
-    'business-fact-extraction',
-    'business-fact-extraction-from-code',
-    'Extract the business facts expressed by this order-processing code and explain the current behavior.',
-    ['code fact map', 'business fact map', 'codewiki delta'],
-    'Do not design a new solution.',
-    'knowledge-capture',
-  ),
-  makeCase(
-    'business-fact-extraction',
-    'extract-business-invariants',
-    'From these service methods and tests, identify the business invariants and open questions.',
-    ['code fact map', 'business fact map', 'codewiki delta'],
-    'Do not rewrite the PRD.',
-    'domain-modeling',
-  ),
-  makeCase(
-    'business-fact-extraction',
-    'extract-code-backed-terms',
-    'Turn this controller, service, and database flow into a terminology map with evidence.',
-    ['code fact map', 'business fact map', 'codewiki delta'],
-    'Do not generate code.',
-    'spec-refinement',
-  ),
-
-  makeCase(
-    'security-audit',
-    'security-injection-auth',
-    'Check this change for injection, auth, and secret handling issues.',
-    ['security findings', 'risk level', 'mitigation advice'],
-    'Do not rewrite code.',
-    'knowledge-capture',
-  ),
-  makeCase(
-    'security-audit',
-    'security-permissions',
-    'Review permission boundaries and data exposure risks.',
-    ['security findings', 'risk level', 'mitigation advice'],
-    'Do not turn into a general review.',
-    'knowledge-capture',
-  ),
-  makeCase(
-    'security-audit',
-    'security-bypass-check',
-    'Find any auth bypass or sensitive-data leaks in this diff.',
-    ['security findings', 'risk level', 'mitigation advice'],
-    'Do not rewrite code or broaden the scope.',
-    'knowledge-capture',
-  ),
-
-  makeCase(
-    'performance-audit',
-    'perf-slow-endpoint',
-    'This endpoint is slow; inspect query cost, cache, and concurrency.',
-    ['performance findings', 'bottleneck map', 'optimization advice'],
-    'Do not rewrite code.',
-    'knowledge-capture',
-  ),
-  makeCase(
-    'performance-audit',
-    'perf-hot-path',
-    'Find bottlenecks in the hot path and suggest improvements.',
-    ['performance findings', 'bottleneck map', 'optimization advice'],
-    'Do not turn into a general review.',
-    'knowledge-capture',
-  ),
-  makeCase(
-    'performance-audit',
-    'perf-memory-latency',
-    'Review memory pressure and response latency risks.',
-    ['performance findings', 'bottleneck map', 'optimization advice'],
-    'Do not rewrite code or broaden the scope.',
-    'knowledge-capture',
-  ),
-
-  makeCase(
-    'project-bootstrap',
-    'bootstrap-new-workspace',
-    'Set up a new workspace for Codex with the right skills and rules.',
-    ['starter structure', 'installed bundle', 'setup notes'],
-    'Do not design product scope.',
-    'workflow-router',
-  ),
-  makeCase(
-    'project-bootstrap',
-    'bootstrap-skill-bundle',
-    'Install the initial skill bundle for a new project.',
-    ['starter structure', 'installed bundle', 'setup notes'],
-    'Do not generate application code.',
-    'workflow-router',
-  ),
-  makeCase(
-    'project-bootstrap',
-    'bootstrap-scaffold',
-    'Bootstrap a fresh repository scaffold and hand it off.',
-    ['starter structure', 'installed bundle', 'setup notes'],
-    'Do not start feature implementation.',
-    'spec-refinement',
-  ),
-
-  makeCase(
-    'environment-deploy',
-    'deploy-runtime-prereqs',
-    'Prepare the runtime and deployment prerequisites for this workspace.',
-    ['environment plan', 'deployment notes', 'bootstrap instructions'],
-    'Do not change product scope.',
-    'feature-build',
-  ),
-  makeCase(
-    'environment-deploy',
-    'deploy-target-setup',
-    'Set up the deployment target and document the bootstrap steps.',
-    ['environment plan', 'deployment notes', 'bootstrap instructions'],
-    'Do not generate business logic.',
-    'project-bootstrap',
-  ),
-  makeCase(
-    'environment-deploy',
-    'deploy-environment-check',
-    'Verify the environment before feature work starts.',
-    ['environment plan', 'deployment notes', 'bootstrap instructions'],
-    'Do not change product scope or generate business logic.',
-    'feature-build',
-  ),
-
-  makeCase(
-    'spec-refinement',
-    'negative-direct-code',
-    'Just code it, the PRD is small.',
-    ['executable spec-refinement'],
-    'Do not jump directly into implementation.',
-    'feature-build',
-  ),
-  makeCase(
-    'code-review',
-    'negative-review-refactor',
-    'Review this change by refactoring it.',
-    ['findings', 'severity'],
-    'Do not perform implementation refactors.',
-    'knowledge-capture',
-  ),
-];
-
-module.exports = {
-  name: 'golden-prompt-suite',
-  purpose: 'Golden prompt set for replay testing the full skill chain.',
-  cases,
-};
-

package/skills/references/golden-prompt-suite.md

@@ -1,33 +0,0 @@
-# 金标提示词套件
-
-## 目的
-
-这套提示词用于真实回放测试。每个 case 都定义了预期首个 skill、返回工件、停止边界和交接目标。
-
-源码是真正的权威：[`golden-prompt-suite.js`](golden-prompt-suite.js)。运行器会直接加载这个文件。
-
-## 使用方式
-
-1. 把提示词发给 skill router 或者直接发给目标 skill。
-2. 对照预期首个 skill 检查结果。
-3. 检查输出工件是否符合预期形状。
-4. 确认 skill 是否停在指定边界。
-5. 验证下一跳是否是预期的交接目标。
-
-## 覆盖范围
-
-- 每个 canonical skill 3 个 case
-- 2 个用于边界回归的负向 case
-- 共 44 个 case
-
-## 运行
-
-- `npm run replay:golden`：真实模型回放
-- `npm run replay:golden:mock`：本地 harness 检查
-
-## 输出字段
-
-- 首个 skill
-- 工件
-- stop rule
-- 交接

package/skills/references/project-requirement-alignment.md

@@ -1,42 +0,0 @@
-# Project Requirement Alignment
-
-## Goal
-
-Use this guide when a task needs both product intent and current project facts.
-
-## Read First
-
-- Product brief or draft PRD
-- Current project facts from repo docs, release notes, or existing behavior
-- Known constraints from the current codebase or operating environment
-
-## Alignment Steps
-
-1. Summarize the product intent in one short paragraph.
-2. Summarize what the current project already does or guarantees.
-3. Mark what is unchanged, what must change, and what is still unknown.
-4. Record conflicts between product demand and current project facts.
-5. Turn the result into either a product brief or an executable spec-refinement, depending on the stage.
-
-## Output Shape
-
-- product intent summary
-- current project facts summary
-- alignment notes
-- open questions
-- execution direction notes
-- acceptance deltas
-- task breakdown plan
-
-## Rules
-
-- Do not merge product intent and project facts into one vague statement.
-- Do not rewrite implementation details as requirements.
-- Do not skip conflicts just because the requirement sounds simple.
-- Do not move into code generation from this guide.
-
-## References
-
-- `skills/references/requirements-separation-map.md`
-- `docs/engineering-workflow.md`
-

package/skills/references/rule-loading-map.md

@@ -1,117 +0,0 @@
-# Rule Loading Map
-
-## Goal
-
-Keep rule loading separate from skill routing. Load the smallest rule set that matches the current task, then add the stack-specific overlay only when needed. When changed files are available, prefer them over workspace-wide heuristics.
-
-## Governance Context
-
-- `workflow-router` decides the next stage.
-- `skills/` decides the reusable execution pattern.
-- `rules/` decides the project constraints and must/never checks.
-- `CI / Test / Evidence` decides whether the result can be accepted.
-- For the higher-level explanation, see [docs/agent-governance-overview.md](../../docs/agent-governance-overview.md).
-
-## Load Order
-
-### 1. Core Layer
-
-Use the core layer when the task is generic, the routing is unclear, or the current workspace does not need more specific rules yet.
-
-- `rules/index.md`
-- `rules/core/index.md`
-- `rules/skill-profile-map.md`
-- `PIG_SKILLS_RULE_SKILL=workflow-router`
-
-### 2. Workflow Layer
-
-Use the workflow layer when the task involves routing, handoff, boundary changes, or stage switching.
-
-- `rules/workflow/index.md`
-- `rules/workflow/refinement.md`
-- `rules/workflow/router.md`
-- `rules/workflow/selection.md`
-- `rules/workflow/stop.md`
-- `PIG_SKILLS_RULE_PROFILE=router|refinement`
-- `PIG_SKILLS_RULE_SKILL=workflow-router|spec-refinement`
-
-### 3. Coding Layer
-
-Use the coding layer when the task involves implementation, refactoring, testing, or scaffolding.
-
-- `rules/coding/index.md`
-- `rules/coding/analysis.md`
-- `rules/coding/implementation.md`
-- `rules/coding/testing.md`
-- `rules/coding/scaffold.md`
-- `rules/coding/boundary.md`
-- `rules/coding/validation.md`
-- `rules/coding/backend/index.md`
-- `rules/coding/backend/database.md`
-- `rules/coding/backend/query.md`
-- `rules/coding/backend/remote.md`
-- `rules/coding/backend/feign.md`
-- `rules/coding/backend/transaction-boundary.md`
-- `rules/coding/backend/transaction-rollback.md`
-- `rules/coding/backend/cache-keying.md`
-- `rules/coding/backend/cache-invalidation.md`
-- `PIG_SKILLS_RULE_PROFILE=analysis|implementation|testing|scaffold`
-- `PIG_SKILLS_RULE_SKILL=technical-design|feature-build|test-design|project-bootstrap|environment-deploy`
-
-### 4. Review Layer
-
-Use the review layer when the task involves code review, security review, performance review, or a quality gate.
-
-- `rules/review/index.md`
-- `rules/review/code.md`
-- `rules/review/java.md`
-- `rules/review/vue.md`
-- `rules/review/ts.md`
-- `rules/review/security.md`
-- `rules/review/performance.md`
-- `rules/review/rubric.md`
-- `rules/review/evidence.md`
-- `PIG_SKILLS_RULE_PROFILE=code|code-java|code-vue|code-ts|security|performance`
-- `PIG_SKILLS_RULE_SKILL=code-review|security-audit|performance-audit`
-
-`code-review` now resolves to `code` in this repository. The loader keeps the generic review profile first, then auto-adds stack overlays such as `code-java`, `code-vue`, and `code-ts` when the workspace or changed-file signal indicates those stacks.
-
-- `PIG_SKILLS_CHANGED_FILES` can be used to pass changed paths for more precise review overlay routing.
-
-### 5. Product / Docs Layer
-
-Use the product/docs layer when the task involves requirement intake, reverse-engineered business facts, domain modeling, API docs, knowledge capture, or contract writing.
-
-- `rules/product/index.md`
-- `rules/product/intake.md`
-- `rules/product/modeling.md`
-- `rules/product/briefing.md`
-- `rules/product/acceptance.md`
-- `rules/docs/index.md`
-- `rules/docs/api.md`
-- `rules/docs/capture.md`
-- `rules/docs/reference.md`
-- `rules/docs/decision-log.md`
-- `rules/docs/contract.md`
-- `rules/docs/examples.md`
-- `rules/docs/capture-summary.md`
-- `PIG_SKILLS_RULE_PROFILE=intake|modeling|api|capture`
-- `PIG_SKILLS_RULE_SKILL=spec-refinement|domain-modeling|business-fact-extraction|api-contract-docs|knowledge-capture`
-
-### 6. Discovery Rules
-
-Do not pull product discovery into the coding bundle. Discovery dependencies should be:
-
-- `skills/references/requirements-separation-map.md`
-- `skills/knowledge-capture/SKILL.md`
-
-## Principles
-
-- Skills should point to this map, then load only the minimum files needed.
-- Do not duplicate rule-layer content inside every skill.
-- Load `core` first, then the matching bundle/profile.
-- `rule_profile` in skill frontmatter is the declaration source; mapping files are only for validation and fallback.
-- In non-production environments, the loader should fail fast when skill metadata and mapping metadata drift apart.
-- A new skill should start from `skills/references/skill-boundary-template.md`, then add only the skill-specific I/O and stop rules.
-- Negative replay tests should use `skills/references/negative-replay-scenarios.md` to validate stop boundaries and handoffs.
-