'reference' 검색 결과

Self-tuning question sensitivity + developer psychographic for gstack (v1: observational). Review which AskUserQuestion prompts fire across gstack skills, set per-question preferences (never-ask / always-ask / ask-only-for-one-way), inspect the dual-track profile (what you declared vs what your behavior suggests), and enable/disable question tuning. Conversational interface — no CLI syntax required. Use when asked to "tune questions", "stop asking me that", "too many questions", "show my profile", "what questions have I been asked", "show my vibe", "developer profile", or "turn off question tuning". (gstack) Proactively suggest when the user says the same gstack question has come up before, or when they explicitly override a recommendation for the Nth time.

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

Reference for the Adobe AEM CLI (@adobe/aem-cli, formerly the helix-cli npm package; commands `aem up`, `aem import`, `aem content`) — installation, the local Edge Delivery dev server, .env / AEM_* configuration, HTTPS/TLS, proxy & certificate trust, content sync with da.live, and troubleshooting. Use when installing, running, or configuring the aem/hlx CLI, when `aem up` fails (port conflicts, cert errors, proxy 404s, pipeline vs. local-file confusion), or when migrating from the old helix-cli package. Do NOT use for da.live content-format rules or the DA Source API contract (use da-content); do NOT use for writing EDS block code (use content-driven-development).

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

[BETA] Expert assistance for the Adobe I/O CLI plugin `@adobe/aio-cli-plugin-aem-rde` — the `aio aem rde` / `aio aem:rde` command tree used to deploy, inspect, log-tail, snapshot, and troubleshoot AEM Rapid Development Environments (RDEs). Activate ONLY when the user explicitly references RDE concepts: 'AEM RDE', 'Rapid Development Environment', `aio aem rde`, `aio aem:rde`, `aem-rde`, RDE snapshots, RDE deploy/install, `rde install`, `rde inspect`, `rde status`, `rde history`, `rde reset`, the `@adobe/aio-cli-plugin-aem-rde` package, or Cloud Manager program/environment configuration that is specifically for an RDE environment. Do NOT activate on generic AEMaaCS phrases like 'deploy to AEM Cloud', 'push my bundle', 'tail the publish log', 'cloud sandbox', or unqualified 'dispatcher-config / frontend / env-config deployments' — those belong to Cloud Manager pipelines, not RDE. This skill is in beta. Verify all outputs before applying them to production projects.

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

The Block Collection and Block Party are repositories for existing AEM blocks, build tools, code snippets, integration patterns, plugins, and more. Use this skill anytime you are developing something and want to find a reference to use as a starting point.

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

Reference for producing Adobe Document Authoring (DA, da.live) and Edge Delivery Services (EDS, aka aem.live/Helix) compatible content. Use whenever generating HTML for DA upload, uploading media binaries to DA, publishing to aem.live, or driving the DA admin API (auth, source PUT, preview/publish). Covers block HTML format (canonical div-class form and accepted table alternate), section structure, page/section metadata, icons, links, images, default content, document skeleton constraints, block cell content normalization, the DA Source API contract, IMS auth, media storage, supported formats, Media Bus vs Content Bus delivery, and silent-failure rules that corrupt content.

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

AEM as a Cloud Service Java/OSGi best practices, guardrails, and legacy-to-cloud pattern transformations. Use for Cloud Service–correct bundles, deprecated APIs, schedulers, ResourceChangeListener, replication, Replicator, JCR observation (javax.jcr.observation.EventListener), OSGi Event Admin (org.osgi.service.event.EventHandler), DAM AssetManager, BPA-style fixes, HTL (Sightly) Cloud SDK lint warnings (data-sly-test redundant constant value comparison), or any time you need the detailed pattern reference modules under this skill.

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

Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.

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

Quick-reference card for all ponytail modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /ponytail-help, "ponytail help", "what ponytail commands", "how do I use ponytail".

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

Elite frontend image-direction skill for generating premium, conversion-aware website design references. CRITICAL OUTPUT RULE — generate ONE separate horizontal image FOR EVERY section. A landing page with 8 sections produces 8 images. Never compress multiple sections into one image. Enforces composition variety (not always left-text / right-image), background-image freedom, varied CTAs, varied hero scales (giant / mid / mini minimalist), narrative concept spine, second-read moments, and a single consistent palette across all images. Optimized for landing pages, marketing sites, and product comps that developers or coding models can accurately recreate.

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

參考圖解析 SKILL — 從截圖、Figma 連結或參考 PNG 中，分解出 proof draft（visualZones + componentIntents + spacingRecipe + contentSlots + unresolved notes）。USE FOR: 拿到新畫面設計稿或截圖時，作為 UI production pipeline 第 1 步。DO NOT USE FOR: 直接生成 normalized recipe 或 screen package（需先完成此步再進 family / MCQ 收斂）。

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

GPT Image 2 image generation workflow for this repo MCP server. Use for gpt-image-2, OpenAI image generation, concept art, UCUF reference exploration, UI icon, badge, card art, prompt drafting, transparent-background asset drafts, and saving generated images to local files under artifacts/ui-source or other workspace paths.

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

EDITOR PREVIEW SCREENSHOT SKILL — Capture the current Cocos Creator Editor window to a PNG file and inspect exactly what is already visible inside the Editor. USE FOR: visual symptoms when the user already has the target screen open in Cocos Editor / Editor Preview. DO NOT USE FOR: browser-driven QA, automatic browser target switching, reference-image comparison pipelines, compile errors, or pure log analysis. If the user wants browser screenshots, remind them to prepare the Browser Review environment and use cocos-preview-qa instead.

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

DALL-E 3 image generation workflow for this repo MCP server. Use for dalle3, DALL-E 3, OpenAI image generation, concept art, UCUF reference exploration, UI icon, badge, card art, prompt drafting, and saving generated images to local files under artifacts/ui-source or other workspace paths.

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

BROWSER REVIEW QA SKILL — Use the built-in browser/headless browser (puppeteer-core) to open a browser-runnable Cocos preview, switch preview targets, capture screenshots, and compare them with reference images. USE FOR: screen-driven QA only when the user has already prepared a Browser Review environment that can run in the browser (`http://localhost:7456`, LoadingScene/preview host/preview target wiring ready). DO NOT USE FOR: current Cocos Editor window screenshots, Editor Preview capture, compile errors, or pure log analysis. If the Browser Review environment is not ready, stop and remind the user to prepare it first.

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

Cross-Reference 進度掃描器 — 自動掃描 assets/scripts/**/*.ts 與 tests/*.ts，比對 cross-ref-code.md B-1 表格，產生進度差異報告。USE FOR: 進度掃描、cross-ref 更新。DO NOT USE FOR: 程式碼編輯、UI layout 調整。

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

DEBUGGING SKILL — Read and analyze Cocos Creator project.log for runtime errors, warnings, and stack traces. USE FOR: any bug report, crash, UI glitch, TypeError, null reference, missing asset, CompositePanel mount fail, ChildPanel route fail, or screen spec wiring error. Load this skill FIRST before any runtime debugging session. DO NOT USE FOR: compile errors (use get_errors tool instead).

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

UI Family 架構師 SKILL — 讀取 proof draft，為每個 visualZone 分配 structural family、themeStack 與 recipe seed，驗證 family 可用性，輸出 family-map 與 recipe 預填欄位。USE FOR: 在 ui-reference-decompose 完成後，進行 family 分派、family-map 產出與 recipe 選擇（UI pipeline Step 2）。DO NOT USE FOR: 直接產生 layout skeleton 或 asset 任務（需先完成此步）。

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

UI brief 生成 SKILL — 從 docs/keep.summary.md、正式規格書、task shard、cross-reference-index 與參考圖整理成可執行的 UI brief 或 task-ready brief。USE FOR: 新 UI 畫面開工前、既有畫面補 task shard 欄位、需要收斂 family / proof / normalized recipe / content_contract / smoke_route。DO NOT USE FOR: 直接修改 ui-spec JSON、直接做視覺 QA。

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

Pick a product archetype from a curated catalog before any UI gets built — the single biggest lever for not looking vibecoded. Routes the request to one of B2B-productivity, enterprise-trust, premium-consumer, playful-consumer, editorial, brutalist-distinctive, dev-tool, or marketing-landing, and returns a complete design philosophy: typography pair, color logic, motion curve, density, icon stance, reference sites, and a "feels like X" claim. Load when the user asks to pick an aesthetic, choose a design direction, decide what a UI should feel like, classify a product visually, says "what should this look like", "make this feel like [Linear/Stripe/Apple/Duolingo/...]", "give me a design direction", "what's the right aesthetic for this", or when frontend-design routes here during archetype selection. Sub-skill of frontend-design.

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

Design a self-improvement loop for a shipped product's AI agents — production traces feed evals, evals feed improvement proposals (prompts, playbooks, retrieval configs), and a human approval gate promotes changes with rollback. Technique-agnostic: chooses per project between ACE-style evolving playbooks, GEPA/MIPROv2 offline optimization, or simple eval-driven iteration via references/techniques.md. Load when the user asks to make my product's agents self-improving, learn from production traces, add a learning loop, evolve prompts or playbooks safely, promote agent improvements, or GEPA-style optimization. NOT harness-evolution (that improves the coding agent), NOT experimentation (product A/B tests), NOT agent-run-retro (dev-phase manual retros — this skill is the production-scale continuation).

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

Compress bloated project or global memory while preserving decisions, rationale, revisit triggers, provenance, and active user preferences. Load when memory exceeds budget, global memory is too large, session logs are repetitive, or before appending to an over-budget memory file.

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

Delete, redact, or archive project and global memories when the user says forget this, delete memory, remove that preference, do not remember, redact sensitive information, or retire stale memory.

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

Write a Product Soul document — the strategic north star that sits above any PRD or feature spec. Captures the product's reason for existing across five lenses: user, business, strategy, product-market fit, and GTM distribution. Load when the user asks to write a product soul, product strategy doc, product north star, product positioning doc, product one-pager, or "why we exist" document. Also triggers on "write the soul of this product", "product strategy document", "what is this product really about", "capture the product vision", or when an agent needs strategic context before making product decisions. The output is docs/product-soul.md — a living document that brainstorming, prd-writing, and inversion can reference for grounding.

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

Prisma ORM CLI commands reference covering init, generate, migrate, db, dev, complete, studio, validate, format, debug, and mcp. Use for ORM/database CLI workflows, not the Prisma Platform CLI. Triggers on "prisma init", "prisma generate", "prisma migrate", "prisma db", "prisma complete", "prisma studio", "prisma mcp".

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