Menu
Build UI with craft and consistency. For interface design (dashboards, apps, tools) — not marketing sites.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs.
Django testing strategies with pytest-django, TDD methodology, factory_boy, mocking, coverage, and testing Django REST Framework APIs.
Spring Security best practices for authn/authz, validation, CSRF, secrets, headers, rate limiting, and dependency security in Java Spring Boot services.
为网页应用快速接入 OpenClaw 通道配置，自动输出可直接复制的 Webhook URL 与 Token。用于用户说“帮我配置 OpenClaw 通道”“给我 Webhook 和 Token”“一键生成接入参数”“OpenClaw 对话接入配置”这类场景，支持外部网页与本地网页两种模式，减少手工查配置和复制错误。
基于 AI 自动生成高质量 PPT 图片和视频，支持智能转场和交互式播放。
Enforce TDD workflow for Kotlin. Write Kotest tests first, then implement. Verify 80%+ coverage with Kover.
Baseado na classificação ocupacional SOC
| name | source-command-init |
| description | Build UI with craft and consistency. For interface design (dashboards, apps, tools) — not marketing sites. |
Use this skill when the user asks to run the migrated source command init.
Before writing any code, read these files completely:
~/.Codex/skills/interface-design/SKILL.md — the foundation, principles, and checks~/.Codex/skills/interface-design/references/principles.md — detailed craft including subtle layering~/.Codex/skills/interface-design/references/example.md — how decisions translate to codeDo not skip this. The craft knowledge is in these files.
Scope: Dashboards, apps, tools, admin panels. Not landing pages or marketing sites.
Before touching code, answer these out loud:
Who is this human? Not "users." Where are they? What's on their mind? A teacher at 7am with coffee is not a developer debugging at midnight.
What must they accomplish? Not "use the dashboard." The verb. Grade submissions. Find the broken deployment. Approve the payment.
What should this feel like? In words that mean something. "Clean" means nothing. Warm like a notebook? Cold like a terminal? Dense like a trading floor?
If you cannot answer these with specifics, stop and ask the user. Do not guess. Do not default.
State the intent AND the technical approach:
Intent: [who, what they need to do, how it should feel]
Palette: [foundation + accent — and WHY these colors fit the product's world]
Depth: [borders / subtle shadows / layered — and WHY]
Surfaces: [your elevation scale — and WHY this temperature]
Typography: [your typeface choice — and WHY it fits the intent]
Spacing: [your base unit]
Every choice must be explainable. If your answer is "it's common" or "it works" — you haven't chosen. You've defaulted.
The test: If another AI given a similar prompt would produce the same output, you have failed. The interface must emerge from THIS user, THIS problem, THIS intent.
Be invisible. Don't announce modes or narrate process.
Never say: "I'm in ESTABLISH MODE", "Let me check system.md..."
Instead: Jump into work. State suggestions with reasoning.
Lead with your exploration and recommendation, then confirm:
"Domain: [concepts from this product's world]
Color world: [colors that exist in this domain]
Signature: [one element unique to this product]
Direction: [approach that connects to the above]"
[AskUserQuestion: "Does that direction feel right?"]
.interface-design/system.md existsThe skill files contain the craft principles. system.md contains project-specific decisions. You need both.
Offer to save when you finish building UI:
"Want me to save these patterns to .interface-design/system.md?"
Always offer — new patterns should be captured whether system.md exists or not.