@pigcloud/skills 1.0.11 → 1.1.2

package/rules/bundles.json

@@ -1,358 +0,0 @@
-{
-  "core": {
-    "description": "通用基础规则",
-    "entry": "core/index.md",
-    "files": [
-      "core/index.md",
-      "core/task-boundary.md",
-      "core/evidence.md",
-      "core/iteration.md",
-      "core/interface.md",
-      "core/layer-boundary.md",
-      "core/code-quality.md",
-      "core/logging.md",
-      "core/security.md"
-    ],
-    "profiles": {
-      "core": {
-        "entry": "core/index.md",
-        "files": [
-          "core/index.md",
-          "core/task-boundary.md",
-          "core/evidence.md",
-          "core/iteration.md",
-          "core/interface.md",
-          "core/layer-boundary.md",
-          "core/code-quality.md",
-          "core/logging.md",
-          "core/security.md"
-        ]
-      }
-    }
-  },
-  "workflow": {
-    "description": "协作、路由、收口和交接规则",
-    "entry": "workflow/index.md",
-    "files": [
-      "workflow/index.md",
-      "workflow/router.md",
-      "workflow/refinement.md",
-      "workflow/handoff.md",
-      "workflow/selection.md",
-      "workflow/stop.md"
-    ],
-    "profiles": {
-      "router": {
-        "entry": "workflow/router.md",
-        "files": [
-          "workflow/index.md",
-          "workflow/router.md"
-        ]
-      },
-      "refinement": {
-        "entry": "workflow/refinement.md",
-        "files": [
-          "workflow/index.md",
-          "workflow/refinement.md",
-          "workflow/selection.md",
-          "workflow/stop.md"
-        ]
-      },
-      "handoff": {
-        "entry": "workflow/handoff.md",
-        "files": [
-          "workflow/index.md",
-          "workflow/handoff.md",
-          "workflow/stop.md"
-        ]
-      }
-    }
-  },
-  "product": {
-    "description": "需求、范围和业务概念规则",
-    "entry": "product/index.md",
-    "files": [
-      "product/index.md",
-      "product/intake.md",
-      "product/project-context.md",
-      "product/modeling.md",
-      "product/briefing.md",
-      "product/acceptance.md"
-    ],
-    "profiles": {
-      "intake": {
-        "entry": "product/intake.md",
-        "files": [
-          "product/index.md",
-          "product/intake.md",
-          "product/project-context.md",
-          "product/briefing.md",
-          "product/acceptance.md"
-        ]
-      },
-      "modeling": {
-        "entry": "product/modeling.md",
-        "files": [
-          "product/index.md",
-          "product/modeling.md",
-          "product/project-context.md",
-          "product/briefing.md"
-        ]
-      }
-    }
-  },
-  "coding": {
-    "description": "编码、重构、测试和代码交付规则",
-    "entry": "coding/index.md",
-    "files": [
-      "coding/index.md",
-      "coding/analysis.md",
-      "coding/implementation.md",
-      "coding/testing.md",
-      "coding/scaffold.md",
-      "coding/boundary.md",
-      "coding/validation.md",
-      "coding/backend/index.md",
-      "coding/backend/database.md",
-      "coding/backend/transaction.md",
-      "coding/backend/cache.md",
-      "coding/backend/feign.md",
-      "coding/backend/query.md",
-      "coding/backend/remote.md",
-      "coding/backend/transaction-boundary.md",
-      "coding/backend/transaction-rollback.md",
-      "coding/backend/cache-keying.md",
-      "coding/backend/cache-invalidation.md"
-    ],
-    "profiles": {
-      "analysis": {
-        "entry": "coding/analysis.md",
-        "files": [
-          "coding/index.md",
-          "coding/analysis.md",
-          "coding/boundary.md",
-          "coding/backend/index.md",
-          "coding/backend/database.md",
-          "coding/backend/query.md",
-          "coding/backend/transaction.md"
-        ]
-      },
-      "implementation": {
-        "entry": "coding/implementation.md",
-        "files": [
-          "coding/index.md",
-          "coding/implementation.md",
-          "coding/boundary.md",
-          "coding/validation.md",
-          "coding/backend/index.md",
-          "coding/backend/database.md",
-          "coding/backend/query.md",
-          "coding/backend/transaction.md",
-          "coding/backend/transaction-boundary.md",
-          "coding/backend/transaction-rollback.md",
-          "coding/backend/cache.md",
-          "coding/backend/cache-keying.md",
-          "coding/backend/cache-invalidation.md",
-          "coding/backend/feign.md",
-          "coding/backend/remote.md"
-        ]
-      },
-      "testing": {
-        "entry": "coding/testing.md",
-        "files": [
-          "coding/index.md",
-          "coding/testing.md",
-          "coding/validation.md",
-          "coding/backend/index.md"
-        ]
-      },
-      "scaffold": {
-        "entry": "coding/scaffold.md",
-        "files": [
-          "coding/index.md",
-          "coding/scaffold.md",
-          "coding/boundary.md",
-          "coding/backend/index.md"
-        ]
-      }
-    }
-  },
-  "docs": {
-    "description": "文档、知识沉淀和接口说明规则",
-    "entry": "docs/index.md",
-    "files": [
-      "docs/index.md",
-      "docs/api.md",
-      "docs/capture.md",
-      "docs/reference.md",
-      "docs/decision-log.md",
-      "docs/contract.md",
-      "docs/examples.md",
-      "docs/capture-summary.md"
-    ],
-    "profiles": {
-      "api": {
-        "entry": "docs/api.md",
-        "files": [
-          "docs/index.md",
-          "docs/api.md",
-          "docs/reference.md",
-          "docs/contract.md",
-          "docs/examples.md"
-        ]
-      },
-      "capture": {
-        "entry": "docs/capture.md",
-        "files": [
-          "docs/index.md",
-          "docs/capture.md",
-          "docs/decision-log.md",
-          "docs/capture-summary.md"
-        ]
-      },
-      "reference": {
-        "entry": "docs/reference.md",
-        "files": [
-          "docs/index.md",
-          "docs/reference.md"
-        ]
-      },
-      "decision-log": {
-        "entry": "docs/decision-log.md",
-        "files": [
-          "docs/index.md",
-          "docs/decision-log.md"
-        ]
-      },
-      "contract": {
-        "entry": "docs/contract.md",
-        "files": [
-          "docs/index.md",
-          "docs/contract.md",
-          "docs/examples.md"
-        ]
-      },
-      "examples": {
-        "entry": "docs/examples.md",
-        "files": [
-          "docs/index.md",
-          "docs/examples.md",
-          "docs/contract.md"
-        ]
-      }
-    }
-  },
-  "review": {
-    "description": "代码、安全、性能与质量门禁规则",
-    "entry": "review/index.md",
-    "files": [
-      "review/index.md",
-      "review/code.md",
-      "review/java.md",
-      "review/vue.md",
-      "review/ts.md",
-      "review/security.md",
-      "review/performance.md",
-      "review/rubric.md",
-      "review/evidence.md"
-    ],
-    "profiles": {
-      "code": {
-        "entry": "review/code.md",
-        "files": [
-          "review/index.md",
-          "review/code.md",
-          "review/rubric.md",
-          "review/evidence.md"
-        ]
-      },
-      "code-java": {
-        "entry": "review/java.md",
-        "files": [
-          "review/index.md",
-          "review/code.md",
-          "review/java.md",
-          "review/rubric.md",
-          "review/evidence.md"
-        ]
-      },
-      "code-vue": {
-        "entry": "review/vue.md",
-        "files": [
-          "review/index.md",
-          "review/code.md",
-          "review/vue.md",
-          "review/rubric.md",
-          "review/evidence.md"
-        ]
-      },
-      "code-ts": {
-        "entry": "review/ts.md",
-        "files": [
-          "review/index.md",
-          "review/code.md",
-          "review/ts.md",
-          "review/rubric.md",
-          "review/evidence.md"
-        ]
-      },
-      "security": {
-        "entry": "review/security.md",
-        "files": [
-          "review/index.md",
-          "review/security.md",
-          "review/rubric.md",
-          "review/evidence.md"
-        ]
-      },
-      "performance": {
-        "entry": "review/performance.md",
-        "files": [
-          "review/index.md",
-          "review/performance.md",
-          "review/rubric.md",
-          "review/evidence.md"
-        ]
-      }
-    }
-  },
-  "overlays": {
-    "description": "仓库、团队或公司级覆盖规则",
-    "entry": "overlays/index.md",
-    "files": [
-      "overlays/index.md",
-      "overlays/pig-cloud.md",
-      "overlays/pig-cloud/controller.md",
-      "overlays/pig-cloud/service.md",
-      "overlays/pig-cloud/mapper.md",
-      "overlays/pig-cloud/dto-vo.md",
-      "overlays/pig-cloud/exception.md",
-      "overlays/pig-cloud/layering.md",
-      "overlays/pig-cloud/rest-response.md",
-      "overlays/pig-cloud/entity.md",
-      "overlays/pig-cloud/validation.md",
-      "overlays/pig-cloud/query-style.md",
-      "overlays/pig-cloud/transactions.md"
-    ],
-    "profiles": {
-      "default": {
-        "entry": "overlays/index.md",
-        "files": [
-          "overlays/index.md",
-          "overlays/pig-cloud.md",
-          "overlays/pig-cloud/controller.md",
-          "overlays/pig-cloud/service.md",
-          "overlays/pig-cloud/mapper.md",
-          "overlays/pig-cloud/dto-vo.md",
-          "overlays/pig-cloud/exception.md",
-          "overlays/pig-cloud/layering.md",
-          "overlays/pig-cloud/rest-response.md",
-          "overlays/pig-cloud/entity.md",
-          "overlays/pig-cloud/validation.md",
-          "overlays/pig-cloud/query-style.md",
-          "overlays/pig-cloud/transactions.md"
-        ]
-      }
-    }
-  }
-}

package/rules/coding/analysis.md

@@ -1,27 +0,0 @@
-# Coding Analysis Rules
-
-## 默认做法
-
-- Read the existing code and identify impact boundaries first.
-- Describe dependencies, risks, and missing inputs before implementation.
-- Return something the next stage can consume directly.
-
-## 禁区
-
-- Do not write implementation recipes here.
-- Do not emit code.
-- Do not leave scope or compatibility questions vague.
-
-## 检查
-
-- Is the boundary clear?
-- Is the dependency impact explicit?
-- Is the next stage ready to start?
-
-## 回放信号
-
-- Trigger when the request is about code impact, scope, compatibility, or design preparation.
-
-## References
-
-- `coding/index.md`

package/rules/coding/backend/cache-invalidation.md

@@ -1,30 +0,0 @@
-# Backend Cache Invalidation Rules
-
-## 默认做法
-
-- Make invalidation explicit and predictable.
-- Tie invalidation to the write path or consistency policy.
-- Prefer the simplest invalidation rule that is still safe.
-- Name the trigger that invalidates the entry.
-- State the freshness window or stale-data tolerance when it matters.
-
-## 禁区
-
-- Do not leave stale-data behavior implicit.
-- Do not mix invalidation policy with unrelated cache concerns.
-- Do not pretend a cache is safe if the write path never invalidates it.
-
-## 检查
-
-- Is invalidation clear?
-- Is the staleness window acceptable?
-- Can the reader identify the exact event that removes or refreshes the cache?
-
-## 回放信号
-
-- Trigger when the task needs cache invalidation or consistency handling.
-
-## References
-
-- `coding/backend/index.md`
-- `coding/backend/cache.md`

package/rules/coding/backend/cache-keying.md

@@ -1,30 +0,0 @@
-# Backend Cache Keying Rules
-
-## 默认做法
-
-- Keep cache keys stable, descriptive, and versionable.
-- Make key structure easy to inspect.
-- Use one keying strategy per cache concern.
-- Include the dimensions that actually change the cached value.
-- Separate tenant, version, and business identity when they matter.
-
-## 禁区
-
-- Do not hide meaning in opaque key names.
-- Do not let different meanings share the same key shape.
-- Do not omit a version dimension when incompatible cache formats can coexist.
-
-## 检查
-
-- Is the key design stable?
-- Can the key be understood without reading implementation?
-- Can a maintainer tell why each segment exists?
-
-## 回放信号
-
-- Trigger when the task needs cache key design or naming.
-
-## References
-
-- `coding/backend/index.md`
-- `coding/backend/cache.md`

package/rules/coding/backend/cache.md

@@ -1,37 +0,0 @@
-# Backend Cache Rules
-
-## 默认做法
-
-- Use this file to choose between keying and invalidation notes.
-- Keep the top-level cache rule focused on the cache concern itself.
-- Use the smallest cache rule that answers the task.
-- If the task needs both naming and freshness, answer keying first and invalidation second.
-- Tell the reader whether the issue is cache shape, cache lifetime, or both.
-- Use this file for cache scope selection, not data consistency design.
-
-## 禁区
-
-- Do not repeat key design details that belong in `cache-keying`.
-- Do not repeat invalidation details that belong in `cache-invalidation`.
-- Do not turn this file into a cache strategy handbook.
-- Do not leave freshness or consistency concerns implicit.
-- Do not use this file as a generic performance rule.
-
-## 检查
-
-- Is the task about cache scope selection, not a detailed rule?
-- Should the answer come from the keying or invalidation subrule?
-- Is the file still short enough to stay an entry point?
-- Would the next step be obvious after reading the chosen subrule?
-- Did the answer keep one cache concern in view?
-- Is this a cache question rather than a broad consistency question?
-
-## 回放信号
-
-- Trigger when the task touches cache read/write, invalidation, or consistency tradeoffs.
-
-## References
-
-- `coding/backend/index.md`
-- `coding/backend/cache-keying.md`
-- `coding/backend/cache-invalidation.md`

package/rules/coding/backend/database.md

@@ -1,32 +0,0 @@
-# Backend Database Rules
-
-## 默认做法
-
-- Prefer lambda-style queries and updates.
-- Keep repository access thin and predictable.
-- Make entity, mapper, or repository changes easy to review.
-- Name the persistence surface affected by the change.
-- State whether the issue is read-path shaping, write-path shaping, or mapping.
-- Keep the output tied to the smallest persistence surface that changes.
-
-## 禁区
-
-- Do not use string column names when a lambda expression is available.
-- Do not let SQL details leak into higher layers.
-- Do not blur read and write behavior in the same explanation when one side is enough.
-
-## 检查
-
-- Is the query type-safe?
-- Is the persistence change limited to the data layer?
-- Can a maintainer see which persistence surface changed?
-- Is the change understandable without opening service code?
-- Is this really about persistence surface selection rather than query shape?
-
-## 回放信号
-
-- Trigger when the task touches persistence, queries, or entity mapping.
-
-## References
-
-- `coding/backend/index.md`

package/rules/coding/backend/feign.md

@@ -1,30 +0,0 @@
-# Backend Feign Compatibility Rules
-
-## 默认做法
-
-- Treat this file as a compatibility entry point, not as a second remote-contract rule.
-- Use `remote.md` for the main contract, failure, and behavior rules.
-- Use this file only when the task is specifically about Feign client usage, wiring, or compatibility notes.
-- Keep any Feign-specific advice short and tied to the client surface.
-
-## 禁区
-
-- Do not duplicate `remote.md`.
-- Do not hide remote contract changes.
-- Do not leave failure handling implicit.
-- Do not turn Feign wiring notes into a remote contract tutorial.
-
-## 检查
-
-- Is this actually a Feign-specific question?
-- Should the answer instead come from `remote.md`?
-- Is the client wiring note short enough to stay an entry point?
-
-## 回放信号
-
-- Trigger when the task touches Feign client wiring or compatibility details.
-
-## References
-
-- `coding/backend/index.md`
-- `coding/backend/remote.md`

package/rules/coding/backend/index.md

@@ -1,42 +0,0 @@
-# Coding Backend Rules
-
-## 默认做法
-
-- Keep backend rules focused on persistence, query shape, unit-of-work, cache policy, and remote contracts.
-- Reuse the smallest backend-specific rule file that covers the task.
-- Keep implementation details out of higher-level coding rules.
-- Split persistence, query, transaction, cache, and remote concerns into separate files.
-- Prefer a dedicated subrule when the task mentions atomicity, cache policy, remote contract handling, or persistence surface selection.
-- Use this file only when the backend concern spans multiple subrules.
-
-## 禁区
-
-- Do not put product discovery into backend rules.
-- Do not duplicate backend details in every coding file.
-- Do not make a single backend file cover every concern.
-- Do not let `feign` duplicate `remote` behavior.
-
-## 检查
-
-- Is the task actually backend-specific?
-- Is there a more precise backend rule file?
-- Would the answer be clearer in `database`, `query`, `transaction`, `cache`, or `remote`?
-- Is the question really about Feign client compatibility rather than remote behavior?
-
-## 回放信号
-
-- Trigger when the request needs database, transaction, cache, or Feign-specific behavior.
-- Trigger when the task crosses query, write, consistency, or remote integration boundaries.
-
-## References
-
-- `coding/backend/database.md`
-- `coding/backend/transaction.md`
-- `coding/backend/cache.md`
-- `coding/backend/feign.md`
-- `coding/backend/query.md`
-- `coding/backend/remote.md`
-- `coding/backend/transaction-boundary.md`
-- `coding/backend/transaction-rollback.md`
-- `coding/backend/cache-keying.md`
-- `coding/backend/cache-invalidation.md`

package/rules/coding/backend/query.md

@@ -1,32 +0,0 @@
-# Backend Query Rules
-
-## 默认做法
-
-- Use type-safe query construction.
-- Keep query intent readable and close to the domain terms.
-- Make pagination and filtering explicit.
-- Call out the main selector, sort, and paging behavior when they matter.
-- Prefer one query shape per request unless the task asks for alternatives.
-- Use this file for query shape, not persistence mapping.
-
-## 禁区
-
-- Do not use string column names when a type-safe form exists.
-- Do not hide pagination or filter semantics.
-- Do not merge unrelated filters into one vague explanation.
-- Do not turn this file into a persistence or transaction rule.
-
-## 检查
-
-- Is the query easy to review?
-- Are filter and paging rules explicit?
-- Can the reader tell which field controls the result set?
-- Is this a query-shape question rather than a data-layer question?
-
-## 回放信号
-
-- Trigger when the task touches entity queries, filtering, or pagination.
-
-## References
-
-- `coding/backend/index.md`

package/rules/coding/backend/remote.md

@@ -1,33 +0,0 @@
-# Backend Remote Rules
-
-## 默认做法
-
-- Keep remote contracts explicit and version-aware.
-- Make timeout, fallback, and error handling visible.
-- Separate remote-call risk from local data logic.
-- Name the remote side, request shape, response shape, and failure policy.
-- State whether the risk is contract drift, transport failure, or downstream behavior.
-- Use this file for remote behavior, not Feign client wiring.
-
-## 禁区
-
-- Do not hide remote contract changes.
-- Do not leave failure handling implicit.
-- Do not treat remote behavior as if it were local code.
-- Do not duplicate Feign compatibility notes here.
-
-## 检查
-
-- Is the remote contract clear?
-- Are failures handled in the right place?
-- Can the reader tell what happens on timeout, retry, or non-200 response?
-- Is this a remote-behavior question rather than a client-wiring question?
-
-## 回放信号
-
-- Trigger when the task touches Feign clients or remote service integration.
-
-## References
-
-- `coding/backend/index.md`
-- `coding/backend/feign.md`

package/rules/coding/backend/transaction-boundary.md

@@ -1,30 +0,0 @@
-# Backend Transaction Boundary Rules
-
-## 默认做法
-
-- Keep the transaction boundary at the service layer.
-- Make the boundary narrow and explicit.
-- Align the boundary with one business operation.
-- Identify the service method that owns the boundary.
-- Prefer a single commit point for the smallest complete business action.
-
-## 禁区
-
-- Do not start transactions in controllers.
-- Do not make one transaction cover unrelated work.
-- Do not spread one business action across multiple ambiguous boundaries.
-
-## 检查
-
-- Is the boundary obvious?
-- Does the transaction match one business action?
-- Can the reader see the exact method where the unit of work starts and ends?
-
-## 回放信号
-
-- Trigger when the task needs a transactional boundary decision.
-
-## References
-
-- `coding/backend/index.md`
-- `coding/backend/transaction.md`