「friction」の検索結果

Use this skill when designing the UX and content strategy for a Salesforce-powered self-service portal or help center — pre-deflection article surfacing, Help Center search UX, friction-calibrated case submission forms, community peer support layers, and deflection measurement. Trigger keywords: design self-service portal, case deflection strategy, help center UX design, reduce support volume with self-service, knowledge base search experience. NOT for picking which contact reasons to deflect and through which channel — use architect/case-deflection-strategy. NOT for building the Experience Cloud site itself — use admin/experience-cloud-site-setup. More trigger keywords: article visibility matrix IsVisibleInCsp IsVisibleInPkb, which articles show in the customer portal, case visibility for portal users, CaseComment IsPublished customer visible comment, self-registration profile and account for a portal, Help Center template does not support login, deflection metrics SOQL KnowledgeArticleViewStat, self-service journey map, moderation policy for a support community.

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

Use when reviewing a codebase for architectural friction, shallow modules, poor test seams, scattered behavior, duplicated orchestration, or opportunities to deepen modules before implementing a ticket or workflow.

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

Surfaces architectural friction and proposes deepening refactors (shallow to deep modules). Renders via mk:preview. NOT for debate (mk:party); NOT for plan critique (mk:plan-ceo-review).

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

Use when surfacing architectural friction and proposing deepening refactors (shallow modules → deep modules) for testability and AI-navigability. Triggers on "improve architecture", "find deepening opportunities", "where is this codebase shallow", "architecture review". Emits structured candidates + precise patches; delegates ALL rendering to mk:preview. NOT for diagram/HTML rendering (see mk:preview); NOT for trade-off deliberation (see mk:party); NOT for plan critique (see mk:plan-ceo-review).

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

Turn friction you just hit into a concrete change to the workflow, so the same problem doesn't recur.

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

Detects and fixes color contrast violations using WCAG 2.1 guidelines and perceptual analysis. Expert in contrast ratio calculation, color blindness simulation, and providing accessible alternatives. Activate on "check contrast", "color accessibility", "WCAG audit", "readability check", "contrast ratio", "hard to read", "can't see text". NOT for general color theory (use color-theory-palette-harmony-expert), brand color selection (use web-design-expert), or non-visual accessibility (use ux-friction-analyzer).

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

Expert-level classical mechanics knowledge. Use when working with Newton's laws, kinematics, dynamics, energy, momentum, rotational motion, oscillations, gravitation, Lagrangian mechanics, or Hamiltonian mechanics. Also use when the user mentions 'force', 'torque', 'momentum', 'energy conservation', 'simple harmonic motion', 'projectile', 'friction', 'center of mass', 'moment of inertia', 'Lagrangian', or 'Hamiltonian'.

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

Improve agent harness configuration based on recent friction points. Use when invoked as `$retro` or when the user asks for autonomous cleanup of Codex, agent harness, or migrated Claude configuration.

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

Use when designing customer onboarding — time-to-first-value, milestone design, friction audit, drop-off diagnosis. Triggers on 'fix onboarding', 'why do new accounts churn fast'.

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

Harness-first workflow for evaluating and improving terminal UIs through real interaction. Use this whenever the user wants to review a TUI experience, compare before/after behavior, identify UX friction, validate navigation or filtering flows, inspect visual stability, or turn observed interaction problems into concrete follow-up tests and improvement recommendations. Prefer this skill any time a TUI should be exercised through a reproducible PTY/session harness instead of only reading code.

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

GStack developer-experience plan review for setup, local commands, docs, test loops, onboarding friction, and maintainability before implementation.

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

GStack developer-experience review for implemented repositories and workflows, focused on setup friction, command reliability, docs gaps, and maintainability.

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

Durable categorized record-keeping for any predicate-enabled walk. Trigger when: - Classifying a step's output for recording (decision, finding, debt, feedback). - Promoting a scratch artifact to the ledger, to repo/docs, or to a category home (.ledger/tech-debt/, .ledger/process-feedback/). - Auditing whether a draft is structurally ready for its destination. - Running a zero-context sensibility read before committing to promotion. - Recording a known limitation as a tech-debt entry (not prose in the log). - Recording a friction, miss, improvement, or process amendment. - Prompt contains: /record, record-keeping, promote, ledger note, zettelkasten, scratch-to-ledger, zero-context read, over-strip, classification trigger, tech-debt, process-feedback, amendment.

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

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," "account creation flow," "people aren't signing up," "signup abandonment," "trial conversion rate," "nobody completes registration," "too many steps to sign up," or "simplify our signup." Use this whenever the user has a signup or registration flow that isn't performing. For post-signup onboarding, see onboarding. For lead capture forms (not account creation), see cro.

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

Use when the user asks to "pre-launch check the landing page", "run a Quality-Score preflight", or "verify ad-to-page message match before launch"; produces an ad↔page continuity report — message-match gaps, above-the-fold check, page-speed read, form-friction count, mobile-render flags — as a pass/fix punch list. Not for redesigning or rewriting the page — use landing-optimizer; not for scoring the account or the RQS — use ad-account-auditor. 落地页体验预检/广告落地页一致性检查

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

Improve conversion performance on marketing pages and forms through diagnosis, message hierarchy, friction analysis, proof, UX hypotheses, instrumentation and experiments.

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

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.

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

Break a user interface under real-world conditions across responsiveness, hostile content, interaction states, accessibility, network failure, interruption, and complete user journeys, reporting observable user harm with evidence rather than aesthetic opinion. Use whenever the user wants to stress-test a UI, verify responsive and edge-case behaviour, inspect loading/error/empty/recovery states, review a flow for friction, or find where an interface fails under reality. Part of the audit suite; inherits the shared constitution while its own job is proving observable user harm.

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

Behavioral UX specialist applying choice architecture, friction audits, and commitment design to guide users toward intended actions without coercion. Use when optimizing conversion flows, onboarding, or checkout UX.

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

Productivity analyst that maps your workflow, scores tasks by time cost and energy drain, and builds a prioritized 4-week automation plan. Use when you want to audit your workflow, figure out what to automate, do a productivity review, identify high-leverage tasks, feel overwhelmed and need to prioritize, or after the compounder surfaces new friction. Part of the architect-system loop. Outputs to system/audit-report.md.

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

Productivity analyst that maps your workflow, scores tasks, and builds a prioritized automation plan. Use when: (1) "audit my workflow", "what should I automate?", "productivity review", (2) Starting a new project and need to identify high-leverage tasks, (3) Feeling overwhelmed and need to prioritize, (4) After /compounder surfaces new friction or patterns. Reads compounder insights when available. Outputs to system/audit-report.md.

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

Weekly review partner that compounds productivity gains over time. Use when: (1) "weekly review", "what did I accomplish this week?", "compound my gains", (2) End of work week to review progress, (3) "what patterns are emerging?", (4) "update the system map", (5) Feeling stuck and need to identify friction. Reads all system/ files to synthesize progress. Outputs to system/compounder/week-{date}.md. Feeds insights back to /audit.

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

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.

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

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.

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