setup-workspace

Initialize a Memnyx workspace, scaffold projects, and sync upstream skill updates.

2|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/MDGrey33/memnyx --skill setup-workspace-mdgrey33
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-workspace
Source: https://github.com/MDGrey33/memnyx/tree/main/.claude/skills/setup-workspace
Command: npx skills add https://github.com/MDGrey33/memnyx --skill setup-workspace-mdgrey33

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the full lifecycle of a Memnyx workspace so engineers can bootstrap a clean Claude Code environment, register projects, and keep upstream skill updates in sync without damaging user-owned files.

Core Features & Use Cases

  • Workspace initialisation: Creates the required sibling-layout workspace structure, deploys skills and starter files, and writes the workspace marker and source reference.
  • Project onboarding: Scaffolds a project under the workspace, generates its Claude instructions and memory files, and registers it in the project registry.
  • Safe upstream syncing: Detects differences between source and workspace, separates upstream-owned updates from user-evolved starter content, and asks before overwriting anything sensitive.
  • Launcher management: Generates the mmn shell launcher and supports optional, consent-gated profile wiring for direct command-line access.
  • Use case: A developer clones Memnyx, initialises a workspace, adds a new project, and later pulls upstream skill changes into the workspace while preserving local edits.

Quick Start

Ask this skill to initialise a Memnyx workspace from the cloned repository, then follow its prompts to register the source workspace and optionally enable the mmn launcher.

Frequently Asked Questions about setup-workspace

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a Claude Code workspace without overwriting my existing project files?

To set up a Claude Code workspace safely, this skill uses idempotent scaffolding and path validation to create files without overwriting user-owned content. It preserves your local edits by separating upstream skill updates from evolved starter files.

What is the best way to register a new project in a sibling source-and-workspace layout?

Project onboarding scaffolds your project under the workspace and registers it in the project registry. This sibling-layout approach generates Claude instructions and memory files while keeping source and workspace directories cleanly separated.

How does workspace syncing handle upstream boilerplate updates without breaking local edits?

Workspace syncing detects differences between source and workspace directories, then asks before overwriting anything sensitive. It separates upstream-owned boilerplate from user-evolved starter content to prevent breaking local edits during updates.

Do I need to manually configure my shell profile to use the mmn launcher after workspace initialization?

No, launcher management generates the mmn shell launcher and supports optional, consent-gated profile wiring. You do not need to manually configure your shell profile; the setup prompts you for direct command-line access integration.

Can I run the workspace initialization multiple times if my scaffolding is incomplete?

Yes, workspace setup uses idempotent file creation, meaning running initialization multiple times is safe and will not duplicate or corrupt existing files. It validates paths and skips existing starter files to complete your scaffolding securely.