「choice」の検索結果

Browser automation powers web testing, scraping, and AI agent interactions. The difference between a flaky script and a reliable system comes down to understanding selectors, waiting strategies, and anti-detection patterns. This skill covers Playwright (recommended) and Puppeteer, with patterns for testing, scraping, and agentic browser control. Key insight: Playwright won the framework war. Unless you need Puppeteer's stealth ecosystem or are Chrome-only, Playwright is the better choice in 2025. Critical distinction: Testing automation (predictable apps you control) vs scraping/agent automation (unpredictable sites that fight back). Different problems, different solutions. Use when "playwright, puppeteer, browser automation, headless, web scraping, e2e test, end-to-end, selenium, chromium, browser test, page.click, locator, playwright, puppeteer, browser, automation, testing, scraping, headless, e2e, selenium, web-testing" mentioned.

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

Researches real projects, papers, and documented failures before proposing a new feature, architecture, or technology choice. Use for design decisions with multiple valid approaches, not for implementing an existing spec or fixing a known bug.

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

影视编剧 (Scriptwriting / Screenwriting) — 为电影 / 电视 / 流媒体剧集写戏剧蓝本的从业者认知操作系统: 决定「讲什么故事、人物是谁为何转变、场景如何被戏剧化、主题为何重要」的学科 —— 区别于导演 (调度 / 视觉实现)、制片 (融资 / 排期)、小说 (无格式 / 场景 / 视觉动作约束)。覆盖 (a) 故事与结构理论 (亚里士多德《诗学》情节 / 人物 / 思想 + 突转 peripeteia / 发现 anagnorisis + 净化 catharsis; Syd Field 范式 / 三幕 / 情节点; Freytag 金字塔; Egri 前提; McKee《故事》掌控性理念 / 鸿沟 / 价值正负转变 / 激励事件 / 渐进式复杂化; Truby《故事剖析》22 步 + 道德论证; Vogler/Campbell 英雄之旅; Blake Snyder《救猫咪》15 拍节拍表; Dan Harmon 故事环; John Yorke 五幕《进入森林》; Frank Daniel 八序列法; 起承转合东亚戏剧结构), (b) 人物 (想要 vs 需要 / 外在目标 vs 内在缺失, 人物弧光 正 / 负 / 平, flaw-wound-ghost 创伤背景, 主动 vs 被动主角的能动性, Egri 三维人物 生理 / 社会 / 心理, 反派是主角的镜子, 群像与关系网, 人物在压力下的选择中显形), (c) 对白 (潜台词 subtext, 对白即动作与冲突而非信息, 避免太直白 on the nose, 人物独特声口, 信息植入 exposition, Mamet/Sorkin 意图-阻碍式对白, 展示而非告知, 中文剧台词工艺), (d) 场景与序列工艺 (场景是有目标 / 冲突 / 转折的微型故事, 场景价值充能与转折点, 晚进早出, 八序列法, set piece, 转场, 场景头 / 动作行 / 括号提示 格式工艺), (e) 主题与前提 (掌控性理念 / 前提, 主题是被戏剧化的论证而非说教, 道德论证 Truby, 主题统一性, 这到底在讲什么), (f) 类型 (类型惯例是对观众的承诺, Snyder 10 类故事, 颠覆 vs 尊重套路, 类型片 vs 文艺片, 中国类型 主旋律 / 古装 / 年代 / 悬疑 / 甜宠 / 都市 / 军旅 / 历史正剧), (g) 格式与工业流程 (好莱坞剧本格式与 Final Draft, logline 一句话故事, treatment 故事大纲, 节拍表, 分场 / 分集大纲, spec 原创剧本 vs 委托, pitch, coverage, 美剧编剧室与 showrunner 制; 中国 大纲→人物小传→分集大纲→剧本, 长剧集 40 集结构, 网络电影 / 网大, 分账剧, 平台定制剧, 微短剧竖屏短剧), (h) 改稿与开发 (写作就是改写, 改稿 / 润色 / 推倒重写, 处理意见 / 改稿意见, 片方与平台 notes, 杀死你的宝贝, 围读, 开发地狱), (i) 改编 (IP改编 小说 / 漫画 / 游戏改编, 忠于精神而非字句, 压缩, 中国网文 IP 热), (j) 中国影视编剧产业现实 (审查 / 广电总局约束, 备案 / 立项, 平台定制剧 爱优腾芒, 分账, 编剧维权 署名权 / 欠薪 / 枪手, 注水剧, 流量 + 大IP 资本逻辑 vs 原创工艺, 导演中心制 vs 编剧话语权), (k) 编剧职业与工艺生涯 (spec vs 委托, 编剧 vs 编审 / 策划, 单兵 vs 编剧室, 在开发链条中的位置, WGA 与署名仲裁规范, 入行, 中国编剧地位与权益)。跨 电影 / 美剧流媒体 / 中国电影与长剧集。不含 导演 / 摄影 / 制片 / 融资 / 表演 / 电影理论批评为终点 / 泛小说写作 / 纪录片 / 新闻 —— 本 skill 是「戏剧化编剧」工艺: 故事 / 人物 / 场景 / 对白 / 主题 / 结构 / 格式 与围绕它们的产业流程。 (Scriptwriting / Screenwriting for film & TV (影视编剧) — the cognitive operating system of practitioners who write the dramatic blueprint of films, television, and streaming series: the discipline of deciding WHAT story is told, WHO the characters are and why they change, HOW the scenes are dramatized, and WHY it matters thematically — distinct from directing (staging/visual realization), producing (financing/scheduling), and prose fiction (which has no format/scene/visual-action constraints). Covers (a) story & structure theory (Aristotle's Poetics — plot/character/thought + reversal peripeteia/recognition anagnorisis + catharsis; Syd Field's paradigm/three-act/plot points; Freytag's pyramid; Lajos Egri's premise; Robert McKee's Story — controlling idea/the gap/value charge/inciting incident/progressive complications; John Truby's 22 steps & moral argument; Christopher Vogler/Joseph Campbell hero's journey; Blake Snyder's Save the Cat 15-beat sheet; Dan Harmon's story circle; John Yorke's 5-act Into the Woods; Frank Daniel's 8-sequence method; 起承转合 East-Asian dramatic structure), (b) character (want vs need/external goal vs internal lack, character arc positive/negative/flat, 人物弧光, flaw-wound-ghost backstory, agency active vs passive protagonist, Egri's 3-dimensional character physiology/sociology/psychology, antagonist as the protagonist's mirror, ensemble & relationship webs, character revealed through choice under pressure), (c) dialogue (subtext 潜台词, dialogue as action & conflict not information, 'on the nose' avoidance, distinct character voice, exposition handling, Mamet/Sorkin intention-obstacle dialogue, show-don't-tell, 台词 craft in Chinese drama), (d) scene & sequence craft (scene as a mini-story with goal/conflict/turn, scene value charge & turning point, enter-late-leave-early, the 8-sequence method, set pieces, transitions, slug line/action line/parenthetical format craft), (e) theme & premise (controlling idea/premise/前提, theme as dramatized argument not message, moral argument Truby, thematic unity, 'what is this really about'), (f) genre (genre conventions as audience promise, Snyder's 10 story types, subverting vs honoring tropes, 类型片 vs 文艺片, Chinese genres 主旋律/古装/年代/悬疑/甜宠/都市/军旅/历史正剧), (g) format & industry process (Holly

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

Use when implementing "go back" / "rewind" / step-navigation features in a Pixi'VN game, or when you need to read the player-facing dialogue/choice history (e.g. for a backlog or "history log" UI) — covers the History module's `stepHistory` API and the "step" vs "paragraph" goBackMode.

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

Guidance for asking clarifying questions when user requests are ambiguous, have multiple valid approaches, or require critical decisions. Use when implementation choices exist that could significantly affect outcomes.

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

Inspect architectural variances with SMARTS; record only explicit user choices. Report-only requests make no changes.

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

Inspect architectural variances with SMARTS; record only explicit user choices. Report-only requests make no changes.

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

Apply Hick's Law to reduce decision time by limiting the number of simultaneous choices presented to users.

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

Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.

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

Applies the existentialist and feminist philosophy of Simone de Beauvoir, French philosopher and author of The Second Sex. Reach for this skill whenever the user is grappling with existential dilemmas, moral ambiguity, gender dynamics, societal expectations, or relationship ethics. Trigger this skill for questions about freedom versus responsibility, bodily autonomy, marginalization, or when the user feels trapped by external labels or "immanence." Use this to help the user reclaim their agency, recognize the social construction of their situation, and make authentic choices that expand their transcendence while respecting the interconnected freedom of others.

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

Applies the reasoning, mental models, and capital allocation frameworks of Warren Buffett, CEO of Berkshire Hathaway and value investor. Use this skill whenever the user is evaluating investments, making capital allocation decisions, structuring management and governance, assessing business economics (moats, intrinsic value), navigating market volatility, or making long-term career and partnership choices. Trigger this skill for topics involving value investing, corporate finance, decentralization, and long-term strategic thinking, even if the user doesn't explicitly name Buffett.

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

Suede-owned paid-acquisition operating system for channel choice, campaign structure, audiences, bidding, budget pacing, negative keywords, retargeting, and kill-or-scale decisions. Use when planning, auditing, or optimizing paid campaigns on Google, Meta, LinkedIn, X, or comparable platforms. NOT FOR: producing creative variants (use suede-ad-creative), implementing measurement (use suede-analytics), or optimizing the landing page (use suede-site-alchemy).

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

Suede-owned community-growth discipline for member purpose, platform choice, seeding, rituals, moderation, health metrics, and earned advocacy. Use when starting, auditing, or growing a Discord, Slack, forum, subreddit, or comparable product community. NOT FOR: public social-channel content (use suede-social), referral-program mechanics (use suede-referrals), or customer-interview research (use suede-customer-research).

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

Suede-affiliated ethical application of behavioral science to marketing decisions, including framing, anchoring, social proof, loss aversion, choice architecture, and friction. Use when the user needs a named psychological model, an evidence-aware application, and a testable hypothesis. NOT FOR: clinical or mental-health advice, deceptive dark patterns, page implementation (use suede-site-alchemy), or pricing design (use suede-pricing).

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

Brainstorms and debates approaches, then drives toward an actionable decision. Use whenever someone needs a thinking partner for a decision they're facing: 'discuss', 'debate', 'brainstorm', 'weigh options', 'tradeoffs', 'should I do X or Y', 'help me decide', 'I'm torn between', 'sanity check my thinking', or 'what do you think about'. The user must be asking for help reasoning through a choice — not asking to build, fix, evaluate, plan, or modify something (even if the topic involves this skill itself). Picks the right decision lens, surfaces tradeoffs and blind spots, pushes back when reasoning is genuinely weak, and never implements.

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

This skill should be used when the user asks to "direct a motion graphics video", "do creative/art direction for a video", "define a motion language", "set the tone and pacing", "make the animation feel consistent", "decide what to animate (and what not to)", "turn a brief/brand into motion choices", or needs the senior creative judgment that sits above specific techniques (gsap/lottie/shader). Covers motion language, tone & energy, pacing/rhythm, motion hierarchy, restraint, and cross-shot consistency.

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

Infrastructure and development cost estimation for technical projects. Use when planning budgets, evaluating build vs buy decisions, or projecting TCO for architecture choices.

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

Use for Codex models/pricing, scheduled tasks, skills, settings, setup, troubleshooting, customization, automations, and self-knowledge—including 'you,' 'your,' 'this app,' or 'this coding agent' when they refer to Codex—and for OpenAI APIs/products and ChatGPT Work. Also use for model choice/migration, prompting, SDKs, Responses, Realtime, agents, evals, and Chat/Work/Codex comparisons. Do not use for generic app/software tasks that merely mention Codex.

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

Use when a screen design needs variants - how many, one document per variant, what makes two variants genuinely different, recommending one, how the human's choice is read, and narrowing to the chosen one in revision

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

Use when a game task could run on more than one engine or the repository has no engine yet - read the repo's engine and pinned version, and only for a brand-new game pick one from platforms, 2D/3D, team language, scale and licensing.

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

Use when a screen must work without network or a mutation must survive a lost connection - local storage choice, the outbox pattern with idempotency keys, background replay, and how to test it with a fake clock and fake network.

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

Revenue-Centric Design (RCD) — evidence-backed principles for making a SaaS or startup product convert, retain, and monetize. Use when the user works on a landing page or CRO ("my page isn't converting"), onboarding/activation ("users sign up but don't stick"), churn/retention ("customers keep canceling"), pricing/monetization ("how should I price this"), checkout/forms ("dropdowns kill conversion", "annotated checkout"), dashboards/data viz ("cognitive load", "KPI shortlists"), positioning/ICP/go-to-market, feature scope, A/B-test rigor, or AI-era differentiation — or asks for the behavioral-science mechanism behind a design choice. Also use when another skill needs the principle or evidence behind a conversion/retention/pricing/checkout move. Never apply to gambling, betting, or casino products.

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

Spawns the decision-scorer agent after architect proposes 2+ variants in an ADR. Produces a weighted scoring table and recommended choice saved to docs/decisions/.

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

The pinned default technology stack for SMB Product-Builder products. One source of truth so the architect, app-scaffolder, auth-engineer, and senior-dev never re-decide the stack per build — they build ON it. Covers framework, ORM/DB, auth, UI, payments/email/SMS, files, jobs, testing, hosting, and observability, with the chosen default + the one sanctioned alternative for each. Applied whenever a new product is scaffolded or a stack choice would otherwise be improvised. Re-deciding the stack every build is the biggest silent time sink; this kills it.

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