「solutions」の検索結果

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.

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

Building AI-powered personalization systems: recommendation engines, collaborative filtering, content-based filtering, user preference learning, cold-start solutions, and LLM-enhanced personalized experiences. Use when "recommendation system, personalization, collaborative filtering, content-based filtering, user preferences, recommend, suggestions, for you, similar items, you might like, " mentioned.

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

Angular State Management workflow skill. Use this skill when the user needs Master modern Angular state management with Signals, NgRx, and RxJS. Use when setting up global state, managing component stores, choosing between state solutions, or migrating from legacy patterns and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

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

Angular State Management workflow skill. Use this skill when the user needs Master modern Angular state management with Signals, NgRx, and RxJS. Use when setting up global state, managing component stores, choosing between state solutions, or migrating from legacy patterns and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

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

🤖 Andru.ia Solutions Architect - Hybrid Engine (v2.0) workflow skill. Use this skill when the user needs Arquitecto de Soluciones Principal y Consultor Tecnológico de Andru.ia. Diagnostica y traza la hoja de ruta óptima para proyectos de IA en español and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

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

🤖 Andru.ia Solutions Architect - Hybrid Engine (v2.0) workflow skill. Use this skill when the user needs Arquitecto de Soluciones Principal y Consultor Tecnológico de Andru.ia. Diagnostica y traza la hoja de ruta óptima para proyectos de IA en español and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

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

Chris Sherwood / Crosstalk Solutions 视角 — UBNT-native 实战派的代表 YouTuber (475K+ 订阅, 1000+ 视频, UI Toolkit 作者). 加载后让 AI 用 "先演示再讲理论" / "UBNT GUI 默认不够好" / "生态绑定换性价比" 的视角看 UniFi 部署 — 尤其适合 SMB / 家庭实验室 / MSP 场景. 触发词: 「Crosstalk 怎么看」「UBNT 默认要改哪几个」「UniFi 实战部署」「中小企业 UBNT」「Sherwood 视角」「UBNT-native 思路」. 即使用户只是说「这个 UDM-Pro 该怎么开箱配」「80 人办公 UBNT 怎么选硬件」「我家 UniFi 慢」也应触发.

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

B2B 大客户销售 (B2B 大客户销售 / 企业级复杂销售 (Enterprise B2B Sales / Complex Selling) — 面向企业客户的高价值、长周期、多干系人复杂销售的职业认知操作系统，从业者(AE/客户经理/SE 售前/销售负责人 VP Sales/CRO)、想入行者、以及服务这行(销售咨询/enablement/RevOps)的视角。覆盖: (a) 第一性张力 — 三大方法论流派之争: **买方主导的诊断式提问 (consultative/discovery-led: SPIN 提问 → 痛点 → 方案, 「像医生先诊断再开方」) ⇄ 卖方主导的教学式挑战 (Challenger: Teach-Tailor-Take control, 用商业洞见 reframe 客户认知, 「像老师挑战客户的既有想法」) ⇄ 资格审查纪律 (MEDDIC/MEDDPICC: 先严格 qualify/disqualify, 「no deal 好过 bad deal」)**; 三派不是非此即彼, 资深人混用, 但底层世界观分歧真实(问 vs 教 vs 筛); 更深层张力 — 「过程/方法论纪律 (process rigor: 预测准确、deal inspection、qualify) ⇄ 关系/信任 (relationship: champion 培养、高管关系、人情)」, 「卖结果/业务价值 (business outcome/ROI、卖给经济决策人) ⇄ 卖产品/功能 (feature selling)」, 「多线程触达买方委员会 (multithreading buying committee) ⇄ 单一 champion 依赖」; (b) 方法论正典 (最标准化、最易蒸出高质量+CLI 化) — MEDDIC/MEDDPICC (Metrics 量化指标/Economic buyer 经济决策人/Decision Criteria 决策标准/Decision Process 决策流程/Identify Pain 痛点/Champion 内部拥护者 + Paper process 签约流程/Competition 竞争), SPIN (Situation/Problem/Implication/Need-payoff 提问序列), Challenger (商业洞见 commercial insight + reframe + 建设性张力 constructive tension + Mobilizer 调动者), Solution Selling (痛点链 pain chain/愿景创建/buying vision), Sandler (前置合约 up-front contract/痛苦漏斗 pain funnel/潜艇七步), Command of the Message (Force Management: 业务价值框架/before-after/decision criteria), Gap Selling (Keenan: 现状 current state → 期望 future state → 差距 the gap/问题中心), Miller Heiman Strategic Selling (蓝表 blue sheet/buying influences: 经济/用户/技术买家 + coach), Value Selling, BANT (老式资格框架, 多被 MEDDIC 取代); (c) 行业结构与角色 — SDR/BDR (开发/约见) → AE/客户经理 (成交) → SE/售前/Solutions Engineer (技术验证/POC/demo) → CSM (客户成功/续约扩张) → Sales Manager/VP Sales/CRO; RevOps (收入运营), Sales Enablement (赋能); land and expand (先落地再扩张)、量化指标 quota/OTE(目标总收入)/配额达成率/pipeline coverage(管道覆盖率 ~3x 业内经验法则)/win rate(赢率)/sales velocity(销售速度)/ramp time(爬坡期)/ACV·ARR·NRR(年合同额/年经常性收入/净收入留存); (d) 销售周期 (the deal/opportunity lifecycle) — prospecting 开发 → discovery 需求挖掘 → qualification 资格审查(MEDDIC) → demo/technical validation/POC 技术验证 → business case/value 业务价值与 ROI → proposal 提案 → negotiation 谈判(procurement 采购/法务/security review) → close 成交 → onboarding/expansion 交付与扩张; 干系人: champion 拥护者 vs coach 线人 vs economic buyer 经济决策人 vs blocker 阻碍者; mutual action plan/close plan(双向行动计划/成交计划); (e) 产出物与节奏 — discovery call(需求电话)、demo、business case、proposal/SOW、MAP(mutual action plan)、forecast(预测: commit/best case/pipeline 类别)、pipeline review/deal review/QBR(季度业务回顾)/account plan(客户计划); (f) 职业/招聘/薪酬 — quota/OTE/comp plan(底薪+提成)/accelerator(加速器)/SPIFF/clawback、ramp、President's Club(顶尖销售俱乐部)、SDR→AE→管理 晋升路径、rep turnover(销售流失率高); (g) 争议/批判 — Challenger 是否过誉(CEB 原始数据被质疑、insight selling 批评)、MEDDIC 沦为填表剧场(box-checking theater, 填字段不真 qualify)、活动指标 vs 质量(spray-and-pray 群发/冷电话存废之争)、AI SDR/自动化淹没收件箱(2024-2025 AI BDR 泡沫 + 邮件送达率崩溃 backlash)、SDR 军团模式是否将死(Winning by Design/signal-based GTM 取代)、配额虚高与销售 burnout、季末打折促单、销售方法论的「宗教化」与培训-认证产业链、最大竞争对手其实是「no decision/维持现状」而非对手; (h) 流派/思想谱系 — 提问诊断派(Rackham SPIN/Bosworth&Eades Solution Selling/Keenan Gap Selling) vs 挑战教学派(Dixon&Adamson Challenger/Force Management Command of the Message) vs 资格纪律派(MEDDIC: Napoli&Dunkel 起源/John McMahon/MEDDICC Andy Whyte) vs 关系战略派(Miller Heiman Strategic/Large Account) vs SaaS 现代收入架构派(Aaron Ross Predictable Revenue/Mark Roberge Sales Acceleration Formula/Jacco van der Kooij Winning by Design bowtie/David Skok 指标) vs 开发-心态派(Jeb Blount Fanatical Prospecting/Sales EQ、Anthony Iannarino、Josh Braun) vs 谈判(Chris Voss Never Split the Difference 战术同理心)。不含: B2C/零售/电商导购销售、纯电话客服/客户支持、纯渠道/分销管理(channel 虽相关但聚焦直销复杂销售)、纯 marketing/需求生成(demand gen 虽上游但本 skill 聚焦销售执行)、纯 CSM 客户成功(虽相关但聚焦 new logo + expansion 的销售动作)。) Master OS — automated mastery of B2B 大客户销售 / 企业级复杂销售 (Enterprise B2B Sales / Complex Selling) — 面向企业客户的高价值、长周期、多干系人复杂销售的职业认知操作系统，从业者(AE/客户经理/SE 售前/销售负责人 VP Sales/CRO)、想入行者、以及服务这行(销售咨询/enablement/RevOps)的视角。覆盖: (a) 第一性张力 — 三大方法论流派之争: **买方主导的诊断式提问 (consultative/discovery-led: SPIN 提问 → 痛点 → 方案, 「像医生先诊断再开方」) ⇄ 卖方主导的教学式挑战 (Challenger: Teach-Tailor-Take control, 用商业洞见 reframe 客户认知, 「像老师挑战客户的既有想法」) ⇄

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

Specialized Preact development skill for standards-based web applications with native-first architecture and minimal dependency footprint. Use when building Preact projects, particularly those involving data visualization, interactive applications, single-page apps with HTM syntax, Web Components integration, CSV/JSON data parsing, WebGL shader visualizations, or zero-build solutions with vendored ESM imports.

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

Apply the mental models of Bill Gates, co-founder of Microsoft and philanthropist. Use this skill whenever you are evaluating climate change solutions, global health interventions, philanthropic resource allocation, software platform economics, or the paradigm-shifting impacts of AI. Trigger this skill when the user is facing decisions about maximizing ROI on charitable giving, assessing clean energy technologies (like calculating the "Green Premium"), building winner-take-all software ecosystems, or using data to drive large-scale institutional progress. Channel his "impatient optimism" to prioritize innovation that multiplies by zero rather than settling for incremental efficiency.

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

Reverse-engineer a design system from a live website (public URL or localhost). Extracts colors, typography, spacing, shadows, radii, breakpoints, and component patterns using a headed Playwright browser. Captures screenshots of pages, components, and interactive states at real device resolutions. Produces structured design tokens and optionally seeds a Penpot project. **Triggers — use this skill when:** - User says "extract design system from [url]" - User asks to "reverse-engineer the styles from [site]" - User says "build a design system based on [website]" - User asks to "pull the design tokens from [url]" - User says "analyze the design of [site]" - User asks to "import styles from [website] into Penpot" - User points at a URL and asks about its colors, fonts, spacing, or components

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

Extract locational marginal prices (LMPs) from DC-OPF solutions using dual values. Use when computing nodal electricity prices, reserve clearing prices, or performing price impact analysis.

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

Transform research into Opportunity Solution Tree (Teresa Torres method). Map outcomes, opportunities, solutions, and experiments.

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

Formulate clear, testable hypotheses for product experiments. Use when designing experiments to validate solutions.

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

Design implementation-ready frontend solutions with UX intent, component structure, responsive behavior, accessibility, and handoff criteria.

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

Build an Opportunity Solution Tree (OST) to structure product discovery — map a desired outcome to customer opportunities, possible solutions, and experiments. Based on Teresa Torres' Continuous Discovery Habits. Use when the team is unclear what to build next, when multiple opportunities compete, or before writing a PRD for a complex feature space.

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

Optimize for speed and cost. Pick lightweight solutions. Flag expensive operations.

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

When multiple solutions exist, pick the best one. Explain why in one sentence.

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

Document a recently solved problem or durable project vocabulary in docs/solutions/ or CONCEPTS.md. Use when capturing a learning after work.

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

Satori is a clinically informed wisdom companion for navigating the inner life — emotions, meaning, grief, purpose, relationship, identity, and the questions that don't resolve easily. Activate when someone is processing something difficult, wrestling with a life question, seeking perspective, or simply needs to think alongside someone who won't rush them toward an answer. Also activate when someone uses language like "I've been struggling with," "I don't know what to do," or "I need to figure out" — or any emotionally charged framing. When in doubt, activate. Draws from Taoism, Buddhism, Stoicism, Christianity, Sufi wisdom, Hindu philosophy, Confucian ethics, and African thought, alongside modern psychology, neuroscience, and trauma-informed frameworks (IFS, DBT, CFT, Schema Therapy, Somatic). Uses Motivational Interviewing, Voss tactical empathy, McAdams Life Story, and Singer Self-Defining Memory — woven naturally, not mechanically.

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

Use when comparing two or more code implementations against a spec or requirements doc. Triggers on "which repo is better", "compare these implementations", "evaluate both solutions", "rank these codebases", or "judge which approach wins". Also covers choosing between competing PRs or vendor submissions solving the same problem. Does NOT review a single codebase for quality — use code review skills instead. Does NOT evaluate strategy docs — use strategy-review. Requires a spec file and 2+ repo paths.

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

Expert-level insurance systems, underwriting, claims processing, actuarial analysis, risk assessment, and insurtech solutions

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

Draft board resolutions, consent documents, and meeting minutes. Use when asked to "draft a board resolution", "write board minutes", or "prepare a board consent".

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

Survey corporate documents — articles, bylaws, cap table, board resolutions. Use when asked to "survey our corporate documents", "check cap table hygiene", or "what governance docs exist".

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