'guide' 검색 결과

Spatial depth design with isometric views, vanishing points, and layered elements that guide attention through 3D-like realism.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

小红书选辑 / anthology 横滚社交模板 — 8 张竖卡连续 auto-scroll snap loop，每张几何裁切 mask（拱 / 椭 / 半穹顶 / 斜）+ 宋体标题 + 一个 SVG 装饰符号 + 角部期号元数据。用于摄影系列 / 艺术指导 / mood reel / 品牌瞬间集 (6-10 帧)。触发："做个 anthology 选辑 / 横滚画廊 / mood reel / 摄影系列展 / 第 0X 辑封面集"。NOT 教程类（用 digital-eguide），NOT < 4 张系列，NOT 文字密集卡（横滚速度藏文字）。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guide users through the get started setup and Chrome DevTools demo.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guide users through browser automation setup using Chrome DevTools MCP only. Use when the user asks to set up browser automation, Chrome DevTools MCP, browser MCP, or runs the browser-setup command.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Documentation, standardization, and governance of the Vue + shadcn-vue design system. Use when creating component documentation, auditing consistency, defining naming conventions, or generating usage guides for the team.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Establish and enforce coding standards, best practices, and architectural patterns across the codebase using linters, formatters, and code review processes. Use when setting up ESLint/Prettier, configuring linting rules, creating code style guides, implementing pre-commit hooks, establishing naming conventions, enforcing TypeScript strict mode, maintaining consistency, conducting architecture reviews, or defining team coding standards.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guide for adding new OAuth-based integrations to Fabric. Use when implementing OAuth providers like Microsoft Teams, GitHub, Google Drive, Slack, or similar services that need OAuth 2.0 authentication for user data access.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build accessible web applications following WCAG 2.1/2.2 guidelines with proper semantic HTML, ARIA attributes, keyboard navigation, screen reader support, and inclusive design. Use when implementing ARIA labels and roles, ensuring keyboard navigation, supporting screen readers, providing text alternatives for images, managing focus, creating accessible forms, building inclusive UI components, testing with accessibility tools, meeting WCAG compliance levels, or designing for users with disabilities.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design consultation: understands your product, researches the landscape, proposes a complete design system (aesthetic, typography, color, layout, spacing, motion), and generates font+color preview pages. Creates DESIGN.md as your project's design source of truth. For existing sites, use /plan-design-review to infer the system instead. Use when asked to "design system", "brand guidelines", or "create DESIGN.md". Proactively suggest when starting a new project's UI with no existing design system or DESIGN.md. (gstack)

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guide for testing code changes in AEM Edge Delivery projects including blocks, scripts, and styles. Use this skill after making code changes and before opening a pull request to validate functionality. Covers unit testing for utilities and logic, browser testing with Playwright, linting, and guidance on what to test and how

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate comprehensive technical documentation for developers taking over an AEM Edge Delivery Services project. Analyzes codebase structure, custom implementations, design tokens, and produces a complete developer guide.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate comprehensive documentation for content authors taking over an AEM Edge Delivery Services project. Analyzes the project structure and produces a complete authoring guide with blocks, templates, configurations, and publishing workflows.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Initialize an Adobe App Builder project end-to-end without Developer Console UI clicks. Creates the Console project and workspace, subscribes APIs (including those needing a product profile), maps user intent to the right template, runs non-interactive `aio app init`, and guides post-init customization. Use whenever the user mentions creating an App Builder app, scaffolding a project, `aio app init`, setting up an Experience Cloud extension, adding actions or web assets, creating a Console project or workspace, adding APIs, or bootstrapping App Builder — even if they don't say "App Builder". Also for SPA templates, AEM extensions, API Mesh, Asset Compute workers, and MCP server projects. Also handles debugging init failures — template not found, `aio app init` hangs or times out, Node version mismatches, npm install failures, post-init build errors, `aio login` issues, `aio app run` showing nothing, or `aio console project create` / `workspace create` / `workspace api add` errors.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guides concurrency and async decisions in Rust. Use when encountering Send/Sync errors (E0277), choosing between threads vs async, designing shared state, or debugging deadlocks.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

50 core Rust coding conventions covering naming, data types, strings, error handling, memory, concurrency, async, and modern crate recommendations. Use when reviewing code style or setting up project conventions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guides Rust performance optimization. Use when profiling, benchmarking, reducing allocations, improving cache locality, choosing between rayon/async/threads, or applying SIMD/parallelism.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guides ownership, borrowing, and lifetime decisions in Rust. Use when encountering E0382, E0597, E0506, E0507, move errors, or when designing data ownership.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guides generic vs trait object decisions in Rust. Use when choosing between static and dynamic dispatch, designing traits, handling E0277/E0038, or deciding between enum and dyn Trait.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guides type-driven design in Rust. Use when encoding invariants in types, applying newtype pattern, implementing type state machines, using PhantomData, or making invalid states unrepresentable.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guides Rust error handling strategy. Use when choosing between Result/Option/panic, using anyhow vs thiserror, propagating errors with ?, or designing custom error types.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guidelines for upgrading Expo SDK versions and fixing dependency issues

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.