setup

Configures Hames workspaces, file rules, and indexes through a preview-and-approve setup workflow.

5|1|Updated May 8, 2026
One-click install
npx skills add https://github.com/baek-labs/hames --skill setup-baek-labs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: setup
Source: https://github.com/baek-labs/hames/tree/main/packages/claude/skills/setup
Command: npx skills add https://github.com/baek-labs/hames --skill setup-baek-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up an AI-managed workspace requires defining folder structures, file placement rules, and indexes, which is error-prone when done manually. This Skill guides users through configuring or reconfiguring Hames in the current project with a read-only preview before any change is applied. ## Core Features & Use Cases - Guided Workspace Configuration: Asks one decision at a time to define workspace names, paths, purposes, subfolder roles, and file rules (extension, name, required, semantic). - Preview-and-Approve Safety: Generates a read-only plan via runtime/setup.js plan, shows the exact proposed tree and file edits, and applies changes only after explicit approval with a matching plan hash. - Recovery and Reconfiguration: Provides read-only recovery previews for damaged settings or missing folders, and preserves existing entry files, manual index text, and archived contracts. - Use Case: A user opens a project folder, invokes /setup, describes the workspaces they want, reviews the complete folder and file-change preview, and approves it once to apply the configuration. ## Quick Start Invoke /setup and describe the workspaces, folder purposes, and file rules you want so Hames can preview and apply the configuration.

Frequently Asked Questions about setup

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

FAQPage Schema
How do I set up a Hames workspace in my project?▼

Invoke /setup in a fresh session and answer one decision at a time about your work, root folder, workspace names, and subfolder roles. Hames shows a complete read-only preview of folders and file changes, then applies it only after your single approval.

How do I reconfigure an existing Hames workspace?▼

Run /setup again; it loads your current choices and changes only what you request, then shows a new preview. Repeated setup with the same choices is read-only, and changing a workspace path never moves your existing files.

Does Hames setup require Git for my project folder?▼

No, ordinary file work needs no Git and no task contract. Non-Git roots default to untracked contracts without initializing Git, while a Git root with an unresolved tracking choice gets exactly one question.

What file rule kinds does Hames setup support?▼

Hames supports four rule kinds: extension (list of extensions), name (regular expression), required (required text), and semantic (a judgment instruction). The setup flow explains the difference between concrete checks and meaning-based judgments.

What happens if my Hames settings are damaged or folders are missing?▼

Run the recovery flow, which provides a read-only recovery preview first. Only after you explicitly choose that recovery does it apply changes with a recovery hash, and it never overwrites newer user edits while rolling back.