Skills for Real Engineers. Straight from my .agents directory.
39 skills
open-design-edit
Agent skill from
Steer one part of an existing design in one direction — bolder, quieter, denser, roomier, simpler, more polished or sturdier — and change nothing else, with a check that proves only that part changed and a before and after to show — use whenever the user wants one part of an existing Open Design design changed in a direction rather than redesigned ("make the hero pop", "tone down the footer", "the table feels cramped", "simplify this section", "clean up the pricing cards", "what if the names are really long?", "make it bolder"), or clicked a verb in the preview, even if they don't mention Open Design; not for a new design or a whole new direction
How to install open-design-edit
install open-design-edit
# install the open-design-agent-kit pack with the skills CLI
npx skills add feimacode/open-design-agent-kit# or add only this skill to Claude Code: copy the folder
packages/claude-plugin-local/skills/open-design-edit/
# into
~/.claude/skills/open-design-edit/ (all projects)
.claude/skills/open-design-edit/ (one project)
1<!-- generated:curated-entry -->23Steer one part of a design: one verb, one part, nothing else changes.45Request: "$ARGUMENTS" — or, if that is empty, the user's request in this conversation (if it isn't clear, ask the user: "Which part should change, and how?")67**How to talk to the user.** Many people using Open Design don't write code, so:8- Use the user's own words. If they say "artifact", "design tokens" or give a file path, use those terms back; otherwise use the plain words below.9- Keep the machinery out of replies: no tool names, no ids like `od:prototype:poster-hero`, no internal files (`.artifact.json`, `.comments.json`, `config.json`), and not the words "register", "manifest", "sidecar", "entry" or "surface", unless the user used them first.10- Explain a print term the first time it comes up, in one short clause, and not again.11- Say where a file is the way the user would find it ("in your Open Design folder, under seed-swap-flyer"). Give a raw path only where the user can click it (Claude Code, Claude Desktop's Code tab, VS Code) or asks for it.12- End each reply that finishes a step with one line on what they can do next, with at most two options ("Want it in Instagram sizes too, or is it ready to print?").1314| Instead of | Say |15|---|---|16| artifact, entry, registered | your design, saved |17| design system, active design system | your style (the first time: "a saved style: colours, fonts and spacing") |18…
Excerpt shown under the repository's MIT license.
More skills in open-design-agent-kit
- ▸od-deck-deck-guizang-editorial
- ▸od-deck-deck-open-slide-canvas
- ▸od-deck-deck-swiss-international
- ▸od-deck-guizang-ppt
- ▸od-deck-ppt-keynote
- ▸od-prototype-article-magazine
- ▸od-prototype-card-twitter
- ▸od-prototype-card-xiaohongshu
- ▸od-prototype-data-report
- ▸od-prototype-doc-kami-parchment
- ▸od-prototype-mockup-device-3d
- ▸od-prototype-poster-hero
Keep exploring
Similar skill repositories
Public repository for Agent Skills
20 skills
An AI skill that provides design intelligence for building professional UI/UX across multiple platforms.
CCCXCUGH6 skills
Persistent Context Across Sessions for Every Agent – Captures everything your agent does during sessions, compresses it with AI, and injects relevant context back into future sessions. Works with Claude Code, OpenClaw, Codex, Gemini, Hermes, Copilot, OpenCode + More
CCCXGHGM+135 skills
Production-grade engineering skills for AI coding agents.
CCCXCU25 skills
Agent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
CCCXCU1 skill