@curdx/flow 2.0.0 → 2.0.2

package/.claude-plugin/marketplace.json

@@ -6,7 +6,7 @@
   },
   "metadata": {
     "description": "Claude Code Discipline Layer — spec-driven workflow + goal-backward verification + Karpathy 4 principles enforced via gates. Stops Claude from faking \"done\" on non-trivial features.",
-    "version": "2.0.0-beta.18"
+    "version": "2.0.2"
   },
   "plugins": [
     {

package/CHANGELOG.md

@@ -1,6 +1,6 @@
 # Changelog
 
-All notable changes to CurDX-Flow will be documented here.
+All notable changes to CurdX-Flow will be documented here.
 
 ## [Unreleased]
 

package/README.md

@@ -1,4 +1,4 @@
-# CurDX-Flow
+# CurdX-Flow
 
 > **Stop Claude Code from faking "done".**
 > Spec-driven workflow + goal-backward verification + Karpathy discipline.
@@ -14,7 +14,7 @@
 
 Claude Code drifts. It claims features work without running the tests. It uses stale library APIs from its training data. It takes three questions worth of code and squeezes in six.
 
-CurDX-Flow is a thin **discipline layer** on top of Claude Code that makes non-trivial feature work actually work:
+CurdX-Flow is a thin **discipline layer** on top of Claude Code that makes non-trivial feature work actually work:
 
 1. **A spec workflow** (research → requirements → design → tasks) for features too big to vibe-code.
 2. **Goal-backward verification** that scans your implementation against your own FR / AC / AD and catches stubs, fake completions, and untested acceptance criteria.
@@ -119,7 +119,7 @@ npm i -g @curdx/flow@^1.1
 
 ## Credits
 
-CurDX-Flow v2 is a distillation, not an invention. Ideas we depend on:
+CurdX-Flow v2 is a distillation, not an invention. Ideas we depend on:
 
 - [**Andrej Karpathy's 4 principles**](https://github.com/forrestchang/andrej-karpathy-skills) — the discipline foundation
 - [**GitHub Spec Kit**](https://github.com/github/spec-kit) — spec-driven development boiled down

package/README.zh.md

@@ -1,4 +1,4 @@
-# CurDX-Flow
+# CurdX-Flow
 
 > **Claude Code 的 AI 工程工作流元框架**
 > 把 Claude Code 变成有工程纪律的 AI 团队 — 编排 MCP 和插件，强制 Karpathy 4 原则，用规格驱动工作流交付高质量软件。
@@ -12,7 +12,7 @@
 
 ## 是什么
 
-CurDX-Flow 是一个 Claude Code 插件，把 6 个验证过的 AI 工程工作流（Karpathy guidelines / BMAD / get-shit-done / gstack / smart-ralph / superpowers）蒸馏成一个可组合系统，然后把基础设施委托给专业的第三方插件（context7 / sequential-thinking / chrome-devtools / claude-mem / pua / frontend-design）。
+CurdX-Flow 是一个 Claude Code 插件，把 6 个验证过的 AI 工程工作流（Karpathy guidelines / BMAD / get-shit-done / gstack / smart-ralph / superpowers）蒸馏成一个可组合系统，然后把基础设施委托给专业的第三方插件（context7 / sequential-thinking / chrome-devtools / claude-mem / pua / frontend-design）。
 
 **不重造轮子。编排好轮子。**
 
@@ -31,7 +31,7 @@ CurDX-Flow 是一个 Claude Code 插件，把 6 个验证过的 AI 工程工作
 
 现有 AI 编程工作流常见问题：
 
-| 问题 | CurDX-Flow 的答案 |
+| 问题 | CurdX-Flow 的答案 |
 |-----|-----------------|
 | 上下文腐烂（长会话质量下降） | Subagent 隔离 + stop-hook 循环 + claude-mem |
 | 无工程纪律（AI 跳步、幻觉） | Karpathy L1 + verification-gate + TDD-gate |
@@ -45,7 +45,7 @@ CurDX-Flow 是一个 Claude Code 插件，把 6 个验证过的 AI 工程工作
 npx @curdx/flow install --all
 ```
 
-这会用 `claude plugin ...` 非交互 CLI 安装 CurDX-Flow 插件、Context7 官方插件、必需 MCP，并安装推荐插件。
+这会用 `claude plugin ...` 非交互 CLI 安装 CurdX-Flow 插件、Context7 官方插件、必需 MCP，并安装推荐插件。
 
 **注意：** 如果你在 `curdx-flow` 项目目录内运行此命令，请使用 `npx --ignore-existing @curdx/flow install --all` 避免 npx 尝试使用本地未安装依赖的包。
 
@@ -121,7 +121,7 @@ claude --plugin-dir ./curdx-flow
 
 ## 致谢
 
-CurDX-Flow 是蒸馏，不是原创。深深致谢：
+CurdX-Flow 是蒸馏，不是原创。深深致谢：
 
 - [**andrej-karpathy-skills**](https://github.com/forrestchang/andrej-karpathy-skills) — 4 原则
 - [**smart-ralph**](https://github.com/Nibzard/smart-ralph) — 规格引擎 + stop-hook 循环

package/agent-preamble/preamble.md

@@ -1,4 +1,4 @@
-# CurDX-Flow Agent Shared Preamble
+# CurdX-Flow Agent Shared Preamble
 
 > All `flow-*` agents and commands inherit this file via `@${CLAUDE_PLUGIN_ROOT}/agent-preamble/preamble.md`.
 > This is a behavioral baseline, not a suggestion. Violation counts as agent failure.

package/bin/curdx-flow.js

@@ -36,7 +36,7 @@ const rest = args.slice(1);
 function printHelp() {
   console.log(`
 ${color.bold("curdx-flow")} ${color.dim(`v${VERSION}`)}
-CurDX-Flow installer & helper for Claude Code
+CurdX-Flow installer & helper for Claude Code
 
 ${color.bold("USAGE")}
   npx @curdx/flow <command> [options]

package/cli/doctor.js

@@ -21,7 +21,7 @@ import { BUNDLED_MCPS, REQUIRED_PLUGINS, RECOMMENDED_PLUGINS } from "./registry.
 export async function doctor(args = []) {
   const verbose = args.includes("--verbose") || args.includes("-v");
 
-  log.title("🏥 CurDX-Flow Health Check");
+  log.title("🏥 CurdX-Flow Health Check");
 
   let errors = 0;
   let warnings = 0;

package/cli/install.js

@@ -78,9 +78,9 @@ export async function install(args = []) {
 
   // Use @clack intro only in interactive TTY mode
   if (process.stdout.isTTY && !yes) {
-    await intro("🚀 CurDX-Flow Installer");
+    await intro("🚀 CurdX-Flow Installer");
   } else {
-    log.title("🚀 CurDX-Flow Installer");
+    log.title("🚀 CurdX-Flow Installer");
   }
 
   // ---------- Step 0: Language selection ----------
@@ -576,13 +576,13 @@ async function promptPluginConfig(plugin, language, config) {
       message: language === "zh"
         ? "输入你的 Context7 API key（或按 Enter 跳过）"
         : "Enter your Context7 API key (or press Enter to skip)",
-      placeholder: "ctx7_...",
+      placeholder: "ctx7sk-...",
       validate: (value) => {
         if (!value) return; // Allow skip
-        if (!value.startsWith("ctx7_")) {
+        if (!value.startsWith("ctx7sk-") && !value.startsWith("ctx7_")) {
           return language === "zh"
-            ? "API key 应该以 ctx7_ 开头"
-            : "API key should start with ctx7_";
+            ? "API key 应该以 ctx7sk- 或 ctx7_ 开头"
+            : "API key should start with ctx7sk- or ctx7_";
         }
       },
     });

package/cli/uninstall.js

@@ -47,7 +47,7 @@ export async function uninstall(args = []) {
   const purge = args.includes("--purge");
   const keepRecommended = args.includes("--keep-recommended");
 
-  log.title("🗑️  CurDX-Flow Uninstaller");
+  log.title("🗑️  CurdX-Flow Uninstaller");
 
   // ---------- Step 1: claude CLI present? ----------
   const cv = claudeVersion();

package/cli/upgrade.js

@@ -9,7 +9,7 @@ import {
 } from "./registry.js";
 
 export async function upgrade(args = []) {
-  log.title("⬆️  CurDX-Flow upgrade");
+  log.title("⬆️  CurdX-Flow upgrade");
 
   if (!claudeVersion()) {
     log.err("claude CLI not found");

package/commands/help.md

@@ -1,18 +1,18 @@
 ---
 name: help
-description: Show CurDX-Flow command list, workflow overview, or troubleshooting guide. With a command name, show that command's detail.
+description: Show CurdX-Flow command list, workflow overview, or troubleshooting guide. With a command name, show that command's detail.
 argument-hint: "[<command-name> | workflow | troubleshoot]"
 allowed-tools: [Read, Bash]
 ---
 
-# CurDX-Flow Help
+# CurdX-Flow Help
 
 ## No argument — quick overview
 
 Show the 9 core slash commands + 5 auto-invoked skills. Keep the table compact, use tabs for alignment.
 
 ```
-🚀 CurDX-Flow v2 — Claude Code Discipline Layer
+🚀 CurdX-Flow v2 — Claude Code Discipline Layer
 
   9 slash commands (explicit control)
   ────────────────────────────────────
@@ -61,7 +61,7 @@ If the argument isn't a known command, list the 9 candidates and the 5 skill nam
 ## `workflow` — standard workflow
 
 ```
-📐 CurDX-Flow v2 Standard Workflow
+📐 CurdX-Flow v2 Standard Workflow
 
 1. One-time setup (outside Claude Code)
    └─ npx @curdx/flow install --all

package/commands/implement.md

@@ -15,7 +15,7 @@ Execute spec tasks per tasks.md. Select the best execution strategy based on arg
 ## Step 1: Preflight Checks
 
 ```bash
-[ ! -d ".flow" ] && { echo "✗ Not a CurDX-Flow project. Run /curdx-flow:init first"; exit 1; }
+[ ! -d ".flow" ] && { echo "✗ Not a CurdX-Flow project. Run /curdx-flow:init first"; exit 1; }
 
 ARGS="$ARGUMENTS"
 SPEC_NAME=""

package/commands/init.md

@@ -1,13 +1,13 @@
 ---
 name: init
-description: Initialize the CurDX-Flow project structure (create the .flow/ directory and core files)
+description: Initialize the CurdX-Flow project structure (create the .flow/ directory and core files)
 argument-hint: "[--force]"
 allowed-tools: [Read, Write, Bash, AskUserQuestion]
 ---
 
-# Initialize CurDX-Flow Project
+# Initialize CurdX-Flow Project
 
-Create the `.flow/` directory structure in the current directory so CurDX-Flow can operate in this project.
+Create the `.flow/` directory structure in the current directory so CurdX-Flow can operate in this project.
 
 ## Execution Steps
 
@@ -56,7 +56,7 @@ Placeholders:
 Append (if not already present):
 
 ```
-# CurDX-Flow runtime files
+# CurdX-Flow runtime files
 .flow/checkpoints/
 .flow/threads/
 .flow/seeds/
@@ -91,7 +91,7 @@ Items the CLI doctor covers (for user reference):
 Output:
 
 ```
-✓ CurDX-Flow project initialized
+✓ CurdX-Flow project initialized
   .flow/
   ├── PROJECT.md       ← fill in your project vision
   ├── CONTEXT.md       ← fill in your preferences

package/commands/review.md

@@ -22,7 +22,7 @@ Distinct from `/curdx-flow:verify`:
 ## Preflight
 
 ```bash
-[ ! -d ".flow" ] && { echo "✗ Not a CurDX-Flow project."; exit 1; }
+[ ! -d ".flow" ] && { echo "✗ Not a CurdX-Flow project."; exit 1; }
 
 SPEC_NAME=$(cat .flow/.active-spec 2>/dev/null)
 [ -z "$SPEC_NAME" ] && { echo "✗ No active spec."; exit 1; }

package/commands/spec.md

@@ -24,7 +24,7 @@ This command writes the four spec documents (`research.md`, `requirements.md`, `
 ```bash
 # 1. A .flow project must exist
 [ ! -d ".flow" ] && {
-  echo "✗ Not a CurDX-Flow project. Run /curdx-flow:init first.";
+  echo "✗ Not a CurdX-Flow project. Run /curdx-flow:init first.";
   exit 1;
 }
 

package/commands/start.md

@@ -25,7 +25,7 @@ Entry point for every feature. Works in four modes depending on flags and existi
 ```bash
 # Require a .flow project
 [ ! -d ".flow" ] && {
-  echo "✗ Not a CurDX-Flow project. Run /curdx-flow:init first.";
+  echo "✗ Not a CurdX-Flow project. Run /curdx-flow:init first.";
   exit 1;
 }
 ```

package/commands/verify.md

@@ -18,7 +18,7 @@ This is the **differentiator command**: it scans the implementation against the
 ## Preflight
 
 ```bash
-[ ! -d ".flow" ] && { echo "✗ Not a CurDX-Flow project."; exit 1; }
+[ ! -d ".flow" ] && { echo "✗ Not a CurdX-Flow project."; exit 1; }
 
 SPEC_NAME=$(cat .flow/.active-spec 2>/dev/null)
 [ -z "$SPEC_NAME" ] && { echo "✗ No active spec. Run /curdx-flow:start first."; exit 1; }

package/gates/verification-gate.md

@@ -180,4 +180,4 @@ Fix recommendations:
 
 ---
 
-_Source: superpowers' verification-before-completion skill. CurDX-Flow turns it into a gate._
+_Source: superpowers' verification-before-completion skill. CurdX-Flow turns it into a gate._

package/knowledge/atomic-commits.md

@@ -1,6 +1,6 @@
 # Atomic Commits — Atomic Commit Rules
 
-> One task, one commit. This is the iron rule for all execution agents in CurDX-Flow.
+> One task, one commit. This is the iron rule for all execution agents in CurdX-Flow.
 >
 > Agents reference this via `@${CLAUDE_PLUGIN_ROOT}/knowledge/atomic-commits.md`.
 
@@ -18,7 +18,7 @@ Why:
 
 ---
 
-## Commit Message Format (Conventional Commits + CurDX-Flow extensions)
+## Commit Message Format (Conventional Commits + CurdX-Flow extensions)
 
 ```
 <type>(<scope>): <summary>
@@ -94,7 +94,7 @@ Added tests for success and failure cases.
 
 ## Footer (reference IDs)
 
-CurDX-Flow extension: if a task references FR / AC / AD / D-NN, list them in the footer:
+CurdX-Flow extension: if a task references FR / AC / AD / D-NN, list them in the footer:
 
 ```
 feat(auth): implement JWT refresh flow
@@ -230,7 +230,7 @@ PR review reads each commit's message.
 - Good commit message → reviewer finishes in 5 minutes
 - Bad commit message → reviewer either rubber-stamps or blocks without reading
 
-CurDX-Flow's `/curdx-flow:ship` command (Phase 6) will turn atomic commits into a clean PR description. Poor commit quality yields poor PR descriptions.
+CurdX-Flow's `/curdx-flow:ship` command (Phase 6) will turn atomic commits into a clean PR description. Poor commit quality yields poor PR descriptions.
 
 ---
 
@@ -255,8 +255,8 @@ Reading this history, anyone can understand:
 - Then TDD red (tests) → green (implementation)
 - Every step is atomic
 
-This is the quality CurDX-Flow demands.
+This is the quality CurdX-Flow demands.
 
 ---
 
-_CurDX-Flow internal rule. Violation counts as a flow-executor task failure._
+_CurdX-Flow internal rule. Violation counts as a flow-executor task failure._

package/knowledge/karpathy-guidelines.md

@@ -1,6 +1,6 @@
 # Karpathy Guidelines — Detailed Version
 
-> Source: Andrej Karpathy's observations on X about LLM coding pitfalls. This is CurDX-Flow's L1 behavior baseline — all agents inherit from it.
+> Source: Andrej Karpathy's observations on X about LLM coding pitfalls. This is CurdX-Flow's L1 behavior baseline — all agents inherit from it.
 >
 > Agents reference this file via `@${CLAUDE_PLUGIN_ROOT}/knowledge/karpathy-guidelines.md`.
 
@@ -216,4 +216,4 @@ These 4 principles **reduce speed to improve accuracy**. For trivial tasks (rena
 
 ---
 
-_Source: Andrej Karpathy's observations on LLM coding pitfalls, distilled for CurDX-Flow._
+_Source: Andrej Karpathy's observations on LLM coding pitfalls, distilled for CurdX-Flow._

package/knowledge/planning-reviews.md

@@ -208,4 +208,4 @@ The two don't overlap. Plan Review prevents "doing the wrong thing", Code Review
 
 ---
 
-_source: gstack's 4 maps review system. CurDX-Flow simplifies to 4 independent commands + one aggregated command._
+_source: gstack's 4 maps review system. CurdX-Flow simplifies to 4 independent commands + one aggregated command._

package/knowledge/spec-driven-development.md

@@ -1,4 +1,4 @@
-# Spec-Driven Development — CurDX-Flow Methodology
+# Spec-Driven Development — CurdX-Flow Methodology
 
 > Spec-driven development (SDD): decompose the path from "idea" to "code" into 4 verifiable phases, each with clear deliverables.
 >

package/knowledge/two-stage-review.md

@@ -1,6 +1,6 @@
 # Two-Stage Review — Two-Stage Code Review
 
-> CurDX-Flow version of Superpowers' code review skill.
+> CurdX-Flow version of Superpowers' code review skill.
 >
 > Agents reference this via `@${CLAUDE_PLUGIN_ROOT}/knowledge/two-stage-review.md`.
 
@@ -231,4 +231,4 @@ Verify is "did we implement the right thing", Review is "is the implementation g
 
 ---
 
-_Source: superpowers' code-review two-stage design, extended with CurDX-Flow's Gate system._
+_Source: superpowers' code-review two-stage design, extended with CurdX-Flow's Gate system._

package/knowledge/wave-execution.md

@@ -384,4 +384,4 @@ As in "Case 3" above. Solutions:
 
 ---
 
-_Source: get-shit-done's wave execution. CurDX-Flow turns it from a concept into executable logic._
+_Source: get-shit-done's wave execution. CurdX-Flow turns it from a concept into executable logic._

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@curdx/flow",
-  "version": "2.0.0",
-  "description": "CLI installer for CurDX-Flow — AI engineering workflow meta-framework for Claude Code",
+  "version": "2.0.2",
+  "description": "CLI installer for CurdX-Flow — AI engineering workflow meta-framework for Claude Code",
   "type": "module",
   "bin": {
     "curdx-flow": "bin/curdx-flow.js"

package/schemas/config.schema.json

@@ -1,7 +1,7 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
   "$id": "https://curdx-flow.dev/schemas/config.schema.json",
-  "title": "CurDX-Flow Project Config",
+  "title": "CurdX-Flow Project Config",
   "description": "Schema for .flow/config.json",
   "type": "object",
   "required": ["version", "mode"],

package/schemas/spec-frontmatter.schema.json

@@ -1,7 +1,7 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
   "$id": "https://curdx-flow.dev/schemas/spec-frontmatter.schema.json",
-  "title": "CurDX-Flow Spec Document Frontmatter",
+  "title": "CurdX-Flow Spec Document Frontmatter",
   "description": "YAML frontmatter at the top of research.md / requirements.md / design.md / tasks.md",
   "type": "object",
   "required": ["spec", "phase", "created", "version"],

package/schemas/spec-state.schema.json

@@ -1,7 +1,7 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
   "$id": "https://curdx-flow.dev/schemas/spec-state.schema.json",
-  "title": "CurDX-Flow Spec State",
+  "title": "CurdX-Flow Spec State",
   "description": "Schema for .flow/specs/<name>/.state.json — tracks phase progress across sessions",
   "type": "object",
   "required": ["version", "spec_name", "phase"],