원클릭으로 Manus에서 모든 스킬 실행

ui

스타5

포크0

업데이트2026년 7월 21일 23:37

Build or fix UI surfaces with a committed point of view: pages, components, layout, typography, motion feel, design review. Triggers: 設計, 做頁面, 做組件, 不好看, 很醜, 突兀, 不協調, 字體, 排版, 樣式, 前端, UI, 截圖, 很死, 死板, 生硬, 沒動效, 沒回饋感, 切換好硬, design, build a page/component, make it look good, typography, feels dead, stiff, lifeless, janky transition, this looks wrong. NOT for backend logic, browser-test verification (use `qa`), root-cause debugging of a broken render (use `debug`), or throwaway variant exploration before a direction is chosen (use `prototype`).

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

panda850819

panda850819/verbs

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

UI

You know design. You lack the craft numbers (references/craft.md) and the will to fight your own defaults. A CJK gut-feel complaint (很傻 / 突兀 / 丑 / 乱) is taste, not a bug — keep the word, name the defect, fix; do not send it to debug.

Fight your defaults. Your first draft is the AI-default — Inter, purple→blue gradient, centered hero with two CTAs, a grid of identical cards. Lock one named direction, then scan the first screen against the default-trap checklist in craft.md and replace what drifted.
Verify the render, not the source. Screenshot at 375px and 1280px in every shipped locale before "done". Wraps, overflow, and widows are invisible in code.
Build past the happy path. States (loading/empty/error) and the shippability layer a visual pass skips — 404, back-nav, form validation, skip-link, footer legal — are in craft.md.

Everything else — fonts, CJK type, OKLCH, CSS bans, motion, spacing, content rules — is craft you cannot derive: references/craft.md. Read it before writing CSS, not after.

이 저장소의 다른 Skills

같은 저장소

advisor

panda850819/verbs

Pull a decorrelated second opinion from a DIFFERENT model on a LOAD-BEARING judgment: a design fork, a pre-commit plan, an irreversible or outward-facing call. Reversible calls just decide. `--panel` = blind critics on a prepared plan. NOT code-diff review (review), NOT mechanical work for Codex (handover), NOT sharpening a fuzzy idea (grill).

2026-07-225

handover

panda850819/verbs

Bounded fresh-context handover for unfinished mechanical build units from an existing plan. A Claude Code or Codex orchestrator may start a fresh Claude or Codex worker and keeps ownership. - /handover [--agent claude|codex] [slug]: sync handoff through `scripts/verbs fresh-run`. - /handover --async [slug]: write a self-contained payload to docs/handoffs/ only; does not spawn Codex or touch git. Use when a locked, file-scoped task benefits from fresh conversation context. NOT for plan writing, closing finished work, PR/ship flow, or exploratory judgment-heavy work (pull a cross-model take with advisor instead).

2026-07-215

review

panda850819/verbs

Review a code diff before PR or on request. Uses a bounded low-risk fast path, scoped evidence, risk-triggered lenses, and cold-context escalation. NOT browser QA, prepared-plan critique, or external artifact trust checks.

2026-07-215

sprint

panda850819/verbs

Focused execution from a concrete outcome to SHIPPED, PAUSED, FAILED, or ABORTED_BY_USER. Adds acceptance-driven loops, bounded review, and delivery evidence beyond native coding behavior. Routes unclear requirements to grill, bugs to debug, UI work to ui, and completed delivery to ship. NOT for hypothetical or planning-only responses.

2026-07-215

harness-slim

panda850819/verbs

Audit and reduce a live multi-runtime agent harness after adoption. Use for installed skill/plugin parity, cold-start context, routing overlap, telemetry, or human-attention load. Produces a reversible proposal; it does not mutate the harness.

2026-07-205

grill

panda850819/verbs

Adversarial requirement discovery. Ask ONE question at a time, hunting for hidden requirements / unknown unknowns. Drills one angle at a time, then by default runs a structured close that writes a brief (+ executable plan) to docs/. Say "quick" or "don't write files" to stop at a chat-only log instead. Use when the user says "grill me on X", "interrogate this idea", "stress test this scope", "what am I missing", "draft a brief", "structured intake". Skip for tasks where scope is already concrete.

2026-07-195

name	ui
description	Build or fix UI surfaces with a committed point of view: pages, components, layout, typography, motion feel, design review. Triggers: 設計, 做頁面, 做組件, 不好看, 很醜, 突兀, 不協調, 字體, 排版, 樣式, 前端, UI, 截圖, 很死, 死板, 生硬, 沒動效, 沒回饋感, 切換好硬, design, build a page/component, make it look good, typography, feels dead, stiff, lifeless, janky transition, this looks wrong. NOT for backend logic, browser-test verification (use `qa`), root-cause debugging of a broken render (use `debug`), or throwaway variant exploration before a direction is chosen (use `prototype`).
user-invocable	true

UI

Fight your defaults. Your first draft is the AI-default — Inter, purple→blue gradient, centered hero with two CTAs, a grid of identical cards. Lock one named direction, then scan the first screen against the default-trap checklist in craft.md and replace what drifted.
Verify the render, not the source. Screenshot at 375px and 1280px in every shipped locale before "done". Wraps, overflow, and widows are invisible in code.
Build past the happy path. States (loading/empty/error) and the shippability layer a visual pass skips — 404, back-nav, form validation, skip-link, footer legal — are in craft.md.

Everything else — fonts, CJK type, OKLCH, CSS bans, motion, spacing, content rules — is craft you cannot derive: references/craft.md. Read it before writing CSS, not after.