6,920 件 ・ 関連度順
概要と使いどころ
Use when diagnosing Superloopy doctor, install, wrapper, plugin cache, hook bootstrap, bundled agents, marketplace, Codex, Claude Code, stale-version, evidence-floor, or host-wiring health problems.
日本語の概要は準備中です。原文の説明を表示しています。
Produce a short motion-graphics video ad — a 15s Facebook/Instagram/TikTok spot — as a rendered MP4. Researches the destination landing page so every on-screen claim matches it, pulls real product imagery off the live site, animates one paused GSAP timeline in a single HTML page, and renders it frame-accurately through Playwright and ffmpeg. Use this whenever the user wants a video ad, promo video, animated ad, "an ad for my product", Meta/TikTok/Reels creative in video form, a 9:16 or 1:1 cut of an existing spot, or a re-render of an earlier ad with a different hook, hero or CTA — including when they never say the words "motion graphics". Not for animating UI inside an app, not for static image ads, and not for long-form or voiceover-led video.
日本語の概要は準備中です。原文の説明を表示しています。
Edit English prose to remove repetitive AI phrasing, inflated language, and mechanical structure while preserving meaning and the author's voice. Use for requests to humanize, de-slop, rewrite naturally, or fix tone. Also compose from the author's English notes or transcripts and ask targeted questions when real details are missing. For Brazilian Portuguese, use the companion humanizar skill.
日本語の概要は準備中です。原文の説明を表示しています。
Edit English prose to remove repetitive AI phrasing, inflated language, and mechanical structure while preserving facts, meaning, and the author's voice. Use for requests to de-slop, humanize, rewrite naturally, fix tone, or review generic English drafts. Also compose from the author's English notes or transcripts and ask targeted questions when real details are missing. For Brazilian Portuguese, use the bundled humanizar skill.
日本語の概要は準備中です。原文の説明を表示しています。
Inspect and diagnose minimal-zine posters, photo restyles, editorial images, and social-card series for subject preservation, factual and text integrity, composition, paper realism, print-process coherence, color signal, anti-AI craft, platform fit, and series continuity. Use when the user asks whether an image has高级感, feels AI-generated, matches Paper Signal or gc-minimal-zine quality, needs improvement, or should be regenerated. Returns evidence-based findings and a targeted correction prompt; regenerates only when the user also asks for a fix.
日本語の概要は準備中です。原文の説明を表示しています。
Plan, art-direct, generate, edit, and quality-check tactile minimal-zine bitmap imagery from almost any subject: landscapes, portraits, objects, products, architecture, interiors, existing photographs, moods, article ideas, cultural essays, data, reviews, and social-media card series. Use for 小红书图片, Instagram carousels, poetic posters, editorial covers, photo restyling, visual essays, evidence-aware explainers, or any request for aged paper, photocopy, risograph, letterpress, sparse type, and restrained single-ink character. Routes the subject before choosing composition, preserves identity and factual content when editing, saves reproducible prompts, invokes the runtime-native image generator, and audits the real raster output. Do not use for glossy commercial ads, deterministic UI/vector assets, or exact diagram rendering.
日本語の概要は準備中です。原文の説明を表示しています。
Plan, write, art-direct, generate, and package a coherent 2-10 image minimal-zine social series from notes, articles, photographs, travel stories, products, reviews, cultural topics, data, PDFs, or mixed subjects. Use for Xiaohongshu/小红书图片, Instagram carousels, social visual essays, recommendation posts, photo diaries, evidence-backed explainers, or any multi-image editorial sequence. Produces analysis, card roles, subject-aware composition, saved prompts, real raster images, natural caption copy, evidence provenance when needed, and series-level QA.
日本語の概要は準備中です。原文の説明を表示しています。
Write blog posts, guides, tutorials, and long-form content. Sounds like a real person, not AI. Use when the user wants polished written content.
日本語の概要は準備中です。原文の説明を表示しています。
Run real browser QA with Playwright. Use when testing a frontend feature, verifying UI before PR, smoke testing after deploy, or investigating reported visual bugs.
日本語の概要は準備中です。原文の説明を表示しています。
Safe testing practices to prevent real-world side-effects. TRIGGER when user asks to "run tests", "test this", "write tests", "debug", "mock", "fixture", "integration test", "unit test", or when testing code that touches network, database, filesystem, or external services. Use BEFORE executing any test that could affect production systems.
日本語の概要は準備中です。原文の説明を表示しています。
Scrape web pages using Scrapling with anti-bot bypass (like Cloudflare Turnstile), stealth headless browsing, spiders framework, adaptive scraping, and JavaScript rendering. This skill should be used when asked to scrape, crawl, or extract data from websites; web_fetch fails; the site has anti-bot protections; write Python code to scrape/crawl; write spiders.
日本語の概要は準備中です。原文の説明を表示しています。
用户在做决策时受到群体压力或主流意见影响，需要区分"从众=安全"和"独立分析=真正保守"。 语言信号:"大家都说""分析师都推荐"/"这是行业惯例"/"为什么不随大流"/"保守一点是不是更安全" 不适用于:已经有独立分析支撑的决策（不需要纠偏时）。
日本語の概要は準備中です。原文の説明を表示しています。
Generate tests in red or expand mode and run-and-heal new tests. Use when the user says "lets expand test coverage", "I want to automate tests", "lets write acceptance tests", or "I want to do ATDD"
日本語の概要は準備中です。原文の説明を表示しています。
Build and grow online communities across all platforms and contexts — from developer/B2B communities (Discord, Slack, Circle, Discourse) to social communities (Twitter/X, Reddit, Farcaster) to crypto/holder communities (Telegram). Covers strategy, platform selection, channel architecture, member journey mapping, onboarding, engagement rituals, ambassador/champions programs, moderation, governance, growth, retention, crisis management, and metrics. Use for: community-led growth, community strategy, developer community, user community, Discord/Slack/forum/Telegram setup, ambassador programs, community health, holder psychology, engagement systems, social community building, cross-platform coordination.
日本語の概要は準備中です。原文の説明を表示しています。
SEO, AEO (Answer Engine Optimization), and GEO strategy for search engines and AI visibility. Use when working on "SEO audit," "technical SEO," "on-page SEO," "AI search optimization," "AEO," "GEO," "AI visibility," "optimize for ChatGPT," "optimize for Perplexity," "AI Overviews," "answer engine optimization," "generative engine optimization," "AI citations," "featured snippets," "meta tags," "schema markup," "search ranking," "content optimization," "E-E-A-T," "structured data," "search console," "SEO health check," "why am I not ranking," "AI search readiness," "backlink strategy," "link building," "domain authority," "programmatic SEO," "SEO at scale," "template-based SEO," "AEO monitoring," "AI search monitoring," "JSON-LD," "rich snippets," "schema.org," "SERP analysis," "search intent," "site architecture," "information architecture," "URL structure," "internal linking," or "navigation." For keyword research, see keyword-research-and-clustering.
日本語の概要は準備中です。原文の説明を表示しています。
CRM integration patterns for Close CRM, HubSpot, and Salesforce. Use when: Close CRM, HubSpot, Salesforce, CRM API, lead sync, deal sync, activity logging, CRM webhook, pipeline automation, contact enrichment.
日本語の概要は準備中です。原文の説明を表示しています。
Review any client-facing message or material (emails, letters, newsletters, social posts, website copy, presentations, performance reports, proposals) for compliance with SEC rules that govern investment advisers — the Marketing Rule (206(4)-1), fiduciary duty / antifraud provisions (206), Books and Records (204-2), and Reg BI where broker-dealer activity applies. Produces a pass/flag/fail markup, required disclosures, a books-and-records scratch-pad entry, and an archiving handoff reminder. Triggers on "compliance check", "/compliance", "is this compliant", "review this before I send it", "can I say this to a client", "check this email/post/deck". Use it whenever an advisor asks to check, review, or look over anything before it goes to a client or prospect — "check this before I send it", "look this over before it goes out" — even a routine note, because deciding that a message needs no changes is part of the review, not a reason to skip it.
日本語の概要は準備中です。原文の説明を表示しています。
Turn a client meeting into next-best-action follow-up for a financial advisor — no drafting required. Given a meeting (via Zocks, Wealthbox, or a pasted transcript), finds the right household, drafts a CRM note plus the action items and opportunities it heard, shows them all in one batch for approval, then writes what's approved and offers to file the record in Drive. Triggers on "log the meeting", "log my meeting with [client]", "meeting follow-up", "post meeting", "/post-meeting", or "follow up on my meeting with [client]".
日本語の概要は準備中です。原文の説明を表示しています。
S7 of see-it-ship-it: what the person hears. Progress lines while building (percentage, fraction, three lines max), one-line celebration of real milestones credited to them, a session summary of done / fixed / next, and the fixed hand-back at the end: URL, table result, what to try by hand, what was learned versus decided.
日本語の概要は準備中です。原文の説明を表示しています。
Coverage-design method for qa-engineer — pyramid ratios per archetype, equivalence/boundary/property case selection, mutation score as the real coverage signal, and a flake-quarantine policy. Turns "coverage is 90%" (a number with no method) into a defensible test plan. Emits TEST-STRATEGY-{slug}.md, which the QA gate checks exists.
日本語の概要は準備中です。原文の説明を表示しています。
Shared review framework that every domain reviewer (pci, oracle, gov, edtech, healthcare, mlops, etc.) MUST follow. Defines the output artifact (TM-{slug}.md), mandatory sections, severity scale, verdict format, the workflow scaffold (when-invoked, Step-0 read-inputs, HANDOFF), and the "domain heuristic vs generic check" boundary. Eliminates duplication across the ~30 reviewer prompts.
日本語の概要は準備中です。原文の説明を表示しています。
Data-model rules that make a schema importable from day one, so the migration-import-engineer is never blocked on missing columns. Every SMB Product-Builder product must let a customer bring their data from an incumbent (ServiceTitan/Toast/Mindbody/Shopify) — that requires provenance (source_ref) and rollback (import_batch_id) on importable entities, and modelling real-world actors as entities rather than inline fields. Applied by architect when writing the data model in ARCH-{slug}.md, and checked by migration-import-engineer. One cheap rule set prevents the migration↔architecture seam gap from recurring across all 40 products.
日本語の概要は準備中です。原文の説明を表示しています。
Scaffold-time observability so a shipped product is not blind in prod from day one — error capture (Sentry), request-id structured logging, and /healthz + /readyz endpoints. stack-baseline pins Sentry but nothing wires it; this is the wiring. Loaded by app-scaffolder (bake into the scaffold), infra-provisioner (prod env + probes), and consumed by l3-support (traces) and devops (deploy gate).
日本語の概要は準備中です。原文の説明を表示しています。
Onboarding-and-switching playbook for SMB Product-Builder products. Defines the first-run experience that turns a prospect leaving an incumbent (ServiceTitan/Toast/Mindbody/Shopify/QuickBooks) into an activated user — import-first onboarding, the activation milestone, sample-data fallback, and the time-to-first-value target. Applied by migration-import-engineer and architect/pm so onboarding is designed as a funnel, not an afterthought. Our whole wedge is "low switching cost"; this skill makes that real on day one.
日本語の概要は準備中です。原文の説明を表示しています。