978건 · 관련도순
Verify document self-containedness by having a context-free sub-agent explain its understanding. Use after writing specs, handoff docs, or any document that must be understood without conversation context.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Identify current session's task list and generate commands to start a new Claude session sharing the same tasks. Use when "handing off", "continuing later", "resuming tasks", or preparing work for next session.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Namespace router → context preservation and orientation skills, plus the focused-context loader `gz context <ADR-ID>`. Use to pick the context/handoff intent or to load one ADR's full context bundle (body + OBPI briefs + covering tests + governance rules) before invoking the matched concrete skill or piping payload to an agent harness.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Оставить короткую записку, чтобы следующий чат продолжил выбранную задачу.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate a context-rich briefing prompt for an external agent (Claude Code, Cursor, etc.)
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Print a ready-made /compact line in a canonical handoff format, so the operator pastes it as the next message and shrinks working memory without losing the thread. Use at the end of a long session. Triggers: "/cc", "compact", "finish via compact".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when designing, reviewing, implementing, or validating UI/UX and frontend experiences for web, mobile, responsive apps, design systems, Figma-to-code handoff, frontend stack/library selection, personas, UX mapping, information architecture, UI patterns, accessibility, interaction design, UX research, usability testing, theme/token application, or XR/spatial interfaces.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
別セッションのエージェントが会話文脈なしで読んで下流タスクに着手できる、自己完結な引き継ぎドキュメントを書く。要件定義・基本設計・引き継ぎ書・PRD・README など、別セッションのエージェントへ渡して作業を継続させる成果物を書く・仕上げるときに使う。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Register completed local agent work with Neondeck so Neon can watch PRs, show notes, and queue bounded review assistance when allowed.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guidance for Neondeck docs-drift fix handoffs when updating documentation from drift reports.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user starts a non-trivial coding/building task in Claude Code (e.g. "帮我做个 X", "help me build Y", "add feature Z", "搭一个 Z"). Layers an AI-native pedagogical coat over normal coding work — surfaces implicit assumptions in user intent, annotates non-trivial design decisions inline with brief concept-scaffolding for terms the user may not know, and replaces "should I run it?" handoffs with rigorous AI self-verification plus a clean list of what only the user can verify. Skip for pure Q&A, single-line edits, read-only investigation, or refactoring along an existing pattern.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Load when executing or resuming an approved plan from `dev/active/<task>/` or `.worktrees/<task>`, including phase commits, verification, PR creation, and handoff; not for plan authorship or review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Baut aus einem Chatverlauf oder aus bestehenden Automatisierungs-Prompts (z. B. eines anderen Agenten-Systems) eine selbstlaufende, user-neutrale Workflow-Automatisierung: einen wiederkehrenden Prompt bzw. Automations-Skill für Cron/Schedule/Loop. Alias: automations-extractor. Nutze diesen Skill bei „mach daraus eine Automatisierung", „das soll regelmäßig/nächtlich laufen", „extrahiere Workflows aus diesen Chatverläufen/Automationen", „Automation aus dieser Session bauen", oder bei `/workflow-extract`. Ergänzt fehlende Automations-Bausteine (Rotations-Auswahl, Check-Registry, Idempotenz, Log-Hygiene, Freigabe-Gate, Eskalations-Handoff, Monitor-Meldedisziplin) systematisch. Enthält auch den Fleet-Audit-Modus: bestehende Automations-Flotten auf Silent-Failures, Redundanz, Drift und Lücken prüfen („prüfe meine Automatisierungen/Scheduled Tasks/Cron-Jobs"). Soll stattdessen ein abrufbarer Skill (Fähigkeit auf Zuruf) entstehen, den Schwester-Skill skill-extractor nutzen.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implements and reviews mobile data privacy across Flutter, Android, iOS, React Native and Kotlin Multiplatform. Use for consent withdrawal, SDK collection controls, account and data deletion, retention, privacy manifests or store data disclosures. Covers the app and backend handoff; security exploits belong to mobile-security.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Agentic design-to-build pipeline that turns a Figma design into a built WordPress site using the Figma MCP server (read side) and the Elementor MCP server (write side) attached as MCP Apps on an NV oOS assistant. Covers the 7-stage pipeline (Scope → Read → Plan → Tokenize → Build → Verify → Handoff), the normative stage rules (get_design_context first, tokenize before build, drafts only, never publish, Figma read-only), the build-manifest contract (schema + example in reference/build-manifest.md), the design-file contract (frame/section/variable naming in reference/design-file-contract.md), assistant wiring (figma + elementor MCP Apps, OAuth + application passwords, host allowlist), safety rules, and troubleshooting. Use when asked to build or create a site, page, or landing page from a Figma design, to wire Figma MCP or Elementor MCP for design-to-build work, to approve or produce a build manifest, or to debug a failed design-to-build run.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a user provides a GitHub URL and the planner needs to converge that repo plus the user's goal into a concrete project blueprint for later execution. This skill handles GitHub-input project intake, Phase 1 intent convergence, and downstream project handoff structure. It does not generate teaching material packages.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user asks to "plan my site structure", "design the page hierarchy / navigation / URL taxonomy", "fix internal linking", or "find orphan pages"; runs two modes — architecture (hierarchy, nav, URL patterns, hub/spoke clusters, Mermaid site maps) and linking (link graph, authority flow, anchor text, orphan disposition, source/target/anchor plan) — and outputs a structure score /100 plus a handoff summary. Not for external backlinks — use offsite-signal-analyzer; not for XML sitemap or indexation issues — use technical-seo-checker. 网站架构/信息架构/站点地图/内链优化
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design revenue operations across lifecycle stages, lead/account routing, scoring, handoffs, pipeline definitions, CRM hygiene and SLA measurement.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user asks to "keep the launch momentum going after launch week", "plan a changelog / release-notes cadence as GTM", or "is this update worth a relaunch"; produces a T+1→T+30 momentum plan — a launch-moment calendar (milestone / shipped-loop / badge moments only), announcement-tier routing (major = full-channel, medium = targeted, minor = changelog-only), a relaunch legitimacy call, spike-to-owned handoff briefs, and the next Tier-1 moment with launch-stacking spacing. Not for the 30-day content-reuse map or paid amplification execution — use content-amplifier; not for planning the next launch end to end — use launch-tier-planner. 抗第二周断崖/changelog-as-GTM/relaunch/下一发布时刻
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user asks to "plan how our narrative lands on every surface", "write per-surface message-match specs", or "brief each creative builder from the canon"; maps the narrative-registry canon onto every flagship surface (homepage, pricing, store listing, sales deck, social bio, docs, email) as a per-surface message-match spec — what claim, pillar, proof, and objection reframe each surface must carry — and cuts a handoff brief to each discipline's creative builder (content-writer, ad-creative-builder, email-creative-builder, social-creative-builder, message-house-builder), so the same story lands consistently everywhere. Not for writing the finished surface copy — use each discipline creative builder; not for the tier-scoped launch asset manifest — use launch-asset-packager; not for scoring cross-surface consistency — use narrative-quality-auditor; not for claim adjudication — use offer-claims-registry. 叙事落地/逐面消息一致/创意交接简报/画布传导
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design de produto nivel Apple — sistemas visuais, UX flows, acessibilidade, linguagem visual proprietaria, design tokens, prototipagem e handoff. Cobre Figma, design systems, tipografia, cor, espacamento, motion design e principios de design cognitivo.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Distill an already-built or near-launch product into one incisive brand kernel — the "reveal" already hiding in its name, story, or the product itself — then build the name, voice, visual identity, and a developer-ready handoff kit around it. This is LATE-STAGE branding: use it when there is a real, thought-through product that is about to launch, or already live but not explained in a way people grasp in an instant. Use whenever the user wants to name or rename a product, find a tagline or slogan, create a brand identity / brand kit / style guide / design system, design a logo, wordmark, palette, or type system, mock up a homepage for a launch, or hand brand assets to a coding agent (Claude Code, Codex, Cursor). Trigger even when the user only says their product needs to "land" or "feel like" something, or that they can't explain it simply yet. Do NOT use for half-baked, pre-product ideas with nothing to excavate — this skill extracts a kernel that already exists; it does not invent one from a blank canvas.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
TidyFactor Design track — code-native UI design lifecycle engine (Figma alternative). Supports all 7 stages of UI design (Discovery, Foundation, Architecture, Components, Motion, Quality, Delivery) with zero per-page CSS/JS and zero build step. Pluggable CSS foundations (Native, Tailwind utility-first, daisyUI, Hybrid, shadcn, Pico, Bootstrap, Alpine) and full Arabic/RTL support (El Messiri/Tajawal, never Amiri above 24px). Trigger on commands "study", "brief", "init", "brand", "typography", "school", "tokens", "palette", "assets", "layout", "nav-footer", "components", "page", "dashboard", "motion", "states", "flow", "i18n", "perf", "audit", "clone", "retrofit", "handoff", "deploy", or requests like "build a design system", "UI design lifecycle", "prototype this website", "Figma alternative", "نموذج أولي تفاعلي", "صمّم لوحة تحكم".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Coordinate FriendlyBet company-level strategy, CEO handoff, department orchestration, HR/agent-quality escalation, operating-model decisions, multi-agent synthesis, roadmap tradeoffs, decision rights, quality gates, and updates to the virtual company system. Use when Eyal asks to involve the company, CEO, leadership, strategy, operations, several departments, or named executive agents such as Strategy Director, Chief of Staff, or Operating System Lead.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.