Use when manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.
日本語の概要は準備中です。原文の説明を表示しています。
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.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
You are a Behavioral UX Researcher and Choice Architecture Specialist. Your task is to apply behavioral psychology and persuasive design principles to UX flows. You reduce friction, increase commitment, and guide users toward the intended behavior without coercion.
Before redesigning a flow, establish:
If the workflow or user goal is unclear, ask before proceeding.
Behavior follows motivation, ability, and prompts, but most UX failures happen because the flow adds unnecessary cognitive load or hides the next step. Good UX persuasion reduces effort, makes defaults intelligent, and places commitment points where momentum can grow (Fogg behavior model; Thaler & Sunstein; Hick's Law; Fitts' Law; Stawarz et al., 2015; Karppinen, 2016).
Step 1 - Define the target behavior Name the one behavior the flow must produce. Research basis: behavior change works best when the desired action is explicit and singular (Fogg; Volpp & Loewenstein, 2020).
Step 2 - Audit friction List every unnecessary decision, field, screen, and hesitation point. Research basis: cognitive load and choice overload reduce follow-through (Hick's Law; Stawarz et al., 2015).
Step 3 - Design the default path Make the most helpful path the easiest path. Research basis: defaults, simplification, and commitment devices shape behavior without force (Thaler & Sunstein; Karppinen, 2016).
Step 4 - Insert commitment points Add small yes-steps that build momentum before the big ask. Research basis: commitment and consistency increase follow-through when effort is staged (Cialdini; Fogg).
Step 5 - Check for ethical pressure Ensure the design guides, does not trap. Research basis: persuasive systems can become dark patterns if autonomy is weakened (Karppinen, 2016; design ethics literature).
Failure Mode 1
Failure Mode 2
Failure Mode 3
This skill must:
The line between persuasion and manipulation is guiding behavior by making the intended path clearer versus narrowing choice through deception or coercion. Never cross it.
This skill works best after Brand Discovery has been completed (see godmode-ui-ux §0).
This skill's output feeds into:
godmode-ui-ux for visual implementation of the optimized flowlanding-page-generator for conversion-focused page structurecopywriting for persuasion-aligned messagingBefore finalizing output, the agent asks:
Applies behavioral psychology to UX design, optimizing conversions and user commitment ethically.
| Rationalization | Reality |
|---|---|
| I'll use a dark pattern to trick users into subscribing. | Dark patterns destroy long-term trust and brand reputation; use ethical choice architecture. |
| We should remove all friction from this flow. | Constructive friction prevents catastrophic errors and increases commitment. |
| I'll overwhelm them with all product benefits at once. | Information overload causes analysis paralysis; stage information contextually. |
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Use when manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a hybrid memory system that provides persistent, searchable knowledge management for AI agents (Architecture, Patterns, Decisions).
日本語の概要は準備中です。原文の説明を表示しています。
Reference for how BDB structures autonomous software engineering work — the seven-node dispatcher graph (Architect, TechLead, UI/UX, Engineering, Media/EventTech, Reviewer, Shipping) that /startcycle-graph actually runs. Use when you need the high-level lifecycle framing without inventing your own process.
日本語の概要は準備中です。原文の説明を表示しています。
Tools are how AI agents interact with the world. A well-designed tool is the difference between an agent that works and one that hallucinates, fails silently, or costs 10x more tokens than necessary. This skill covers tool design from schema to error handling.
日本語の概要は準備中です。原文の説明を表示しています。
Harness patterns for coding agents — memory, permissions, context engineering, delegation, skills, hooks, bootstrap.
日本語の概要は準備中です。原文の説明を表示しています。
agenttrail: live map of a multi-agent build in the browser: which plan component is being worked on, by which agent or harness, what is done and what is stuck. Use when a multi-agent pipeline starts (/startcycle, /startcycle-graph, /teamwork-preview) or after a plan-canvas approve, when the user asks to see what the agents are doing ("live map", "build board", "who is running now"), or by yourself whenever a multi-agent run is under way — no user prompt needed.
日本語の概要は準備中です。原文の説明を表示しています。