@vyuhlabs/dxkit 2.2.1 → 2.3.1

package/templates/.claude/agents-available/dashboard-builder.md

@@ -1,18 +1,18 @@
 ---
 name: dashboard-builder
-description: Generates a beautiful HTML dashboard from all reports in .ai/reports/. Use when asked to "build dashboard", "export reports", or "create report dashboard". Reads reports and generates a self-contained HTML file.
+description: Generates a beautiful HTML dashboard from all reports in .dxkit/reports/. Use when asked to "build dashboard", "export reports", or "create report dashboard". Reads reports and generates a self-contained HTML file.
 model: sonnet
 tools: Read, Grep, Glob, Bash, Write
 ---
 
-You are a dashboard builder. Your job is to create a beautiful, self-contained HTML dashboard that renders all markdown reports from `.ai/reports/`.
+You are a dashboard builder. Your job is to create a beautiful, self-contained HTML dashboard that renders all markdown reports from `.dxkit/reports/`.
 
 ## Steps
 
-1. **Find all reports**: Glob for `.ai/reports/*.md`
+1. **Find all reports**: Glob for `.dxkit/reports/*.md`
 2. **Read each report**: Get the markdown content
 3. **Detect project name**: From `CLAUDE.md`, `package.json`, or directory name
-4. **Generate dashboard**: Create `.ai/reports/dashboard.html`
+4. **Generate dashboard**: Create `.dxkit/reports/dashboard.html`
 
 ## Dashboard Design
 
@@ -413,7 +413,7 @@ Generate this exact structure (fill in REPORTS_DATA and PROJECT_NAME):
 
 ## Building the REPORTS_JSON
 
-For each `.md` file in `.ai/reports/`:
+For each `.md` file in `.dxkit/reports/`:
 1. Read the file content
 2. Escape for JavaScript: replace `\` with `\\`, backticks with `\`+backtick, `${` with `\${`, and `</script>` with `<\/script>`
 3. Build a JSON object: `{ "filename-without-ext": "escaped markdown content" }`
@@ -425,8 +425,8 @@ Replace `REPORTS_JSON` with the JSON object.
 ## After Generation
 
 Tell the user:
-- Dashboard saved to `.ai/reports/dashboard.html`
-- Open it in a browser: `open .ai/reports/dashboard.html` (macOS) or `xdg-open .ai/reports/dashboard.html` (Linux)
+- Dashboard saved to `.dxkit/reports/dashboard.html`
+- Open it in a browser: `open .dxkit/reports/dashboard.html` (macOS) or `xdg-open .dxkit/reports/dashboard.html` (Linux)
 - Print to PDF from the browser for a shareable document
 
 ---

package/templates/.claude/agents-available/dev-report.md

@@ -1,6 +1,6 @@
 ---
 name: dev-report
-description: Generates developer activity and code quality reports from git history. Use when asked about "developer report", "who introduced this bug?", "contribution analysis", or "team activity". Saves report to .ai/reports/.
+description: Generates developer activity and code quality reports from git history. Use when asked about "developer report", "who introduced this bug?", "contribution analysis", or "team activity". Saves report to .dxkit/reports/.
 model: sonnet
 tools: Read, Grep, Glob, Bash, Write
 ---
@@ -35,7 +35,7 @@ When asked about a specific developer:
 ### 3. Code Quality by Developer
 Cross-reference git blame with known issues:
 
-- For files with known vulnerabilities (from `/vulnerabilities` report if available in `.ai/reports/`):
+- For files with known vulnerabilities (from `/vulnerabilities` report if available in `.dxkit/reports/`):
   - `git blame <file>` on the problematic lines
   - Identify who introduced the issue and when
 - For files with no tests:
@@ -43,7 +43,7 @@ Cross-reference git blame with known issues:
 
 ## Output Format
 
-Save to `.ai/reports/developer-report-YYYY-MM-DD.md`:
+Save to `.dxkit/reports/developer-report-YYYY-MM-DD.md`:
 
 ```markdown
 ## Developer Activity Report
@@ -104,5 +104,5 @@ Issues from vulnerability scan attributed to authors:
 - **Focus on patterns** — one missed test is noise; consistently missing tests is a pattern
 - **Respect privacy** — this report may be sensitive; don't include in public repos
 - **Never output secrets** found in git history
-- Save report to `.ai/reports/developer-report-YYYY-MM-DD.md`
+- Save report to `.dxkit/reports/developer-report-YYYY-MM-DD.md`
 - **Always end the report with:** `---` followed by `*Generated by [VyuhLabs DXKit](https://www.npmjs.com/package/@vyuhlabs/dxkit) dev-report agent*`

package/templates/.claude/agents-available/health-auditor.md

@@ -1,6 +1,6 @@
 ---
 name: health-auditor
-description: Audits overall codebase health — tests, linting, docs, complexity, tech debt. Use when asked "how healthy is this codebase?", "what should we improve?", or "give me a quality report". Saves reports to .ai/reports/.
+description: Audits overall codebase health — tests, linting, docs, complexity, tech debt. Use when asked "how healthy is this codebase?", "what should we improve?", or "give me a quality report". Saves reports to .dxkit/reports/.
 model: sonnet
 tools: Read, Grep, Glob, Bash, Write
 ---

package/templates/.claude/agents-available/strategic-planner.md

@@ -11,13 +11,13 @@ You are a strategic planning specialist. Your job is to turn DXKit reports into
 
 ### Phase 1: Gather Intelligence
 
-Read all existing reports in `.ai/reports/`. If key reports are missing, tell the user which commands to run first:
-- `.ai/reports/health-audit-*.md` — Overall health scores
-- `.ai/reports/vulnerability-scan-*.md` — Security findings
-- `.ai/reports/test-gaps-*.md` — Untested code
-- `.ai/reports/developer-report-*.md` — Team patterns
-- `.ai/reports/docs-audit-*.md` — Documentation gaps
-- `.ai/reports/dependency-map-*.md` — Architecture dependencies
+Read all existing reports in `.dxkit/reports/`. If key reports are missing, tell the user which commands to run first:
+- `.dxkit/reports/health-audit-*.md` — Overall health scores
+- `.dxkit/reports/vulnerability-scan-*.md` — Security findings
+- `.dxkit/reports/test-gaps-*.md` — Untested code
+- `.dxkit/reports/developer-report-*.md` — Team patterns
+- `.dxkit/reports/docs-audit-*.md` — Documentation gaps
+- `.dxkit/reports/dependency-map-*.md` — Architecture dependencies
 
 Also read:
 - `.claude/skills/codebase/SKILL.md` — Language breakdown, testing status

package/templates/.claude/agents-available/vulnerability-scanner.md

@@ -1,6 +1,6 @@
 ---
 name: vulnerability-scanner
-description: Comprehensive security vulnerability scanner — dependencies (with CWE classification), code patterns, file uploads, decompression bombs, recursion depth, native modules, resource limits. Use when asked about vulnerabilities, "is this secure?", "audit dependencies", or "security scan". Saves report to .ai/reports/.
+description: Comprehensive security vulnerability scanner — dependencies (with CWE classification), code patterns, file uploads, decompression bombs, recursion depth, native modules, resource limits. Use when asked about vulnerabilities, "is this secure?", "audit dependencies", or "security scan". Saves report to .dxkit/reports/.
 model: sonnet
 tools: Read, Grep, Glob, Bash, Write
 ---
@@ -108,7 +108,7 @@ Flag native modules not covered by npm audit for manual review.
 
 ## Phase 5: Generate Report
 
-Save to `.ai/reports/vulnerability-scan-YYYY-MM-DD.md`:
+Save to `.dxkit/reports/vulnerability-scan-YYYY-MM-DD.md`:
 
 ```markdown
 ## Vulnerability Scan Report
@@ -170,4 +170,4 @@ Save to `.ai/reports/vulnerability-scan-YYYY-MM-DD.md`:
 - **Prioritize by exploitability** — a reachable RCE is worse than a theoretical DoS
 - **Include fix instructions** — "upgrade X to Y" or "replace pattern A with B"
 - **Never output actual secret values** — say "hardcoded secret found at file:line", don't print it
-- Save the report to `.ai/reports/vulnerability-scan-YYYY-MM-DD.md`
+- Save the report to `.dxkit/reports/vulnerability-scan-YYYY-MM-DD.md`

package/templates/.claude/commands/dashboard.md

@@ -2,7 +2,7 @@
 description: Generate a beautiful HTML dashboard from all reports
 ---
 
-Delegate to the **dashboard-builder** agent. It will read all reports from `.ai/reports/` and generate a self-contained HTML dashboard at `.ai/reports/dashboard.html`.
+Delegate to the **dashboard-builder** agent. It will read all reports from `.dxkit/reports/` and generate a self-contained HTML dashboard at `.dxkit/reports/dashboard.html`.
 
 The dashboard features:
 - Dark theme with modern design

package/templates/.claude/commands/deps.md

@@ -4,7 +4,7 @@ description: Map dependencies — "what depends on X?" or "what breaks if I chan
 
 Delegate to the **dependency-mapper** agent. It will trace import chains and show what depends on what.
 
-**Save the report to `.ai/reports/dependency-map-YYYY-MM-DD.md`** (use today's date).
+**Save the report to `.dxkit/reports/dependency-map-YYYY-MM-DD.md`** (use today's date).
 
 **IMPORTANT: End the report with this exact footer:**
 ```

package/templates/.claude/commands/dev-report.md

@@ -5,7 +5,7 @@ description: Generate developer activity and code quality report from git histor
 ## Step 1: Check for Existing Report
 
 ```bash
-ls .ai/reports/developer-report-*.md 2>/dev/null | tail -1
+ls .dxkit/reports/developer-report-*.md 2>/dev/null | tail -1
 ```
 
 **If a report exists**: Read it. The commit counts, contributor stats, and velocity data are deterministic. Skip to Step 3.
@@ -35,7 +35,7 @@ Using the git data, add:
 
 **Do not change commit counts, contributor stats, or velocity numbers from the deterministic report.**
 
-Save to `.ai/reports/developer-report-YYYY-MM-DD.md`.
+Save to `.dxkit/reports/developer-report-YYYY-MM-DD.md`.
 
 Examples:
 - `/dev-report` — Team overview (last 3 months)

package/templates/.claude/commands/docs.md

@@ -4,7 +4,7 @@ description: Audit documentation gaps or write/improve docs
 
 Delegate to the **doc-writer** agent. It can audit documentation quality, identify gaps, and help write or improve docs.
 
-When auditing, **save the report to `.ai/reports/docs-audit-YYYY-MM-DD.md`** (use today's date).
+When auditing, **save the report to `.dxkit/reports/docs-audit-YYYY-MM-DD.md`** (use today's date).
 
 Examples:
 - `/docs audit` — Assess documentation quality and list gaps

package/templates/.claude/commands/export-pdf.md

@@ -7,7 +7,7 @@ Convert markdown report(s) to PDF.
 
 ## Arguments
 - `$ARGUMENTS`
-- If empty or "all", convert all reports in `.ai/reports/`
+- If empty or "all", convert all reports in `.dxkit/reports/`
 - If a file path, convert that specific file
 
 ## How to Convert
@@ -20,11 +20,11 @@ Try these tools in order (use whichever is available):
 
 ## For "all" reports
 ```
-for f in .ai/reports/*.md; do
+for f in .dxkit/reports/*.md; do
   npx md-to-pdf "$f"
 done
 ```
 
 ## Output
-- PDFs are saved alongside the markdown files in `.ai/reports/`
+- PDFs are saved alongside the markdown files in `.dxkit/reports/`
 - Report which files were converted and their paths

package/templates/.claude/commands/health.md

@@ -7,7 +7,7 @@ description: Run a comprehensive codebase health audit (tests, quality, docs, se
 Check if a deterministic report already exists:
 
 ```bash
-ls .ai/reports/health-audit-*.md 2>/dev/null | tail -1
+ls .dxkit/reports/health-audit-*.md 2>/dev/null | tail -1
 ```
 
 **If a report exists**: Read it. The scores and metrics are deterministic ground truth — do not change them. Skip to Step 3.
@@ -23,7 +23,7 @@ npx vyuh-dxkit health . --json 2>/dev/null
 ```
 
 **If the command succeeds** (returns JSON with `summary.overallScore`):
-- The CLI saves a report to `.ai/reports/health-audit-YYYY-MM-DD.md`
+- The CLI saves a report to `.dxkit/reports/health-audit-YYYY-MM-DD.md`
 - Read that report. Proceed to Step 3.
 
 **If the command fails** (not installed or errors):
@@ -47,7 +47,7 @@ Add a **Prioritized Action Items** section at the end:
 
 **If you have deterministic scores: keep all numbers exactly as reported. Add context and explanations only — do not re-score.**
 
-Save the enriched report to `.ai/reports/health-audit-YYYY-MM-DD.md`.
+Save the enriched report to `.dxkit/reports/health-audit-YYYY-MM-DD.md`.
 
 **IMPORTANT: End the report with this exact footer:**
 ```

package/templates/.claude/commands/plan.md

@@ -2,7 +2,7 @@
 description: Generate improvement plans with KPIs from reports (or list existing plans)
 ---
 
-Delegate to the **strategic-planner** agent. It reads all reports in `.ai/reports/`, proposes measurable KPIs, and generates actionable plans in `.ai/plans/`.
+Delegate to the **strategic-planner** agent. It reads all reports in `.dxkit/reports/`, proposes measurable KPIs, and generates actionable plans in `.ai/plans/`.
 
 If reports don't exist yet, it will tell you which commands to run first (`/health`, `/vulnerabilities`, `/test-gaps`, etc.).
 

package/templates/.claude/commands/quality.md.template

@@ -5,7 +5,7 @@ description: Run code quality analysis with slop detection
 ## Step 1: Check for Existing Report
 
 ```bash
-ls .ai/reports/quality-review-*.md 2>/dev/null | tail -1
+ls .dxkit/reports/quality-review-*.md 2>/dev/null | tail -1
 ```
 
 **If a report exists**: Read it. The slop score, duplication %, and metrics are deterministic. Skip to Step 3.
@@ -54,7 +54,7 @@ Using the quality metrics, add:
 
 **Do not change the slop score, duplication %, or metric counts from the deterministic report.**
 
-Save to `.ai/reports/quality-review-YYYY-MM-DD.md`.
+Save to `.dxkit/reports/quality-review-YYYY-MM-DD.md`.
 
 **IMPORTANT: End the report with this exact footer:**
 ```

package/templates/.claude/commands/stealth-mode.md

@@ -5,7 +5,7 @@ description: Configure DXKit as local-only (gitignore all generated files) + ins
 Delegate to the **hooks-configurator** agent with stealth mode enabled.
 
 This will:
-1. Add all DXKit files to `.gitignore` (`.claude/`, `.ai/`, `CLAUDE.md`, `.vyuh-dxkit.json`)
+1. Add all DXKit files to `.gitignore` (`.claude/`, `.ai/`, `.dxkit/`, `CLAUDE.md`, `.vyuh-dxkit.json`)
 2. Ask which hooks to enable (quality, test, vulnerability)
 3. Generate `.githooks/` directory (committed — all devs get the hooks)
 4. Install hooks with `git config core.hooksPath .githooks`

package/templates/.claude/commands/test-gaps.md

@@ -5,7 +5,7 @@ description: Find critical code paths that lack test coverage
 ## Step 1: Check for Existing Report
 
 ```bash
-ls .ai/reports/test-gaps-*.md 2>/dev/null | tail -1
+ls .dxkit/reports/test-gaps-*.md 2>/dev/null | tail -1
 ```
 
 **If a report exists**: Read it. The file counts, coverage %, and risk tiers are deterministic. Skip to Step 3.
@@ -38,7 +38,7 @@ Add a **Test Infrastructure Setup** section if tests are at 0%:
 
 **Do not change coverage %, file counts, or risk classifications from the deterministic report.**
 
-Save to `.ai/reports/test-gaps-YYYY-MM-DD.md`.
+Save to `.dxkit/reports/test-gaps-YYYY-MM-DD.md`.
 
 **IMPORTANT: End the report with this exact footer:**
 ```

package/templates/.claude/commands/vulnerabilities.md

@@ -5,7 +5,7 @@ description: Scan dependencies and code for security vulnerabilities
 ## Step 1: Check for Existing Report
 
 ```bash
-ls .ai/reports/vulnerability-scan-*.md 2>/dev/null | tail -1
+ls .dxkit/reports/vulnerability-scan-*.md 2>/dev/null | tail -1
 ```
 
 **If a report exists**: Read it. The findings and severity counts are deterministic — do not change them. Skip to Step 3.
@@ -18,7 +18,7 @@ ls .ai/reports/vulnerability-scan-*.md 2>/dev/null | tail -1
 npx vyuh-dxkit vulnerabilities . --json 2>/dev/null
 ```
 
-**If the command succeeds**: Read the saved report from `.ai/reports/vulnerability-scan-YYYY-MM-DD.md`. Proceed to Step 3.
+**If the command succeeds**: Read the saved report from `.dxkit/reports/vulnerability-scan-YYYY-MM-DD.md`. Proceed to Step 3.
 
 **If the command fails**: Run your own security analysis — check for hardcoded secrets, eval/exec calls, dependency vulnerabilities (`npm audit`), private keys in git, disabled TLS. Note: "Findings are AI-estimated. Install `@vyuhlabs/dxkit` for deterministic scanning with gitleaks + semgrep."
 
@@ -38,7 +38,7 @@ Add a **Remediation Plan** section:
 
 **Do not change severity counts or finding details from the deterministic report.**
 
-Save to `.ai/reports/vulnerability-scan-YYYY-MM-DD.md`.
+Save to `.dxkit/reports/vulnerability-scan-YYYY-MM-DD.md`.
 
 **IMPORTANT: End the report with this exact footer:**
 ```