1.7万 件 ・ 関連度順
概要と使いどころ
Space/aerospace mission monitoring: dark command center, amber telemetry on navy, monospace precision. Functional clarity above all. For ops dashboards, build/deploy status, and real-time monitoring.
日本語の概要は準備中です。原文の説明を表示しています。
A playful, arcade-inspired interface for games — built on the VT323 pixel typeface, hard-edged 0px corners, chunky pill buttons that physically press into solid offset blocks
日本語の概要は準備中です。原文の説明を表示しています。
Narrative-driven design using visuals, copy, and interaction to guide users through engaging, emotionally resonant journeys.
日本語の概要は準備中です。原文の説明を表示しています。
A clean, product-oriented default. Use when the brief doesn't call for a specific mood — good for B2B tools, dashboards, and utility pages. Content-first, chrome-second.
日本語の概要は準備中です。原文の説明を表示しています。
Build premium scroll-driven web pages and product showcases inspired by high-end app, hardware, and product interaction patterns. Use for Raycast-like, Apple-like, NVIDIA-like, RTX/GPU, SaaS, AI browser, parallax, sticky scroll, pinned reveal, Three.js GLB model, Web Audio sound effect, responsive accessibility, and performance-safe frontend requests.
日本語の概要は準備中です。原文の説明を表示しています。
A radically minimal, blank-canvas interface built as a pure edge-to-edge surface, with almost no color and typography carrying the visual weight. Black serves as the only filled color, the only divider, and the sole surface tone cards.
日本語の概要は準備中です。原文の説明を表示しています。
Generate a single-file industrial-archive product landing page (Nordic museum aesthetic, hash-routed detail pages). Takes a natural-language description of one or more "exhibit-style" products (objects, tools, hardware, watches, kitchenware, lighting, audio, instruments, anything with a designed/forged/restrained quality); outputs ONE working .html file. Visitors see a black-framed cover that flips between exhibits, sidebar index, side meta column (material/origin/year/dimension), and click any exhibit → full detail page (giant italic title, spec table, hero image, lead + 3 prose paragraphs, gallery, prev/next). Runs in BOTH Claude Code (writes to ~/Desktop) and GLM / online chat (outputs HTML inline). Trigger: "做个工业风产品落地页", "做克制之物风格的展品页", "industrial-archive-gen ...", or when user drags this skill folder into chat asking for a product page in the Nordic-industrial archive style.
日本語の概要は準備中です。原文の説明を表示しています。
Team operations dashboard template — Linear/Asana-clean hybrid with sprint status hero, 4-segment progress bar, workstream cards, chronological activity stream with colored event badges, right-rail with today's schedule + team-presence + upcoming milestones. For team status snapshots, OKR reviews, "team this week" all-hands views.
日本語の概要は準備中です。原文の説明を表示しています。
截图 / UI / 工具流解释类社交卡 — 必须给截图一个"舞台"：可读裁切 + 标注层级 + 出现的理由。骨架：封面 + 大截图 + 3 个标注 / 截图裁切 + 放大细节 + 结论 / before-after 截图对 / 产品 UI 框 + 编号 callout / 3 步工作流。截图要大到手机能看清，箭头节制，加一个 takeaway 标题。触发："做个工具教程卡 / AI 工作流卡 / UI 解释卡 / 截图说明卡 / before-after 卡"。NOT 原图直接丢上画布，NOT 装饰性无关截图。
日本語の概要は準備中です。原文の説明を表示しています。
High-contrast, expressive style with creative typography and bold color choices for visually striking interfaces.
日本語の概要は準備中です。原文の説明を表示しています。
Soft, rounded 3D-like shapes mimicking malleable clay with playful, puffy elements and colorful surfaces.
日本語の概要は準備中です。原文の説明を表示しています。
Canonical UI/UX best practices ruleset with 14 sections and 70+ rules prioritized P0–P3. Use when implementing, reviewing, or auditing UI components. P0 rules are mandatory — violations are bugs. All rules reference tokens from ui-theme-reference.
日本語の概要は準備中です。原文の説明を表示しています。
Bidirectional Figma skill — read designs and write back to Figma. READ: extract tokens, map Vue/Reka UI components, translate Auto Layout to Tailwind. WRITE: push components, screens, and design tokens from code to Figma. Requires /figma:figma-use skill before every use_figma call.
日本語の概要は準備中です。原文の説明を表示しています。
Launch, inspect, or tear down an isolated fleet of ready SDD Composy tasks: one branch and Git worktree per member, a bound LOOP, cmux/tmux/headless presentation, no automatic merge. Use to run several ready tasks in parallel — 'rodar várias tarefas em paralelo', 'lançar o fleet', 'fleet status', 'tear down member X'. Do NOT use for a single task (sdd-execute, sdd-loop) or for merging without the explicit teardown token.
日本語の概要は準備中です。原文の説明を表示しています。
Canonical design token registry — colors, typography, spacing, sizing, border radius, shadows, z-index, breakpoints, motion, and focus tokens. Used by ui-best-practices rules and all agents that implement or review UI components. Includes CSS variable template for quick project setup.
日本語の概要は準備中です。原文の説明を表示しています。
Discover, build, verify, and optionally export (HTML, optional PDF) the evidence manifest of one SDD Composy task in evidence_required, routing it toward review_required. Use when acceptance evidence must be assembled or checked — 'juntar as evidências da task', 'gerar o relatório de evidências', 'verify the evidence manifest'. Do NOT use to run tests (sdd-qa), review code (sdd-review), or inspect the trace (sdd-trace).
日本語の概要は準備中です。原文の説明を表示しています。
Implement exactly one SDD Composy task in the ready state with dependency preflight, TDD RED evidence, allowed paths, real verification commands, and the guarded transition to qa_required. Use when a ready task should be executed — 'executar a TASK-003', 'implementar a próxima tarefa', 'run task 4'. Do NOT use for changes without an approved task (sdd-quick), for autonomous multi-stage correction (sdd-loop), or for QA, review, or verification.
日本語の概要は準備中です。原文の説明を表示しています。
Adversarial verification of one SDD Composy task in verify_required: reproduce every claim with fresh commands, build the truth table, refute stale evidence, and produce the verdict that gates complete. Use when review is done and the task claims to be finished — 'verificar a TASK-003', 'a task está pronta mesmo?', 'is this task really complete'. Do NOT use for QA, code review, or a general 'verify my work' outside an SDD task.
日本語の概要は準備中です。原文の説明を表示しています。
Review or refactor an existing SKILL.md and its bundled resources — a smaller always-loaded core, conditional references, preserved behavior, lean/guided consumer profiles, and an A/B protocol to compare a candidate with the previous version. Use when a skill repeats itself, loads references on every run, triggers too broadly or misses legitimate requests, or needs its efficiency measured across models. Do NOT use for writing a new skill from scratch, refactoring application code, translating a skill verbatim, or performing the target skill's own task.
日本語の概要は準備中です。原文の説明を表示しています。
Assess release readiness from applicable criteria, all current defects, risks, limitations, and recorded human decisions without approving release.
日本語の概要は準備中です。原文の説明を表示しています。
Initialize or inspect project-local PWDEV QA context without overwriting existing state or installing tools.
日本語の概要は準備中です。原文の説明を表示しています。
Use when an existing skill must be refactored to cut context and ambiguity without losing behavior, safety or fallbacks — 'refatorar a skill', 'reduzir esta SKILL.md', 'revisar skill com métricas' — with before/after metrics, preserved invariants and three review rounds.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants a small, well-bounded change done now without a plan file — a bugfix, config change, rename, doc update or simple refactor touching 1–5 files — 'corrigir rapidinho', 'quick fix no X', 'renomear Y'. Presents a mini-plan, implements after approval, verifies and commits. Do NOT use for more than 5 files, architectural decisions, migrations or new UI flows (use feat-feature / feat-backend / feat-frontend).
日本語の概要は準備中です。原文の説明を表示しています。
Adversarially verify an implementation against its objective, acceptance criteria, definition of done, and prohibitions using fresh evidence. Use for completion gates, release readiness, or independent verification after implementation and review.
日本語の概要は準備中です。原文の説明を表示しています。