design-system

スター561

フォーク103

更新日2026年6月29日 21:52

Make frontend output look intentional, not AI-generated. Use for any UI work — components, pages, layouts.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

Archive228

Archive228/loopkit

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Design System

Default AI UI is gray, centered, and timid. Don't ship that.

Type — one distinctive display face + one clean body face. Real scale (e.g. 12/14/16/20/28/40), not everything 16px.
Color — one strong accent, a real neutral ramp, intentional contrast. No 5 competing brand colors.
Space — a spacing scale (4/8/12/16/24/32...). Generous whitespace. Align to a grid.
Motion — purposeful only: feedback on action, transitions on state. No decorative bounce.
Hierarchy — one clear focal point per screen. Size, weight, and space do the work, not borders everywhere. Before done: would a senior designer ship this, or does it look like a default Tailwind template? If the latter, push the contrast and the type.

このリポジトリの他の Skills

同じリポジトリ

evaluator-calibration

Archive228/loopkit

Calibrate a reviewer persona with few-shot rubric examples so skepticism stays consistent and doesn't drift lenient over long runs.

2026-07-10561

feature-list-json

Archive228/loopkit

Enumerate every end-to-end feature as strict JSON entries with passes:false, editable-passes-only discipline, and priority order. The ledger fresh-context sessions read to know what's done, what's next, and what they're forbidden to touch.

2026-07-10561

harness-stripping

Archive228/loopkit

Systematically remove one harness component at a time and measure impact, killing scaffolding that no longer earns its complexity.

2026-07-10561

init-script-contract

Archive228/loopkit

Author idempotent init.sh under 120s plus sibling test.sh, stop.sh, reset.sh, serve.sh with fixed names the harness relies on.

2026-07-10561

planner-spec-expand

Archive228/loopkit

Expand a 1-4 sentence product brief into a full spec with a design language, acceptance surface, and an ordered feature list.

2026-07-10561

progress-reading-protocol

Archive228/loopkit

Run the fixed 6-step session-opening sequence — pwd, read progress, git log, count remaining features, init.sh, smoke-test last feature — before touching any new work. The orientation ritual that lets fresh-context sessions reconstruct project state in under a minute.

2026-07-10561

name	design-system
description	Make frontend output look intentional, not AI-generated. Use for any UI work — components, pages, layouts.
when_to_use	building UI, a component, a page, "make this look good"

Design System

Default AI UI is gray, centered, and timid. Don't ship that.

Type — one distinctive display face + one clean body face. Real scale (e.g. 12/14/16/20/28/40), not everything 16px.
Color — one strong accent, a real neutral ramp, intentional contrast. No 5 competing brand colors.
Space — a spacing scale (4/8/12/16/24/32...). Generous whitespace. Align to a grid.
Motion — purposeful only: feedback on action, transitions on state. No decorative bounce.
Hierarchy — one clear focal point per screen. Size, weight, and space do the work, not borders everywhere. Before done: would a senior designer ship this, or does it look like a default Tailwind template? If the latter, push the contrast and the type.