@bovinphang/frontend-craft 2.9.0 → 3.0.0

package/skills/cc-cpp-project-standard/references/common/engineering-practices.sources.json

@@ -0,0 +1,377 @@
+{
+  "schemaVersion": 1,
+  "sources": [
+    {
+      "id": "google-review",
+      "publisher": "Google",
+      "title": "Code review standard",
+      "url": "https://google.github.io/eng-practices/review/reviewer/standard.html",
+      "section": "Engineering principles and code health",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Living public guidance; revision unknown",
+      "licenseStatus": "unknown",
+      "adoption": "adopt",
+      "limits": "Use evidence and project standards; personal preference alone is not a blocker."
+    },
+    {
+      "id": "ms-playbook",
+      "publisher": "Microsoft ISE",
+      "title": "Test planning",
+      "url": "https://microsoft.github.io/code-with-engineering-playbook/automated-testing/test-planning/",
+      "section": "Risk, test scope and responsibilities",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Living ISE playbook; revision unknown",
+      "licenseStatus": "unknown",
+      "adoption": "adopt",
+      "limits": "Team practice, not a company-wide mandate; retain existing tools."
+    },
+    {
+      "id": "ms-faults",
+      "publisher": "Microsoft ISE",
+      "title": "Fault injection testing",
+      "url": "https://microsoft.github.io/code-with-engineering-playbook/automated-testing/fault-injection-testing/",
+      "section": "Controlled failure and observations",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Living ISE playbook; revision unknown",
+      "licenseStatus": "unknown",
+      "adoption": "adopt",
+      "limits": "Run scoped, controlled failures; do not infer production reliability from a small example."
+    },
+    {
+      "id": "google-ts",
+      "publisher": "Google",
+      "title": "TS/JS style guide",
+      "url": "https://google.github.io/styleguide/tsguide.html",
+      "section": "Environment caveat; types and exceptions",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Public guide; revision unknown",
+      "licenseStatus": "unknown",
+      "adoption": "conditional",
+      "limits": "Google explicitly notes internal constraints differ; no blanket ban overriding a justified project convention."
+    },
+    {
+      "id": "typescript-publishing",
+      "publisher": "TypeScript",
+      "title": "Publishing declaration files",
+      "url": "https://www.typescriptlang.org/docs/handbook/declaration-files/publishing.html",
+      "section": "Types and declaration dependencies",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Living handbook; check installed compiler/module resolution",
+      "licenseStatus": "unknown",
+      "adoption": "adopt",
+      "limits": "Validate the actual packed consumer; do not upgrade compiler or module mode on this basis."
+    },
+    {
+      "id": "rust-api",
+      "publisher": "Rust library team",
+      "title": "Rust API Guidelines",
+      "url": "https://rust-lang.github.io/api-guidelines/",
+      "section": "Type safety, dependability and future proofing",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Living recommendations; revision unknown",
+      "licenseStatus": "unknown",
+      "adoption": "adopt",
+      "limits": "Guidance rather than language law; preserve edition and MSRV."
+    },
+    {
+      "id": "tokio-join",
+      "publisher": "Tokio project",
+      "title": "JoinHandle",
+      "url": "https://docs.rs/tokio/latest/tokio/task/struct.JoinHandle.html",
+      "section": "Drop, abort and completion",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Page observed 1.54.1; project runtime/version determines applicability",
+      "licenseStatus": "unknown",
+      "adoption": "conditional",
+      "limits": "Tokio-specific mechanics only when Tokio is already used; no new runtime dependency."
+    },
+    {
+      "id": "uber-go",
+      "publisher": "Uber",
+      "title": "Go Style Guide",
+      "url": "https://github.com/uber-go/guide/blob/master/style.md",
+      "section": "Errors, interfaces and goroutine lifetime",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Living master; revision unknown",
+      "licenseStatus": "unknown",
+      "adoption": "adopt",
+      "limits": "Do not import Uber dependencies or turn buffer-size style into a correctness theorem."
+    },
+    {
+      "id": "go-context",
+      "publisher": "Go project",
+      "title": "context package",
+      "url": "https://pkg.go.dev/context",
+      "section": "Cancellation propagation and ownership",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Standard library; check owning go.mod/toolchain",
+      "licenseStatus": "unknown",
+      "adoption": "adopt",
+      "limits": "A cancellation signal alone does not confirm worker exit."
+    },
+    {
+      "id": "google-java",
+      "publisher": "Google",
+      "title": "Java Style Guide",
+      "url": "https://google.github.io/styleguide/javaguide.html",
+      "section": "Source structure and exception handling",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Living public style; revision unknown",
+      "licenseStatus": "unknown",
+      "adoption": "conditional",
+      "limits": "Naming/layout follows local standard; style is distinct from runtime correctness."
+    },
+    {
+      "id": "oracle-resources",
+      "publisher": "Oracle",
+      "title": "Try-with-resources",
+      "url": "https://docs.oracle.com/javase/tutorial/essential/exceptions/tryResourceClose.html",
+      "section": "Closing resources and suppressed exceptions",
+      "checkedAt": "2026-11-08",
+      "versionScope": "JDK8 tutorial; not a source for newer runtime features",
+      "licenseStatus": "unknown",
+      "adoption": "adopt",
+      "limits": "Preserve primary cause and borrowed-resource ownership; check actual API contract."
+    },
+    {
+      "id": "java-executor",
+      "publisher": "Oracle",
+      "title": "ExecutorService",
+      "url": "https://docs.oracle.com/en/java/javase/17/docs/api/java.base/java/util/concurrent/ExecutorService.html",
+      "section": "Shutdown, termination and awaitTermination",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Java SE17 documentation",
+      "licenseStatus": "unknown",
+      "adoption": "conditional",
+      "limits": "Check target JDK; no automatic virtual-thread or JDK migration."
+    },
+    {
+      "id": "google-python",
+      "publisher": "Google",
+      "title": "Python Style Guide",
+      "url": "https://google.github.io/styleguide/pyguide.html",
+      "section": "Imports, exceptions and mutable state",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Living public guide; revision unknown",
+      "licenseStatus": "unknown",
+      "adoption": "conditional",
+      "limits": "Keep current formatter/type checker and library responsibilities."
+    },
+    {
+      "id": "python-asyncio",
+      "publisher": "Python project",
+      "title": "Coroutines and tasks",
+      "url": "https://docs.python.org/3/library/asyncio-task.html",
+      "section": "Cancellation and task ownership",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Page observed 3.15.2; feature availability follows project Python",
+      "licenseStatus": "unknown",
+      "adoption": "conditional",
+      "limits": "Newer TaskGroup/timeout features require a supported project version; no upgrade implied."
+    },
+    {
+      "id": "cert-c",
+      "publisher": "CMU SEI",
+      "title": "MEM00-C allocation and release",
+      "url": "https://cmu-sei.github.io/secure-coding-standards/sei-cert-c-coding-standard/recommendations/memory-management-mem/mem00-c/",
+      "section": "MEM00-C memory responsibility",
+      "checkedAt": "2026-11-08",
+      "versionScope": "2016-edition standard family; MEM00-C is a recommendation",
+      "licenseStatus": "unknown",
+      "adoption": "adopt",
+      "limits": "Do not label recommendations as mandatory CERT rules or apply C++ ownership machinery to pure C."
+    },
+    {
+      "id": "cpp-core",
+      "publisher": "C++ Core Guidelines editors",
+      "title": "C++ Core Guidelines",
+      "url": "https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines",
+      "section": "Resource and lifetime interfaces",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Page dated 2026-06-14, living release0.8",
+      "licenseStatus": "unknown",
+      "adoption": "adopt",
+      "limits": "Adapt to existing exception policy and compiler; borrowing does not imply ownership."
+    },
+    {
+      "id": "google-cpp",
+      "publisher": "Google",
+      "title": "C++ Style Guide",
+      "url": "https://google.github.io/styleguide/cppguide.html",
+      "section": "Exceptions and project consistency",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Living public guide; revision unknown",
+      "licenseStatus": "unknown",
+      "adoption": "conditional",
+      "limits": "Its exception/standard policy is not universal; preserve the owning project policy and C ABI."
+    },
+    {
+      "id": "ms-sal",
+      "publisher": "Microsoft",
+      "title": "Understanding SAL",
+      "url": "https://learn.microsoft.com/en-us/cpp/code-quality/understanding-sal?view=msvc-170",
+      "section": "Parameter preconditions and output guarantees",
+      "checkedAt": "2026-11-08",
+      "versionScope": "MSVC170 documentation view",
+      "licenseStatus": "unknown",
+      "adoption": "conditional",
+      "limits": "SAL is an optional toolchain-specific expression, not a portable mandatory annotation."
+    },
+    {
+      "id": "aws-retry",
+      "publisher": "AWS",
+      "title": "Timeouts, retries and backoff with jitter",
+      "url": "https://aws.amazon.com/builders-library/timeouts-retries-and-backoff-with-jitter/",
+      "section": "Timeouts, bounded retries and retry amplification",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Article dated 2019-12-05; official Builder Center redirect",
+      "licenseStatus": "unknown",
+      "adoption": "adopt",
+      "limits": "Retry only semantically safe operations within a total budget; failure classes alone do not grant write replay."
+    },
+    {
+      "id": "aws-idempotency",
+      "publisher": "AWS",
+      "title": "Making retries safe with idempotent APIs",
+      "url": "https://aws.amazon.com/builders-library/making-retries-safe-with-idempotent-APIs/",
+      "section": "Caller intent, duplicate requests and atomic recording",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Builders Library; revision unknown",
+      "licenseStatus": "unknown",
+      "adoption": "adopt",
+      "limits": "A process-local example does not establish database/multi-process exactly-once."
+    },
+    {
+      "id": "react-effects",
+      "publisher": "React project",
+      "title": "useEffect",
+      "url": "https://react.dev/reference/react/useEffect",
+      "section": "Cleanup and fetching race conditions",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Page observed React19.3; use installed project API",
+      "licenseStatus": "unknown",
+      "adoption": "adopt",
+      "limits": "Abort and stale-result checks complement each other; no React upgrade implied."
+    },
+    {
+      "id": "react-act",
+      "publisher": "React project",
+      "title": "act",
+      "url": "https://react.dev/reference/react/act",
+      "section": "Applying updates before assertions",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Page observed React19.3; verify sample versions",
+      "licenseStatus": "unknown",
+      "adoption": "adopt",
+      "limits": "DOM simulation is not browser E2E or native desktop execution."
+    },
+    {
+      "id": "vue-watchers",
+      "publisher": "Vue project",
+      "title": "Watchers",
+      "url": "https://vuejs.org/guide/essentials/watchers.html",
+      "section": "Side-effect cleanup",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Vue3; onWatcherCleanup requires3.5+ and synchronous registration",
+      "licenseStatus": "unknown",
+      "adoption": "conditional",
+      "limits": "Use supported callback cleanup on older Vue3; no framework migration."
+    },
+    {
+      "id": "tauri-permissions",
+      "publisher": "Tauri project",
+      "title": "Permissions",
+      "url": "https://v2.tauri.app/security/permissions/",
+      "section": "Command allow/deny and capability scope",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Tauri2 docs; check installed version/configuration",
+      "licenseStatus": "unknown",
+      "adoption": "conditional",
+      "limits": "Rust command-unit tests do not activate webview permissions or prove packaged GUI security."
+    },
+    {
+      "id": "electron-security",
+      "publisher": "Electron project",
+      "title": "Security",
+      "url": "https://www.electronjs.org/docs/latest/tutorial/security",
+      "section": "IPC sender checks and renderer trust",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Living docs; match installed Electron",
+      "licenseStatus": "unknown",
+      "adoption": "conditional",
+      "limits": "Handler tests do not prove sandbox/context isolation is active in a packaged app."
+    },
+    {
+      "id": "spring-tests",
+      "publisher": "Spring project",
+      "title": "Testing Spring Boot applications",
+      "url": "https://docs.spring.io/spring-boot/3.5/reference/testing/spring-boot-applications.html",
+      "section": "Test slices and application tests",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Boot3.5 docs observed3.5.16; preserve sample/project versions",
+      "licenseStatus": "unknown",
+      "adoption": "conditional",
+      "limits": "Test scope matters; MVC tests do not establish live DB/transaction or deployment behavior."
+    },
+    {
+      "id": "fastapi-lifespan",
+      "publisher": "FastAPI project",
+      "title": "Lifespan events",
+      "url": "https://fastapi.tiangolo.com/advanced/events/",
+      "section": "Acquire and release application resources",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Living FastAPI documentation; match pinned dependencies",
+      "licenseStatus": "unknown",
+      "adoption": "conditional",
+      "limits": "Use actual lifespan execution in tests; import does not own a live connection."
+    },
+    {
+      "id": "gin-binding",
+      "publisher": "Gin project",
+      "title": "Binding",
+      "url": "https://gin-gonic.com/en/docs/binding/",
+      "section": "Binding errors and validation",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Living Gin documentation; match pinned module",
+      "licenseStatus": "unknown",
+      "adoption": "conditional",
+      "limits": "Writing/aborting a response does not replace explicit control-flow return in the current handler."
+    },
+    {
+      "id": "axum-extractors",
+      "publisher": "Axum project",
+      "title": "Extractors",
+      "url": "https://docs.rs/axum/latest/axum/extract/",
+      "section": "Extractor order and rejections",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Latest route observed0.8.9; fixed0.8.9 route unavailable via browser tool",
+      "licenseStatus": "unknown",
+      "adoption": "conditional",
+      "limits": "Pinned existing example is authoritative for compilation; do not assume source signatures across releases."
+    },
+    {
+      "id": "drogon-filters",
+      "publisher": "Drogon project",
+      "title": "Middleware and Filter",
+      "url": "https://github.com/drogonframework/drogon/wiki/ENG-05-Middleware-and-Filter",
+      "section": "Filter callbacks and continuation",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Living wiki; match compiled example version",
+      "licenseStatus": "unknown",
+      "adoption": "conditional",
+      "limits": "Synthetic role headers are not authentication; callback lifetime must follow actual ownership."
+    },
+    {
+      "id": "node-typescript",
+      "publisher": "Node.js project",
+      "title": "Modules: TypeScript",
+      "url": "https://nodejs.org/api/typescript.html",
+      "section": "Type-stripping history, enabling, and separate type checking",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Page observed26.13.0; sample>=22.18, actual24.14.1 tested; product Node>=22 unchanged",
+      "licenseStatus": "unknown",
+      "adoption": "conditional",
+      "limits": "Native stripping is not type checking and ignores tsconfig. Missing sample capability is MISSING, not a product runtime upgrade."
+    }
+  ]
+}

package/skills/cc-cpp-project-standard/references/engineering-practices.md

@@ -0,0 +1,106 @@
+---
+practiceCards:
+  - id: "cc-cpp-project-standard:raii-borrowing"
+    level: "required"
+    sourceIds: ["cpp-core"]
+    caseIds: ["EP-CPP-01"]
+    evidence: "case"
+  - id: "cc-cpp-project-standard:exception-abi"
+    level: "conditional"
+    sourceIds: ["cpp-core","google-cpp","cert-c"]
+    caseIds: ["EP-CPP-01","EP-C-01"]
+    evidence: "review-only"
+  - id: "cc-cpp-project-standard:teardown-lifetime"
+    level: "conditional"
+    sourceIds: ["cpp-core","cert-c"]
+    caseIds: ["EP-CPP-01","EP-IPC-01"]
+    evidence: "review-only"
+---
+
+# Local engineering decisions
+
+Locate the actual role, toolchain and existing conventions, then read relevant [shared principles](common/engineering-practices.md). These conditions apply to this entry, not every project. Structure checks do not prove all semantics or execution.
+
+<a id="cc-cpp-project-standard:raii-borrowing"></a>
+## RAII owns acquired resources, not every pointer
+
+Level: required
+
+### Risk
+Wrapping a borrowed pointer with a default owning deleter can free someone else’s object.
+
+### Applies
+For C++ ownership-facing APIs, constructors and error paths; distinguish own, borrow and shared lifetime first.
+
+### Decision
+Use RAII for resources this unit acquires; preserve a non-owning representation for borrowed values. unique_ptr expresses exclusive ownership, shared_ptr needs a real shared-lifetime contract.
+
+### Exceptions
+A custom owner must match its allocator/deleter. Smart pointers do not make a dangling borrow safe or remove external lifetime preconditions.
+
+### Examples
+Better: local unique_ptr owns a newly acquired lease while the input remains borrowed. Worse: make shared_ptr from every raw input pointer.
+
+### Verification
+Run local borrow/partial-construction assertions. The defective test uses a heap-owned caller object and guards against a second delete, not an unstable UB crash.
+
+### Sources
+cpp-core — [registry and limits](common/engineering-practices.sources.json).
+
+Evidence IDs: EP-CPP-01; case. [Local runnable example](../examples/engineering/README.md). Execution status and scope require actual records; a related ID does not prove every decision on this card.
+
+<a id="cc-cpp-project-standard:exception-abi"></a>
+## Respect the owning project exception and ABI policy
+
+Level: conditional
+
+### Risk
+Enabling exceptions globally or unwinding across a foreign ABI can break a valid existing contract.
+
+### Applies
+When exceptions or FFI boundaries actually exist; Google and other projects intentionally choose different policies.
+
+### Decision
+Read compiler flags and boundary contracts first. In exception-enabled code make partial construction exception-safe; with disabled exceptions use the existing explicit-failure path. Keep C ABI failure/output contracts stable.
+
+### Exceptions
+noexcept is not a converter from throwing allocation to error codes. The local exception-enabled example is one isolated target, not authority to change user flags or standards.
+
+### Examples
+Better: preserve the project’s error policy and allocator cleanup. Worse: enable exceptions or migrate C just because a guideline prefers a pattern.
+
+### Verification
+Compile with the actual project policy and test failure translation/cleanup. The sample proves its own C++ boundary only; no cross-ABI unwind has been verified.
+
+### Sources
+cpp-core, google-cpp, cert-c — [registry and limits](common/engineering-practices.sources.json).
+
+Evidence IDs: EP-CPP-01, EP-C-01; review-only.  Execution status and scope require actual records; a related ID does not prove every decision on this card.
+
+<a id="cc-cpp-project-standard:teardown-lifetime"></a>
+## Stop users before releasing shared dependencies
+
+Level: conditional
+
+### Risk
+A callback can outlive a native object or plugin code even after one owner resets its handle.
+
+### Applies
+For concurrent callbacks, native plugins and desktop shutdown; a sequential local RAII scope need not acquire a scheduler.
+
+### Decision
+Stop new calls, cancel/drain owned work and observe completion before releasing buffers, callback targets or unloading code. Name the owner of each join and final release.
+
+### Exceptions
+Reference counting protects only correctly modeled ownership; it does not prevent every dangling alias or prove callback quiescence. Forced shutdown needs an explicit incomplete-state policy.
+
+### Examples
+Better: confirm callbacks have ended before unloading a plugin. Worse: reset one shared_ptr and assume all borrowed pointers are invalidated safely.
+
+### Verification
+Use controlled teardown interleavings and actual native tools; local partial-construction tests do not establish race freedom, GUI exit or code-unload safety.
+
+### Sources
+cpp-core, cert-c — [registry and limits](common/engineering-practices.sources.json).
+
+Evidence IDs: EP-CPP-01, EP-IPC-01; review-only.  Execution status and scope require actual records; a related ID does not prove every decision on this card.

package/skills/cc-cpp-project-standard/references/practice.md

@@ -0,0 +1,37 @@
+# C++ project engineering
+
+## Specialist checks
+
+1. Read the actual C++ standard, standard library, compiler matrix, build presets and exported ABI before choosing features.
+
+2. Represent ownership with an appropriate RAII owner; keep borrowed pointers explicitly borrowed. Do not invent shared ownership around a pointer owned elsewhere.
+
+3. Specify exception guarantees and release resources during partial construction. Catch at explicit boundaries, convert failures accurately and keep destructors safe.
+
+4. Keep allocation/release paired across DLL/FFI boundaries. Prevent exceptions and unstable implementation types from crossing unsupported ABI contracts.
+
+5. Review destruction order, callback lifetime and synchronization with unload. Test competing teardown and error paths rather than only successful construction.
+
+6. Validate the existing build and available diagnostics on declared platforms. Report missing tooling; a successful compile is not evidence of race or lifetime safety.
+
+<a id="scope"></a>
+## Scope and examples
+
+Use for:
+- Review RAII and exception safety in a C++ library
+- Keep a plugin ABI while clarifying ownership
+- Reduce header and template dependency boundaries
+- Test C++ destruction and partial construction
+
+Do not upgrade the C++ standard or replace the build system without a task need; pure C interfaces retain their own contract.
+
+## Evidence to deliver
+
+- Repository/contract evidence and the exact affected scope.
+- Chosen approach, invariants, resource/error or failure boundaries.
+- Commands actually run and results, unrun checks and unproven claims.
+- Compatibility, recovery/rollback or follow-up limits; review findings need verified locations.
+
+## Primary reference
+
+[Relevant official/project documentation](https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines) (checked 2026-11-06). Match the actual project version before applying version-sensitive details; the page version does not authorize an upgrade.

package/skills/cc-debug-methodology/SKILL.md

@@ -0,0 +1,8 @@
+---
+name: cc-debug-methodology
+description: Use when diagnosing unexplained engineering failures, build errors, service exceptions, inconsistent data, or cross-layer faults before selecting a repair.
+---
+
+# Evidence-driven diagnosis
+
+Read and follow the [shared method](references/method.md). Select project-specific tools and domain checks from the actual repository; this workflow does not require a frontend stack.

package/skills/cc-debug-methodology/references/method.md

@@ -0,0 +1,13 @@
+# Evidence-driven diagnosis
+
+Use five steps to establish a root cause before applying a fix.
+
+1. **Classify:** describe the observable failure, impact, version, environment and minimal reproduction. Identify the relevant subsystem using project evidence. Cross-layer failures start from the visible symptom and trace across boundaries.
+2. **Collect:** reproduce with the smallest failing command or operation; collect necessary logs, traces, state, configuration and recent changes. Redact credentials and sensitive payloads. A domain adapter supplies stack-specific probes.
+3. **Hypothesize:** keep at most three hypotheses ranked by evidence. Each states "X causes Y; Z can confirm or falsify it." Do not substitute a symptom or speculative repair for a cause.
+4. **Verify:** vary one factor at a time, start with the strongest hypothesis and record confirmed/falsified/pending. If all are falsified, collect more evidence. Three consecutive failed verifications of the same hypothesis require reporting the block rather than repeating it.
+5. **Fix and validate:** apply the smallest confirmed repair, preserve a regression reproduction and run affected then broader existing checks. Report baseline failures separately; do not disable tests or weaken validation to claim success.
+
+For dependency or environment failures, compare exact toolchain/dependency versions, lockfile and CI/local differences before upgrading packages. Keep migrations separate from ordinary defect repairs. Avoid adding retries, changing timeouts or suppressing errors without proving the cause and the intended semantics.
+
+Deliver `reports/debug-YYYY-MM-DD-HHmmss.md` with symptom and reproduction, evidence, hypothesis/result table, root cause, modified files/behavior, executed verification, residual risk and the next useful action. Do not claim a fix or a green suite without observed results.

package/skills/cc-doc-sync-core/SKILL.md

@@ -0,0 +1,8 @@
+---
+name: cc-doc-sync-core
+description: Use when project documentation, multilingual READMEs, setup instructions, CLI usage, or public capability descriptions drift from implementation, configuration, tests, or release metadata.
+---
+
+# Documentation synchronization
+
+Read and follow the [shared method](references/method.md). Select project-specific tools and domain checks from the actual repository; this workflow does not require a frontend stack.

package/skills/cc-doc-sync-core/references/method.md

@@ -0,0 +1,12 @@
+# Documentation synchronization
+
+Synchronize public documentation from implementation facts, not from the desired design.
+
+1. Identify the repository stack, document entry points and requested scope. Include root READMEs, nested package/application/runtime READMEs and deployment guides; exclude dependencies, generated outputs and third-party directories.
+2. Collect authoritative project sources: manifests/lockfiles, configuration, env examples, commands, schemas, public APIs, tests, CI, build and deployment files. Use sources for the actual stack rather than require a particular language's manifest.
+3. Compare commands, environment variable names, paths, versions, API behavior, capabilities, setup and deployment instructions. Keep only stable public facts; do not present proposals or experimental designs as supported behavior.
+4. Check every existing language entry. Public identifiers, commands, version constraints, support matrices, report paths and examples must agree. Translate prose according to the existing convention; explicitly report translations requiring human review.
+5. Update affected README/docs/ADR/changelog and user-facing metadata together. An ADR records context, decision, alternatives, impact, verification and rollback clues; it is not a full review report.
+6. Run the project's existing consistency checks, relevant type/tests/build or packaging checks and legacy-reference search. Record each checked document, source of truth, updated language, unchanged entry and unresolved uncertainty.
+
+Do not invent commands or environment variables, overwrite private documents outside the requested scope, or replace a README with internal implementation details. A successful prose edit alone does not prove factual consistency.

package/skills/{fec-drawio-studio → cc-drawio-studio}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: fec-drawio-studio
+name: cc-drawio-studio
 description: Use when creating editable technical diagrams with draw.io / diagrams.net sources, including architecture diagrams, ERD, UML, sequence diagrams, flowcharts, ML model diagrams, official shape lookup, brand symbols, Graphviz auto-layout, codebase structure maps, .drawio validation, or draw.io CLI export fallback. Do not use for ordinary raster image generation, freehand sketches, interactive canvas/Three.js scenes, or decorative SVG animation. Chinese triggers include draw.io, diagrams.net, editable architecture diagrams, .drawio, ER diagrams, UML, sequence diagrams, auto layout, shape retrieval, code structure diagrams.
 ---
 
@@ -36,11 +36,11 @@ Generate, verify and export draw.io / diagrams.net technical diagrams that can b
 4. Checksum preview
    - Run after each generation of `.drawio`:
      ```bash
-     node skills/fec-drawio-studio/scripts/diagram-lint.mjs diagram.drawio --format markdown
+     node skills/cc-drawio-studio/scripts/diagram-lint.mjs diagram.drawio --format markdown
      ```
    - If the machine has draw.io desktop CLI, do not embed XML when exporting the preview PNG, and control the width:
      ```bash
-     node skills/fec-drawio-studio/scripts/drawio-export.mjs diagram.drawio --format png --output diagram.png --width 2000
+     node skills/cc-drawio-studio/scripts/drawio-export.mjs diagram.drawio --format png --output diagram.png --width 2000
      ```
    - If CLI is not available, use [diagram-url.mjs](scripts/diagram-url.mjs) to generate diagrams.net viewer/editor URL; first read [data-residency.md](references/data-residency.md) when strictly offline or data residency is sensitive.
 
@@ -48,8 +48,8 @@ Generate, verify and export draw.io / diagrams.net technical diagrams that can b
    - Save `.drawio` source files and PNG/SVG/PDF/JPG required by users.
    - If the final PNG is embedded in XML using draw.io `-e`, run after exporting:
      ```bash
-     node skills/fec-drawio-studio/scripts/drawio-export.mjs diagram.drawio --format png --output diagram.drawio.png --scale 2 --embed
-     node skills/fec-drawio-studio/scripts/png-embed-fix.mjs diagram.drawio.png
+     node skills/cc-drawio-studio/scripts/drawio-export.mjs diagram.drawio --format png --output diagram.drawio.png --scale 2 --embed
+     node skills/cc-drawio-studio/scripts/png-embed-fix.mjs diagram.drawio.png
      ```
    - Report source files, exported files, verification results, and external dependencies that cannot be automatically verified.
 

package/skills/{fec-drawio-studio → cc-drawio-studio}/references/flowchart-quality.md

@@ -43,7 +43,7 @@ Use this reference when a draw.io / diagrams.net deliverable is a process, workf
 Before delivery, run:
 
 ```bash
-node skills/fec-drawio-studio/scripts/diagram-lint.mjs diagram.drawio --format markdown --strict
+node skills/cc-drawio-studio/scripts/diagram-lint.mjs diagram.drawio --format markdown --strict
 ```
 
 Then manually check that the opened diagram has no crossed main-path connectors, no clipped labels, no collapsed-looking stages, and no unreadably small text at the default diagrams.net zoom.