cue-ai 0.4.0 → 0.5.0

package/resources/claude-plugins-official/plugins/code-modernization/commands/modernize-harden.md

@@ -1,64 +0,0 @@
----
-description: Security vulnerability scan with a reviewable remediation patch — OWASP, CWE, CVE, secrets, injection
-argument-hint: <system-dir>
----
-
-Run a **security hardening pass** on `legacy/$1`: find vulnerabilities, rank
-them, and produce a reviewable patch for the critical ones.
-
-This command never edits `legacy/` — it writes findings and a proposed patch
-to `analysis/$1/`. The user reviews and applies (or not).
-
-## Scan
-
-Spawn the **security-auditor** subagent:
-
-"Adversarially audit legacy/$1 for security vulnerabilities. Cover what's
-relevant to the stack: injection (SQL/NoSQL/OS command/template), broken
-auth, sensitive data exposure, access control gaps, insecure deserialization,
-hardcoded secrets, vulnerable dependency versions, missing input validation,
-path traversal. For each finding return: CWE ID, severity
-(Critical/High/Med/Low), file:line, one-sentence exploit scenario, and
-recommended fix. Run any available SAST tooling (npm audit, pip-audit,
-OWASP dependency-check) and include its raw output."
-
-## Triage
-
-Write `analysis/$1/SECURITY_FINDINGS.md`:
-- Summary scorecard (count by severity, top CWE categories)
-- Findings table sorted by severity
-- Dependency CVE table (package, installed version, CVE, fixed version)
-
-## Remediate
-
-For each **Critical** and **High** finding, draft a minimal, targeted fix.
-Do **not** edit `legacy/` — write all fixes as a single unified diff to
-`analysis/$1/security_remediation.patch`, with a comment line above each
-hunk citing the finding ID it addresses (`# SEC-001: parameterize the query`).
-
-Add a **Remediation Log** section to SECURITY_FINDINGS.md mapping each
-finding ID → one-line summary of the proposed fix and the patch hunk that
-implements it.
-
-## Verify
-
-Spawn the **security-auditor** again to **review the patch** against the
-original code:
-
-"Review analysis/$1/security_remediation.patch against legacy/$1. For each
-hunk: does it fully remediate the cited finding? Does it introduce new
-vulnerabilities or change behavior beyond the fix? Return one verdict per
-hunk: RESOLVES / PARTIAL / INTRODUCES-RISK, with a one-line reason."
-
-Add a **Patch Review** section to SECURITY_FINDINGS.md with the verdicts.
-If any hunk is PARTIAL or INTRODUCES-RISK, revise the patch and re-review.
-
-## Present
-
-Tell the user the artifacts are ready:
-- `analysis/$1/SECURITY_FINDINGS.md` — findings, remediation log, patch review
-- `analysis/$1/security_remediation.patch` — review, then apply if appropriate
-  with `git -C legacy/$1 apply ../../analysis/$1/security_remediation.patch`
-- Re-run `/modernize-harden $1` after applying to confirm resolution
-
-Suggest: `glow -p analysis/$1/SECURITY_FINDINGS.md`

package/resources/claude-plugins-official/plugins/code-modernization/commands/modernize-map.md

@@ -1,104 +0,0 @@
----
-description: Dependency & topology mapping — call graphs, data lineage, batch flows, rendered as navigable diagrams
-argument-hint: <system-dir>
----
-
-Build a **dependency and topology map** of `legacy/$1` and render it visually.
-
-The assessment gave us domains. Now go one level deeper: how do the *pieces*
-connect? This is the map an engineer needs before touching anything.
-
-## What to produce
-
-Write a one-off analysis script (Python or shell — your choice) that parses
-the source under `legacy/$1` and extracts the four datasets below. Three
-principles apply across stacks; getting them wrong produces a misleading map:
-
-1. **Edges live in two places** — direct calls in source, *and* dispatcher/
-   router calls whose targets are variables (config tables, route maps,
-   dependency injection, dynamic dispatch). Resolve variables against config
-   before declaring an edge unresolvable.
-2. **The code↔storage join is usually external configuration**, not source —
-   job/deployment descriptors map logical names to physical stores.
-3. **Entry points usually live in deployment config**, not source — without
-   parsing it, every top-level module looks unreachable.
-
-Extract:
-
-- **Program/module call graph** — direct calls (`CALL`, method invocations,
-  `import`/`require`) *and* dispatcher calls (`EXEC CICS LINK/XCTL`, DI
-  container wiring, framework routing, reflection/factory). Resolve variable
-  call targets against route tables, copybooks, config, or constant pools.
-- **Data dependency graph** — which modules read/write which data stores,
-  joined through the relevant config: `SELECT…ASSIGN TO` ↔ JCL `DD` (batch
-  COBOL), `EXEC CICS READ/WRITE…FILE()` ↔ CSD `DEFINE FILE` (CICS online),
-  `EXEC SQL` table refs (embedded SQL), ORM annotations/mappings (Java/.NET),
-  model files (Node/Python/Ruby). Include UI/screen bindings (BMS maps, JSPs,
-  templates) — they're dependencies too.
-- **Entry points** — whatever the stack's outermost invoker is, read from
-  where it's defined: JCL `EXEC PGM=` and CICS CSD `DEFINE TRANSACTION`
-  (mainframe), `web.xml`/route annotations/route files (web), `main()`/argv
-  parsing (CLI), queue/scheduler subscriptions (event-driven).
-- **Dead-end candidates** — modules with no inbound edges. **Only meaningful
-  once all the entry-point and call-edge types above are in the graph.**
-  Suppress the dead claim for anything that could be the target of an
-  unresolved dynamic call. A grep-only graph will mark most dispatcher-driven
-  modules (CICS programs, Spring controllers, ORM-bound DAOs) dead when they
-  aren't.
-
-If the source is fixed-column (COBOL columns 8–72, RPG, etc.), slice the
-code area and strip comment lines before regex matching, or you'll match
-sequence numbers and commented-out code.
-
-Save the script as `analysis/$1/extract_topology.py` (or `.sh`) so it can be
-re-run and audited. Have it write a machine-readable
-`analysis/$1/topology.json` and print a human summary. Run it; show the
-summary (cap at ~200 lines for very large estates).
-
-## Render
-
-From the extracted data, generate **three Mermaid diagrams** and write them
-to `analysis/$1/TOPOLOGY.html` as a self-contained page that renders in any
-browser.
-
-The HTML page must use: dark `#1e1e1e` background, `#d4d4d4` text,
-`#cc785c` for `<h2>`/accents, `system-ui` font, all CSS **inline** (no
-external stylesheets). Load Mermaid from a CDN in `<head>`:
-
-```html
-<script type="module">
-  import mermaid from 'https://cdn.jsdelivr.net/npm/mermaid@11/dist/mermaid.esm.min.mjs';
-  mermaid.initialize({ startOnLoad: true, theme: 'dark' });
-</script>
-```
-
-Each diagram goes in a `<pre class="mermaid">...</pre>` block. Do **not**
-wrap diagrams in markdown ` ``` ` fences inside the HTML.
-
-1. **`graph TD` — Module call graph.** Cluster by domain (use `subgraph`).
-   Highlight entry points in a distinct style. Cap at ~40 nodes — if larger,
-   show domain-level with one expanded domain.
-
-2. **`graph LR` — Data lineage.** Programs → data stores.
-   Mark read vs write edges.
-
-3. **`flowchart TD` — Critical path.** Trace ONE end-to-end business flow
-   (e.g., "monthly billing run" or "process payment") through every program
-   and data store it touches, in execution order. If production telemetry is
-   available (see `/modernize-assess` Step 4), annotate each step with its
-   p50/p99 wall-clock.
-
-Also export the three diagrams as standalone `.mmd` files for re-use:
-`analysis/$1/call-graph.mmd`, `analysis/$1/data-lineage.mmd`,
-`analysis/$1/critical-path.mmd`.
-
-## Annotate
-
-Below each `<pre class="mermaid">` block in TOPOLOGY.html, add a `<ul>`
-with 3-5 **architect observations**: tight coupling clusters, single
-points of failure, candidates for service extraction, data stores
-touched by too many writers.
-
-## Present
-
-Tell the user to open `analysis/$1/TOPOLOGY.html` in a browser.

package/resources/claude-plugins-official/plugins/code-modernization/commands/modernize-reimagine.md

@@ -1,83 +0,0 @@
----
-description: Multi-agent greenfield rebuild — extract specs from legacy, design AI-native, scaffold & validate with HITL
-argument-hint: <system-dir> <target-vision>
----
-
-**Reimagine** `legacy/$1` as: $2
-
-This is not a port — it's a rebuild from extracted intent. The legacy system
-becomes the *specification source*, not the structural template. This command
-orchestrates a multi-agent team with explicit human checkpoints.
-
-## Phase A — Specification mining (parallel agents)
-
-Spawn concurrently and show the user that all three are running:
-
-1. **business-rules-extractor** — "Extract every business rule from legacy/$1
-   into Given/When/Then form. Output to a structured list I can parse."
-
-2. **legacy-analyst** — "Catalog every external interface of legacy/$1:
-   inbound (screens, APIs, batch triggers, queues) and outbound (reports,
-   files, downstream calls, DB writes). For each: name, direction, payload
-   shape, frequency/SLA if discernible."
-
-3. **legacy-analyst** — "Identify the core domain entities in legacy/$1 and
-   their relationships. Return as an entity list + Mermaid erDiagram."
-
-Collect results. Write `analysis/$1/AI_NATIVE_SPEC.md` containing:
-- **Capabilities** (what the system must do — derived from rules + interfaces)
-- **Domain Model** (entities + erDiagram)
-- **Interface Contracts** (each external interface as an OpenAPI fragment or
-  AsyncAPI fragment)
-- **Non-functional requirements** inferred from legacy (batch windows, volumes)
-- **Behavior Contract** (the Given/When/Then rules — these are the acceptance tests)
-
-## Phase B — HITL checkpoint #1
-
-Present the spec summary. Ask the user **one focused question**: "Which of
-these capabilities are P0 for the reimagined system, and are there any we
-should deliberately drop?" Wait for the answer. Record it in the spec.
-
-## Phase C — Architecture (single agent, then critique)
-
-Design the target architecture for "$2":
-- Mermaid C4 Container diagram
-- Service boundaries with rationale (which rules/entities live where)
-- Technology choices with one-line justification each
-- Data migration approach from legacy stores
-
-Then spawn **architecture-critic**: "Review this proposed architecture for
-$2 against the spec in analysis/$1/AI_NATIVE_SPEC.md. Identify over-engineering,
-missed requirements, scaling risks, and simpler alternatives." Incorporate
-the critique. Write the result to `analysis/$1/REIMAGINED_ARCHITECTURE.md`.
-
-## Phase D — HITL checkpoint #2
-
-Enter plan mode. Present the architecture. Wait for approval.
-
-## Phase E — Parallel scaffolding
-
-For each service in the approved architecture (cap at 3 to keep the run
-tractable; tell the user which you deferred), spawn a **general-purpose agent
-in parallel**:
-
-"Scaffold the <service-name> service per analysis/$1/REIMAGINED_ARCHITECTURE.md
-and AI_NATIVE_SPEC.md. Create: project skeleton, domain model, API stubs
-matching the interface contracts, and **executable acceptance tests** for every
-behavior-contract rule assigned to this service (mark unimplemented ones as
-expected-failure/skip with the rule ID). Write to modernized/$1-reimagined/<service-name>/."
-
-Show the agents' progress. When all complete, run the acceptance test suites
-and report: total tests, passing (scaffolded behavior), pending (rule IDs
-awaiting implementation).
-
-## Phase F — Knowledge graph handoff
-
-Write `modernized/$1-reimagined/CLAUDE.md` — the persistent context file for
-the new system, containing: architecture summary, service responsibilities,
-where the spec lives, how to run tests, and the legacy→modern traceability
-map. This file IS the knowledge graph that future agents and engineers will
-load.
-
-Report: services scaffolded, acceptance tests defined, % behaviors with a
-home, location of all artifacts.

package/resources/claude-plugins-official/plugins/code-modernization/commands/modernize-transform.md

@@ -1,78 +0,0 @@
----
-description: Transform one legacy module to the target stack — idiomatic rewrite with behavior-equivalence tests
-argument-hint: <system-dir> <module> <target-stack>
----
-
-Transform `legacy/$1` module **`$2`** into **$3**, with proof of behavioral
-equivalence.
-
-This is a surgical, single-module transformation — one vertical slice of the
-strangler fig. Output goes to `modernized/$1/$2/`.
-
-## Step 0 — Plan (HITL gate)
-
-Read the source module and any business rules in `analysis/$1/BUSINESS_RULES.md`
-that reference it. Then **enter plan mode** and present:
-- Which source files are in scope
-- The target module structure (packages/classes/files you'll create)
-- Which business rules / behaviors this module implements
-- How you'll prove equivalence (test strategy)
-- Anything ambiguous that needs a human decision NOW
-
-Wait for approval before writing any code.
-
-## Step 1 — Characterization tests FIRST
-
-Before writing target code, spawn the **test-engineer** subagent:
-
-"Write characterization tests for legacy/$1 module $2. Read the source,
-identify every observable behavior, and encode each as a test case with
-concrete input → expected output pairs derived from the legacy logic.
-Target framework: <appropriate for $3>. Write to
-`modernized/$1/$2/src/test/`. These tests define 'done' — the new code
-must pass all of them."
-
-Show the user the test file. Get a 👍 before proceeding.
-
-## Step 2 — Idiomatic transformation
-
-Write the target implementation in `modernized/$1/$2/src/main/`.
-
-**Critical:** Write code a senior $3 engineer would write from the
-*specification*, not from the legacy structure. Do NOT mirror COBOL paragraphs
-as methods, do NOT preserve legacy variable names like `WS-TEMP-AMT-X`.
-Use the target language's idioms: records/dataclasses, streams, dependency
-injection, proper error types, etc.
-
-Include: domain model, service logic, API surface (REST controller or
-equivalent), and configuration. Add concise Javadoc/docstrings linking each
-class back to the rule IDs it implements.
-
-## Step 3 — Prove it
-
-Run the characterization tests:
-```bash
-cd modernized/$1/$2 && <appropriate test command for $3>
-```
-Show the output. If anything fails, fix and re-run until green.
-
-## Step 4 — Side-by-side review
-
-Generate `modernized/$1/$2/TRANSFORMATION_NOTES.md`:
-- Mapping table: legacy file:lines → target file:lines, per behavior
-- Deliberate deviations from legacy behavior (with rationale)
-- What was NOT migrated (dead code, unreachable branches) and why
-- Follow-ups for the next module that depends on this one
-
-Then show a visual diff of one representative behavior, legacy vs modern:
-```bash
-delta --side-by-side <(sed -n '<lines>p' legacy/$1/<file>) modernized/$1/$2/src/main/<file>
-```
-
-## Step 5 — Architecture review
-
-Spawn the **architecture-critic** subagent to review the transformed code
-against $3 best practices. Apply any HIGH-severity feedback; list the rest
-in TRANSFORMATION_NOTES.md.
-
-Report: tests passing, lines of legacy retired, location of artifacts.

package/resources/claude-plugins-official/plugins/code-review/.claude-plugin/plugin.json

@@ -1,9 +0,0 @@
-{
-  "name": "code-review",
-  "description": "Automated code review for pull requests using multiple specialized agents with confidence-based scoring",
-  "author": {
-    "name": "Anthropic",
-    "email": "support@anthropic.com"
-  }
-}
-

package/resources/claude-plugins-official/plugins/code-review/LICENSE

@@ -1,202 +0,0 @@
-
-                                 Apache License
-                           Version 2.0, January 2004
-                        http://www.apache.org/licenses/
-
-   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
-   1. Definitions.
-
-      "License" shall mean the terms and conditions for use, reproduction,
-      and distribution as defined by Sections 1 through 9 of this document.
-
-      "Licensor" shall mean the copyright owner or entity authorized by
-      the copyright owner that is granting the License.
-
-      "Legal Entity" shall mean the union of the acting entity and all
-      other entities that control, are controlled by, or are under common
-      control with that entity. For the purposes of this definition,
-      "control" means (i) the power, direct or indirect, to cause the
-      direction or management of such entity, whether by contract or
-      otherwise, or (ii) ownership of fifty percent (50%) or more of the
-      outstanding shares, or (iii) beneficial ownership of such entity.
-
-      "You" (or "Your") shall mean an individual or Legal Entity
-      exercising permissions granted by this License.
-
-      "Source" form shall mean the preferred form for making modifications,
-      including but not limited to software source code, documentation
-      source, and configuration files.
-
-      "Object" form shall mean any form resulting from mechanical
-      transformation or translation of a Source form, including but
-      not limited to compiled object code, generated documentation,
-      and conversions to other media types.
-
-      "Work" shall mean the work of authorship, whether in Source or
-      Object form, made available under the License, as indicated by a
-      copyright notice that is included in or attached to the work
-      (an example is provided in the Appendix below).
-
-      "Derivative Works" shall mean any work, whether in Source or Object
-      form, that is based on (or derived from) the Work and for which the
-      editorial revisions, annotations, elaborations, or other modifications
-      represent, as a whole, an original work of authorship. For the purposes
-      of this License, Derivative Works shall not include works that remain
-      separable from, or merely link (or bind by name) to the interfaces of,
-      the Work and Derivative Works thereof.
-
-      "Contribution" shall mean any work of authorship, including
-      the original version of the Work and any modifications or additions
-      to that Work or Derivative Works thereof, that is intentionally
-      submitted to Licensor for inclusion in the Work by the copyright owner
-      or by an individual or Legal Entity authorized to submit on behalf of
-      the copyright owner. For the purposes of this definition, "submitted"
-      means any form of electronic, verbal, or written communication sent
-      to the Licensor or its representatives, including but not limited to
-      communication on electronic mailing lists, source code control systems,
-      and issue tracking systems that are managed by, or on behalf of, the
-      Licensor for the purpose of discussing and improving the Work, but
-      excluding communication that is conspicuously marked or otherwise
-      designated in writing by the copyright owner as "Not a Contribution."
-
-      "Contributor" shall mean Licensor and any individual or Legal Entity
-      on behalf of whom a Contribution has been received by Licensor and
-      subsequently incorporated within the Work.
-
-   2. Grant of Copyright License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      copyright license to reproduce, prepare Derivative Works of,
-      publicly display, publicly perform, sublicense, and distribute the
-      Work and such Derivative Works in Source or Object form.
-
-   3. Grant of Patent License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      (except as stated in this section) patent license to make, have made,
-      use, offer to sell, sell, import, and otherwise transfer the Work,
-      where such license applies only to those patent claims licensable
-      by such Contributor that are necessarily infringed by their
-      Contribution(s) alone or by combination of their Contribution(s)
-      with the Work to which such Contribution(s) was submitted. If You
-      institute patent litigation against any entity (including a
-      cross-claim or counterclaim in a lawsuit) alleging that the Work
-      or a Contribution incorporated within the Work constitutes direct
-      or contributory patent infringement, then any patent licenses
-      granted to You under this License for that Work shall terminate
-      as of the date such litigation is filed.
-
-   4. Redistribution. You may reproduce and distribute copies of the
-      Work or Derivative Works thereof in any medium, with or without
-      modifications, and in Source or Object form, provided that You
-      meet the following conditions:
-
-      (a) You must give any other recipients of the Work or
-          Derivative Works a copy of this License; and
-
-      (b) You must cause any modified files to carry prominent notices
-          stating that You changed the files; and
-
-      (c) You must retain, in the Source form of any Derivative Works
-          that You distribute, all copyright, patent, trademark, and
-          attribution notices from the Source form of the Work,
-          excluding those notices that do not pertain to any part of
-          the Derivative Works; and
-
-      (d) If the Work includes a "NOTICE" text file as part of its
-          distribution, then any Derivative Works that You distribute must
-          include a readable copy of the attribution notices contained
-          within such NOTICE file, excluding those notices that do not
-          pertain to any part of the Derivative Works, in at least one
-          of the following places: within a NOTICE text file distributed
-          as part of the Derivative Works; within the Source form or
-          documentation, if provided along with the Derivative Works; or,
-          within a display generated by the Derivative Works, if and
-          wherever such third-party notices normally appear. The contents
-          of the NOTICE file are for informational purposes only and
-          do not modify the License. You may add Your own attribution
-          notices within Derivative Works that You distribute, alongside
-          or as an addendum to the NOTICE text from the Work, provided
-          that such additional attribution notices cannot be construed
-          as modifying the License.
-
-      You may add Your own copyright statement to Your modifications and
-      may provide additional or different license terms and conditions
-      for use, reproduction, or distribution of Your modifications, or
-      for any such Derivative Works as a whole, provided Your use,
-      reproduction, and distribution of the Work otherwise complies with
-      the conditions stated in this License.
-
-   5. Submission of Contributions. Unless You explicitly state otherwise,
-      any Contribution intentionally submitted for inclusion in the Work
-      by You to the Licensor shall be under the terms and conditions of
-      this License, without any additional terms or conditions.
-      Notwithstanding the above, nothing herein shall supersede or modify
-      the terms of any separate license agreement you may have executed
-      with Licensor regarding such Contributions.
-
-   6. Trademarks. This License does not grant permission to use the trade
-      names, trademarks, service marks, or product names of the Licensor,
-      except as required for reasonable and customary use in describing the
-      origin of the Work and reproducing the content of the NOTICE file.
-
-   7. Disclaimer of Warranty. Unless required by applicable law or
-      agreed to in writing, Licensor provides the Work (and each
-      Contributor provides its Contributions) on an "AS IS" BASIS,
-      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-      implied, including, without limitation, any warranties or conditions
-      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
-      PARTICULAR PURPOSE. You are solely responsible for determining the
-      appropriateness of using or redistributing the Work and assume any
-      risks associated with Your exercise of permissions under this License.
-
-   8. Limitation of Liability. In no event and under no legal theory,
-      whether in tort (including negligence), contract, or otherwise,
-      unless required by applicable law (such as deliberate and grossly
-      negligent acts) or agreed to in writing, shall any Contributor be
-      liable to You for damages, including any direct, indirect, special,
-      incidental, or consequential damages of any character arising as a
-      result of this License or out of the use or inability to use the
-      Work (including but not limited to damages for loss of goodwill,
-      work stoppage, computer failure or malfunction, or any and all
-      other commercial damages or losses), even if such Contributor
-      has been advised of the possibility of such damages.
-
-   9. Accepting Warranty or Additional Liability. While redistributing
-      the Work or Derivative Works thereof, You may choose to offer,
-      and charge a fee for, acceptance of support, warranty, indemnity,
-      or other liability obligations and/or rights consistent with this
-      License. However, in accepting such obligations, You may act only
-      on Your own behalf and on Your sole responsibility, not on behalf
-      of any other Contributor, and only if You agree to indemnify,
-      defend, and hold each Contributor harmless for any liability
-      incurred by, or claims asserted against, such Contributor by reason
-      of your accepting any such warranty or additional liability.
-
-   END OF TERMS AND CONDITIONS
-
-   APPENDIX: How to apply the Apache License to your work.
-
-      To apply the Apache License to your work, attach the following
-      boilerplate notice, with the fields enclosed by brackets "[]"
-      replaced with your own identifying information. (Don't include
-      the brackets!)  The text should be enclosed in the appropriate
-      comment syntax for the file format. We also recommend that a
-      file or class name and description of purpose be included on the
-      same "printed page" as the copyright notice for easier
-      identification within third-party archives.
-
-   Copyright [yyyy] [name of copyright owner]
-
-   Licensed under the Apache License, Version 2.0 (the "License");
-   you may not use this file except in compliance with the License.
-   You may obtain a copy of the License at
-
-       http://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing, software
-   distributed under the License is distributed on an "AS IS" BASIS,
-   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-   See the License for the specific language governing permissions and
-   limitations under the License.