shinpr/nautilus · Archived

recipe-refine-visuals

Use when a design-capable human wants to refine the auto-derived Visual Tokens in `docs/product/design/brand-direction.md`

First seen Jul 22, 2026

Installation

$ npx skills add shinpr/nautilus --skill recipe-refine-visuals

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from shinpr/nautilus · top by installs.

npx skills add shinpr/nautilus

Browse all from shinpr/nautilus

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Declared

Repository health

Stars 3
License LICENSE
Default branch main
Open issues 0
Status Archived

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents opencode

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,551 B
  • docs SUMMARY.md 151 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Context: Refine the Visual Tokens in docs/product/design/brand-direction.md after recipe-blueprint has created an initial set.

This side workflow applies when a human with design judgment explicitly requests refinement of the auto-derived token set.

Required Skills [LOAD BEFORE EXECUTION]

  1. [LOAD IF NOT ACTIVE] blueprint-standards — brand-direction template and Visual Token structure
  2. [LOAD IF NOT ACTIVE] design-perspective — accessibility and persona-aware design review

Workflow

  1. Read docs/product/design/brand-direction.md
  2. Review current Visual Tokens against design principles, personas, and prototype learnings
  3. Verify:

- text-on-surface contrast ratio is at least 4.5:1 for normal text - heading text is at least 1.25x the body size in the primary hierarchy step - spacing tokens form a consistent increasing scale without reversals

  1. Apply exact overrides supplied by the user and mark the source as expert-refined
  2. When the request requires a new design choice, present only that choice and its rationale; update the file after the user confirms it

Scope Boundaries

Included: colors, typography, spacing, radius, shadow values Not included: redesigning the entire blueprint or introducing implementation-specific component APIs