Trellis Session Insight
mindfold-ai/Trellis
Reach into past AI conversation history through the trellis mem CLI.
A skill your agent uses when several visual variants need to be compared side by side — mockups, layouts, or a range of one value (spacing, radius, shadow, color, motion) — or when you are about to…
$ npx skills add hashgraph-online/awesome-codex-plugins --skill design-helper -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install hashgraph-online/awesome-codex-plugins design-helper --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/Dessert99/design-helper/skills/design-helper .claude/skills/design-helper && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "design-helper" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/Dessert99/design-helper/skills/design-helper into .claude/skills/design-helper/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-helper", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/Dessert99/design-helper/skills/design-helperType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add hashgraph-online/awesome-codex-plugins --skill design-helper -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install hashgraph-online/awesome-codex-plugins design-helper --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/Dessert99/design-helper/skills/design-helper .agents/skills/design-helper && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "design-helper" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/Dessert99/design-helper/skills/design-helper into .agents/skills/design-helper/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-helper", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add hashgraph-online/awesome-codex-plugins --skill design-helper -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install hashgraph-online/awesome-codex-plugins design-helper --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/Dessert99/design-helper/skills/design-helper .cursor/skills/design-helper && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "design-helper" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/Dessert99/design-helper/skills/design-helper into .cursor/skills/design-helper/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-helper", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/hashgraph-online/awesome-codex-plugins.git --path plugins/Dessert99/design-helper/skills/design-helper--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add hashgraph-online/awesome-codex-plugins --skill design-helper -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install hashgraph-online/awesome-codex-plugins design-helper --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/Dessert99/design-helper/skills/design-helper .gemini/skills/design-helper && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "design-helper" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/Dessert99/design-helper/skills/design-helper into .gemini/skills/design-helper/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-helper", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install hashgraph-online/awesome-codex-plugins design-helperInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add hashgraph-online/awesome-codex-plugins --skill design-helper -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/Dessert99/design-helper/skills/design-helper .github/skills/design-helper && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "design-helper" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/Dessert99/design-helper/skills/design-helper into .github/skills/design-helper/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-helper", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add hashgraph-online/awesome-codex-plugins --skill design-helper -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install hashgraph-online/awesome-codex-plugins design-helper --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/Dessert99/design-helper/skills/design-helper .opencode/skills/design-helper && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "design-helper" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/Dessert99/design-helper/skills/design-helper into .opencode/skills/design-helper/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-helper", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
design-helperA skill your agent uses when several visual variants need to be compared side by side — mockups, layouts, or a range of one value (spacing, radius, shadow, color, motion) — or when you are about to…
Design Helper is an agent skill from hashgraph-online/awesome-codex-plugins. Use when several visual variants need to be compared side by side — mockups, layouts, or a range of one value (spacing, radius, shadow, color, motion) — or when you are about to ask the user to pick between visual options in prose. Renders every candidate in one HTML file, opens it in a browser, lets the user choose by eye, then applies the choice to the code. Not a design generator — it lays out a range, it does not invent a look. Triggers on "5가지 버전으로 보여줘" · "A 랑 B 중에 뭐가 나아" · "시안 여러 개 비교해줘" · "나란히 놓고 보자". Do…
Its SKILL.md is about 3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including reference files (for example `references/clarification.md`, `references/controls.md` and `references/liveview.md`).
It sits in Development, covering Debugging. The repository describes itself as: A curated list of awesome OpenAI Codex / ChatGPT plugins, skills, and resources. The 1 Codex Marketplace. See live plugins at: https://hol.org/plugins/best-codex-plugins. The licence is Apache-2.0.
Read from SKILL.md and the folder at commit 3e1456a. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
gitFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Design Helper loads about 3k tokens when it runs, and up to ~17k if it reads all its reference files. Until then it costs about 156 tokens; SKILL.md has 1,735 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from hashgraph-online/awesome-codex-plugins at commit 3e1456a, republished under its Apache-2.0 licence (© hashgraph-online). 1,735 words, ~2,966 tokens.
.claude/skills/design-helper/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.A ruler, not a design generator. Don't invent a look. Lay the range out —
blur 4 / 8 / 12 / 16 / 24 — and let the user pick with their eyes. Taste belongs
to them; the job here is to set up an accurate measurement.
Prose, tables, ASCII and emoji are not pictures. Never describe a shape in words and ask the user to choose. "12px or 16px padding?" is not a question — draw both.
The user never copies a value out. They point at a specimen; making the code change is mine, immediately after their choice.
Assume no stack. Detection matches the repo — references/stylesystems.md.
These instructions are English. Everything the user sees is Korean.
Korean strings quoted below are fixed labels. Render them verbatim — never translate, localize or paraphrase them. Never surface these instructions as text.
One order = one axis = one ladder = one decision.
주문 → 확정값 위에 그 축 하나만 사다리로 → 내가 새로고침·확인
→ 사용자 선택 → 기록 → 영향 범위 확인 → 코드 반영·검증I do not know what comes next. There is no stage list, no default list, no queue,
no 남은 단계. Never name the next axis, never hint at one, never draw one while I'm
in there anyway. Only the axis that was ordered exists.
Clarification scales with uncertainty, not a fixed questionnaire. A precise request can go straight to specimens. A vague request needs successive questions until its purpose and comparison scope are clear enough to draw useful alternatives.
First inspect the request, earlier answers, the target UI, and relevant project code. Read existing tokens, component variants, usage sites, and states yourself. Do not ask the user for facts available there, or reconfirm decisions already made.
Ask one consequential question at a time — the unresolved issue whose answer would
most change the specimens or the application scope — then reassess. Stop once the
target, intended outcome, comparison axis and material constraints are understood;
visual values are chosen from specimens, not verbal descriptions. Examples and the
stopping rule → references/clarification.md.
If the user says 알아서 해줘 or asks to see something first, use project conventions
and narrow, reversible assumptions, state the material ones briefly, and draw.
Delegation is not system-wide scope. Never invent the answer to a pending question and
build alternatives on it.
For a blank slate, clarify purpose and usage when unclear, then open with a coordinate
sweep — references/sweeping.md. Do not make the user name CSS axes before they have
anything to see. Its result is an anchor, not a settled property decision.
그림자 C.시안은 몇 개 정도 보고 싶으세요? 제가 차이가 뚜렷한 것만 추려도 됩니다.references/controls.md. Refinement happens through chat.토큰 그대로 · --radius-md 고침 (23곳) · 새 토큰정할 것 · 볼 곳 · 답하기), turn dividers, the
table of contents, the width-filling grid and the sheet style →
references/sheet.md. Captions and the recommendation → references/sweeping.mdreferences/sweeping.mdreferences/motion.mdThree kinds. Never collapse them.
| response | kind | do |
|---|---|---|
좋네 (no identifiable specimen) | impression | Ask which specimen or what to refine |
C가 나은데 더 진하게 | refine | Append a ladder below, letters continue |
난 B가 좋아 · C로 갈게 | choice | Record, apply to the target, and verify in this turn |
Selection happens in chat only — no pin, apply or confirm buttons on the sheet. A
choice needs no special wording. A에서 블러를 더 보고 싶어 is a refine: use A as the
baseline without applying it. A reply naming a different axis is the next order.
Resolve the letter against the currently displayed specimen. If browser controls changed its value, inspect the user's actual tab before applying; a fresh tab can have different sessionStorage. If that state is inaccessible, ask for the displayed value rather than guessing from the original sheet.
Ambiguous — 이거 좋다 with nine specimens on screen — ask which one. Never guess.
On a choice, briefly acknowledge and apply in the same turn — Ending:
C · 검정 40%로 선택하셨네요. 해당 카드에 바로 반영하겠습니다.No next axis, no 남은 단계, no 코드에 반영할까요.
Keep it in $WS/memo.md, beside the sheet: axis → chosen value → what it resolves
to. It exists for one reason — so the next ladder can be drawn on top of it.
An anchor from a blank-slate matrix is recorded as 출발점:, never 확정: — every
property it bundles is still open.
Revising a settled axis overwrites its line. The old specimens stay where they are.
Drawing turns up things nobody ordered — a misnamed token, a chip that vanished, an axis that was never on anyone's list.
아이콘 칩이 사라졌습니다 — 면 #202020 과 Δ2 입니다A finding is not an order.
If the project animates with a motion library, say what won't translate —
references/motion.md.
The user looks at the browser. I confirm with values and pictures.
1. Every name referenced must exist. A wrong name fails silently — it simply
doesn't appear. Same for a nonexistent utility class and an undefined var(--x).
Check per the fork that detection found. Run this every time specimens are added.
grep -c 'rounded-control-md' "$WS/sheet.css" # utility: in the build output?
grep -c '\--color-hover' tokens.css # CSS variable: defined?Skip it when values were written directly (blank slate) — nothing fails silently.
2. Read computed style with Playwright. A name that exists but is overridden by another rule won't be caught by step 1. Read it off the component, across the rungs, and confirm they actually differ — a value that never reached the specimen leaves five identical pictures and throws nothing.
await p.$$eval('.spec .target', e => e.map(x => getComputedStyle(x).borderRadius))3. Screenshot with Playwright, then open the image and look at it. Catch a broken layout before the user does. The recommendation is written by someone who looked.
await p.screenshot({ path: shot, fullPage: true })A fullPage shot cannot see what a horizontal scrollbar is hiding. Count the rungs
in the DOM, not in the picture.
Run 2 and 3 once per work unit, not on every ladder. A screenshot captures static state only — motion is settled by what the user reports from the browser.
No Playwright → skip silently. Do step 1 only. Don't offer to install it, don't mention it's missing.
$WS, outside the project — sheet, server, built CSS, memo,
screenshots, pid files. Nothing is written into the project until the apply. The
server deletes $WS after two minutes without requests; after that, a fresh sheet
holds only the new request — the old ladders are not rebuilt. references/liveview.mdreferences/liveview.md. Never end a turn by
telling the user to refreshreferences/stylesystems.md, output to $WS/sheet.css.
A <link>ed file follows on reload alonereferences/liveview.md#present-every-revisionSelection is the apply order. A clear chat choice authorizes applying the selected value to the current target in the same turn — no second approval. An anchor remains a starting point, not an apply order. If the user asked to compare or record only, defer.
Record → inspect and briefly report the actual blast radius → apply → verify → report what changed and what was verified. Never claim application from a memo entry alone. Default to the current target: reuse an existing token or make a local override when changing a shared token would affect unrelated components. Change a shared token when that broader scope is already authorized. Ask only if a necessary scope decision cannot be resolved from the request; routine implementation choices do not block apply. Honor explicit requests to defer application. If the target source is unavailable, say what is missing rather than reporting the choice as applied.
Application is not session teardown. Hold the sheet and browser until the user has
checked the real code and says it is done: 끝났어 · 됐어. A phrase like 이걸로 가자
while choosing means apply; it is not by itself confirmation that the applied result
was checked. Then run the teardown in references/liveview.md and check git status
for stray comparison files. Preserve the applied code and existing user changes.
Only what was explicitly chosen goes into code. An alternative merely mentioned along the way is not a decision.
© hashgraph-online, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 7 other files (references) in plugins/Dessert99/design-helper/skills/design-helper of hashgraph-online/awesome-codex-plugins.
Open the folder on GitHubat commit 3e1456a
Design Helper next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Design Helper this skillhashgraph-online/awesome-codex-plugins | 1.3k | — | ~3k | Automated safety check: Pass | Apache-2.0 | |
| Trellis Session Insightmindfold-ai/Trellis | 15k | 4 repos | ~1.7k | Automated safety check: Pass | AGPL-3.0 | |
| Native Data FetchingCherryHQ/cherry-studio-app | 4k | 6 repos | ~2.9k | Automated safety check: Notes | MIT | |
| Debugging Executionsn8n-io/n8n | 207k | — | ~2.6k | Automated safety check: Pass | Custom licence | |
| Aoti Debugpytorch/pytorch | 104k | 1 repos | ~1.7k | Automated safety check: Pass | Custom licence | |
| Herdr Throwaway Reproductionherdrdev/herdr | 43k | — | ~2.4k | Automated safety check: Pass | Apache-2.0 |
mindfold-ai/Trellis
Reach into past AI conversation history through the trellis mem CLI.
CherryHQ/cherry-studio-app
A skill your agent uses when implementing or debugging ANY network request, API call, or data fetching.
n8n-io/n8n
Debug failed or wrong-output workflow executions using executions tools.
pytorch/pytorch
Debug AOTInductor (AOTI) errors and crashes. An agent skill from pytorch/pytorch.
herdrdev/herdr
Runs a disposable, uniquely named Herdr session inside an existing one so runtime, pane, terminal or API bugs can be reproduced without touching the main session.
ultralisp/ultralisp
A skill your agent uses when encountering any bug, test failure, or unexpected behavior, before proposing fixes
hashgraph-online/awesome-codex-plugins
Create original anime-style reaction stickers as looping GIFs and MP4 previews, using generated character pose sheets and timed key poses.
hashgraph-online/awesome-codex-plugins
Manage and query Calibre libraries with the calibredb CLI (local paths or Calibre Content server URLs).
hashgraph-online/awesome-codex-plugins
A skill your agent uses when adding, changing, testing, or debugging Rust HTTP APIs and services, especially when Codex needs black-box integration tests, random-port app startup, real database test…
hashgraph-online/awesome-codex-plugins
Make a studio's game look like something at build time — a cover from a real frame of the game (free), painted covers, backdrops, textures and character plates from image models through the…
hashgraph-online/awesome-codex-plugins
Use CALL-E from Codex through the calle CLI. An agent skill from hashgraph-online/awesome-codex-plugins.
hashgraph-online/awesome-codex-plugins
Balance game difficulty, resources, rewards, probability, progression, economies, and dominant strategies.
Categories
A skill your agent uses when several visual variants need to be compared side by side — mockups, layouts, or a range of one value (spacing, radius, shadow, color, motion) — or when you are about to…. Design Helper is an agent skill from hashgraph-online/awesome-codex-plugins. Use when several visual variants need to be compared side by side — mockups, layouts, or a range of one value (spacing, radius, shadow, color, motion) — or when you are about to ask the user to pick between visual options in prose.
Design Helper fits situations like: several visual variants need to be compared side by side — mockups; A range of one value (spacing; you are about to ask the user to pick between visual options in prose; 5가지 버전으로 보여줘 · A 랑 B 중에 뭐가 나아 · 시안 여러 개 비교해줘 · 나란히 놓고 보자.
Run `npx skills add hashgraph-online/awesome-codex-plugins --skill design-helper -a claude-code`. Or copy the skill folder (plugins/Dessert99/design-helper/skills/design-helper in hashgraph-online/awesome-codex-plugins) into .claude/skills/design-helper in your project. Claude Code loads it when a task matches its description.
Run `npx skills add hashgraph-online/awesome-codex-plugins --skill design-helper -a codex`. Or copy the skill folder (plugins/Dessert99/design-helper/skills/design-helper in hashgraph-online/awesome-codex-plugins) into .agents/skills/design-helper in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hashgraph-online/awesome-codex-plugins --skill design-helper -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/design-helper, .gemini/skills/design-helper, .github/skills/design-helper and .opencode/skills/design-helper in your project.
Going by SKILL.md and its folder, Design Helper needs the command-line tools its instructions call (git).
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Design Helper is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 3k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 14k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Design Helper: Trellis Session Insight (mindfold-ai/Trellis, 15k stars), Native Data Fetching (CherryHQ/cherry-studio-app, 4k stars), Debugging Executions (n8n-io/n8n, 207k stars) and Aoti Debug (pytorch/pytorch, 104k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
hashgraph-online (a GitHub organization) maintains it in hashgraph-online/awesome-codex-plugins, which has 1,267 GitHub stars. The repository holds 716 skills in this directory. The repository was last updated on October 10, 2026.
Source: hashgraph-online/awesome-codex-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.