「how」の検索結果

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.

日本語の概要は準備中です。原文の説明を表示しています。

Build a long-form X (Twitter) thread (tweetstorm) using a 2026 thread formula (listicle-thread, story thread, curiosity-gap opener, how-I teardown), picked by goal (bookmarks, likes, reposts, replies). Structures tweet 1 as a promise plus open loop, paces one beat per tweet, and closes for the repost. Publishes via Publora, which auto-splits long content into a numbered (1/N) thread. Not for single tweets (use x-post-writer) or auditing a draft (use x-humanizer --mode audit).

日本語の概要は準備中です。原文の説明を表示しています。

Reverse-engineer the hook from a viral X (Twitter) tweet or thread URL. Identifies which of the 10 canonical 2026 X formulas it uses (one-liner contrarian, data-point, build-in-public, quote-tweet, mini-list, relatable cold-open, listicle-thread, story thread, curiosity-gap, how-I teardown), explains why it worked, and returns a blank template mapped to your topic with its primary goal. Use to learn from a tweet you admire. Not for writing your own (use x-post-writer or x-thread-builder).

日本語の概要は準備中です。原文の説明を表示しています。

Remove the AI tells human readers react to in a tweet or thread: 2026 vocabulary by density, reveal bridges, staccato stacks, stacked triads, performed sincerity. Also --mode audit (280-char fit and format), --mode profile (learns how you write) and --mode interview (fills your Story Bank: the numbers, turning points and positions posts are made of). Not for writing from scratch (use x-post-writer). Keywords: humanize, de-AI tweet, AI slop, interview me, audit before posting.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user asks which paad skills exist, what a paad skill does, which one fits their situation, or how to invoke one — including "what can paad do", "list the paad skills", "is there a paad skill for X", or a request for the arguments of a named paad skill

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user wants to set up automated daily promotion / marketing for their Claude Code skills — researching how top skills are promoted on marketplaces (ClawHub / openclaw / SkillsMP / agentskills.io), generating a per-skill marketing plan, auto-posting to X (Twitter) via xurl, and drafting community discussion posts (Reddit / HN / Discord). Triggers — "推广 skills", "营销 skills", "自动发推广", "每天自动推广", "skill marketing", "promote my skills", "/wjs-promoting-skills".

日本語の概要は準備中です。原文の説明を表示しています。

This skill should be used when the user asks anything about Adobe After Effects — to "write an After Effects expression", "make a wiggle / loopOut / inertial bounce", "rig a control with a slider / null", "build a MOGRT / Essential Graphics template", "export AE to Lottie or Media Encoder"; OR to "export from After Effects", "export with transparency / an alpha channel", "fix a black background on export", "choose ProRes vs H.264", "which codec / what bitrate for 1080p / 4K", "stop H.264 disappearing from the Render Queue"; OR when "After Effects is slow / laggy / crashing / froze", "RAM preview won't play in real time", "AE is using all my memory / render takes forever", "how do I speed up After Effects"; OR to "organize my After Effects project", "relink missing footage", "fix broken links after moving files", "set a folder structure / naming conventions", "batch rename layers", or "write an ExtendScript / .jsx script". Covers expressions & rigging, export recipes, performance triage, and project hygiene.

日本語の概要は準備中です。原文の説明を表示しています。

Edit drafts into natural prose, inspect AI-sounding patterns, or review how a specified audience might respond passage by passage. Zero Slop runs inside the user's existing AI assistant with local tools that protect source details. Use for humanizing or de-slopping writing, polishing outward-facing prose, social drafts, final editorial checks, or an explicit simulated reader review. Preserve facts, voice and format; reader simulations are hypotheses, not human feedback.

日本語の概要は準備中です。原文の説明を表示しています。

Generate professional SVG logos from project context: 7 brand variants plus a showcase HTML page. Use for product marks, wordmarks, icons, and favicons. Don't use for raster-only logos, illustrations, or full brand guidelines.

日本語の概要は準備中です。原文の説明を表示しています。

Prepare a git repo before new work: review uncommitted changes, fix .gitignore, delete merged branches, end on clean main, or inspect one branch before deciding. Don't use for dead code, commit-and-push, releases, LICENSE files, or git how-tos.

日本語の概要は準備中です。原文の説明を表示しています。

Generate a Technical Architecture Document (TAD) from a PRD. Use when asked to design system architecture or define how a product is built. Updates tad.md and reports GitHub links. Don't use for PRD authoring, sprint tasks, or code implementation.

日本語の概要は準備中です。原文の説明を表示しています。

Apply this skill whenever the user is navigating early-stage startups, bootstrapping, product innovation, branding, or overcoming the fear of failure. Sara Blakely, founder of Spanx and self-made billionaire, approaches business by leveraging 'the outsider advantage,' relying on intuition, and obsessing over consumer empathy. Trigger this skill for discussions about funding trade-offs (bootstrapping vs. VC), naming products, dealing with imposter syndrome, entering an industry with zero experience, or building an authentic, vulnerability-driven company culture. Reach for her mental models when users are tempted to share fragile ideas too early, fear embarrassment, or need to rethink how they approach product-market fit.

日本語の概要は準備中です。原文の説明を表示しています。

Applies the reasoning of David Silver, lead researcher on AlphaGo and AlphaZero at DeepMind, to problems of AI design, reinforcement learning, and open-ended discovery. Use this skill whenever you are designing AI systems, evaluating learning algorithms, balancing exploration vs. exploitation, choosing research problems, or discussing how to break past human performance ceilings. Reach for this whenever the user asks about self-play, Monte-Carlo Tree Search, tabula rasa learning, AGI, or moving from human-curated data to autonomous experience. It helps shift the focus from hardcoding human knowledge to building systems that learn for themselves.

日本語の概要は準備中です。原文の説明を表示しています。

Applies the reasoning, principles, and frameworks of Andrew Ng (machine learning pioneer, co-founder of Coursera and DeepLearning.AI, Stanford University, and former Google Brain lead). Use this skill whenever the user is navigating AI application development, agentic workflows, automation strategy, AI-native software engineering, or rapid prototyping. Trigger this skill when discussing career advice in the AI era, evaluating AI regulations, structuring machine learning projects, or deciding how to integrate AI into a business. It emphasizes task-based automation, data-centric ML, and driving the cost of proof-of-concepts to zero.

日本語の概要は準備中です。原文の説明を表示しています。

Applies the analytical and therapeutic philosophy of Ludwig Wittgenstein, 20th-century philosopher of language (Tractatus / Philosophical Investigations). Use this skill when the user is stuck in conceptual confusion, debating semantics, trapped by abstract definitions, or trying to solve a problem that is actually just a linguistic misunderstanding. Trigger this for topics involving the limits of language, meaning as use, logical clarification, or when the user is over-theorizing instead of looking at practical applications. It helps dissolve 'fly-bottle' traps by examining how words are actually used in context.

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill whenever you need to reason about public health, epidemiology, preventive medicine, healthy aging, longevity, lifestyle vs. genetics, or dietary patterns. Kay-Tee Khaw, an epidemiologist at the University of Cambridge, focuses on population health and how modest lifestyle changes impact chronic disease. Trigger this skill when evaluating health interventions, discussing longevity, analyzing real-world health data, or giving advice on diet and lifestyle. Apply her frameworks to shift focus from extreme interventions and isolated nutrients toward whole-food patterns, population-level risk shifts, and the compression of morbidity.

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill to apply the rigorous epidemiological reasoning of Julie E. Buring (epidemiologist and women's health trialist) to study design, clinical trial critiques, cardiovascular risk assessment, and evidence-based integrative medicine. Trigger this skill whenever you are evaluating medical literature, designing cohort studies or RCTs, assessing conflicting research findings, or analyzing cardiovascular risk factors (especially in women). Reach for this when users ask about the validity of supplements, the discrepancy between observational and randomized data, or how to future-proof a clinical registry.

日本語の概要は準備中です。原文の説明を表示しています。

Suede-owned operations-assessment discipline that maps how work actually happens before anyone designs a system: floor-level interviews with the people who do the work, an inventory of every silo including spreadsheets and inboxes used as databases, friction quantified in the requester's own numbers, opportunities ranked by annual value against build complexity, and adoption watched for the thirty days after launch. Use when nobody can answer what to automate, when an operation needs auditing before a build, when tribal-knowledge and key-person risk has to surface, or when a shipped system is quietly being routed around. NOT FOR: deciding what to build and in what order once the map exists (use suede-ops-architecture); researching external customers rather than internal operators (use suede-customer-research); lead lifecycle, scoring, and CRM routing rules (use suede-revops); product instrumentation and dashboards (use suede-analytics); getting a new user to first value (use suede-onboarding).

日本語の概要は準備中です。原文の説明を表示しています。

Suede AI blunt A-F ship grade for a code change across correctness, security and permissions, data and state, domain truth, UX and release behavior, tests and verification, and deploy readiness, with Instant-F triggers and evidence-based grade caps on auth, payment, migration, and public-API surfaces. Use when asked to grade this, give it a letter, is this an A, how ready is this to ship, or should this merge: when the caller wants the verdict without a findings list. NOT FOR: findings, evidence, and fix briefs (use suede-code-review, or suede-code for findings plus grade); enforcing the verdict in CI (use suede-ci-gate); eval coverage for AI behavior (use suede-ai-eval).

日本語の概要は準備中です。原文の説明を表示しています。

Suede-owned artist campaign rollout. Use when an artist, song, release, era, show, or catalog moment needs a complete campaign across surfaces: hooks, rituals, visuals, merch, rollout calendar, email, site copy, fan actions, setlists, and collaborator outreach. NOT FOR: single-surface conversion copy (use suede-copy); sync licensing packaging (use suede-sync-packaging); software, repo, or skill-pack releases (use suede-launch-packaging).

日本語の概要は準備中です。原文の説明を表示しています。

Suede-owned marketing attribution discipline. Use when the user wants to figure out which marketing actually drives conversions and revenue, choose or interpret an attribution model, or reconcile conflicting numbers across tools. Also use when the user mentions 'attribution,' 'attribution model,' 'first-touch vs last-touch,' 'multi-touch,' 'which channel drives revenue,' 'what's my real CAC,' 'my dashboards disagree,' 'Google/Meta says X but GA says Y,' 'MMM,' 'incrementality,' 'geo lift,' 'holdout test,' 'how did you hear about us,' 'self-reported attribution,' 'dark social,' or wants to instrument attribution themselves, 'stitch my bookings to their source,' 'SavvyCal/Calendly attribution,' 'close the identify gap,' 'track conversions on a third-party domain,' 'first-party attribution.' NOT FOR: general analytics instrumentation and reporting (use suede-analytics) or revenue-ops pipeline work (use suede-revops).

日本語の概要は準備中です。原文の説明を表示しています。

Suede-owned content-strategy discipline for audience questions, content pillars, topic clusters, editorial priorities, cadence, distribution, refreshes, and stop-doing decisions. Use when deciding what to publish, why it deserves resources, and how the portfolio compounds. NOT FOR: writing an individual asset (use suede-copy), technical or on-page SEO audits (use suede-seo-audit), or social-channel production (use suede-social).

日本語の概要は準備中です。原文の説明を表示しています。

Generate a self-contained handoff prompt that lets the user continue work in a fresh coding agent session with empty context. The prompt captures everything a new agent needs: project, goal, progress, decisions, current state, and remaining work. **Triggers — use this skill when:** - User says "handoff", "hand off", "hand-off" - User asks to "generate a continuation prompt" - User says "give me a prompt to continue this" - User asks to "wrap up for a new session" - User says "context transfer", "session transfer" - User asks "how do I pick this up later" - User wants to "pass this to another agent"

日本語の概要は準備中です。原文の説明を表示しています。

Manage design work in Penpot — create projects, organize pages, build components, export assets, review designs visually, and handle design-to-code handoff. Use when asked to create designs, manage Penpot projects, build components, export tokens, set up a new design project, review a design, take screenshots, or show what something looks like.

日本語の概要は準備中です。原文の説明を表示しています。