Awesome-omni-skills minimalist-ui

Protocol: Premium Utilitarian Minimalism UI Architect workflow skill. Use this skill when the user needs creating clean editorial interfaces with warm monochrome palettes, crisp borders, restrained motion, and flat bento layouts and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

install

source · Clone the upstream repo

git clone https://github.com/diegosouzapw/awesome-omni-skills

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/diegosouzapw/awesome-omni-skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/minimalist-ui" ~/.claude/skills/diegosouzapw-awesome-omni-skills-minimalist-ui && rm -rf "$T"

manifest: skills/minimalist-ui/SKILL.md

Protocol: Premium Utilitarian Minimalism UI Architect

Overview

This public intake copy packages

plugins/antigravity-awesome-skills-claude/skills/minimalist-ui

from

https://github.com/sickn33/antigravity-awesome-skills

into the native Omni Skills editorial shape without hiding its origin.

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses

metadata.json

plus

ORIGIN.md

as the provenance anchor for review.

Protocol: Premium Utilitarian Minimalism UI Architect

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Limitations, 1. Protocol Overview, 2. Absolute Negative Constraints (Banned Elements), 3. Typographic Architecture, 4. Color Palette (Warm Monochrome + Spot Pastels), 5. Component Specifications.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

Use when the user wants a refined minimalist UI inspired by tools like Notion, Linear, or editorial workspace products.
Use when designing warm monochrome interfaces with crisp borders, generous whitespace, muted pastel accents, and quiet motion.
Use when the task should avoid gradients, heavy shadows, saturated colors, pill-heavy components, and generic SaaS visuals.
Use when the request clearly matches the imported source intent: creating clean editorial interfaces with warm monochrome palettes, crisp borders, restrained motion, and flat bento layouts.
Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.
Use when provenance needs to stay visible in the answer, PR, or review packet.

Operating Table

Situation	Start here	Why it matters
First-time use	`metadata.json`	Confirms repository, branch, commit, and imported path before touching the copied workflow
Provenance review	`ORIGIN.md`	Gives reviewers a plain-language audit trail for the imported source
Workflow execution	`SKILL.md`	Starts with the smallest copied file that materially changes execution
Supporting context	`SKILL.md`	Adds the next most relevant copied source file without loading the entire package
Handoff decision	`## Related Skills`	Helps the operator switch to a stronger native skill when the task drifts

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
Read the overview and provenance files before loading any copied upstream support files.
Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes.
Validate the result against the upstream expectations and the evidence you can point to in the copied files.
Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity.
Before merge or closure, record what was used, what changed, and what the reviewer still needs to verify.

Imported Workflow Notes

Imported: Limitations

Minimalism can hide hierarchy when content is dense; validate scannability, contrast, and navigation clarity with real content.
This skill assumes the product can support restrained palettes and typography-led layouts; do not override an established brand system without cause.
Subtle motion and flat surfaces still need responsive, keyboard, and screen-reader verification in the target project.

Examples

Example 1: Ask for the upstream workflow directly

Use @minimalist-ui to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @minimalist-ui against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @minimalist-ui for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @minimalist-ui using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.
Keep provenance, source commit, and imported file paths visible in notes and PR descriptions.
Point directly at the copied upstream files that justify the workflow instead of relying on generic review boilerplate.
Treat generated examples as scaffolding; adapt them to the concrete task before execution.
Route to a stronger native skill when architecture, debugging, design, or security concerns become dominant.

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in

plugins/antigravity-awesome-skills-claude/skills/minimalist-ui

, fails to mention provenance, or does not use any copied source files at all. Solution: Re-open

metadata.json

ORIGIN.md

, and the most relevant copied upstream files. Load only the files that materially change the answer, then restate the provenance before continuing.

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated

SKILL.md

, but they cannot quickly tell which references, examples, or scripts matter for the current task. Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Related Skills

```
@linear-claude-skill
```
- Use when the work is better handled by that native specialization after this imported skill establishes context.
```
@linkedin-automation
```
- Use when the work is better handled by that native specialization after this imported skill establishes context.
```
@linkedin-cli
```
- Use when the work is better handled by that native specialization after this imported skill establishes context.
```
@linkedin-profile-optimizer
```
- Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

Resource family	What it gives the reviewer	Example path
`references`	copied reference notes, guides, or background material from upstream	`references/n/a`
`examples`	worked examples or reusable prompts copied from upstream	`examples/n/a`
`scripts`	upstream helper scripts that change execution or validation	`scripts/n/a`
`agents`	routing or delegation notes that are genuinely part of the imported package	`agents/n/a`
`assets`	supporting assets or schemas copied from the source package	`assets/n/a`

Imported Reference Notes

Imported: 1. Protocol Overview

Name: Premium Utilitarian Minimalism & Editorial UI Description: An advanced frontend engineering directive for generating highly refined, ultra-minimalist, "document-style" web interfaces analogous to top-tier workspace platforms. This protocol strictly enforces a high-contrast warm monochrome palette, bespoke typographic hierarchies, meticulous structural macro-whitespace, bento-grid layouts, and an ultra-flat component architecture with deliberate muted pastel accents. It actively rejects standard generic SaaS design trends.

Imported: 2. Absolute Negative Constraints (Banned Elements)

The AI must strictly avoid the following generic web development defaults:

DO NOT use the "Inter", "Roboto", or "Open Sans" typefaces.
DO NOT use generic, thin-line icon libraries like "Lucide", "Feather", or standard "Heroicons".
DO NOT use Tailwind's default heavy drop shadows (e.g.,
```
shadow-md
```
,
```
shadow-lg
```
,
```
shadow-xl
```
). Shadows must be practically non-existent or heavily customized to be ultra-diffuse and low opacity (< 0.05).
DO NOT use primary colored backgrounds for large elements or sections (e.g., no bright blue, green, or red hero sections).
DO NOT use gradients, neon colors, or 3D glassmorphism (beyond subtle navbar blurs).
DO NOT use
```
rounded-full
```
(pill shapes) for large containers, cards, or primary buttons.
DO NOT use emojis anywhere in code, markup, text content, headings, or alt text. Replace with proper icons or clean SVG primitives.
DO NOT use generic placeholder names like "John Doe", "Acme Corp", or "Lorem Ipsum". Use realistic, contextual content.
DO NOT use AI copywriting clichés: "Elevate", "Seamless", "Unleash", "Next-Gen", "Game-changer", "Delve". Write plain, specific language.

Imported: 3. Typographic Architecture

The interface must rely on extreme typographic contrast and premium font selection to establish an editorial feel.

Primary Sans-Serif (Body, UI, Buttons): Use clean, geometric, or system-native fonts with character. Target:
```
font-family: 'SF Pro Display', 'Geist Sans', 'Helvetica Neue', 'Switzer', sans-serif
```
.

Editorial Serif (Hero Headings & Quotes): Target:

font-family: 'Lyon Text', 'Newsreader', 'Playfair Display', 'Instrument Serif', serif

. Apply tight tracking (

letter-spacing: -0.02em

-0.04em

) and tight line-height (

1.1

Monospace (Code, Keystrokes, Meta-data): Target:

font-family: 'Geist Mono', 'SF Mono', 'JetBrains Mono', monospace

Text Colors: Body text must never be absolute black (
```
#000000
```
). Use off-black/charcoal (
```
#111111
```
or
```
#2F3437
```
) with a generous
```
line-height
```
of
```
1.6
```
for legibility. Secondary text should be muted gray (
```
#787774
```
).

Imported: 4. Color Palette (Warm Monochrome + Spot Pastels)

Color is a scarce resource, utilized only for semantic meaning or subtle accents.

Canvas / Background: Pure White
```
#FFFFFF
```
or Warm Bone/Off-White
```
#F7F6F3
```
/
```
#FBFBFA
```
.
Primary Surface (Cards):
```
#FFFFFF
```
or
```
#F9F9F8
```
.
Structural Borders / Dividers: Ultra-light gray
```
#EAEAEA
```
or
```
rgba(0,0,0,0.06)
```
.
Accent Colors: Exclusively use highly desaturated, washed-out pastels for tags, inline code backgrounds, or subtle icon backgrounds.
- Pale Red:
```
#FDEBEC
```
  (Text:
```
#9F2F2D
```
  )
- Pale Blue:
```
#E1F3FE
```
  (Text:
```
#1F6C9F
```
  )
- Pale Green:
```
#EDF3EC
```
  (Text:
```
#346538
```
  )
- Pale Yellow:
```
#FBF3DB
```
  (Text:
```
#956400
```
  )

Imported: 5. Component Specifications

Bento Box Feature Grids:
- Utilize asymmetrical CSS Grid layouts.
- Cards must have exactly
```
border: 1px solid #EAEAEA
```
  .
- Border-radius must be crisp:
```
8px
```
  or
```
12px
```
  maximum.
- Internal padding must be generous (e.g.,
```
24px
```
  to
```
40px
```
  ).
Primary Call-To-Action (Buttons):
- Solid background
```
#111111
```
  , text
```
#FFFFFF
```
  .
- Slight border-radius (
```
4px
```
  to
```
6px
```
  ). No box-shadow.
- Hover state should be a subtle color shift to
```
#333333
```
  or a micro-scale
```
transform: scale(0.98)
```
  .
Tags & Status Badges:
- Pill-shaped (
```
border-radius: 9999px
```
  ), very small typography (
```
text-xs
```
  ), uppercase with wide tracking (
```
letter-spacing: 0.05em
```
  ).
- Background must use the defined Muted Pastels.
Accordions (FAQ):
- Strip all container boxes. Separate items only with a
```
border-bottom: 1px solid #EAEAEA
```
  .
- Use a clean, sharp
```
+
```
  and
```
-
```
  icon for the toggle state.
Keystroke Micro-UIs:
- Render shortcuts as physical keys using
```
<kbd>
```
  tags:
```
border: 1px solid #EAEAEA
```
  ,
```
border-radius: 4px
```
  ,
```
background: #F7F6F3
```
  , using the Monospace font.
Faux-OS Window Chrome:
- When mocking up software, wrap it in a minimalist container with a white top bar containing three small, light gray circles (replicating macOS window controls).

Imported: 6. Iconography & Imagery Directives

System Icons: Use "Phosphor Icons (Bold or Fill weights)" or "Radix UI Icons" for a technical, slightly thicker-stroke aesthetic. Standardize stroke width across all icons.
Illustrations: Monochromatic, rough continuous-line ink sketches on a white background, featuring a single offset geometric shape filled with a muted pastel color.
Photography: Use high-quality, desaturated images with a warm tone. Apply subtle overlays (
```
opacity: 0.04
```
warm grain) to blend photos into the monochrome palette. Never use oversaturated stock photos. Use reliable placeholders like
```
https://picsum.photos/seed/{context}/1200/800
```
when real assets are unavailable.
Hero & Section Backgrounds: Sections should not feel empty and flat. Use subtle full-width background imagery at very low opacity, soft radial light spots (
```
radial-gradient
```
with warm tones at
```
opacity: 0.03
```
), or minimal geometric line patterns to add depth without breaking the clean aesthetic.

Imported: 7. Subtle Motion & Micro-Animations

Motion should feel invisible — present but never distracting. The goal is quiet sophistication, not spectacle.

Scroll Entry: Elements fade in gently as they enter the viewport. Use

translateY(12px)

opacity: 0

resolving over

600ms

with

cubic-bezier(0.16, 1, 0.3, 1)

. Use

IntersectionObserver

, never

window.addEventListener('scroll')

Hover States: Cards lift with an ultra-subtle shadow shift (
```
box-shadow
```
transitioning from
```
0 0 0
```
to
```
0 2px 8px rgba(0,0,0,0.04)
```
over
```
200ms
```
). Buttons respond with
```
scale(0.98)
```
on
```
:active
```
.
Staggered Reveals: Lists and grid items enter with a cascade delay (
```
animation-delay: calc(var(--index) * 80ms)
```
). Never mount everything at once.
Background Ambient Motion: Optional. A single, very slow-moving radial gradient blob (
```
animation-duration: 20s+
```
,
```
opacity: 0.02-0.04
```
) drifting behind hero sections. Must be applied to a
```
position: fixed; pointer-events: none
```
layer. Never on scrolling containers.
Performance: Animate exclusively via
```
transform
```
and
```
opacity
```
. No layout-triggering properties (
```
top
```
,
```
left
```
,
```
width
```
,
```
height
```
). Use
```
will-change: transform
```
sparingly and only on actively animating elements.

Imported: 8. Execution Protocol

When tasked with writing frontend code (HTML, React, Tailwind, Vue) or designing a layout:

Establish the macro-whitespace first. Use massive vertical padding between sections (e.g.,
```
py-24
```
or
```
py-32
```
in Tailwind).
Constrain the main typography content width to
```
max-w-4xl
```
or
```
max-w-5xl
```
.
Apply the custom typographic hierarchy and monochromatic color variables immediately.
Ensure every card, divider, and border adheres strictly to the
```
1px solid #EAEAEA
```
rule.
Add scroll-entry animations to all major content blocks.
Ensure sections have visual depth through imagery, ambient gradients, or subtle textures — no empty flat backgrounds.
Provide code that reflects this high-end, uncluttered, editorial aesthetic natively without requiring manual adjustments.