Profession playbooks
LogiShell is one system. The first hour is not. A designer and an engineer already have a model (Claude, Codex, or Gemini) and a set of files they live in. The playbook says how that job walks in, which skills to drop in, and what "done" looks like.
Each playbook is a page with a stable URL. Add a new one by adding a markdown file next to these.
- Designer — screens, tokens, review. The agent sees the frame the way the file tree sees the repo.
- Engineer — map, scan, terminals, the skill that is a deploy.
The shape is always: keep your model, add the MCP door, add the skills.