UI/UX, 로고, 슬라이드, 이미지 생성 (7.3천건)
Select at most one eligible Proto UI work item and return a read-only proposal without changing GitHub or repository state. Use after pui-orient when requested contribution work is not yet bounded, or when a user asks what ready task fits the current capability and permission envelope. Do not post a claim, assign anyone, decide readiness, or invent work.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reproduce and repair a bounded Proto UI regression whose expected behavior and owning layer are already governed. Use this before domain implementation skills whenever work starts from a reproducible failure, including bug fixes, drift repairs, broken exports, Runtime failures, Adapter parity defects, Prototype defects, or public-projection regressions. Do not use when expected semantics or ownership is unresolved.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implement one governed Proto UI Adapter-profile realization slice. Use when target and runtime range, supported or omitted Module role, Host Capability fidelity, lifecycle translation, failure behavior, compatibility boundary, and evidence scope are fixed by current authority. Use pui-adapter-assess for research or readiness assessment and pui-regression first for a governed failing behavior.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Repair one independently verified Proto UI maintenance finding when governing authority or an explicit product decision fixes the expected result. Use for the bounded remediation and its evidence packet before independent review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Trace a Proto UI change through authoritative spec lifecycle, legacy explanation, dated context, implementation, executable evidence, package surfaces, and public projections. Use before deciding scope, changing behavior, reviewing a pull request, or investigating drift.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Establish Proto UI repository state, live contributor authority, Agent comprehension scope, task risk, and authorization before work begins. Use at the start of a development session, before autonomous task selection, after a material repository update, or when permission or assessment state may have changed.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Record one authorized non-remediation terminal outcome in Proto UI's autonomous-maintenance state. Use after a supported no-finding result, an independently rejected finding, or a blocked mission whose terminal evidence is complete.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Maintain an existing Proto UI Prototype or implement a governed Base or design-language component slice. Use for governed component behavior, anatomy, inheritance, exports, CLI registration, style projection, demos, or public preview work. Do not use to admit a new semantic subject or invent Base ownership from a component name.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Assess and route one bounded Proto UI dependency drift, advisory, or update question. Use to trace manifest and lockfile identity, consumer impact, compatibility evidence, provenance, update risk, and the exact next update or no-action transition. This leaf remains read-only.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply one exact-target Proto UI collaboration update through the ordinary governed primitive or an explicitly current-user connected-operation path for archive/ref recovery, Issue reopening/linking, additive carrier publication and service control. Do not manufacture review dispositions, merge, close, release or change privileged settings.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply one independently reviewable numeric Proto UI package-budget increase for an already accepted capability, using canonical cost evidence and existing development authorization. Use for standalone ceiling transactions, not feature implementation, measurement-policy changes, spending limits, publication or release.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Assess one bounded Proto UI Adapter question without changing repository or external state. Use for new-Adapter research, target compatibility, catalog readiness, reviewed Module support or omission evidence, Host Capability fidelity, lifecycle translation, dependency risk, or implementation readiness. Do not catalog, implement, repair, or approve the Adapter slice.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Access Claude Design and Claude artifacts when the request names Claude Design, a Claude artifact, Slides deck, or Design System artifact, or contains a claude.ai/design or claude.ai artifact URL or a .dc.html file. Use for creating and editing designs, decks, design systems, and artifact pages; assets, comments, artifact databases, sharing, versions, rendering, standalone-to-artifact migration, and code-to-design or design-to-code synchronization; otherwise stay inactive.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create or redesign product UI in an existing codebase, including a wireframe, substantive visual variations, and an interactive prototype. Use for requests about UI layout, visual direction, screens, flows, components, a landing page, dashboard, or making an interface feel polished. Do not use for backend work, system architecture, decks, or logic-only UI fixes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review or polish a product UI for accessibility, brand fidelity, hierarchy, rhythm, responsive behavior, themes, interaction states, and generic AI-template patterns. Use for visual audits, accessibility checks, UX polish, UI critique, or pre-ship design review. Do not use for generic code review, backend review, or API design.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply product-grounded visual quality constraints during user-visible UI changes. Use for layout, styling, content hierarchy, theming, responsive behavior, or interaction affordances. Stay inactive for logic-only changes that preserve the rendered interface.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Extract, document, or normalize a product UI design system from code, screenshots, or brand sources. Use for visual tokens, theme variables, typography, spacing, colors, radii, shadows, component inventories, variants, states, or building a reusable UI library. Do not use for software architecture, database schemas, or generic system design.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
MUST USE when designing ClickHouse architectures, selecting between ingestion or modeling patterns, or translating best practices into workload-specific system designs. Complements clickhouse-best-practices with decision frameworks and explicit provenance labels.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Extract comprehensive site specifications from simple descriptions. Use when analyzing a user's theme request to determine site type, audience, tone, layout requirements, and typography.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design and build reactive, type-safe, production-grade backends on Convex. Covers schema, queries/mutations/actions, indexes, auth, file storage, scheduling, real-time multiplayer, mobile backends, and LLM/agent workflows on Convex's one-platform stack.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design tools that agents can use effectively, including when to reduce tool complexity. Use when creating, optimizing, or reducing agent tool sets.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Facilitate design discussion — research context, clarify requirements, draft RFC/ADR
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write effective Architecture Decision Records. Use when: (1) Creating a new ADR, (2) Recording a design decision, (3) User mentions ADR, decision, trade-off, or alternatives
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.