From memplexor
Initialize Memplexor project memory — analyze repo, create .claude/memory/, generate project guidelines skill, verify hooks. Idempotent.
How this command is triggered — by the user, by Claude, or both
Slash command
/memplexor:setup [--dry-run] [--refresh] [--force] [--preserve-memory] [--help]This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# /setup — Memplexor bootstrap You are running the Memplexor `/setup` command in the current project at `$PWD`. ## Arguments Parse `$ARGUMENTS` (space-separated flags): - `--dry-run` → analyze + report only, write nothing - `--refresh` → re-run analysis, refresh generated files only - `--force` → overwrite generated files even if they lack the generation marker; never delete user memory - `--preserve-memory` → default; preserve CURRENT.md, HISTORY.md, sessions/* - `--help` → print this usage and exit If `--help`: print the argument list above and stop. ## Step 1 — Detect project root ...
You are running the Memplexor /setup command in the current project at $PWD.
Parse $ARGUMENTS (space-separated flags):
--dry-run → analyze + report only, write nothing--refresh → re-run analysis, refresh generated files only--force → overwrite generated files even if they lack the generation marker; never delete user memory--preserve-memory → default; preserve CURRENT.md, HISTORY.md, sessions/*--help → print this usage and exitIf --help: print the argument list above and stop.
project_root is the current working directory ($PWD). Never write outside it.
Read whichever of these exist (use Glob/Read; never assume):
| File | Signal |
|---|---|
package.json | Node + scripts + framework deps |
pnpm-lock.yaml / yarn.lock / package-lock.json / bun.lockb | Package manager |
pyproject.toml / requirements.txt / Pipfile / poetry.lock | Python |
Cargo.toml | Rust |
go.mod | Go |
Gemfile | Ruby |
composer.json | PHP |
Makefile | Build commands |
tsconfig.json / .eslintrc* / .prettierrc* / ruff.toml | Style/typecheck |
Dockerfile / docker-compose.yml | Containers |
.github/workflows/* / .gitlab-ci.yml | CI |
README.md | High-level description |
Detect:
src/, app/, lib/, tests/, pkg/, etc.)Compute the file list. THESE ARE THE ONLY PATHS YOU WRITE. Do not create
.claude/memory/CURRENT.md or .claude/memory/HISTORY.md at the memory root —
those go inside context/ and progress/.
.claude/memory/ (mkdir -p)
.claude/memory/context/ (mkdir -p)
.claude/memory/progress/ (mkdir -p)
.claude/memory/sessions/ (mkdir -p)
.claude/memory/context/CURRENT.md (seed if absent unless --force)
.claude/memory/progress/HISTORY.md (append setup entry; create if absent)
.claude/skills/project-guidelines/SKILL.md (generate or refresh)
Forbidden paths (never create these):
.claude/memory/CURRENT.md — wrong, use context/CURRENT.md.claude/memory/HISTORY.md — wrong, use progress/HISTORY.md$PWDIf --dry-run: print the plan, exit. Do not write.
<!-- Generated by Memplexor --> in the first line of every generated file--refresh or --force, else preserve--forceUse atomic writes (write to .tmp.<rand> then rename) for any file you overwrite.
<!-- Generated by Memplexor -->
# Current Project Context
**Last updated:** <ISO-8601 with timezone offset>
## Where We Are
* Project initialized with Memplexor.
* Detected stack: <languages, frameworks>
* Package manager: <manager>
## Recent Work
* (none — fresh setup)
## Next Steps
* Start a new Claude Code session to confirm SessionStart context injection fires.
* Run `/memory-status` to inspect memory health.
## Open Questions
* (add yours here — survives save-hook rewrites)
## Important Files
* <list 5-10 key files / directories detected>
## Warnings or Constraints
* (add yours here — survives save-hook rewrites)
## <ISO-8601> — setup complete
* Initialized Memplexor project memory.
* Generated project guidelines skill.
* Verified hook registration.
* Detected stack: <stack>
* Next: start a new Claude Code session to verify SessionStart injection.
See templates/project-guidelines.SKILL.md for the full structure. Fill in:
name: project-guidelinesdescription: one sentence naming the stack + that these are project conventionsThe plugin's hooks/hooks.json already registers SessionStart, Stop, PreCompact at
install time. Confirm the plugin is loaded by checking that ${CLAUDE_PLUGIN_ROOT}
resolves and the script files exist. Report status.
Print a single concise summary:
Created:
* <list of newly created files>
Refreshed:
* <list of files updated because of --refresh / --force>
Preserved:
* <list of user-authored files left untouched>
Skipped:
* <list of files skipped + reason>
Warnings:
* <missing test command, no README, etc.>
Next:
* Start a new Claude Code session to verify SessionStart injection.
* Run /memory-status to inspect.
$PWD — no parent traversal.npx claudepluginhub krzemienski/memplexor --plugin memplexor/setupInitializes or resumes project setup via interactive Q&A, creating conductor/ artifacts for product definition, guidelines, tech stack, workflow, and style guides.
/setupWalks an enterprise admin through configuring the Claude Office add-in to call their own cloud (Vertex, Bedrock, Foundry, or gateway), producing a customized manifest.xml for M365 deployment.
/setupChecks local Codex CLI readiness, prompts to install if unavailable via npm, and optionally toggles stop-time review gate.
/setupInteractive setup wizard that detects installed AI providers, configures authentication, and optimizes token usage. Auto-runs on first install and surfaces a status dashboard on manual invocation.