nexus-dev-toolkit 3.0.0__tar.gz → 3.0.1__tar.gz

{nexus_dev_toolkit-3.0.0/nexus_dev_toolkit.egg-info → nexus_dev_toolkit-3.0.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: nexus-dev-toolkit
-Version: 3.0.0
+Version: 3.0.1
 Summary: LLM-agnostic developer workflow toolkit — Day 0 scaffold + Day 1 EPAV
 Author-email: Ronald dela Cruz <rcdelacruz@users.noreply.github.com>
 License-Expression: MIT
@@ -24,7 +24,7 @@ Dynamic: license-file
 [![Python](https://img.shields.io/pypi/pyversions/nexus-dev-toolkit)](https://pypi.org/project/nexus-dev-toolkit/)
 [![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)
 
-Developer workflow toolkit for AI-assisted development. Gives any team a structured Day 0 scaffold and repeatable Day 1 feature cycle via the EPAV methodology.
+Developer workflow toolkit for Claude Code. Gives any team a structured Day 0 scaffold and repeatable Day 1 feature cycle via the EPAV methodology.
 
 ---
 
@@ -32,7 +32,7 @@ Developer workflow toolkit for AI-assisted development. Gives any team a structu
 
 Ad-hoc AI prompting doesn't scale. Every dev prompts differently, context drifts, and nobody knows what the AI was told last sprint.
 
-`nexus-dev-toolkit` gives your team a single workflow:
+nexus-dev-toolkit gives your team a single workflow:
 
 - **Day 0** — scaffold the project once, production-grade, zero credentials needed
 - **Day 1** — every feature follows the same four steps: evaluate → plan → apply → validate
@@ -41,67 +41,78 @@ Every skill, every rule, every pattern lives in the project repo — versioned,
 
 ---
 
-## The Workflow
+## Setup
 
-### Day 0 — `/scaffold` (once per project)
+### 1. Install prerequisites
 
-```
-nexus init <project-dir>
+**uv** (recommended package manager):
+```bash
+curl -LsSf https://astral.sh/uv/install.sh | sh
 ```
 
-Sets up `.claude/commands/`, `.claude/settings.json`, and `knowledge/`. Then in Claude Code:
-
-```
-/scaffold
+**Claude Code:**
+```bash
+npm install -g @anthropic-ai/claude-code
+claude login
 ```
 
-EVALUATE → PLAN → APPLY → VALIDATE. Produces a production-grade project: correct stack from your arch doc, mock auth, mock data, design system, AGENTS.md — all from your architecture document. Runs with `npm install && npm run dev` (or equivalent) from commit one.
+**graphify** _(strongly recommended)_ — builds a queryable knowledge graph of your codebase. EPAV skills query this graph to understand blast radius and cross-file dependencies before touching any code.
 
-### Day 1 — EPAV (every feature, every sprint)
+| | With graphify | Without graphify |
+|---|---|---|
+| Context loading | Scoped subgraph — fast, low token cost | Full file reads — slow, high token cost |
+| Blast radius | Accurate, graph-backed | Best-effort, grep-based |
+| Auto-update | PostToolUse hook keeps graph current | N/A |
+| EPAV skills | Full capability | Degraded but functional |
 
+```bash
+uv tool install graphifyy   # PyPI package name has double y; command is "graphify"
+graphify install             # registers /graphify skill into Claude Code
 ```
-/evaluate   →   /plan   →   /apply   →   /validate
-```
-
-Each step is a built-in skill in `.claude/commands/`. Every task starts with a row from the dev tasks CSV. Every task ends with acceptance criteria verified.
-
----
 
-## Install
-
-**Requirements:** Python 3.10+, `uv` (recommended) or `pip`
+### 2. Install nexus-dev-toolkit
 
 ```bash
-# Recommended
 uv tool install nexus-dev-toolkit
-
-# Or via pip
-pip install nexus-dev-toolkit
 ```
 
----
-
-## Quick Start
+### 3. Initialize your project
 
 ```bash
 cd my-project
 nexus init .
 ```
 
-Then open the project in Claude Code and type `/scaffold`.
+### 4. Build the knowledge graph
+
+Open the project in Claude Code and run:
+```
+/graphify .
+```
+
+This generates `graphify-out/graph.json` — required by all EPAV skills.
+
+### 5. Start Day 0
+
+```
+/scaffold
+```
 
 ---
 
-## Commands
+## The Workflow
+
+### Day 0 — `/scaffold` (once per project)
+
+EVALUATE → PLAN → APPLY → VALIDATE. Produces a production-grade project from your architecture document and Figma design: correct stack, mock auth, mock data, design system, AGENTS.md — zero external dependencies. Runs `npm install && npm run dev` (or equivalent) from commit one.
+
+### Day 1 — EPAV (every feature, every sprint)
 
-```bash
-nexus init .                 # set up .claude/commands/ + knowledge/ + .mcp.json
-nexus skill add code-review  # create a custom skill in .claude/commands/
-nexus skill list             # list all skills
-nexus rule add api-standards # create a rule in knowledge/rules/
-nexus rule list              # list all rules
-nexus update                 # update to latest version
 ```
+/evaluate   →   /plan   →   /apply   →   /validate
+```
+
+Each step is a built-in skill in `.claude/commands/`. Every task starts from the dev tasks CSV. Every task ends with acceptance criteria verified.
 
 ---
 
@@ -116,7 +127,7 @@ nexus update                 # update to latest version
 │   ├── apply.md       ← /apply     — implement the plan
 │   ├── validate.md    ← /validate  — verify acceptance criteria
 │   └── epav.md        ← /epav      — full cycle guide
-└── settings.json      ← PostToolUse hook: graphify auto-updates after every file edit
+└── settings.json      ← PostToolUse: graphify auto-updates after every file edit
 knowledge/
 ├── rules/             ← coding standards, arch decisions
 ├── patterns/          ← reusable implementation patterns
@@ -127,8 +138,23 @@ knowledge/
 
 ---
 
+## Commands
+
+```bash
+nexus init .                 # set up .claude/commands/ + knowledge/ + .mcp.json
+nexus skill add code-review  # create a custom skill in .claude/commands/
+nexus skill list             # list all skills
+nexus rule add api-standards # create a rule in knowledge/rules/
+nexus rule list              # list all rules
+nexus update                 # update to latest version
+```
+
+---
+
 ## MCP Server
 
+`nexus init` writes `.mcp.json` automatically. For Claude Desktop, add manually:
+
 ```json
 {
   "mcpServers": {
@@ -140,8 +166,6 @@ knowledge/
 }
 ```
 
-`nexus init` writes `.mcp.json` automatically.
-
 ### MCP Tools
 
 | Tool | Purpose |

{nexus_dev_toolkit-3.0.0 → nexus_dev_toolkit-3.0.1}/README.md

@@ -4,7 +4,7 @@
 [![Python](https://img.shields.io/pypi/pyversions/nexus-dev-toolkit)](https://pypi.org/project/nexus-dev-toolkit/)
 [![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)
 
-Developer workflow toolkit for AI-assisted development. Gives any team a structured Day 0 scaffold and repeatable Day 1 feature cycle via the EPAV methodology.
+Developer workflow toolkit for Claude Code. Gives any team a structured Day 0 scaffold and repeatable Day 1 feature cycle via the EPAV methodology.
 
 ---
 
@@ -12,7 +12,7 @@ Developer workflow toolkit for AI-assisted development. Gives any team a structu
 
 Ad-hoc AI prompting doesn't scale. Every dev prompts differently, context drifts, and nobody knows what the AI was told last sprint.
 
-`nexus-dev-toolkit` gives your team a single workflow:
+nexus-dev-toolkit gives your team a single workflow:
 
 - **Day 0** — scaffold the project once, production-grade, zero credentials needed
 - **Day 1** — every feature follows the same four steps: evaluate → plan → apply → validate
@@ -21,67 +21,78 @@ Every skill, every rule, every pattern lives in the project repo — versioned,
 
 ---
 
-## The Workflow
+## Setup
 
-### Day 0 — `/scaffold` (once per project)
+### 1. Install prerequisites
 
-```
-nexus init <project-dir>
+**uv** (recommended package manager):
+```bash
+curl -LsSf https://astral.sh/uv/install.sh | sh
 ```
 
-Sets up `.claude/commands/`, `.claude/settings.json`, and `knowledge/`. Then in Claude Code:
-
-```
-/scaffold
+**Claude Code:**
+```bash
+npm install -g @anthropic-ai/claude-code
+claude login
 ```
 
-EVALUATE → PLAN → APPLY → VALIDATE. Produces a production-grade project: correct stack from your arch doc, mock auth, mock data, design system, AGENTS.md — all from your architecture document. Runs with `npm install && npm run dev` (or equivalent) from commit one.
+**graphify** _(strongly recommended)_ — builds a queryable knowledge graph of your codebase. EPAV skills query this graph to understand blast radius and cross-file dependencies before touching any code.
 
-### Day 1 — EPAV (every feature, every sprint)
+| | With graphify | Without graphify |
+|---|---|---|
+| Context loading | Scoped subgraph — fast, low token cost | Full file reads — slow, high token cost |
+| Blast radius | Accurate, graph-backed | Best-effort, grep-based |
+| Auto-update | PostToolUse hook keeps graph current | N/A |
+| EPAV skills | Full capability | Degraded but functional |
 
+```bash
+uv tool install graphifyy   # PyPI package name has double y; command is "graphify"
+graphify install             # registers /graphify skill into Claude Code
 ```
-/evaluate   →   /plan   →   /apply   →   /validate
-```
-
-Each step is a built-in skill in `.claude/commands/`. Every task starts with a row from the dev tasks CSV. Every task ends with acceptance criteria verified.
-
----
 
-## Install
-
-**Requirements:** Python 3.10+, `uv` (recommended) or `pip`
+### 2. Install nexus-dev-toolkit
 
 ```bash
-# Recommended
 uv tool install nexus-dev-toolkit
-
-# Or via pip
-pip install nexus-dev-toolkit
 ```
 
----
-
-## Quick Start
+### 3. Initialize your project
 
 ```bash
 cd my-project
 nexus init .
 ```
 
-Then open the project in Claude Code and type `/scaffold`.
+### 4. Build the knowledge graph
+
+Open the project in Claude Code and run:
+```
+/graphify .
+```
+
+This generates `graphify-out/graph.json` — required by all EPAV skills.
+
+### 5. Start Day 0
+
+```
+/scaffold
+```
 
 ---
 
-## Commands
+## The Workflow
+
+### Day 0 — `/scaffold` (once per project)
+
+EVALUATE → PLAN → APPLY → VALIDATE. Produces a production-grade project from your architecture document and Figma design: correct stack, mock auth, mock data, design system, AGENTS.md — zero external dependencies. Runs `npm install && npm run dev` (or equivalent) from commit one.
+
+### Day 1 — EPAV (every feature, every sprint)
 
-```bash
-nexus init .                 # set up .claude/commands/ + knowledge/ + .mcp.json
-nexus skill add code-review  # create a custom skill in .claude/commands/
-nexus skill list             # list all skills
-nexus rule add api-standards # create a rule in knowledge/rules/
-nexus rule list              # list all rules
-nexus update                 # update to latest version
 ```
+/evaluate   →   /plan   →   /apply   →   /validate
+```
+
+Each step is a built-in skill in `.claude/commands/`. Every task starts from the dev tasks CSV. Every task ends with acceptance criteria verified.
 
 ---
 
@@ -96,7 +107,7 @@ nexus update                 # update to latest version
 │   ├── apply.md       ← /apply     — implement the plan
 │   ├── validate.md    ← /validate  — verify acceptance criteria
 │   └── epav.md        ← /epav      — full cycle guide
-└── settings.json      ← PostToolUse hook: graphify auto-updates after every file edit
+└── settings.json      ← PostToolUse: graphify auto-updates after every file edit
 knowledge/
 ├── rules/             ← coding standards, arch decisions
 ├── patterns/          ← reusable implementation patterns
@@ -107,8 +118,23 @@ knowledge/
 
 ---
 
+## Commands
+
+```bash
+nexus init .                 # set up .claude/commands/ + knowledge/ + .mcp.json
+nexus skill add code-review  # create a custom skill in .claude/commands/
+nexus skill list             # list all skills
+nexus rule add api-standards # create a rule in knowledge/rules/
+nexus rule list              # list all rules
+nexus update                 # update to latest version
+```
+
+---
+
 ## MCP Server
 
+`nexus init` writes `.mcp.json` automatically. For Claude Desktop, add manually:
+
 ```json
 {
   "mcpServers": {
@@ -120,8 +146,6 @@ knowledge/
 }
 ```
 
-`nexus init` writes `.mcp.json` automatically.
-
 ### MCP Tools
 
 | Tool | Purpose |

{nexus_dev_toolkit-3.0.0 → nexus_dev_toolkit-3.0.1}/nexus_cli.py

@@ -8,7 +8,7 @@ import typer
 from rich.console import Console
 from rich.table import Table
 
-app = typer.Typer(name="nexus", no_args_is_help=True, help="nexus-dev-toolkit — LLM-agnostic developer workflow toolkit")
+app = typer.Typer(name="nexus", no_args_is_help=False, help="nexus-dev-toolkit — Day 0 scaffold + Day 1 EPAV workflow for Claude Code")
 skill_app = typer.Typer(name="skill", no_args_is_help=True, help="Manage skills in .claude/commands/")
 rule_app = typer.Typer(name="rule", no_args_is_help=True, help="Manage rules in knowledge/rules/")
 app.add_typer(skill_app, name="skill")
@@ -16,6 +16,31 @@ app.add_typer(rule_app, name="rule")
 
 console = Console()
 
+_VERSION = "3.0.1"
+
+_LOGO = """\
+[cyan]███╗   ██╗███████╗██╗  ██╗██╗   ██╗███████╗[/cyan]
+[cyan]████╗  ██║██╔════╝╚██╗██╔╝██║   ██║██╔════╝[/cyan]
+[cyan]██╔██╗ ██║█████╗   ╚███╔╝ ██║   ██║███████╗[/cyan]
+[cyan]██║╚██╗██║██╔══╝   ██╔██╗ ██║   ██║╚════██║[/cyan]
+[cyan]██║ ╚████║███████╗██╔╝ ██╗╚██████╔╝███████║[/cyan]
+[cyan]╚═╝  ╚═══╝╚══════╝╚═╝  ╚═╝ ╚═════╝ ╚══════╝[/cyan]
+[dim white]dev toolkit[/dim white]  [dim cyan]v{version}[/dim cyan]"""
+
+
+def _print_logo() -> None:
+    from rich.padding import Padding
+    console.print()
+    console.print(Padding(_LOGO.format(version=_VERSION), (0, 2)))
+    console.print()
+
+
+@app.callback(invoke_without_command=True)
+def _callback(ctx: typer.Context) -> None:
+    if ctx.invoked_subcommand is None:
+        _print_logo()
+        console.print(ctx.get_help())
+
 # ── Built-in skills shipped with the package ──────────────────────────────────
 
 _SKILLS_SRC = Path(__file__).parent / "tools" / "epav" / "skills"
@@ -121,7 +146,7 @@ def init(
 ) -> None:
     """Initialize .claude/commands/, .claude/settings.json, and knowledge/ in a project."""
     root = Path(project_dir).resolve()
-    console.print(f"\n  [cyan]▶[/cyan]  Initializing nexus in [bold]{root}[/bold]\n")
+    console.print(f"  [cyan]▶[/cyan]  Initializing nexus in [bold]{root}[/bold]\n")
 
     created = _init_project(root)
     for f in created:

{nexus_dev_toolkit-3.0.0 → nexus_dev_toolkit-3.0.1/nexus_dev_toolkit.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: nexus-dev-toolkit
-Version: 3.0.0
+Version: 3.0.1
 Summary: LLM-agnostic developer workflow toolkit — Day 0 scaffold + Day 1 EPAV
 Author-email: Ronald dela Cruz <rcdelacruz@users.noreply.github.com>
 License-Expression: MIT
@@ -24,7 +24,7 @@ Dynamic: license-file
 [![Python](https://img.shields.io/pypi/pyversions/nexus-dev-toolkit)](https://pypi.org/project/nexus-dev-toolkit/)
 [![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)
 
-Developer workflow toolkit for AI-assisted development. Gives any team a structured Day 0 scaffold and repeatable Day 1 feature cycle via the EPAV methodology.
+Developer workflow toolkit for Claude Code. Gives any team a structured Day 0 scaffold and repeatable Day 1 feature cycle via the EPAV methodology.
 
 ---
 
@@ -32,7 +32,7 @@ Developer workflow toolkit for AI-assisted development. Gives any team a structu
 
 Ad-hoc AI prompting doesn't scale. Every dev prompts differently, context drifts, and nobody knows what the AI was told last sprint.
 
-`nexus-dev-toolkit` gives your team a single workflow:
+nexus-dev-toolkit gives your team a single workflow:
 
 - **Day 0** — scaffold the project once, production-grade, zero credentials needed
 - **Day 1** — every feature follows the same four steps: evaluate → plan → apply → validate
@@ -41,67 +41,78 @@ Every skill, every rule, every pattern lives in the project repo — versioned,
 
 ---
 
-## The Workflow
+## Setup
 
-### Day 0 — `/scaffold` (once per project)
+### 1. Install prerequisites
 
-```
-nexus init <project-dir>
+**uv** (recommended package manager):
+```bash
+curl -LsSf https://astral.sh/uv/install.sh | sh
 ```
 
-Sets up `.claude/commands/`, `.claude/settings.json`, and `knowledge/`. Then in Claude Code:
-
-```
-/scaffold
+**Claude Code:**
+```bash
+npm install -g @anthropic-ai/claude-code
+claude login
 ```
 
-EVALUATE → PLAN → APPLY → VALIDATE. Produces a production-grade project: correct stack from your arch doc, mock auth, mock data, design system, AGENTS.md — all from your architecture document. Runs with `npm install && npm run dev` (or equivalent) from commit one.
+**graphify** _(strongly recommended)_ — builds a queryable knowledge graph of your codebase. EPAV skills query this graph to understand blast radius and cross-file dependencies before touching any code.
 
-### Day 1 — EPAV (every feature, every sprint)
+| | With graphify | Without graphify |
+|---|---|---|
+| Context loading | Scoped subgraph — fast, low token cost | Full file reads — slow, high token cost |
+| Blast radius | Accurate, graph-backed | Best-effort, grep-based |
+| Auto-update | PostToolUse hook keeps graph current | N/A |
+| EPAV skills | Full capability | Degraded but functional |
 
+```bash
+uv tool install graphifyy   # PyPI package name has double y; command is "graphify"
+graphify install             # registers /graphify skill into Claude Code
 ```
-/evaluate   →   /plan   →   /apply   →   /validate
-```
-
-Each step is a built-in skill in `.claude/commands/`. Every task starts with a row from the dev tasks CSV. Every task ends with acceptance criteria verified.
-
----
 
-## Install
-
-**Requirements:** Python 3.10+, `uv` (recommended) or `pip`
+### 2. Install nexus-dev-toolkit
 
 ```bash
-# Recommended
 uv tool install nexus-dev-toolkit
-
-# Or via pip
-pip install nexus-dev-toolkit
 ```
 
----
-
-## Quick Start
+### 3. Initialize your project
 
 ```bash
 cd my-project
 nexus init .
 ```
 
-Then open the project in Claude Code and type `/scaffold`.
+### 4. Build the knowledge graph
+
+Open the project in Claude Code and run:
+```
+/graphify .
+```
+
+This generates `graphify-out/graph.json` — required by all EPAV skills.
+
+### 5. Start Day 0
+
+```
+/scaffold
+```
 
 ---
 
-## Commands
+## The Workflow
+
+### Day 0 — `/scaffold` (once per project)
+
+EVALUATE → PLAN → APPLY → VALIDATE. Produces a production-grade project from your architecture document and Figma design: correct stack, mock auth, mock data, design system, AGENTS.md — zero external dependencies. Runs `npm install && npm run dev` (or equivalent) from commit one.
+
+### Day 1 — EPAV (every feature, every sprint)
 
-```bash
-nexus init .                 # set up .claude/commands/ + knowledge/ + .mcp.json
-nexus skill add code-review  # create a custom skill in .claude/commands/
-nexus skill list             # list all skills
-nexus rule add api-standards # create a rule in knowledge/rules/
-nexus rule list              # list all rules
-nexus update                 # update to latest version
 ```
+/evaluate   →   /plan   →   /apply   →   /validate
+```
+
+Each step is a built-in skill in `.claude/commands/`. Every task starts from the dev tasks CSV. Every task ends with acceptance criteria verified.
 
 ---
 
@@ -116,7 +127,7 @@ nexus update                 # update to latest version
 │   ├── apply.md       ← /apply     — implement the plan
 │   ├── validate.md    ← /validate  — verify acceptance criteria
 │   └── epav.md        ← /epav      — full cycle guide
-└── settings.json      ← PostToolUse hook: graphify auto-updates after every file edit
+└── settings.json      ← PostToolUse: graphify auto-updates after every file edit
 knowledge/
 ├── rules/             ← coding standards, arch decisions
 ├── patterns/          ← reusable implementation patterns
@@ -127,8 +138,23 @@ knowledge/
 
 ---
 
+## Commands
+
+```bash
+nexus init .                 # set up .claude/commands/ + knowledge/ + .mcp.json
+nexus skill add code-review  # create a custom skill in .claude/commands/
+nexus skill list             # list all skills
+nexus rule add api-standards # create a rule in knowledge/rules/
+nexus rule list              # list all rules
+nexus update                 # update to latest version
+```
+
+---
+
 ## MCP Server
 
+`nexus init` writes `.mcp.json` automatically. For Claude Desktop, add manually:
+
 ```json
 {
   "mcpServers": {
@@ -140,8 +166,6 @@ knowledge/
 }
 ```
 
-`nexus init` writes `.mcp.json` automatically.
-
 ### MCP Tools
 
 | Tool | Purpose |

{nexus_dev_toolkit-3.0.0 → nexus_dev_toolkit-3.0.1}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "nexus-dev-toolkit"
-version = "3.0.0"
+version = "3.0.1"
 description = "LLM-agnostic developer workflow toolkit — Day 0 scaffold + Day 1 EPAV"
 authors = [
     {name = "Ronald dela Cruz", email = "rcdelacruz@users.noreply.github.com"}