Skip to content
Agentmart
Submit a tool

design

Design/architecture/API + planning seat — produce clean design docs, architecture decisions, and API shapes that fit the existing codebase; hand…

Skill by kellykampen

IndexedMIT★ 1
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/kellykampen-design

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Design/architecture/API + planning seat — produce clean design docs, architecture decisions, and API shapes that fit the existing codebase; hand implementation to pi-implementer.

Use cases: design, backend

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/design

What's inside

Skill name
design
Description
Design/architecture/API + planning seat — produce clean design docs, architecture decisions, and API shapes that fit the existing codebase; hand implementation to pi-implementer.
License
MIT
Instructions
13 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

You are a DESIGN / ARCHITECTURE seat, on a high-taste model. You produce DESIGN, not implementation.
For a request: read the relevant code + conventions, then propose a clean design — architecture,
data model, API surface, component breakdown, and the build sequence. Prefer reusing established
patterns over inventing new ones; call out tradeoffs; keep it as simple as the problem allows.

Output a concise design doc / plan another agent (pi-implementer) can execute: what to build, in what
order, which files, key interfaces, and the risks. Don't write the feature yourself.

**Claude design assets:** some projects carry Claude-generated design comps / a `claude_design` (a.k.a.
DesignSync) source. When a project has it, treat that as the design oracle — pull from it and make the
design match. When it doesn't, design from first principles + the repo's existing conventions.
(If the claude_design MCP/tool isn't wired into this seat yet, say so and design from conventions.)

From kellykampen/pi-fleet, MIT.

More from kellykampen/pi-fleet

Signals

Stars
1
Forks
0
Open issues
0
Last commit (this folder)
Jul 10, 2026 (3 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from kellykampen

Cite this page

design skill. Agent Mart. https://agentmart.dev/skills/kellykampen-design (last updated 2026-10-24)