cxc-qa
無料Use for manual web, TUI, CLI, API and desktop QA. Triggers: smoke test, visual QA, screenshot check, CJK clipping, 수동 QA, 실제로 되는지 확인, 동작 확인, 직접 돌려봐.
日本語の概要は準備中です。原文の説明を表示しています。
1,276 件 ・ 関連度順
概要と使いどころ
Use for manual web, TUI, CLI, API and desktop QA. Triggers: smoke test, visual QA, screenshot check, CJK clipping, 수동 QA, 실제로 되는지 확인, 동작 확인, 직접 돌려봐.
日本語の概要は準備中です。原文の説明を表示しています。
AI browser automation via CDP. Use when you need to control a browser, navigate pages, click elements, fill forms, extract content, or take screenshots.
日本語の概要は準備中です。原文の説明を表示しています。
Design focused empty states for zero-data, no-results, permission, and error situations with clear value framing, strong CTAs, and less dead chrome. Use when the user mentions blank pages, zero-data screens, no results, permission states, or dead controls—not broader onboarding strategy.
日本語の概要は準備中です。原文の説明を表示しています。
Identify the source of an image or video frame — TV show episode, movie scene, geographic location, or original publication. This skill should be used when the user asks to identify where an image is from, trace a screenshot back to its source, geolocate a photo, find what show or movie a frame is from, or do a reverse image search. Chains Google Vision, Picarta geolocation, and Gemini in parallel with graceful degradation. Triggers on: reverse image search, identify source, what show is this, where was this taken, trace image, identify video, what movie, which episode, geolocate photo, image source.
日本語の概要は準備中です。原文の説明を表示しています。
Desktop GUI automation via OpenInterpreter — mouse, keyboard, screenshot, and OCR control for native macOS/Linux applications. Three modes: Library (Claude reasons, OI executes), OS subprocess (full autonomous computer use), and Local agent (Ollama, offline). This skill should be used when interacting with desktop apps that have no CLI or API, automating GUI workflows, reading screen content via OCR, or controlling mouse/keyboard.
日本語の概要は準備中です。原文の説明を表示しています。
Plan and record evidence-backed LLM and AI-search citation checks across approved assistant/search surfaces with timestamped queries, locales, modes, cited URLs, snippets, screenshots or transcripts, and caveats. Use this skill when the user asks whether ChatGPT, Perplexity, Claude, Gemini, Copilot, or another assistant cites a target site, but do not claim citation without direct evidence.
日本語の概要は準備中です。原文の説明を表示しています。
Standardized commit + PR workflow for tbh-meter. Analyzes changes, makes conventional commits (subjects feed the release changelog), and for any overlay/UI change captures a seed-driven screenshot to attach to the PR. Use when asked to commit, open a PR, or "commit this".
日本語の概要は準備中です。原文の説明を表示しています。
Boot and drive the tbh-meter app + reader locally to see a change working — what runs on macOS (UI only; the reader is win32-only) and how to feed the overlay/list fake data. Use when asked to run/start the meter, verify a change in the running app, screenshot the overlay, or reproduce a bug locally.
日本語の概要は準備中です。原文の説明を表示しています。
Route a 50-minute live iOS launch sprint across the lightweight requirements, Claude Design handoff, SwiftUI implementation, landing page, ASO, Simulator screenshot, promo-video, and privacy-scan skills bundled in this plugin. Use as the main entry point when the whole talk workflow should be planned or executed.
日本語の概要は準備中です。原文の説明を表示しています。
Timebox and coordinate a live three-lane iOS launch sprint from audience idea to tested SwiftUI app, landing page, ASO copy, screenshots, promo video, and privacy report. Use for a 50-minute talk, demo rehearsal, fallback drill, or any request to finish a tiny local iOS product under a hard deadline.
日本語の概要は準備中です。原文の説明を表示しています。
Render a deterministic 15-second vertical promo video from real Simulator screenshots with a three-beat viewer challenge and no Remotion initialization. Use in a twelve-minute parallel launch lane, as a reliable fallback to a richer Claude Design animation, or whenever ffmpeg and ImageMagick are available.
日本語の概要は準備中です。原文の説明を表示しています。
Automate App Store screenshot capture across devices and languages
日本語の概要は準備中です。原文の説明を表示しています。
Designer's eye QA: finds visual inconsistency, spacing issues, hierarchy problems, AI slop patterns, and slow interactions — then fixes them. Iteratively fixes issues in source code, committing each fix atomically and re-verifying with before/after screenshots. For plan-mode design review (before implementation), use /plan-design-review. Use when asked to "audit the design", "visual QA", "check if it looks good", or "design polish".
日本語の概要は準備中です。原文の説明を表示しています。
Report-only QA testing. Systematically tests a web application and produces a structured report with health score, screenshots, and repro steps — but never fixes anything. Use when asked to "just report bugs", "qa report only", or "test but don't fix". For the full test-fix-verify loop, use /qa instead.
日本語の概要は準備中です。原文の説明を表示しています。
Extract, document, or normalize a product UI design system from code, screenshots, or brand sources. Use for visual tokens, theme variables, typography, spacing, colors, radii, shadows, component inventories, variants, states, or building a reusable UI library. Do not use for software architecture, database schemas, or generic system design.
日本語の概要は準備中です。原文の説明を表示しています。
Create or redesign product UI in an existing codebase, including a wireframe, substantive visual variations, and an interactive prototype. Use for requests about UI layout, visual direction, screens, flows, components, a landing page, dashboard, or making an interface feel polished. Do not use for backend work, system architecture, decks, or logic-only UI fixes.
日本語の概要は準備中です。原文の説明を表示しています。
Drive a real web browser: navigate, read, find, click, fill, screenshot
日本語の概要は準備中です。原文の説明を表示しています。
One-shot NowStack Mobile Android deployment with GPC Google Play Console CLI. Use when preparing Play Store releases, uploading AABs, syncing listings/screenshots, monitoring rollout health, or submitting Android without EAS Submit.
日本語の概要は準備中です。原文の説明を表示しています。
One-shot NowStack Mobile iOS deployment with asc App Store Connect CLI. Use when preparing TestFlight/App Store releases, uploading IPAs, syncing screenshots/metadata, validating review readiness, or submitting the iOS app without EAS Submit.
日本語の概要は準備中です。原文の説明を表示しています。
One-shot NowStack Mobile iOS deployment with asc App Store Connect CLI. Use when preparing TestFlight/App Store releases, uploading IPAs, syncing screenshots/metadata, validating review readiness, or submitting the iOS app without EAS Submit.
日本語の概要は準備中です。原文の説明を表示しています。
Prepare and submit NowStack Mobile iOS App Store releases. Use for real 6.5-inch app screenshots, metadata, IAP, review details, validation, and submit.
日本語の概要は準備中です。原文の説明を表示しています。
Release a NowStack Mobile Android app to Google Play production - listing, screenshots, Data safety, content rating, release notes, then promote the tested internal build to the production track with a staged rollout. Use for "release on Android", "publish to Play production", "promote to production", "ship the Android update". If no build is on a testing track yet, run ns-android-beta first.
日本語の概要は準備中です。原文の説明を表示しています。
Stock Screener — pre-built screens (growth, value, momentum, dividend, earnings beats) plus custom natural language criteria. Returns top 10-20 matches ranked by Screen Fit Score (0-100). Triggered by "trade screen growth/value/momentum/dividend/earnings" or "trade screen custom <criteria>".
日本語の概要は準備中です。原文の説明を表示しています。
Three-tier video pipeline: ffmpeg Quick (5s, instant) → ffmpeg Enhanced with Ken Burns (15s, polished) → Remotion Animated (60-90s, production-grade). Takes static slides from Paper MCP or any PNGs and assembles them into platform-ready video. Make sure to use this skill whenever the user has slides, images, or PNGs and wants to turn them into video — even if they just say 'make a video from these', 'animate my slides', 'I have images and need a TikTok', or 'stitch these together'. Also use when they mention ffmpeg video assembly, Remotion-animated slide assembly, Ken Burns effects, or any slides-to-video pipeline. Owns the slides→MP4 assembly pipeline; for writing, debugging, or running `remotion render` on Remotion code itself, see /remotion-best-practices; for screen-recorded product demos, see /marketing-demo. Works with any PNG source — Paper exports, Canva, screenshots, anything.
日本語の概要は準備中です。原文の説明を表示しています。