'bloc' 검색 결과

Modular grid layout with card-like blocks, clear hierarchy, soft spacing, and subtle visual contrast for organized, scannable interfaces.

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

Notebook-collage weekly digest template — spiral-bound reporter's notebook aesthetic with cobalt tape, mint folder tab, binder clip, receipt block, ruled baseline grid; built for AI-product / team / design weekly digests delivered as a downloadable high-res page.

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

Use when an approved PRD roadmap must go to GitHub — 'publicar o roadmap no GitHub', 'criar o project e as issues do PRD', 'publish PRD roadmap' — handing over to pwdev-github (Project from a template, issues, sub-issues, blocked-by). Do NOT use for a single issue with the whole PRD (prd-export).

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

Cria, atualiza, comenta, fecha e reabre issues do GitHub e gerencia as tarefas de um GitHub Project — mover Status, editar campos, sub-issues e dependências "blocked by", inclusive em lote. Use quando o usuário disser "criar issue", "abrir uma issue", "fechar a issue #12", "reabrir", "comentar na issue", "atribuir para", "mover para Em andamento", "marcar como concluída", "bloqueada por", "sub-issue", "o que está bloqueando", "tarefas do project", "fechar as tasks da feature", ou citar #123 num repo GitHub. Não use para criar um Project novo (skill github-project) nem para publicar um roadmap inteiro (skill github-publish).

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

Use when the user wants a code review of an explicit range or set of files — correctness, security, performance, conventions, tests — with stable findings (CR-nnn, BLOCKER..INFO) and rule citations — 'revisar os últimos commits', 'code review da feature X', 'review base..HEAD'. Plans a REPORT-mode review (no code changes, no commit). Do NOT use to fix code (feat-feature / feat-quick), to write tests (feat-test) or for UI/UX design critique.

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

Use quando um roadmap pwdev-roadmap/1 (roadmap.json) precisar ir para o GitHub — 'publicar o roadmap', 'criar as issues do roadmap', 'publish roadmap.json' — com issues, sub-issues, milestones, blocked-by e campos do Project, com dry-run, idempotente e retomável. Não use para uma issue avulsa (github-issues).

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

Execute approved PWDEV Flow plans one atomic task at a time with test-first implementation, fresh verification, blocker handling, and durable evidence. Use after the plan gate is approved or for approved Flow correction tasks.

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

Design robust error handling strategies including try-catch blocks, custom error classes, error boundaries, graceful degradation, and comprehensive logging. Use when implementing exception handling, creating custom error types, setting up error boundaries in React, designing error response formats for APIs, implementing retry logic, handling async errors and promise rejections, logging errors for monitoring, creating user-friendly error messages, or building fault-tolerant systems that fail gracefully.

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

Restrict file edits to a specific directory for the session. Blocks Edit and Write outside the allowed path. Use when debugging to prevent accidentally "fixing" unrelated code, or when you want to scope changes to one module. Use when asked to "freeze", "restrict edits", "only edit this folder", or "lock down edits". (gstack)

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

Full safety mode: destructive command warnings + directory-scoped edits. Combines /careful (warns before rm -rf, DROP TABLE, force-push, etc.) with /freeze (blocks edits outside a specified directory). Use for maximum safety when touching prod or debugging live systems. Use when asked to "guard mode", "full safety", "lock it down", or "maximum safety". (gstack)

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

Orchestrates legacy AEM (6.x, AMS, on-prem) to AEM as a Cloud Service migration using BPA CSV or cache, CAM/MCP target discovery, and one-pattern-per-session workflow. Use for BPA/CAM findings, Cloud Service blockers, or fixes for scheduler, ResourceChangeListener, replication, EventListener, OSGi EventHandler, DAM AssetManager, HTL data-sly-test lint. OSGi configs → Cloud Manager — scan ui.config, .cfg.json, secrets, $[secret:]/$[env:] — agent follows references/osgi-cfg-json-cloud-manager.md when prompted. Transformation steps live in the best-practices skill—read it and the right references/ modules before editing code.

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

Search for existing content pages containing a specific block in AEM Edge Delivery Services. Reports URLs with occurrences and variants to help identify test content during development.

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

Generate structured HTML from authoring analysis for AEM Edge Delivery Services. Creates section structure, applies block tables, handles metadata, and manages images folder.

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

Identify section boundaries and content sequences within a scraped webpage for AEM Edge Delivery Services import. Performs two-level analysis (sections, then sequences per section) and surveys available blocks.

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

Diagnose and fix common AEM 6.5 LTS replication issues including blocked queues, connectivity failures, and content distribution problems

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

Analyze content sequences within a section and provide neutral descriptions for AEM Edge Delivery Services. Invoked per section during page import to identify breaking points between default content and blocks.

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

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).

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

Compare two versions of an AEM Edge Delivery Services page to identify what changed. Fetches preview vs live, or two different URLs, and produces a detailed content diff showing added, removed, and modified content, metadata, and blocks. Use when reviewing changes before publishing, auditing content modifications, or tracking content evolution.

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

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.

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

Evaluate learning progress, identify blockers, and adjust the learning plan

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

Teaches the AI to design like a high-end agency. Defines the exact fonts, spacing, shadows, card structures, and animations that make a website feel expensive. Blocks all the common defaults that make AI designs look cheap or generic.

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

Sets up an `## Agent skills` block in AGENTS.md/CLAUDE.md and `docs/agents/` so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc layout. Run before first use of `to-issues`, `to-prd`, `triage`, `diagnose`, `tdd`, `improve-codebase-architecture`, or `zoom-out` — or if those skills appear to be missing context about the issue tracker, triage labels, or domain docs.

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

Explain missing evidence or blocked guidance before proceeding.

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

Decompose an unknown quantity into 3-5 estimable factors and produce a defensible order-of-magnitude answer without needing precise data. Load when the user needs to size something without data — market size, resource requirements, effort estimates, user numbers, costs — or when a decision is blocked by "we don't know the numbers". Also triggers on "ballpark this", "rough estimate", "how big is this market", "how long would this take", "how many users", or when deep-thinking diagnoses a sizing/estimation frame. The goal is not precision — it is a defensible answer that enables a decision to be made. Based on Enrico Fermi's estimation method.

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