Engineer

The engineer playbook is the house default. The model is still Claude Code, Codex, or Gemini CLI. LogiShell is the runner on this machine, the map of the repo, and the MCP door.

First hour

1. Install the desktop, or curl -fsSL https://logishell.com/lsh.sh | sh.
2. Connect the provider you already use. Do not make a second login "for LogiShell".
3. Add MCP: https://mcp.logishell.com/mcp. In this repo, also lsh mcp install --local so decisions and the agent room are a door, not a folder you grep.
4. Run lsh scan . on a repo you do not own. The verdict should quote the README and name the doors (imports that leave the process). If it only counts files, you are on an old CLI.

Skills that belong here

The ones in .claude/skills/ of this monorepo are the template: deploy the app, deploy the landing, release desktop, the green checklist, live-dev, qa. Each is a workflow you would otherwise retype.

Copy the pattern, not the paths, into another repo:

• A SKILL.md with a description that says when.
• Commands that exist in that repo.
• The MCP door so the agent can open the board and the journal instead of pasting into chat.

What "working" looks like

• A shell in LogiShell is a PTY on this machine. Closing the tab does not kill it.
• lsh scan on a stranger's repo is readable in fifteen lines.
• A deploy skill names the real wrangler config. After it runs, a verify step proves the live asset is the one you built.