「friction」の検索結果

Operations reconnaissance — audit process documentation, vendor contracts, compliance posture, OKR health, and cross-functional friction points to understand where operations is the bottleneck. Use when asked to "audit our operations", "where are we slow", "what processes are broken", or "before designing a compliance program".

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

Operational efficiency audit — identify waste, redundancy, and friction across processes, tools, and team workflows. Use when asked to "audit our operations for waste", "where are we inefficient", "what tools are we paying for but not using", or "reduce operational overhead".

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

Usability review — evaluate an existing flow or UI against usability heuristics, flag friction points, and recommend fixes. Use when asked to "review the UX", "usability audit", "what's wrong with this flow", "UX feedback", "critique this design", or "why are users dropping off here".

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

Applying motion study and time analysis to household work. Based directly on Lillian Gilbreth's *The Home-Maker and Her Job* and *Cheaper by the Dozen*, this skill covers the therblig-motion catalog, task decomposition, batch processing, parallelism, routine chart design, and the ergonomics of work surfaces. Use when diagnosing why a household is running out of time, designing a weekly routine, teaching task sharing to children, or reducing the friction of any repeated household task.

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

Designing the household as an operating system. Covers room-function mapping, work-triangle analysis, storage topology, utility flow, and the Richards/Beecher lineage that treats the home as an engineered environment rather than a stage set. Use when planning a new kitchen, reorganizing a room, diagnosing friction in a daily routine, or teaching a learner to see the house as a system with inputs, flows, and outputs.

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

Conversational guide for using tools/session-retro/observe.mjs to capture friction, wins, corrections, decisions, gaps, tool-use, and checkpoints as they happen during a session. Use at session start (to kick off the log), at inflection points (to record events), and at session end (to archive and feed the retrospective generator).

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

Use when the user asks for a hypothetical walkthrough of a system to expose tensions, frictions, gaps, or contradictions between its expected and evidenced flow.

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

When the user wants to optimize any form that is NOT signup/registration — including lead capture forms, contact forms, demo request forms, application forms, survey forms, or checkout forms. Also use when the user mentions "form optimization," "lead form conversions," "form friction," "form fields," "form completion rate," or "contact form." For signup/registration forms, see signup-flow-cro. For popups containing forms, see popup-cro.

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

When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions "signup conversions," "registration friction," "signup form optimization," "free trial signup," "reduce signup dropoff," or "account creation flow." For post-signup onboarding, see onboarding-cro. For lead capture forms (not account creation), see form-cro.

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

Write YouTube community-tab posts: text updates, polls, image-caption posts, and questions that drive comments and bring subscribers back between video uploads. Tuned to the community tab's role as a low-friction touchpoint that keeps a channel warm and feeds session signals. Returns a copy-paste block (community posts have no publishing API, so this is always manual by design). Use to write a community post or poll. Not for video titles or descriptions (use yt-title-optimizer and yt-description-writer).

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

Two-layer funnel audit on collected data only — stress-test the awareness layer (hooks, messaging, proof placement, attention leaks on live pages and ads) and the lead-capture layer (opt-ins and lead magnets scored on the four Value Equation variables, friction findings, weakest-magnet rewrite), plus a phone-path check under the Phone Capture Fit Rule. Use when "funnel audit", "audit my funnel", "why is my funnel leaking", "top of funnel isn't converting", "audit our lead magnets", "opt-in audit", "awareness to lead audit", "where are we losing people", "lead capture audit", or any request to diagnose the full awareness-to-lead flow rather than one page.

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

Use when the user says 'audit my conversion rate', 'cro check', 'find conversion leaks', or asks what is hurting conversion before a paid campaign or after a redesign. Scores six friction dimensions: above-the-fold clarity, CTA hierarchy, form length, social proof, speed, trust signals.

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

Designs Claude Code prompts and CC environments. Produces CLAUDE.md drafts, agent topologies, scope-authorization frameworks, halt triggers, Skills/hooks/MCP plans, chat-to-CC handoff specs, and EXECUTION_PLAN.md remediation plans. Five modes: DESIGN (new CC deployments), EVOLVE (updates from friction), RESEARCH (evaluate a CC tool/pattern), TEMPLATE (reusable artifacts), REMEDIATE (consume hygiene findings → produce + execute plan). Do NOT use REMEDIATE for direct cleanup (Cat 1–10 — use rootnode-repo-hygiene Phase 2). Do NOT use for hygiene scanning (rootnode-repo-hygiene), chat prompts (rootnode-prompt-validation), or chat Projects (rootnode-project-audit).

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

Start and maintain a fire using friction, spark, and solar methods. Covers site selection, material grading (tinder/kindling/fuel), fire lay construction (teepee, log cabin, platform), ignition techniques (ferro rod, flint & steel, bow drill), flame nurturing, and Leave No Trace extinguishing. Use when needing warmth, light, or a signal in a wilderness setting, when boiling water for purification, when cooking foraged food, or in an emergency survival situation requiring heat or morale support.

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

Fix GraphSnapshot tests blocking CI on every feature PR. Use when: (1) every PR fails CI with "Snapshot mismatch" despite correct behavior, (2) fixing snapshots requires build → regen → commit → wait CI cycle per PR, (3) snapshot test in test/unit/*.test.js glob breaks on any intentional change, (4) pre-push hook runs pnpm build + snapshots:update on every push (2-3min overhead). Solution: move GraphSnapshot.test.js to test/unit/snapshots/ so it's excluded from the *.test.js glob. Run manually via pnpm snapshots:update when needed.

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

Audits existing landing pages for conversion rate optimization. Scores hero section, CTA placement, social proof, objection handling, and form friction on a 1-10 scale. Use when someone says 'audit my landing page', 'improve conversions', 'why isn't my page converting', 'CRO audit', 'landing page feedback', 'optimize my signup page', 'page review', 'conversion rate', 'bounce rate is high', 'nobody is signing up', or anything about improving an existing page's performance. Even if they just share a URL and say 'what do you think' or 'how can I improve this' — if there's a page involved and conversion matters, this is the skill. Always use this over generic advice when an actual page exists to audit.

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

Optimizes multi-step conversion flows including signup, onboarding, upgrade, and checkout. Maps each step, identifies friction and drop-off risks, then recommends specific copy/UX changes with A/B test plans. Use when someone says 'signup flow', 'onboarding optimization', 'checkout conversion', 'paywall optimization', 'activation rate', 'funnel analysis', 'why are users dropping off', 'registration flow', 'trial conversion', 'free to paid', 'upgrade flow', 'user journey', or wants to improve any multi-step user journey. If they mention steps, screens, or a sequence that leads to signup, payment, or activation, this is the skill. Even casual mentions like 'users aren't finishing signup' or 'our onboarding sucks' should trigger this. Use this instead of page-cro when the problem spans multiple screens rather than a single page.

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

Provides a complete workflow for implementing verified email retrieval on Android Credential Manager API. Use this skill to integrate a secure, OTP-less email verification flow into an Android app. This skill solves the problem of high-friction sign-up processes by leveraging cryptographically verified credentials from trusted providers like Google.

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

Use when signup or onboarding conversion needs targeted analysis of friction, motivation, guardrails, and experiment opportunities.

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

Think out loud about a problem, decision, or approach — Socratic friction to help you find clarity, not sympathy

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

Use when a task needs the judgment of an Automotive Engineer — computing weight transfer and tire friction-circle limits for a braking-while-cornering maneuver to set brake-force distribution, sizing a powertrain and gear ratio against a 0-60 mph acceleration target while checking traction versus power limits, sizing a crumple zone's crush distance against FMVSS 208 occupant-deceleration limits, or checking a powertrain-mount or driveline natural frequency against engine firing-order excitation for NVH isolation. Distinct from an automotive-service-technician (diagnoses and repairs a vehicle already designed) — this role owns the system-level design decisions (structure, powertrain sizing, suspension geometry, restraint/crash structure, NVH) that produce the vehicle the technician later services.

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

Audit a codebase for product-market fit readiness -- evaluate startup PMF signals, core value loop tightness, feature scatter vs focus ratio, user activation funnel friction, retention hook infrastructure, pricing flexibility, analytics event coverage, CI/CD iteration speed, and growth-stage maturity for pre-seed through Series A products.

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

Diagnose why a landing page, homepage, pricing page, or signup form is not converting, and produce a ranked fix list with a test plan. Runs a structured audit across motivation, value clarity, friction, anxiety, and CTA hierarchy rather than giving generic design opinions. Use when the user says "why isn't this page converting", "improve our conversion rate", "CRO", "conversion audit", "this page isn't working", "high traffic low signups", "people bounce", "review our landing page", or shares a URL and asks what is wrong with it. For rewriting the words only, see copy-review. For writing a new page from scratch, see landing-page-writer. For the statistics of running the test afterwards, see growth-experiment.

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

Audit paid-ad landing pages for message match, mobile experience, performance, accessibility, trust, forms, consent, tracking, security, and conversion friction. Use for landing-page audit, post-click experience, LP audit, conversion-rate optimization, form optimization, ad-to-page message match, redirects, blocked navigation, or requests involving private, loopback, link-local, or metadata IP destinations.

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