New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Hardwarevisualizer Design Review

by shm11C3 in shm11C3/HardwareVisualizer

Review or shape HardwareVisualizer product and architecture changes against the maintainer's design principles.

GPL-3.0Auto-check passedMedia & Creative

Install Hardwarevisualizer Design Review

skills CLI
$ npx skills add shm11C3/HardwareVisualizer --skill hardwarevisualizer-design-review -a claude-code

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

GitHub CLI
$ gh skill install shm11C3/HardwareVisualizer hardwarevisualizer-design-review --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/shm11C3/HardwareVisualizer.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/hardwarevisualizer-design-review .claude/skills/hardwarevisualizer-design-review && 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
hardwarevisualizer-design-review
GitHub stars
183
Token cost
~1k tokens
SKILL.md length
487 words
Files
2
Skills in repo
6
Repo updated
First seen
Licence
GPL-3.0

At a glance

Review or shape HardwareVisualizer product and architecture changes against the maintainer's design principles.

  • Works in 6 steps: Frame The Product Claim → Map Ownership → Check Semantics → …
  • Reviewing behavior that affects hardware availability
  • SKILL.md covers Load The Decision Context, Review Workflow and Decision
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Hardwarevisualizer Design Review is an agent skill from shm11C3/HardwareVisualizer. Review or shape HardwareVisualizer product and architecture changes against the maintainer's design principles. Use when planning, implementing, or reviewing behavior that affects hardware availability, collection cost, live/history semantics, settings, persistence, user selection, Core/App ownership, optional components, privacy, or user-visible evidence.

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Media & Creative, covering Design review and critique. The repository describes itself as: A cross-platform hardware monitor with real-time metrics, local history, and customizable dashboards. The licence is GPL-3.0.

When your agent uses it

  • Reviewing behavior that affects hardware availability
  • Collection cost
  • Live/history semantics
  • Core/App ownership

Example prompts

  • “/hardwarevisualizer-design-review”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Frame The Product Claim
  2. Map Ownership
  3. Check Semantics
  4. Check Cost And Optionality
  5. Check User Intent And Privacy
  6. Define Proof Before Editing

What it can do on your machine

Read from SKILL.md and the folder at commit fc54f73. 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.

    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

Hardwarevisualizer Design Review loads about 1k tokens when it runs. Until then it costs about 98 tokens; SKILL.md has 487 words of instructions outside code blocks.

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

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 shm11C3/HardwareVisualizer at commit fc54f73, republished under its GPL-3.0 licence (© shm11C3). 487 words, ~1,001 tokens.

Download SKILL.mdSave it as .claude/skills/hardwarevisualizer-design-review/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
hardwarevisualizer-design-review
description
Review or shape HardwareVisualizer product and architecture changes against the maintainer's design principles. Use when planning, implementing, or reviewing behavior that affects hardware availability, collection cost, live/history semantics, settings, persistence, user selection, Core/App ownership, optional components, privacy, or user-visible evidence.

HardwareVisualizer Design Review

Load The Decision Context

Read only the context relevant to the change:

  1. docs/design-principles.md.
  2. The applicable terms in CONTEXT.md.
  3. The nearest scoped AGENTS.md and owner README.
  4. Relevant ADRs, including their status.
  5. Current code/tests/runtime evidence for the claimed behavior.

Treat lessons, handoffs, issue comments, and AI memory as leads. Verify them against the current branch and canonical sources before using them as facts.

Review Workflow

1. Frame The Product Claim

State the user-visible outcome in one sentence. Name the issue or explicit request that anchors scope. Separate adjacent cleanup or features unless they are necessary for the same claim.

2. Map Ownership

Identify who owns each part:

  • hardware fact and collection;
  • product policy and fallback;
  • presentation and wire conversion;
  • interaction/view state;
  • lifecycle and background work;
  • persisted value and migration.

Reject designs that move Tauri into Core, OS access into commands/frontend, or Application Preferences into frontend Tauri Store for convenience.

3. Check Semantics

Ask:

  • Is the value live, short-window, archived, daily-record, or UI-local?
  • Is the subject automatic focus, current data, or explicit user selection?
  • Are the availability/validity states defined by this domain preserved rather than flattened into a generic status model?
  • Does a partial provider/device failure preserve useful results?
  • Does uncertainty avoid destructive deactivation or data loss?

Use existing CONTEXT.md terms. Propose a glossary change before inventing a new synonym for an existing concept.

4. Check Cost And Optionality

Confirm collection/rendering cost follows visible or explicit background value. Do not stop legitimate archive/tray work merely because the main window is hidden.

For an optional component, verify it was attempted and all useful fallbacks are insufficient before showing guidance. Do not label unsupported hardware as a missing installation.

Show full SKILL.md (205 more words)Show less
5. Check User Intent And Privacy

Explicit user choices must survive automatic refresh while they remain valid. If a selected subject is temporarily absent, use a coherent fallback without unnecessarily deleting the stored intent. Only choices classified as Application Preferences are required to survive restart as app configuration; UI-local state may be reset.

Persist only the local identifiers needed for the feature and do not introduce telemetry or portable identity without an explicit product decision.

6. Define Proof Before Editing

Choose evidence that proves the actual claim:

  • focused unit/integration contract;
  • runtime log or SQLite state;
  • web/mock UI behavior;
  • native Tauri integration;
  • rendered screenshot at relevant viewports;
  • measured performance/CI timing;
  • release artifact/signature inspection.

Do not substitute one evidence class for another.

Decision

Return one of these outcomes before or alongside implementation:

  • Aligned: existing principles and ownership cover the change.
  • Aligned with guardrail: proceed with a named test, rule, or migration.
  • ADR required: a specific trade-off or exception needs a recorded decision.
  • Clarification required: canonical sources conflict or product intent is not discoverable.
  • Not aligned: explain the violated principle and the smallest viable design correction.

When implementation is requested and the decision is aligned, continue through the change and validation. Do not stop at the review summary.

© shm11C3, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .agents/skills/hardwarevisualizer-design-review of shm11C3/HardwareVisualizer.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit fc54f73

Compare with similar skills

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

Hardwarevisualizer Design Review compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Hardwarevisualizer Design Review this skillshm11C3/HardwareVisualizer183—~1kAutomated safety check: PassGPL-3.0
Consult ClaudeEpicenterHQ/epicenter4.8k—~2kAutomated safety check: PassCustom licence
System Atlasinkboard/system-atlas430—~2.3kAutomated safety check: PassMIT
Design Image Studiokangarooking/design-image-studio102—~1.5kAutomated safety check: PassMIT
Kicad Reviewmixelpixx/Konnect927—~3.2kAutomated safety check: PassAGPL-3.0
Design AuditUniClipboard/UniClipboard1.9k—~554Automated safety check: PassAGPL-3.0

Similar skills

  • Consult Claude

    EpicenterHQ/epicenter

    Assign Claude Code a read-only investigation, recommendation, or finished text draft.

    4.8k GitHub stars~2k tokensUpdated yesterday
    Media & CreativeAuto-check passed

  • System Atlas

    inkboard/system-atlas

    Build and maintain an explorable, progressively-disclosed isometric "atlas" of a system's architecture — an interactive page (hover to read, click to pin, go inside for steps, moving data packets…

    430 GitHub stars~2.3k tokensUpdated 1 mo ago
    Media & CreativeAuto-check passed

  • Design Image Studio

    kangarooking/design-image-studio

    Directly generate design-oriented AI images with strong creative direction and prompt engineering.

    102 GitHub stars~1.5k tokensUpdated 5 mo ago
    Media & CreativeAuto-check passed

  • Kicad Review

    mixelpixx/Konnect

    Design review and validation workflow for KiCAD projects via MCP tools.

    927 GitHub stars~3.2k tokensUpdated 4 days ago
    Media & CreativeAuto-check passed

  • Design Audit

    UniClipboard/UniClipboard

    定期审计代码库的工程设计问题（高心智复杂度、单一真相源被破坏、catch-all 胖接口、死代码、散落魔法字面量、泄漏抽象、资源生命周期靠环形缓冲）与可优化点，范围限定为自上次审计以来的 git churn，每条发现都落到 file:line 并对照本项目自己的 VISION.md / 各级 AGENTS.md / memory…

    1.9k GitHub stars~554 tokensUpdated today
    Media & CreativeAuto-check passed

  • L1 AI Design Review

    PaperMoonuu/Design-workflow-skills

    L1 × AI 设计评审：对已完成的单页、局部 UI 设计稿进行小型迭代评审，识别影响面、状态遗漏、文案与一致性风险，并给出 P0/P1/P2 建议和验收清单。用户提供 Figma 链接、截图、前后设计稿或可评审原型，并要求设计走查、风险评审或开发前 UI 检查时使用；不用于设计前方案预检、完整多页面流程或 L2 开发交付。

    316 GitHub stars~492 tokensUpdated 17 days ago
    Media & CreativeAuto-check passed

More from shm11C3/HardwareVisualizer

  • Capture Project Learning

    shm11C3/HardwareVisualizer

    Turn a HardwareVisualizer maintainer correction, repeated failure, surprising invariant, or costly investigation into an evidence-backed learning record and the right durable guardrail.

    183 GitHub stars~858 tokensUpdated yesterday
    Auto-check passed

  • Change Kind Naming

    shm11C3/HardwareVisualizer

    Decide the correct change kind and semantically align branch names, PR titles, commit prefixes, and PR template types.

    183 GitHub stars~994 tokensUpdated yesterday
    Auto-check passed

  • Gh AI Review Triage

    shm11C3/HardwareVisualizer

    Triage and optionally address AI-generated GitHub PR review feedback from Copilot, CodeRabbit, or similar bots.

    183 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Deliver Pull Request

    shm11C3/HardwareVisualizer

    Deliver a focused HardwareVisualizer change as a pull request, then address its CI and review feedback to completion.

    183 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed

  • Verify Identity Contracts

    shm11C3/HardwareVisualizer

    Verify the id/key contract between backend producers and frontend consumers before implementing any change that joins, selects, persists, or attributes entities keyed by backend-produced ids (GPUs…

    183 GitHub stars~1.7k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Hardwarevisualizer Design Review

What does Hardwarevisualizer Design Review do?

Review or shape HardwareVisualizer product and architecture changes against the maintainer's design principles. Hardwarevisualizer Design Review is an agent skill from shm11C3/HardwareVisualizer. Review or shape HardwareVisualizer product and architecture changes against the maintainer's design principles.

When should I use Hardwarevisualizer Design Review?

Hardwarevisualizer Design Review fits situations like: reviewing behavior that affects hardware availability; collection cost; live/history semantics; core/App ownership.

How do I install Hardwarevisualizer Design Review in Claude Code?

Run `npx skills add shm11C3/HardwareVisualizer --skill hardwarevisualizer-design-review -a claude-code`. Or copy the skill folder (.agents/skills/hardwarevisualizer-design-review in shm11C3/HardwareVisualizer) into .claude/skills/hardwarevisualizer-design-review in your project. Claude Code loads it when a task matches its description.

How do I install Hardwarevisualizer Design Review in Codex?

Run `npx skills add shm11C3/HardwareVisualizer --skill hardwarevisualizer-design-review -a codex`. Or copy the skill folder (.agents/skills/hardwarevisualizer-design-review in shm11C3/HardwareVisualizer) into .agents/skills/hardwarevisualizer-design-review in your project. Codex loads it when a task matches its description.

Can I use Hardwarevisualizer Design Review 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 shm11C3/HardwareVisualizer --skill hardwarevisualizer-design-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/hardwarevisualizer-design-review, .gemini/skills/hardwarevisualizer-design-review, .github/skills/hardwarevisualizer-design-review and .opencode/skills/hardwarevisualizer-design-review in your project.

What does Hardwarevisualizer Design Review need to run?

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

Does Hardwarevisualizer Design Review 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 Hardwarevisualizer Design Review 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 Hardwarevisualizer Design Review use?

Hardwarevisualizer Design Review is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Hardwarevisualizer Design Review use?

About 1k tokens (SKILL.md is roughly 4k 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 Hardwarevisualizer Design Review?

Skills that share tags, products or a category with Hardwarevisualizer Design Review: Consult Claude (EpicenterHQ/epicenter, 4.8k stars), System Atlas (inkboard/system-atlas, 430 stars), Design Image Studio (kangarooking/design-image-studio, 102 stars) and Kicad Review (mixelpixx/Konnect, 927 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Hardwarevisualizer Design Review?

shm11C3 (a GitHub user) maintains it in shm11C3/HardwareVisualizer, which has 183 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 9, 2026.

Source: shm11C3/HardwareVisualizer on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.