scalardb

Nexus Architect

System architecture toolkit for Claude Code and Codex. Claude Code uses this repository as three plugins with 77 skills; Codex uses the same skill files through AGENTS.md compatibility rules.

• product (23 skills) — Product direction: validation-driven, dialogue-based pipeline from product vision to SLA/NFR; hands off to architect for system implementation design
• architect (43 skills) — Legacy refactoring, greenfield design, database migration, consulting deliverables
• scalardb (11 skills) — ScalarDB application development toolkit

Installation

As a Claude Code Plugin (Recommended)

# 1. Add the marketplace
claude plugin marketplace add wfukatsu/nexus-architect

# 2. Install the plugins
claude plugin install product@nexus-architect --scope user
claude plugin install architect@nexus-architect --scope user
claude plugin install scalardb@nexus-architect --scope user

After installation, commands are available as /product:skill-name, /architect:skill-name, and /scalardb:skill-name.

To update to the latest version:

claude plugin update product@nexus-architect
claude plugin update architect@nexus-architect
claude plugin update scalardb@nexus-architect

Manual Installation

# 1. Clone the repository
git clone https://github.com/wfukatsu/nexus-architect.git

# 2. Add as a local marketplace
claude plugin marketplace add ./nexus-architect

# 3. Install the plugins
claude plugin install product@nexus-architect --scope user
claude plugin install architect@nexus-architect --scope user
claude plugin install scalardb@nexus-architect --scope user

Verify Installation

In a Claude Code session, type any command to confirm:

/product:start
/architect:start
/scalardb:model

If the skills are recognized, the installation is successful.

Using with Codex

Codex can use the same skill files without installing Claude Code plugins.

# 1. Clone the repository
git clone https://github.com/wfukatsu/nexus-architect.git
cd nexus-architect

# 2. Optional Python dependencies
pip install -r requirements.txt

Open Codex at the repository root. AGENTS.md tells Codex how to translate Claude Code conventions:

• /product:<name> -> skills/product/<name>/SKILL.md (product skills are nested under skills/product/)
• /architect:<name> -> skills/<name>/SKILL.md
• /scalardb:<name> -> skills/<name>/SKILL.md
• CLAUDE_PLUGIN_ROOT -> the repository root
• .claude/docs/* -> skills/common/references/*
• .claude/rules/* -> rules/* (product rules are nested under rules/product/*)
• ${CLAUDE_PLUGIN_ROOT}/subagents/* -> skills/common/subagents/*

Then invoke the same command text in chat:

/product:start
/architect:start ./path/to/target
/architect:pipeline ./path/to/target
/scalardb:model
/scalardb:review-code ./path/to/app

When a skill asks to use Claude tools, Codex follows these mappings:

Claude Code reference	Codex behavior
Read, Glob, Grep, LS	Use shell reads, rg, rg --files, find, or ls
Write, Edit, MultiEdit	Edit files with apply_patch
Bash	Run shell commands
AskUserQuestion	Present numbered choices in chat and wait for the reply
Task, Subagent	Run in the main Codex thread unless the user explicitly asks for sub-agents
WebFetch, WebSearch	Use Codex web access, Context7, or approved curl

After editing generated reports or Mermaid diagrams in Codex, run the hooks manually when relevant:

hooks/validate-frontmatter.sh reports/before/example/technology-stack.md
hooks/validate-mermaid.sh reports/before/example/codebase-structure.md

Claude Code continues to use the plugin metadata and slash commands unchanged. See Using Nexus Architect with Codex for the full Codex guide.

Quick Start

# Product direction (greenfield: start here, then hand off to /architect:define-requirements)
/product:start

# Interactive workflow (recommended)
/architect:start ./path/to/target

# Automated full pipeline
/architect:pipeline ./path/to/target

# Individual skills
/architect:investigate ./path/to/target
/architect:analyze ./path/to/target
/architect:evaluate-mmi ./path/to/target

# ScalarDB development
/scalardb:scaffold
/scalardb:model
/scalardb:build-app

Commands

Product Direction (/product:*)

Validation-driven pipeline from product vision to SLA/NFR. Hands off to /architect:define-requirements for system implementation design.