DESIGN GARDEN · FIELD GUIDE

Look around first.Then plantyour first flower.

A design skill that grows, and a community that listens when you say “something feels off”. You do not need code. You only need to know which button to press now.

You do not have to be a designer first.

Install

Three paths. The skill ZIP works with most agents; the DSH plugin is for DeepSeek Harness; if you do not want to install anything, jump to the gallery.

Recommended · any agent

Download the skill

One ZIP, one complete design-garden. Works with ZCode, Claude Code, and any agent that reads SKILL.md.

Download design-garden-skill.zip

About 200 KB · unzip into ~/.agents/skills/

The unzipped folder should contain SKILL.md at its root.

One command

Install from GitHub

Already use a terminal? This line is enough. Update later with git pull.

git clone https://github.com/iifzx/design-garden.git ~/.agents/skills/design-garden

Works in Windows PowerShell too; ~ is your home directory.

DeepSeek Harness

Install the DSH plugin

The plugin carries the skill and an index. Once installed, DSH can call design-garden directly — no manual skills folder.

dsh plugin --profile web add "git+https://github.com/iifzx/design-garden.git#af66da5a4c6633a9393b0615ceff2532f387db20&path:/dsh"

Pinned to a commit, so upstream changes cannot break the install.

Other agent installs
Claude Code
/plugin marketplace add iifzx/design-garden
ZCode (inside a project)
git clone https://github.com/iifzx/design-garden.git <your-project>/.zcode/skills/design-garden

Try one sentence after installing

If it does not trigger at first, add “use design-garden” to the sentence.

  1. Make a poster

    Use design-garden to make a poster for our neighborhood stray-cat adoption day. A3, for the elevator, something people will stop for.
  2. Fix an existing piece

    This image feels too busy. Use design-garden to find what is wrong and give me two fixes: one safe, one bold.
  3. Name a style

    I want it to feel like a botanical field guide: chalk paper, thin rules, handwritten labels — not techy.

Use it without installing

Browse the knowledge base, view works, vote, and submit. Installation only lets your own agent call the skill.

GitHub button tour

GitHub is not an exam. It puts “look, ask, change, vote” in a few fixed places. Every button below tells you where it is, what it does, and whether a beginner needs it.

Star StarSave Start here
Where
Top right of the repository, next to the Star count
What it does
Saves the repo and gives the project a public signal. The Star count is the first thing visitors use to judge whether a project is worth reading.

Beginner advicePress this first. You can Star without signing in, but only a signed-in Star is remembered.

Code ▾ CodeDownload / clone Start here
Where
The green button above the file list
What it does
Downloads the whole repo as a ZIP, or copies the git clone URL. No git? Choose Download ZIP.

Beginner advicePress it to install the skill. The green button does not “run code”; it only gives you the code.

Issues IssuesQuestions and submissions Start here
Where
The tab row at the top of the repository
What it does
Ask a question, report a knowledge bug, or submit a work. Each template gives you the shape to fill.

Beginner adviceThe most useful tab for beginners. Pick a template, fill the title; no code.

New issue New issueCreate Only to contribute
Where
Top right of the Issues page
What it does
Opens a submission or question form. Write a clear title and fill the template; you can drag images straight into the editor.

Beginner advicePress it to submit. GitHub turns the dropped image into a link for you.

README.md READMEProject home page Start here
Where
Below the file list, rendered automatically
What it does
The project's own manual: what it is, how to install, how to use. Much faster than reading the file tree.

Beginner adviceRead the README before installing anything.

Fork ForkCopy to your account Only to contribute
Where
Top right, next to Star
What it does
Copies the repo to your account. Your edits happen in your copy and do not touch the original.

Beginner adviceOnly needed if you want to edit files and open a PR. Using the skill does not require a Fork.

Pull requests Pull requestsMerge requests Only to contribute
Where
The tab row at the top
What it does
After someone edits files, they ask for the change to be merged into the main line. Every diff and discussion lives here.

Beginner adviceLook here if you want to contribute content; ignore it if you only use the skill.

Discussions DiscussionsForum Only to contribute
Where
The tab row (maintainers can disable it)
What it does
A looser space than Issues. Vote threads, work showcases, and open questions often live here.

Beginner adviceUse it to talk or find vote threads. If the tab is missing, use Issues.

Actions ActionsAutomation Not urgent
Where
The tab row at the top
What it does
Runs checks, deploys the site, and syncs votes after each push. A red cross means a check failed, not that you did something wrong.

Beginner adviceNot urgent. Open it if you want to see how the site updates itself.

Watch WatchSubscribe Not urgent
Where
Top right, next to Star
What it does
Notifies you about new Issues, PRs, or Releases. You can choose to receive only threads you participate in.

Beginner adviceNot urgent. Skip it if you do not want the email.

About AboutSidebar Start here
Where
The right side of the file list
What it does
One-line description, website, topics, license, Stars and Forks. The fastest way to judge whether a repo is usable.

Beginner advicePress this first. License and website tell you more than the Star count.

Releases ReleasesVersions Not urgent
Where
Below the About sidebar
What it does
Packaged versions and release notes. Some projects only offer downloads here.

Beginner adviceNot urgent. For beginners, Code → Download ZIP usually works.

main ▾ BranchVersion line Not urgent
Where
Above the file list, on the left
What it does
Switches the version you are viewing. main is the main line; other branches may be experiments or a PR.

Beginner adviceNot urgent. Stay on main unless someone asks you to inspect a branch.

History HistoryFile history Not urgent
Where
Top right after opening a file
What it does
Shows who changed a file, when, and why. You can compare old versions and read the exact diff.

Beginner adviceOpen it when curious or looking for an older version. Useful when reading the knowledge base.

Settings SettingsRepository settings Maintainers only
Where
Far right of the tab row
What it does
Permissions, webhooks, and Pages deployment. You cannot see it without maintainer access.

Beginner adviceMaintainers only. If the tab is missing, you do not need it.

Three buttons are enough

Star saves, Issues asks and submits, Code downloads. Learn the rest only when you need them; not knowing them will not stop you from using the project.

StarIssuesCode

GitHub moves things slightly between redesigns; trust the name, not the exact position.

Repository map

This repo is not only code. It is a manual, a gallery, a set of automated checks, and an entrance for beginners. Follow this order and you will not get lost.

First visit: only these three

Repository map
PathWhat it isWhat you can do here
SKILL.md The skill's router: the agent reads it first, then loads knowledge for the task. Read it to see how the skill chooses which knowledge to load.
knowledge/40 knowledge files The design manual: core principles, 9 domains, 18 styles, 3 case studies. Find a specific technique; every file opens with when to load it.
learnings/9 notes Field notes: what worked and what failed after real tasks. Read what real use taught, or contribute an entry.
evals/ Blind tasks and rubrics: new knowledge has to beat the old version to move from experimental to proven. Open it when you want the evidence behind a rule.
examples/ Real outputs: posters, pages, icons, social images, each with model credit. Look for inspiration, or see what the workflow actually ships.
scripts/ Zero-dependency Node scripts: build the sites, validate knowledge, run blind tests. Start here to change the site or add a check.
docs/ Beginner guides, the GitHub tour, and promo material. First visit: read start-here and github-tour.
dsh/ DeepSeek Harness plugin: a self-contained bundle, index, and sync scripts. DSH users install it; read its README to change it.
start/ The standalone beginner site you are reading (source). Copy, styles, and data rendering live here.
community/ Community works and vote data: featured, submissions, votes, themes. After a submission is merged, its JSON appears in submissions/.
.github/ Issue templates, PR template, and Actions workflows. Change the submission form or the sync jobs here.
site/ Generated site output; do not edit by hand (also gitignored). Generated by scripts/build_site.mjs and build_start_site.mjs.

The numbers come from the repository at build time, not from a marketing deck.

Submit

Submission is not an exam. We check three things: it is yours, the image is legible, and the note says something. We do not grade “professional polish”.

  1. Pick one real work

    A poster, icon, logo, page, slide, or illustration. One image is enough; no nine-grid dump.

  2. Open the submission form

    A GitHub account is your identity; you can look around without one. The template lists what to fill.

  3. Drag the image into the body

    Drop a PNG/JPG/WebP into the issue editor; GitHub creates the link. Three sentences: context, one design decision, one unsolved problem.

  4. Wait for review

    A maintainer reads the image and the note in a PR. Once merged, it enters the gallery and the current vote. Usually 24–72 hours.

60-second self-check

Do not submit

  • Someone else's work, or a client draft that is not public
  • A pure AI collage with no explanation
  • “Is this pretty?” with no context
  • An ad built around a QR code or contact details
  • SVG files (bitmap only in the first version, for safety)

License and credit

You keep the copyright. Submission agrees to display under CC BY 4.0 with your name. Do not submit client work you cannot publish.

Review checks only the three things above. A rejection names what is missing, not just “not suitable”.

Vote

Voting does not happen on this site — it happens on the work's GitHub issue. You tap 👍; the site shows the count at the next sync.

This month · 2026-11

One design for everyday life

A market stall, a community event, a family shop — pick a real scene near you and make a poster, an icon, or a page.

Deadline 2026-11-30 Open

Current board

Counts synced 2026-11-17

  1. No works this month yet. The first submission starts the board.

    Submit the first work

Rules

  1. One person, one vote: tap 👍 on a work's GitHub issue. One account counts once; you can change your reaction.
  2. The site displays results only. Counts are synced from GitHub reactions by a scheduled Action.
  3. You can ask friends to vote for your work, but bought, automated, or bulk-account votes are removed.
  4. Maintainers remove invalid votes; they do not edit votes for taste.

Blind pick first, then vote

Ignore the author; choose on first look. This choice stays in your browser and does not count. After the reveal, go to GitHub for the real vote.

Perlume store assets, portrait 3:4
APerlume store assets, portrait 3:4Doubao
Bike repair shop landing page
BBike repair shop landing pageGLM-5.3-Flash

The blind pick uses exhibit works; it is practice, not the official vote.

Design tools

Three 30-second tools: spin a style, run the delivery checklist, and turn a need into a sentence.

30 sec

Style roulette

Not sure what it should feel like? Spin a style, then ask the agent to work inside it.

Press once to see what today brings.
See all 18 styles

All 18 recipes live in knowledge/styles/. Spin again if you dislike it.

30 sec

Delivery checklist

Ten items, 30 seconds. Tick them before shipping.

Glossary

Six words are enough

  • agentA program on your computer that can do tasks for you.
  • skillA professional manual installed into an agent; design-garden is a design manual.
  • repoThe project's home on GitHub: files, history, and discussion.
  • issueA trackable question or submission with a number; it can be replied to and closed.
  • PRA “please merge my change” request; review happens here.
  • reaction / 👍An emoji response on GitHub; this project uses 👍 as the vote.

One sentence

Turn a need into plain words

Three blanks make one sentence an agent can follow.

Use design-garden to make a neighborhood adoption-day poster, for the building elevator, A3. I want it to feel like a botanical guide: chalk paper, thin rules, handwritten labels.

Blank fields fall back to the grey example.