'eyes' 검색 결과

Diagnose, fix, or validate SwiftUI animation and scroll behavior by temporarily instrumenting views with MotionEyes, capturing console traces over time, and comparing motion data to user intent or test expectations. Use when users report bugs such as wrong direction, premature fade, timing or easing mismatch, unexpected movement, missing movement, incorrect relative movement between views, scroll jumps, scroll restoration drift, content-offset desynchronization, or when they want to turn MotionEyes traces into focused assertions. Prefer XcodeBuildMCP log capture first and fallback to CLI log streaming; remove only agent-added MotionEyes instrumentation after validation.

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

Pixel-based motion and UI change analysis from frame sequences or screenshots using computer vision and visual comparison. Use when `.transition` or visual effects are not observable via MotionEyes logs, when you only have screenshots/video, when you need regression diffs across builds, or when you need to summarize on-screen changes without instrumentation. Do not use when MotionEyes traces are available and you need precise timing/values; use `motioneyes-animation-debug` instead.

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

Create hand-drawn SVG illustration cards featuring expressive creatures or living objects that represent coding and design ideas. A supplied brush library supports uneven ink outlines, loose watercolor fills, large eyes, and consistent details across a set.

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

• Creating a loading illustration with a snail mascot
• Adding a character illustration to an error page
• Illustrating a coding concept for a blog header

Use the unprimed sub agent as a second set of eyes before accepting visual work — MANDATORY before declaring any user-reported visual bug fixed or claiming a visual change verified; primed eyes pass defects fresh eyes catch.

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

Run a targeted fresh-eyes blunder pass over code, specs, plans, reviews, closure gates, or skill edits. Use when asked to reread with fresh eyes, find obvious bugs, catch mistakes/oversights/omissions, check for embarrassing misses, or do a second independent pass before closure. Use it as the final falsification/check pass for another workflow, not as a substitute for implementation or verification.

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

Review and rewrite architecture decision records, documents that explain design choices, from a newcomer’s perspective. Identify missing context, buried decisions, and temporary details, then reorganize each document so future readers can follow the reasoning.

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

• Reviewing design decisions from a new team member’s perspective
• Making an ADR’s decision and reasoning easier to follow
• Removing temporary project context from long-lived records

AWT — AI-Powered E2E Testing (Beta) workflow skill. Use this skill when the user needs AI-powered E2E web testing — eyes and hands for AI coding tools. Declarative YAML scenarios, Playwright execution, visual matching (OpenCV + OCR), platform auto-detection (Flutter/React/Vue), learning DB. Install: npx skills add ksgisang/awt-skill --skill awt -g and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

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

AWT — AI-Powered E2E Testing (Beta) workflow skill. Use this skill when the user needs AI-powered E2E web testing — eyes and hands for AI coding tools. Declarative YAML scenarios, Playwright execution, visual matching (OpenCV + OCR), platform auto-detection (Flutter/React/Vue), learning DB. Install: npx skills add ksgisang/awt-skill --skill awt -g and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

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

Look at real hardware, screens, panels, and wiring on a desk or workbench through a camera, so Claude can SEE physical output that no unit test, log, or API can. Use whenever the user says "are you seeing this?", "olha isso", "look at this", "watch this", "can you see...", "check the camera", "look at the screen" / "look at the display", "is this wired right?", or "what's this part?"; asks to visually verify a rendered display, LCD, LED, or panel; wants a wiring, polarity, or voltage-rail check before power-on; or needs to confirm a font, layout, clipping, or on-screen value renders correctly instead of trusting green tests. Grabs the current camera frame(s) and reads them; supports a watch mode for an action in progress. Needs a snapshot-capable camera reachable over HTTP (Android IP Webcam app, Raspberry Pi camera-streamer, or any snapshot URL) set via CCE_CAM_URL.

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

API와 개발 도구 계획을 개발자의 관점에서 대화하며 검토합니다. 경쟁 제품과의 차이와 도입 과정의 장애물을 정리하고 목적에 맞게 개선점을 살펴봅니다.

• API나 SDK 계획 재검토
• 개발자의 초기 도입 장애물 확인
• 경쟁 제품과 개발자 경험 비교

Build reusable data packages for local 2D character animation. Define separate body parts, rotation points, layer order, movement limits, and views so a shared renderer can animate each character using its own rig data.

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

• Prepare a 2D character for local animation
• Define joint rotation points and movement limits
• Organize mouths, eyes, and props as separate parts

Create YAML test scenarios for web applications and run them in a real browser with Playwright. Use image matching and text recognition to check screens, then organize failure findings for investigation.

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

• Test a checkout flow in a real browser
• Check screens with image matching and text recognition
• Investigate browser test failures

Analyze local documents or public web pages and produce a Word report with source screenshots beside each factual claim. Yellow highlights identify the supporting passages so readers can visually check the analysis against the original.

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

• Review an analysis alongside its source passages
• Analyze Word documents or PDFs with visual evidence
• Turn a public web page analysis into a Word report

Process large email, document, and transcript archives by routing items to AI models according to their importance. Rule-based privacy checks run before model calls, while extracted information becomes linked knowledge pages with progress checkpoints.

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

• Extract useful information from large email archives
• Organize decisions and advice from meeting transcripts
• Route reports to suitable models by importance

Create original SVG illustrations with expressive cartoon characters, bold ink outlines, and a prominent prop. Use the transparent artwork for onboarding, empty states, success screens, blog headers, or marketing cards, with checks for consistent styling and believable hands.

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

• Illustrations for onboarding screens
• Character artwork for empty states and error pages
• Celebratory illustrations for success screens

Create flat SVG illustrations of long-legged people in design and coding scenes. Large black shapes, bright colors, and consistent poses give onboarding screens, error pages, and marketing cards a shared visual style.

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

• Illustrations for onboarding screens
• Character art for error pages
• Cards showing design and coding work

Create original SVG illustration cards featuring a cosy animal with computers, books, or mugs. A bright pink background, softly shaded shapes, and fine grain give the scenes a textured, painted feel for product pages and blog headers.

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

• Illustrating an empty state with a cosy animal
• Creating artwork for an onboarding step
• Making an autumn-themed blog header

Create original SVG illustration cards of people coding, thinking, or resting. The style combines thick, uneven black marker lines, offset mint shapes, and cream paper for onboarding screens, error pages, editorial headers, and marketing cards.

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

• Illustrate an empty state
• Add character art to onboarding
• Create an illustration for a 404 page

Hunt client-side DOM vulnerabilities — DOM Clobbering (overwrite JS globals via HTML injection), PostMessage hijacking (missing origin check), Service Worker abuse (intercept requests from same-origin script), CSS Injection/Exfiltration (attribute selectors → token char-by-char via OOB), client-side template injection, dangerouslySetInnerHTML. Grounded in named public research: Gareth Heyes / PortSwigger DOM-clobbering + DOM-Invader, Michał Bentkowski DOMPurify clobbering bypasses, jQuery htmlPrefilter XSS (CVE-2020-11022 / CVE-2020-11023), d0nut CSS-exfil research. Use when hunting DOM-XSS, client-side auth bypass, or token exfiltration without server-side interaction.

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

End-to-end website audit through ICP eyes. Builds synthetic personas (if they don't already exist), runs a structured scorecard review of the client's site, then runs a head-to-head competitive comparison against top competitors. Produces a single consolidated report with persona feedback, competitive positioning, and prioritized recommendations. The complete "how do our buyers actually experience our site vs the competition?" workflow.

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

Evaluate a website, landing page, content, or any online asset through the eyes of pre-built synthetic ICP personas. Loads personas from buyer-persona-generator output, then runs them against target URLs. Supports three modes: structured scorecard, freeform focus group, and head-to-head competitive comparison. Reusable — run against the same site after changes, or against new content anytime.

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

Final QC gate for a rendered 9:16 video ad, run before it is published. One script checks what a machine can decide — exact 1080x1920 size, a hook that moves and speaks in the first second, no frozen stretches, no dead air, no black frames, the brand's real logo on the end card (never a favicon, never a redrawn or wrong logo), end-card colours near the brand palette — and builds one contact sheet (frames with the TikTok/Reels UI safe zones shaded, beside the logo, product images and a font specimen) for the checks that need eyes — font, product likeness, product consistency across scenes, safe zones. A declared silent-text profile covers silent, text-led formats such as kinetic text (no audio track needed, short blank beats between text beats allowed within fixed bounds). Exit 0 PASS / 2 FAIL / 3 ERROR. Use on every finished video master before pinning it.

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

Review a business plan or product strategy through the eyes of a smart-money seed/Series-A investor. Asks the brutal questions: Is this fundable? What's the moat? What's the exit story? Outputs a verdict with one of four modes — SEED VIABLE / LATER ROUND ONLY / BOOTSTRAP-ONLY / UNFUNDABLE. Use when the user has a business plan and wants to know if it would survive an investor pitch. Triggered by: 'investor review', 'is this fundable', 'VC perspective', '投资人视角'.

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

Use when sculpting a realistic head, face, portrait, body or creature in ZBrush (anatomy, landmarks, proportions, "the face looks off", eyes, lips, jaw), adding skin, pores, wrinkles or reptile and dragon scales with alphas, Surface Noise, layers or morph targets, planning subdivision or HD Geometry for a film close-up, reprojecting detail, sculpting cloth folds or running Dynamics cloth, growing FiberMesh fur or hair, making horns, or judging a character sculpt the way a senior character artist would.

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