agentleFS
shinprshinpr/nautilus/.agents/skills/recipe-refine-visuals/SKILL.md

recipe-refine-visuals

Skill7 starsChanged 3 months agoMITView on GitHub

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

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When the request requires a new design choice, present only that choice and its rationale.

    line 27

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
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
  4. Apply exact overrides supplied by the user and mark the source as expert-refined
  5. 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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.