117건 · 관련도순
Upload preview images and videos for a Remotion Element to remotion.media, then update the corresponding URLs. The skill also handles local asset cleanup according to whether previews come from fresh renders or committed submissions.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create disposable OpenWork previews for hands-on review of app and Den changes. Choose local, Daytona, or Freestyle environments as supported, reopen existing previews, update supported frontend changes while preserving progress, and reset or stop environments when finished.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Guides a pull request from local checks through a recorded demo, GitHub upload, merge, and development environment verification. Explains the project's test and preview labels, attachment requirements, and rules for keeping the pull request current.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Use this skill whenever the user wants to see how their branch will look on the live Gaia website before merging — "preview this branch", "show me what this looks like", "deploy a preview", "trigger a design preview", "can I see the site with these changes", "preview the skill profile", "check how this renders on the site", "spin up a preview deployment". This skill dispatches a Cloudflare Worker preview deployment for the current branch via GitHub Actions — no local build tooling required. Ideal for containerized environments, design reviews, and confirming that newly curated skills or profile pages render correctly before a PR is merged to main. The preview does NOT regenerate docs; it deploys `docs/` from the branch as-is. If your change depends on regenerated Class S artifacts, run `gaia dev docs` and commit those first — the preview then reflects them.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Launch the Remotion documentation site locally and open it in the Codex in-app browser. The workflow installs dependencies, builds the project, starts Docusaurus, and reports the actual preview URL and server status.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Manage Claude Code Viewer (CCV): preview in-progress CCV changes on ccv-preview, register HTML artifacts, download files, or schedule jobs via CCV local API. Use when user asks for CCV preview, ccv-preview, browser visual QA, UI/UX validation, CCV artifacts, CCV file download, or CCV scheduler jobs. Treat preview/プレビュー as the CCV app preview service first; use artifacts only when the user explicitly asks for artifact/dashboard/report HTML. Do NOT use for generic web app previews outside CCV, production deployment, Cloudflare config, or Anthropic remote triggers.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Inspect and test web pages through a browser automation command-line tool. Navigate, click, enter text, capture screenshots, and extract page details, with a focus on checking local OpenDesign previews and reviewing web app quality.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Browse pages, click controls, fill fields, and inspect screenshots or console messages through Superset's browser pane. Use it to preview a running web app, check interface behavior, and work through browser tasks in a visible session.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Package a finished local web project for GitHub with a tailored README and a preview from the running project. Audit files before pushing, publish compatible projects through GitHub Pages, and verify the repository and live demo.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guide HyperFrames video projects from setup and component selection through checks, previews, and rendering. Use command-line tools to inspect timelines, diagnose failures, compare frames, and choose local, batch, or cloud rendering for the finished composition.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Capture a public webpage through Latchshot and save a local PNG, JPEG, or PDF. Use viewport images, full-page screenshots, or website thumbnails for reports, visual checks, archives, and social previews.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Generate Preline theme CSS from a brand color or a desired mood using bundled local scripts. Preview output before saving, create light and dark themes, and review or fix theme tokens, the named values that define styling.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Install a .NET SDK locally for safe preview testing, specific-version pinning, or reproducible team setups — without modifying the system-wide installation. USE FOR: trying .NET previews safely, testing specific SDK versions, installing MAUI or other workloads on a preview, updating or replacing an existing local SDK, creating reproducible team/CI install scripts, configuring global.json paths. DO NOT USE FOR: system-wide SDK installs, .NET hosts older than 10, runtime-only installs, or projects not using SDK-style commands.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Start a local preview of the app for the user and share an HTTPS link to it. Use when asked for a local preview, to "run it", "spin it up", "show me", or for a link to try a change on this machine (not Cursor Cloud; that is the run-app skill).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Install a .NET SDK locally for safe preview testing, specific-version pinning, or reproducible team setups — without modifying the system-wide installation. USE FOR: trying .NET previews safely, testing specific SDK versions, installing MAUI or other workloads on a preview, updating or replacing an existing local SDK, creating reproducible team/CI install scripts, configuring global.json paths. DO NOT USE FOR: system-wide SDK installs, .NET hosts older than 10, runtime-only installs, or projects not using SDK-style commands.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
AI 에이전트의 작업 로그를 GitHub PR이나 이슈에 첨부할 기록으로 정리합니다. 관련 내용을 추리고 민감한 정보를 제거해 미리 보며, 별도 승인을 받아 게시합니다.
Review local character animations before sharing previews or final renders. Check structured design data, asset files, browser errors, sampled motion frames, and MP4 metadata, then classify the result as pass, revise, or fail.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Inspect and transform local DICOM medical imaging files, including metadata, image frames, and compression formats. Generate technical inventories and preview images, check installed codecs, and review pseudonymized derivatives without treating those checks as proof of de-identification.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Launch and troubleshoot the actual AO desktop app to inspect interface changes with local data. Supports reviewing combined pull request branches and diagnosing lingering Electron processes, port conflicts, and mismatches in the app’s preload bridge.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Set up iterative design-to-code development loop with Anima SDK. Use when rapidly iterating on Figma-to-code output, comparing framework outputs, or building a local preview server for generated components. Trigger with: "anima local dev", "anima dev loop", "anima preview", "anima iteration".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Previews, provisions, or diagnoses a uv-managed local Python .venv with `databricks environments setup-local`. Use when the user wants to set up or fix one for Databricks Connect, cluster or serverless compute, `--job-task`, or a bundle target, or when setup-local fails.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Product marketing and go-to-market strategy for B2B SaaS launches and positioning. Use this skill when planning a product launch, developing positioning and messaging, analyzing competitive landscape, building customer advocacy programs, designing a customer referral program (who may accept the reward, how the introduction is made), designing a win/loss interview program, working out why we lose deals, designing GTM strategy, creating category positioning, planning analyst briefings, or deciding which country to expand into and how far to localize. Also use it for an early-stage startup where the founder is still doing the selling — running founder-led sales, setting up a design-partner program, judging whether you have product-market fit, deciding what not to do yet, deciding when to hire the first AE or first marketer, and moving upmarket to larger buyers. Also use it when your company has just acquired another (or is about to), to plan the marketing integration: what you may and may not do between signing and close, the first letter to the acquired customers, whether to keep, endorse, fold in or retire the acquired brand, merging the two marketing databases without mailing people who opted out, when to start cross-selling, and announcing a product sunset. Also use it to design a demand-generation campaign and the channel plan it runs on: one campaign with one job, the offer for buyers who are and are not in market, what each channel is for, the kill and scale rules set before launch, the follow-up sales agrees to, the yearly calendar of always-on programs and tentpole campaigns, and which channels to keep, test or stop. Also use it for brand marketing and demand creation — how much to spend on brand versus performance, what to measure when a brand campaign produces no conversion event, and how to answer "we cannot attribute it". Also triggers on: founder-led sales, founder-led GTM, design partners, design partner agreement, first customers, first 10 customers, do we have product-market fit, PMF, Sean Ellis test, very disappointed survey, pre-seed, seed stage, when to hire our first AE, first sales hire, first marketing hire, moving upmarket, going upmarket, enterprise readiness, first enterprise deal, what do enterprise buyers need before they sign, positioning, product launch, beta program, early access program, design partners, private preview, public preview, general availability, GA launch, when can we call it GA, can sales sell a beta feature, selling the roadmap, launch tier, competitive intelligence, messaging, customer advocacy, win/loss analysis, win/loss interviews, why we lose deals, closed-lost analysis, loss reason, close-reason field, competitive displacement, displace an incumbent, rip and replace, competitive takeout, switch from a competitor, win deals from a competitor, incumbent contract, renewal window, auto-renewal notice period, switching costs, EU Data Act, cloud switching rights, why do we lose to no decision, GTM, category design, ideal customer profile, ICP, what is our real ICP, who actually buys from us, refresh our ICP from closed-won deals, ICP refresh before planning, analyst briefing, G2 review, international expansion, market entry, expand into Europe, which country should we launch in next, localization, translate our site, in-country go-to-market, regional GTM, is cold email legal in Germany, brand marketing, brand awareness, brand vs performance, brand versus demand gen, demand creation, demand capture, 95-5 rule, out of market buyers, category entry points, distinctive brand assets, mental availability, brand tracking, brand health, brand lift, share of search, how do we measure brand, justify brand spend, brand budget. Also triggers on public-sector marketing: sell to government, government marketing, public sector go-to-market, federal marketing, state and local government, SLED, FedRAMP, FedRAMP marketing claims, can we say FedRAMP ready, GovRAMP, StateRAMP, VPAT, accessibility confor
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Operational guide for the NV oOS WordPress Playground demo blueprints — the Content Graph "Project Asteria" demo, the Complete bundle × local Ollama demo, and the Docs Hub wp.org Live Preview demo. Covers blueprint authoring patterns (embedded runPHP seed snippets, generator scripts, preview-safe vs standalone split), CORS hosting gotchas, the CI Plugin Check gate (built-ZIP scan, rsync/distignore sync, ABSPATH guards), Playground worker crash modes (PHP-side localhost fetches, inline-script UTF-8, SPA SSE-hold mount bursts, crash-truncation SyntaxErrors), local Ollama integration (OLLAMA_ORIGINS, browser policy matrix, plugin settings + assistant meta keys), and the CLI validation harness (probe builder, mount quirks, server-mode 502 boot). Use when extending or debugging the demo blueprints, adding a new Playground demo, or triaging a crashing Playground instance.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.