2.3천건 · 관련도순
Build documentation sites from Markdown with VitePress, then configure navigation, search, and themes. The skill also covers embedding Vue components, organizing multilingual content, and preparing deployment settings for supported hosting platforms.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Build soft, clay-like interface components using rounded corners and layered shadows. Includes CSS variables and examples for cards, buttons, inputs, and toggles, with guidance for dark mode, readable text contrast, and visible keyboard focus.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create and organize Claude Code plugins with guidance on configuration files, commands, agents, skills, hooks, and MCP servers. Learn where components belong, how automatic loading works, and how to reference files across different installation locations.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create working web pages, components, and application interfaces with a clear visual direction. The skill connects purpose and audience to typography, color, layout, and motion, producing cohesive designs implemented in frontend code.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Build AI chat interfaces with @ant-design/x, a React library of interface components. Get guidance on choosing and combining message bubbles, input boxes, conversation lists, attachments, and source citations, with API references and common implementation pitfalls.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create and organize Claude Code plugins with guidance on configuration files, commands, agents, skills, hooks, and MCP servers. Learn where components belong, how automatic loading works, and how to reference files across different installation locations.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Build React interfaces with coss components using documented imports, properties, and composition patterns. It helps select components, implement forms and overlays, preserve accessibility, and address migration mistakes when moving from shadcn/Radix to coss/Base UI.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Write Google Ads headlines, descriptions, and responsive search ad components. Create alternative messages for A/B testing, which compares ad versions, and develop copy ideas aimed at improving the click-through rate of existing ads.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Work through topology problems about connectedness, the property of a space having no separation into two nonempty open parts. It outlines proof strategies, path construction, and connected components, with command examples for symbolic calculation and proof tools.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Guide authorized mobile app security testing across stored data, certificate checks, exposed components, and compiled code analysis. The skill organizes scope, alternative investigation paths, reproduction evidence, and completion criteria for findings and unsuccessful tests.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Build and query Kusto graphs from natural language. Covers transient graphs (make-graph), persistent graph models/snapshots, pattern matching (graph-match), shortest paths, connected components, and graph-to-table export. Generates the edges-first thinking: define edges, define node lookups, union, make-graph. WHEN: make-graph, graph-match, graph-shortest-paths, graph-to-table, graph-mark-components, persistent graph, graph model, graph snapshot, build a graph from data, find paths between nodes, pattern matching in graph, connected components, transient graph, Kusto graph, KQL graph.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when building React components with TypeScript, typing hooks, handling events, or when React TypeScript, React 19, Server Components are mentioned. Covers type-safe patterns for React 18-19 including generic components, proper event typing, and routing integration (TanStack Router, React Router).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build and query Kusto graphs from natural language. Covers transient graphs (make-graph), persistent graph models/snapshots, pattern matching (graph-match), shortest paths, connected components, and graph-to-table export. Generates the edges-first thinking: define edges, define node lookups, union, make-graph. WHEN: make-graph, graph-match, graph-shortest-paths, graph-to-table, graph-mark-components, persistent graph, graph model, graph snapshot, build a graph from data, find paths between nodes, pattern matching in graph, connected components, transient graph, Kusto graph, KQL graph.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Search DigiKey for electronic components and download datasheets — primary source for prototype orders and the preferred API method for fetching datasheets. Find parts by keyword or MPN, check pricing/stock, download datasheets via API, analyze specifications. Sync and maintain a local datasheets directory — extract components from schematics, download missing datasheets, keep them up to date. Also supports batch MPN-list seeding (`--mpn-list`) for bulk workflows without a KiCad project. Use when the user asks about electronic components, part specs, datasheets, pricing, stock, footprints, or needs to download a datasheet — even without mentioning "DigiKey". Also for "sync datasheets", "download datasheets for my board/project", or mentions a datasheets directory. DigiKey is the default distributor for prototyping. For BOM workflows, see the bom skill.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Search DigiKey for electronic components and download datasheets — primary source for prototype orders and the preferred API method for fetching datasheets. Find parts by keyword or MPN, check pricing/stock, download datasheets via API, analyze specifications. Sync and maintain a local datasheets directory — extract components from schematics, download missing datasheets, keep them up to date. Also supports batch MPN-list seeding (`--mpn-list`) for bulk workflows without a KiCad project. Use when the user asks about electronic components, part specs, datasheets, pricing, stock, footprints, or needs to download a datasheet — even without mentioning "DigiKey". Also for "sync datasheets", "download datasheets for my board/project", or mentions a datasheets directory. DigiKey is the default distributor for prototyping. For BOM workflows, see the bom skill.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Cascade PCB components, add lumped elements, export Touchstone, and bridge to eye diagram or antenna array workflows. TRIGGER: user asks to cascade or connect multiple RF PCB components, add lumped R/L/C, export S-parameters to Touchstone, or combine PCB elements into a circuit. Invoke BEFORE writing pcbcascade or circuit code — cascade rules and port matching are non-obvious. SKIP: designing individual components (use the specific matlab-design-pcb-* skill), EM analysis of a single component (use matlab-analyze-em), material/stackup setup only (use matlab-manage-pcb-material), optimization (use matlab-optimize-pcb-design).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when creating a new TDesign React component. It provides a complete SOP for scaffolding components in the packages/components or packages/pro-components directories, including file structure, code patterns, and registration steps.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Share state between components that don't have a direct parent-child parameter relationship, using cascading values, scoped services with change events, or CascadingValueSource via DI. USE WHEN the user needs a CascadingParameter or CascadingValue that works across render mode boundaries, a shopping cart or notification count accessible from multiple pages, a theme or user preference cascaded app-wide, or when components in different parts of the tree must react when shared data changes. Also USE WHEN cascading values aren't reaching interactive children in per-page interactivity mode, or when the user needs to understand scoped vs singleton service lifetime for state on Blazor Server. DO NOT USE for direct parent-child parameter passing or EventCallback (see author-component), for persisting state across prerender-to-interactive transitions (see support-prerendering), or for service abstractions for data fetching in Auto/WebAssembly (see fetch-and-send-data).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Validate consistency across SEED Design component documentation layers (design guidelines in ./docs/content/docs/components, Rootage specs in ./packages/rootage/components, and React docs in ./docs/content/react/components). Use when auditing documentation completeness, before releases, or validating new component docs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then guards against regression. Use when asked to make a route's navigation instant (its static shell commits immediately), fix a route whose static shell isn't prerendered/served/prefetched, grow a route's static shell or fix its slow first paint, diagnose which Suspense boundary keeps a route out of its static shell, or write the instant() e2e guard for one. Requires Next.js 16.3+ with cacheComponents; directs an upgrade if older.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert Next.js performance optimization skill covering Core Web Vitals, image/font optimization, caching strategies, streaming, bundle optimization, and Server Components best practices. Use when optimizing Next.js applications for Core Web Vitals (LCP, INP, CLS), implementing next/image and next/font, configuring caching with unstable_cache and revalidateTag, converting Client Components to Server Components, implementing Suspense streaming, or analyzing and reducing bundle size. Supports Next.js 16 + React 19 patterns.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate React components with TypeScript, proper props, hooks, and accessibility. Use when creating new React components, UI elements, or refactoring existing components.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill for ANY work involving React, Next.js, TypeScript, or Tailwind in the browser layer. This includes building components and pages, but equally covers debugging and fixing frontend issues: CSS/Tailwind classes not applying, form validation behavior, hydration mismatches between server and client renders, styling bugs, layout shifts, and rendering problems. Also use for refactoring components (e.g., splitting Server vs Client Components), data fetching patterns, state management, bundle optimization, and frontend tooling. If the problem involves what users see or interact with in a web browser — whether building, fixing, or refactoring — use this skill. Not for backend APIs, databases, infrastructure, or DevOps.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Decide which plugin component type to use and how to organize components at scale. Covers the component lifecycle (discovery and activation phases), decision framework for choosing between commands, skills, agents, hooks, and MCP servers, and organization patterns for each component type. Use when asking "which component type should I use", "command vs skill vs agent", "when to use a hook vs MCP server", "component lifecycle", "how to organize plugin components", "plugin structure patterns", or "scale a plugin with many components".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.