A skill your agent uses for standard or complex new work before coding or planning.

Apache-2.0Auto-check passed

Install Design

skills CLI
$ npx skills add hashgraph-online/awesome-codex-plugins --skill design -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install hashgraph-online/awesome-codex-plugins design --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/ouonet/praxis/skills/design .claude/skills/design && rm -rf skills-src

Use ~/.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/

Facts

Skill name
design
GitHub stars
1.2k
Token cost
~1.3k tokens
SKILL.md length
626 words
Files
1
Skills in repo
686
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses for standard or complex new work before coding or planning.

  • Works in 2 steps: docs/staging/specs/YYYY-MM-DD-.md must… → Confirm with the user.
  • Complex new work before coding
  • SKILL.md covers Before designing, Multi-module changes, Spec = list of decisions and Two layers, one file:…, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Design is an agent skill from hashgraph-online/awesome-codex-plugins. Use for standard or complex new work before coding or planning. Also handles vague goals — clarifies before designing.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

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.

When your agent uses it

  • Complex new work before coding

Example prompts

  • “/design”

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

  1. docs/staging/specs/YYYY-MM-DD-.md must exist on disk before handing off to plan. For multi-module work, the coordinator spec and every…
  2. Confirm with the user.

What it can do on your machine

Read from SKILL.md and the folder at commit 78497e5. It shows what the files ask for, not the result of running them.

  • Tool permissions

    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.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Design loads about 1.3k tokens when it runs. Until then it costs about 31 tokens; SKILL.md has 626 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~31
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

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.

Safety

Auto-check passed

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.

SKILL.md

The full file from hashgraph-online/awesome-codex-plugins at commit 78497e5, republished under its Apache-2.0 licence (© hashgraph-online). 626 words, ~1,290 tokens.

Download SKILL.mdSave it as .claude/skills/design/SKILL.md (or your agent's skills folder).
name
design
description
Use for standard or complex new work before coding or planning. Also handles vague goals — clarifies before designing.

Design

<gate> No code until user approves the spec. </gate>

Before designing

Goal too vague to name what to build, for whom, or what success looks like? Ask one question per turn until it's concrete. Don't propose solutions until then. Working notes can hold hypotheses, experiments, ruled-out directions (spike code → temporary worktree).

Clarify in dependency order. Resolve facts from the repo/tools; ask only the current decision frontier requiring user judgment. Don't ask downstream questions before prerequisite decisions or map the full dependency tree. Stop when implementation-affecting contract, data, failure, and test decisions are decided or deferred.

Goal clear? Propose 2-3 approaches with trade-offs; recommend one. Then write the spec.

Multi-module changes

If topology=multi-module (triage announcement or coordinator spec/plan declaration), read ../references/multi-module.md before designing. Create the coordinator spec with the declaration block (topology: multi-module, change-set, coordinator, repos) - this declaration is the on-disk mode marker downstream skills rely on.

  • Identify workspace modules and Git boundaries separately.
  • For multiple repositories, ask the user to designate one existing repository as coordinator. This is an implementation-affecting decision; do not infer it.
  • Put only shared contracts and integration acceptance needed by this change in the coordinator spec.
  • Put module-local decisions and acceptance in a spec inside each module's owning repository. Reference shared contracts; never duplicate them.
  • Assign one stable change-set ID (in the declaration block) and declare every participating repository path relative to the coordinator.
  • A missing repository or unresolved shared contract blocks handoff.

Spec = list of decisions

A spec answers the open questions for THIS change. Typical:

  • contract / interface?
  • data shape?
  • failure modes?
  • out of scope?
  • what test proves it?
  • architecture?
  • convention?

Do spec idiomatically. Record convention — stack best practices + project conventions for this change (see ../references/quality.md); tdd/review verify against it.

No question → no section. Don't fill "Risks" / "Non-goals" if empty.

Use declarations, not narrative:

contract:  <interface>
invariant: <what must hold>
test:      <how we'll know>
convention: <stack best practices + project conventions — see ../references/quality.md>
deferred:  <not deciding now>

Reference code by path; never paste it.

Before handoff, close only decisions that affect implementation: contract, data, failure, test. Unresolved Working notes in those areas become decisions, deferred, or questions.

Two layers, one file: docs/staging/specs/YYYY-MM-DD-<topic>.md

  • Top: decisions, contracts, invariants (permanent).
  • ## Working notes: scratch, open questions, hypotheses, ruled-out directions (stripped at ship).
Show full SKILL.md (285 more words)Show less

Roadmap

docs/ROADMAP.md already exists?

  • Does this work add new milestones? Append them to docs/ROADMAP.md.
  • Otherwise, no roadmap action needed.

docs/ROADMAP.md does not exist?

  • This work spans ≥ 3 milestones → create docs/ROADMAP.md:
    markdown
    - [ ] M1: <one-line goal>
    - [ ] M2: <one-line goal>
    - [ ] M3: <one-line goal>
  • Otherwise → no roadmap needed. Describe full scope in spec.

Stubs are intent, not commitment; update before expanding.

If roadmap exists or was created, reference the current milestone in staging spec:

milestone: M1 (see docs/ROADMAP.md)

Spec review gate

After spec is written to disk and before handing off to plan, inspect the spec to decide how many reviewers to dispatch. Read ../references/reviewers.md for the trigger table and reviewer charters.

Count the triggers that match the spec. If only trigger 1 fires (the baseline), dispatch a single spec-compliance reviewer — this is the default behavior, same cost as today. If multiple triggers fire, dispatch each reviewer as an independent subagent in parallel.

All reviewers receive the spec path (not the spec content — let them read it). Collect findings, then synthesize: evaluate each finding critically, resolve conflicts between reviewers, spot what was missed, judge severity, and patch the spec once. Present to user: what was found, fixed, deferred — and why.

Report to user: which triggers fired, which reviewers ran, what was found and fixed.

Abandon

If the user decides not to proceed after clarification, stop here. No spec, no plan, no ship. Record reason briefly in working notes. If exploration produced a knowledge artifact (protocol spec, RE findings, data structure map), save it to docs/decisions/ via archive.

Gates

<gate>

  1. docs/staging/specs/YYYY-MM-DD-<topic>.md must exist on disk before handing off to plan. For multi-module work, the coordinator spec and every affected module spec must exist in their owning repositories.
  2. Confirm with the user.

</gate>

© 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

Files

Just SKILL.md in plugins/ouonet/praxis/skills/design of hashgraph-online/awesome-codex-plugins.

Open the folder on GitHubat commit 78497e5

Compare with similar skills

Design 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.

Design compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Design this skillhashgraph-online/awesome-codex-plugins1.2k—~1.3kAutomated safety check: PassApache-2.0
Telemetry Standardssupabase/supabase111k—~2kAutomated safety check: PassApache-2.0
Cpp Coding Standardsaffaan-m/ECC275k4 repos~5.6kAutomated safety check: PassMIT
Java Coding Standardsaffaan-m/ECC275k1 repos~2.9kAutomated safety check: PassMIT
Coding Standardsaffaan-m/ECC275k3 repos~2.6kAutomated safety check: PassMIT
Coding Standardsaffaan-m/ECC275k2 repos~2.6kAutomated safety check: PassMIT

Similar skills

  • Telemetry Standards

    supabase/supabase

    Official

    PostHog event tracking standards for Supabase Studio. An agent skill from supabase/supabase.

    111k GitHub stars~2k tokensUpdated today
    Data & AnalyticsAuto-check passed
  • C++ coding standards based on the C++ Core Guidelines (isocpp.github.io).

    275k GitHub starsUsed in 4 repos~5.6k tokens
    DevelopmentAuto-check passed
  • Java coding standards for Spring Boot and Quarkus services: naming, immutability, Optional usage, streams, exceptions, generics, CDI, reactive patterns, and project layout.

    275k GitHub starsUsed in 1 repo~2.9k tokens
    DevelopmentAuto-check passed
  • Coding Standards

    affaan-m/ECC

    适用于TypeScript、JavaScript、React和Node.js开发的通用编码标准、最佳实践和模式. An agent skill from affaan-m/ECC.

    275k GitHub starsUsed in 3 repos~2.6k tokens
    DevelopmentAuto-check passed
  • Coding Standards

    affaan-m/ECC

    TypeScript、JavaScript、React、Node.js開発のための汎用コーディング標準、ベストプラクティス、パターン。

    275k GitHub starsUsed in 2 repos~2.6k tokens
    DevelopmentAuto-check passed
  • Coding Standards

    affaan-m/ECC

    TypeScript, JavaScript, React, Node.js 개발을 위한 범용 코딩 표준, 모범 사례 및 패턴.

    275k GitHub starsUsed in 2 repos~2.7k tokens
    DevelopmentAuto-check passed

More from hashgraph-online/awesome-codex-plugins

All 686 skills in this repo
  • Anime Reaction Gif

    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.

    1.2k GitHub stars~922 tokensUpdated today
    Auto-check passed
  • Calibredb

    hashgraph-online/awesome-codex-plugins

    Manage and query Calibre libraries with the calibredb CLI (local paths or Calibre Content server URLs).

    1.2k GitHub stars~1k tokensUpdated today
    Auto-check passed
  • Rust API Test Harness

    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…

    1.2k GitHub stars~1.7k tokensUpdated today
    Auto-check passed
  • Art

    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…

    1.2k GitHub stars~2.4k tokensUpdated today
    Auto-check passed
  • Game Balance Economy

    hashgraph-online/awesome-codex-plugins

    Balance game difficulty, resources, rewards, probability, progression, economies, and dominant strategies.

    1.2k GitHub stars~618 tokensUpdated today
    Auto-check passed
  • Manuscript Engagement Analytics

    hashgraph-online/awesome-codex-plugins

    Analyze nonfiction manuscripts for reader engagement signals, including heading-level word counts, slow starts, long slogs, weak takeaway titles, value pacing, beta-reader comment dropoff, and…

    1.2k GitHub stars~875 tokensUpdated today
    Auto-check passed

Questions about Design

What does Design do?

A skill your agent uses for standard or complex new work before coding or planning. Design is an agent skill from hashgraph-online/awesome-codex-plugins. Use for standard or complex new work before coding or planning.

When should I use Design?

Design fits situations like: complex new work before coding.

How do I install Design in Claude Code?

Run `npx skills add hashgraph-online/awesome-codex-plugins --skill design -a claude-code`. Or copy the skill folder (plugins/ouonet/praxis/skills/design in hashgraph-online/awesome-codex-plugins) into .claude/skills/design in your project. Claude Code loads it when a task matches its description.

How do I install Design in Codex?

Run `npx skills add hashgraph-online/awesome-codex-plugins --skill design -a codex`. Or copy the skill folder (plugins/ouonet/praxis/skills/design in hashgraph-online/awesome-codex-plugins) into .agents/skills/design in your project. Codex loads it when a task matches its description.

Can I use Design in Cursor, Gemini CLI or GitHub Copilot?

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 -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, .gemini/skills/design, .github/skills/design and .opencode/skills/design in your project.

What does Design need to run?

SKILL.md names no scripts, command-line tools or credentials: Design is instructions for the agent only.

Does Design access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Design safe to install?

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.

What licence does Design use?

Design 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.

How many tokens does Design use?

About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Design?

Skills that share tags, products or a category with Design: Telemetry Standards (supabase/supabase, 111k stars), Cpp Coding Standards (affaan-m/ECC, 275k stars), Java Coding Standards (affaan-m/ECC, 275k stars) and Coding Standards (affaan-m/ECC, 275k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Design?

hashgraph-online (a GitHub organization) maintains it in hashgraph-online/awesome-codex-plugins, which has 1,242 GitHub stars. The repository holds 686 skills in this directory. The repository was last updated on October 8, 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.