LogiShell docs Open app

Designer

You already talk to a model. LogiShell is not a new one. It is the room where the screen, the tokens, and the review live as files, and the door the model uses to reach them.

First hour

  1. Install the desktop or open app.logishell.com.
  2. Keep Claude Code, Codex, or Gemini CLI. Connect the one you already signed into.
  3. Add the MCP door: https://mcp.logishell.com/mcp (or claude mcp add --transport http logishell https://mcp.logishell.com/mcp).
  4. Drop the designer skills into .claude/skills/ of the project (or into the provider's user skills folder). The files are markdown. Copy the folder, that is the install.

After that a message like "review this screen against our tokens" is enough. The agent picks the skill by its description, opens the files through MCP, and writes the note where the work already lives.

How a designer skill is built

Same as any skill. See Skills. The difference is the job, not the format.

A useful set for a design project:

SkillWhen the agent should pick it
review-layoutA screenshot or a frame landed, and it must be checked against tokens, type, and spacing.
extract-tokensA new colour, type size, or radius showed up and should become a named token, not a one-off.
design-changelogThe file changed and someone who was not in Figma needs a sentence they can ship.
hand-offEngineering will open this next: the skill names the file, the token, the leftover question.

Each one is a SKILL.md. The body names the real files (tokens.css, the board, the note path). If those names move, the skill moves in the same PR.

What "working" looks like

MCP plus the model, on this job

designer
  → Claude / Codex / Gemini
       → skill "review-layout"
            → MCP: read the repo, open the frame, write the note

Gemini is fine when that is the model you already have. Codex is fine when that is the model you already have. The skill does not care. The door does not care. The markdown is the same file.