「mind」の検索結果

World-class growth strategy expertise combining Andrew Chen's marketplace and network effects wisdom, Brian Balfour's growth frameworks, Casey Winters' Pinterest/Grubhub playbooks, and the best of Silicon Valley growth thinking. Growth is not marketing. Growth is the systematic application of product, engineering, and data to create compounding user acquisition, activation, and retention. It's a mindset, not a department. Use when "growth strategy, how do we grow, acquisition strategy, retention strategy, viral growth, network effects, growth loops, product-led growth, plg, ltv cac, unit economics, growth model, flywheel, compound growth, channel strategy, referral program, activation rate, magic moment, aha moment, growth experimentation, growth, strategy, acquisition, retention, viral, network-effects, plg, loops, experimentation" mentioned.

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

World-class accessibility design expertise combining the inclusive design principles of Microsoft's Inclusive Design team, the technical rigor of the W3C WCAG working group, and the lived experience perspective of disability advocates. Accessibility is not a feature - it's a fundamental quality attribute that makes products usable by everyone. Great accessibility design is invisible to those who don't need it and essential to those who do. It benefits everyone: captions help in noisy environments, keyboard navigation helps power users, high contrast helps in bright sunlight. When you design for the extremes, you improve the experience for all. Accessibility is not a checklist - it's a mindset that asks "who are we excluding?" at every design decision. Use when "accessibility, a11y, wcag, screen reader, keyboard navigation, color contrast, alt text, aria, focus management, skip link, assistive technology, inclusive design, ada compliance, section 508, accessible, voiceover, nvda, jaws, tab order, focus trap, accessibility, a11y, wcag, inclusive-design, screen-reader, keyboard-navigation, color-contrast, aria, focus-management, assistive-technology" mentioned.

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

Create and edit JSON Canvas files (.canvas) with nodes, edges, groups, and connections. Use when working with .canvas files, creating visual canvases, mind maps, flowcharts, or when the user mentions Canvas files in Obsidian.

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

Checks production-bound code for observability, error handling at system boundaries, input validation, graceful degradation, and resource management, scaled to the project's real stakes. Use before declaring a production feature done.

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

产品营销 (PMM, Product Marketing) — 拥有「产品如何被定位 / 表达 / 发布 / 卖进市场」的从业者认知操作系统: 是产品 / 销售 / 市场 / 客户之间的连接组织, 负责把产品能力翻译成市场价值, 并把市场声音带回产品。覆盖 (a) 定位与差异化 (April Dunford 「刻意选择语境」框架 + 竞争性替代方案 + 卖价值不卖功能 + 选择「让你优势成立的市场参照系」, 对照 Ries & Trout 经典「定位是占领心智」), (b) 信息传递与叙事 (messaging 层级 / 信息屋 + 价值主张 + 收益导向 vs 战略叙事「换框架」Andy Raskin + 表达清晰度 Emma Stratton / Punchy + 初创 homepage 定位 FletchPMM), (c) 进入市场 (GTM) 策略与产品发布 (发布分级 T1/T2/T3 + 发布流程与跨职能编排 + GTM 打法 PLG vs SLG vs 混合 + 滩头细分选择), (d) 市场与竞争情报 (竞品分析 + battlecard 战卡 + 输赢分析 win/loss + 竞争赋能 Klue/Crayon/Clozd), (e) 买家与客户研究 (ICP 理想客户画像 + 买家 / 用户 persona + Jobs-to-be-Done 任务理论 Christensen/Moesta/Ulwick ODI + 客户之声 VoC + 用真实买家测信息 Wynter/Peep Laja), (f) 销售赋能 (战卡 + pitch / 销售 deck + 一页纸 + demo 叙事 + 异议处理 + 销售培训 + 内容采用率 — 你的产出只值销售实际用到的那部分), (g) 定价与打包 (价值定价 + 打包分层 + 《Monetizing Innovation》Ramanujam/Simon-Kucher + PLG 定价 — 常与产品 / 财务共担), (h) 细分与品类 (市场细分 + TAM/SAM/SOM + 技术采用生命周期与跨越鸿沟 Geoffrey Moore + 品类设计与叙事 Play Bigger / Christopher Lochhead — 稀有且昂贵, 不是默认选项), (i) 需求生成与内容协同 (campaign 信息 + 思想领导力 + 漏斗内容 TOFU/MOFU/BOFU + ABM 基于客户营销), (j) 分析师与影响者关系 (Gartner 魔力象限 + Forrester Wave + 分析师 briefing — To B 场景, 对 pay-to-play 影响诚实标注), (k) 客户营销与倡导 (参考客户 + case study + 评测站 G2/TrustRadius/Capterra 运营 + 社区), (l) PMM 运营与度量 (影响管道 + 赢率 + 发布采用率 + 信息穿透率 + 角色汇报线「向产品还是向市场」之争 + PMM 作为战略职能 vs 接单工具人陷阱); 跨 B2B SaaS (该学科重心) / B2C 消费 / 开发者 PLG / 平台产品。不含 产品管理 (PM 造产品 / 拥有 roadmap, PMM 拥有市场 — 相邻且极易混淆) / 增长 / 效果营销 / 付费投放 (平行学科) / 品牌 / 企业传播 / 公关为终点 / 需求生成为终点 (PMM 与之协同但不等同) / 平面设计 /「做 slide 和周边的团队」(PMM 抗争的接单工具人窄化) / 泛泛「市场营销」。 (Product Marketing (PMM) — the cognitive operating system of practitioners who own how a product is positioned, messaged, launched, and sold into a market: the connective tissue between product, sales, marketing, and customers, responsible for translating product capability into market value and bringing the voice of the market back into product. Covers (a) positioning & differentiation (April Dunford's deliberate-context framing, competitive alternatives, value-not-features, framing the market in which your strengths matter — vs Ries & Trout classic perception-in-the-mind positioning), (b) messaging & narrative (messaging hierarchy / house, value proposition, benefit-led vs strategic-narrative / change-the-frame messaging Andy Raskin, clarity craft Emma Stratton/Punchy, homepage & startup positioning FletchPMM), (c) go-to-market (GTM) strategy & product launches (launch tiers T1/T2/T3, launch process & cross-functional orchestration, GTM motion PLG vs SLG vs hybrid, beachhead segment selection), (d) market & competitive intelligence (competitive analysis, battlecards, win/loss analysis, competitive enablement Klue/Crayon/Clozd), (e) buyer & customer research (ICP ideal customer profile, buyer & user personas, Jobs-to-be-Done Christensen/Moesta/Ulwick ODI, voice of customer, message testing with real buyers Wynter/Peep Laja), (f) sales enablement (battlecards, pitch & sales decks, one-pagers, demo narratives, objection handling, sales training, content adoption — output is only as good as what sales actually uses), (g) pricing & packaging (value-based pricing, packaging & tiering, Monetizing Innovation Ramanujam/Simon-Kucher, PLG pricing — often shared with product/finance), (h) segmentation & category (market segmentation, TAM/SAM/SOM, technology adoption lifecycle & crossing the chasm Geoffrey Moore, category design & narrative Play Bigger / Christopher Lochhead — rare and expensive, not a default), (i) demand-gen & content partnership (campaign messaging, thought leadership, funnel content TOFU/MOFU/BOFU, ABM account-based marketing), (j) analyst & influencer relations (Gartner Magic Quadrant, Forrester Wave, analyst briefings — for B2B, with honest read on pay-to-play perception), (k) customer marketing & advocacy (references, case studies, reviews G2/TrustRadius/Capterra presence, community), (l) PMM operations & metrics (influenced pipeline, win rate, launch adoption, message pull-through, the role's reporting line product-vs-mark

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

摄影 (摄影 (Photography) — 以静态影像为产出的视觉创作 + 服务行业：从看见 → 用光 → 构图 → 拍摄 → 后期 → 交付的认知操作系统，覆盖商业摄影 (commercial: 产品/广告/电商/美食)、人像摄影 (portrait: 影楼/写真/婚礼/时尚/环境人像)、纪实与街头摄影 (documentary/photojournalism/street)，以及与之贯通的风光、新闻、艺术摄影。面向职业摄影师 / 助理 / 修图师 / 想转职业的资深爱好者 / 服务这行的人 (器材厂商、图库、后期外包、影楼运营)。覆盖: (a) 第一性张力 — **光 (light is the craft — 看光、控光、塑光：硬光/柔光、方向、色温、光比、布光是摄影第一性) ⇄ 器材 (gear — 相机/镜头/灯具迷信, 'GAS' gear-acquisition-syndrome, 'the best camera is the one you have with you' — 器材不是摄影)**; **决定性瞬间/抓取 (decisive moment, Cartier-Bresson, 等待与预判, 纪实/街头不可重来) ⇄ 构建/导演 (constructed/directed, 商业与人像是布光摆姿造光的'制造'而非'捕获')**; **前期/拍对 (get it right in camera, 曝光/白平衡/构图当场拍对) ⇄ 后期/暗房 (post/darkroom, Ansel Adams 'negative is the score, print is the performance' — RAW 冲洗/调色/修图是创作一半)**; **作者性/艺术表达 (vision, personal voice, 'photograph what you feel not what you see') ⇄ 服务性/商业交付 (client brief, 影楼标准化出片, 'shoot the brief not your ego', 摄影是生意)**; **真实/未操纵 (truth, photojournalism ethics, 不过度 PS, 新闻摄影伦理) ⇄ 修饰/理想化 (retouch, 商业人像液化磨皮, 广告的'谎言')**; **决定性技术参数 (曝光三角 aperture/shutter/ISO, 景深, 互易律) ⇄ 看见/眼力 (seeing, 'photography is about seeing not cameras', 构图/光感是 tacit 眼力)**; **胶片/慢/不可见 (film, 慢工, 不可即时回看, 暗房) ⇄ 数码/即时/海量 (digital, chimping, 连拍, 后期无限)**; AI 对摄影的冲击 ('是不是摄影'、生成式填充/换天/AI 修图、真实性危机); (b) 核心工作流 / pipeline (最标准、最易蒸高质量+CLI 化) — 通用链: 看光选光 → 曝光三角决策 (光圈定景深/快门定动静/ISO 兜底) → 测光与曝光 (评价/点测光, 向右曝光 ETTR, 直方图, 区域系统) → 构图 (三分法/引导线/框架/负空间/前景) → 对焦 → 拍摄 → 选片 culling → RAW 后期 (Lightroom/Capture One: 曝光/白平衡/色调曲线/HSL/局部) → 精修 retouch (Photoshop: 频率分离/液化/D&B) → 调色 grading → 输出交付 (色彩管理/sRGB/打印/图库上传); 子流派 SOP: 影棚商业布光 (主光/辅光/轮廓光/背景光, 三点布光, 光质修饰器 softbox/beauty-dish/grid)、婚礼/纪实一天流程、街头扫街、产品/电商台面、人像引导摆姿 posing & direction; (c) 工具栈 — 相机系统 (无反主导: Sony A 系 / Canon R / Nikon Z / 富士 X&GFX / 徕卡 M; 中画幅 Phase One/Hasselblad/GFX 商业; 残幅 vs 全幅 vs 中幅)、镜头 (大三元, 定焦 vs 变焦, 35/50/85 人像三剑客, 微距, 移轴)、灯具 (机顶闪 Godox/Profoto, 影室灯, 常亮 LED, 持续光 vs 闪光)、修饰器 (柔光箱/反光伞/束光筒/雷达罩/旗板)、测光/附件 (测光表, 灰卡, 三脚架, 滤镜 ND/CPL/渐变)、后期软件 (Adobe Lightroom Classic/CC 主导, Capture One 商业/影室, Photoshop 精修, DxO PhotoLab/PureRAW 降噪, Capture One vs Lightroom 之争, 国产: 醒图/泼辣 Polarr/Snapseed 移动端, RawTherapee/Darktable 开源, AI: Lightroom 生成式/Photoshop Generative Fill/Topaz Photo AI/Gigapixel/Luminar Neo)、色彩管理 (X-Rite/Calibrite 校色仪, ICC, 显示器)、图库/交付 (Pixieset/图虫/500px/视觉中国/Getty/Adobe Stock, 客片在线选片); (d) 知识正典 — Ansel Adams 'The Camera / The Negative / The Print' 三部曲 + 区域系统 (Zone System)、Henri Cartier-Bresson 'The Decisive Moment'、Michael Freeman 'The Photographer's Eye' (构图) 'The Photographer's Mind'、Bryan Peterson 'Understanding Exposure' (曝光入门圣经)、Scott Kelby 'Digital Photography Book' 系列 + Lightroom/Photoshop 书、Joe McNally 'The Hot Shoe Diaries / Sketching Light' (闪光灯)、Light Science & Magic (布光科学经典教材)、Roland Barthes 'Camera Lucida' (摄影哲学)、Susan Sontag 'On Photography'、John Szarkowski 'The Photographer's Eye'、National Geographic 摄影指南、Robert Capa / Sebastião Salgado / Steve McCurry (纪实)、Annie Leibovitz / Richard Avedon / Peter Lindbergh (人像/时尚)、Galen Rowell / Ansel Adams (风光); (e) figures/流派 — 风光/系统派 (Ansel Adams 区域系统奠基、Galen Rowell 探险风光、Marc Adamus); 决定性瞬间/纪实街头派 (Henri Cartier-Bresson 奠基、Robert Capa 战地、Sebastião Salgado 社会纪实、Steve McCurry、Vivian Maier、Daido Moriyama、森山大道/荒木经惟 日本派、Vivian Maier); 人像/时尚派 (Richard Avedon、Annie Leibovitz、Peter Lindbergh、Platon、Joey L、Lindsay Adler 时尚布光); 布光/教育派 (Joe McNally、Zack Arias 'one light'、Profoto/strobist David Hobby 'Strobist' 闪光灯启蒙博客、Karl Taylor 商业布光教学); 商业/广告派 (Chase Jarvis 'CreativeLive'创办+'best camera'、Joel Grimes、Tim Wallace 汽车); 后期/修图派 (Pratik Naik、Aaron Nace 'Phlearn'); 街头当代派 (Eric Kim 街头博客、Joel Meyerowitz、Saul Leiter 色彩街头); 中文圈 (李涛 'photoshop教学'、宁思潇潇 器材评测、thomas 'Thomas看看世界' 风光后期、阿刘 风光、668 人像); 哲学/批评 (Susan Sontag、Roland Barthes、John Szarkowski MoMA); (f) 行业话术/黑话 — 曝光三角 exposure triangle / 光圈 aperture f-stop / 快门 shutter speed / 感光度 ISO / 景深 DoF depth of field / 焦段 focal length / 等效 / 全画幅 full-frame vs 残幅 crop / 大三元 / 定焦 prime / 互易律 reciprocity / 向右曝光 ETTR / 直方图 histogram / 高光溢出 clipping / 动态范围 dynamic range / 宽容度 / 白平衡 WB

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

独立开发者与微型 SaaS — 单人或极小团队 (≤3 人) 构建可持续订阅收入的软件产品商业, 有别于自由职业/咨询、企业级 SaaS 和开源维护: (a) 产品发现与验证 (自己的痒 vs 市场优先 Nugent/Walling; 着陆页冒烟测试; 先接 Stripe 再写代码; JTBD 访谈适配独立开发者场景; Reddit/HN/X/社区痛点挖掘; Mom Test 验证框架; 公开构建作为验证机制); (b) 独立开发者技术架构 (无聊技术论 McKinley; 单体优先; serverless vs VPS 在 ≤$100/月预算下的取舍; Rails/Django/Laravel/Next.js 等框架的出货速度选型; 托管服务优先于自建; Supabase/PlanetScale/Neon 数据库即服务; Clerk/Auth0 认证即服务; Stripe/Paddle/LemonSqueezy 支付; Vercel/Fly.io/Railway 部署; AI 辅助编码 Cursor/Copilot 作为力量倍增器); (c) 无营销团队的分发与增长 (SEO 作为微型 SaaS 护城河; Product Hunt 发布; AppSumo 终身授权利弊; 冷邮件; Twitter/X 公开构建; IndieHackers 社区分发; 集成市场 Shopify/WordPress/Zapier/Slack 应用目录; 联盟计划; 一人内容营销); (d) 定价与变现 (SaaS 定价心理学; freemium vs 免费试用 vs 纯付费; 按席位 vs 按用量 vs 固定费率; 年付折扣; 老用户保价; 微型 SaaS 流失率控制; MRR/ARR/LTV/CAC 在微型规模的含义; $10K MRR 里程碑心理学); (e) 独立创始人心智模型与生活设计 (default alive vs default dead Graham; 拉面盈利 Levels; 生活方式生意 vs 增长生意的光谱; 独立开发者倦怠预防; 时间管理与上下文切换成本; 地理套利与远程优先; 一次构建反复销售的资产思维; 社区作为支持网络 IndieHackers/WIP/MicroConf); (f) 法务与运营基础 (公司注册地选择 LLC/Ltd/GmbH 税效; Stripe Atlas vs Firstbase vs 本地律师; 服务条款与隐私政策; GDPR/CCPA 低成本合规; 知识产权基础; 首次雇人的承包商 vs 员工选择; 独立开发者会计 SaaS — Xero/QuickBooks; 多辖区税务义务)。中国独立开发者生态: 出海作为主导策略 (从中国构建面向全球市场的产品以避开国内竞争/监管); 即刻/V2EX/少数派作为社区枢纽; 微信小程序作为替代分发; 小报童/爱发电作为中文市场变现; 人民币定价心理学; 支付宝/微信支付集成; ICP 备案要求; 中国区 App Store 审核差异; 独立开发者周刊。诚实处理: 生存偏差 (每一个 Pieter Levels 背后是数千个从未达到 $1K MRR 的人), AI 对微型 SaaS 生态位的颠覆 (wrapper 产品脆弱), 独自构建的孤独与心理健康成本, 公开构建的表演性质 vs 真正透明, AppSumo 终身授权上瘾毁坏单位经济, 样板代码销售的伦理边界。不含: 企业级 SaaS (不同 GTM/销售/融资模型), 不含: 自由职业/咨询 (用时间换钱非建资产), 不含: 开源维护 (不同可持续性模型), 不含: 风投支持的创业 (不同增长期望), 不含: 无代码/低代码平台构建 (相邻但不同受众), 不含: 内容创作作为主业。 (Independent Developer and Micro-SaaS — the craft of single-person or tiny-team (≤3 people) software product businesses that generate sustainable recurring revenue without venture capital, distinct from freelancing/consulting, enterprise SaaS, and open-source maintainership: (a) product discovery and validation (scratching your own itch vs market-first Nugent/Walling; landing page smoke tests; Stripe checkout before code; Jobs-to-Be-Done interview adapted to solo context; Reddit/HN/X/community pain-point mining; idea validation frameworks Fitzpatrick Mom Test; build-in-public as validation mechanism); (b) technical architecture for solo operators (boring technology thesis Mckinley; monolith-first; serverless vs VPS tradeoffs for ≤$100/mo infra; framework selection for shipping speed — Rails/Django/Laravel/Next.js/Remix/SvelteKit; managed services over self-hosted whenever possible; database-as-a-service Supabase/PlanetScale/Neon/Turso; auth-as-a-service Clerk/Auth0/Supabase Auth; payment integration Stripe/Paddle/LemonSqueezy; deployment Vercel/Fly.io/Railway/Render; monorepo vs polyrepo for solo; AI-assisted coding Cursor/Copilot as force multiplier); (c) distribution and growth without a marketing team (SEO as moat for micro-SaaS Ahrefs-style content marketing on 1-person budget; Product Hunt launches; AppSumo lifetime deals tradeoffs; cold email outreach; Twitter/X building in public; IndieHackers community distribution; integration marketplaces Shopify/WordPress/Zapier/Slack app directories as channels; affiliate programs; content marketing at scale-of-one); (d) pricing and monetization (SaaS pricing psychology Patel/Campbell; freemium vs free trial vs paid-only; per-seat vs usage-based vs flat-rate; annual discount strategies; grandfathering existing customers; churn reduction for micro-SaaS — Baremetrics/ProfitWell/ChartMogul analytics; MRR/ARR/LTV/CAC at micro scale; the $10K MRR milestone psychology); (e) solo founder mental model and lifestyle design (default alive vs default dead Graham; ramen profitability Levels; lifestyle business vs growth business spectrum; burnout prevention for solo operators — no team to delegate to; time management and context-switching costs; geographic arbitrage and remote-first; the 'build once sell twice' asset mindset; community as support network IndieHackers/WIP/MicroConf); (f) legal and operational basics (incorporation LLC/Ltd/Gm

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

Captures and organizes chaotic brain dumps into a structured, actionable system with zero information loss. Use this skill whenever the user says 'capture this', 'brain dump', 'let me dump some ideas', 'I've got a bunch of thoughts', 'here's everything on my mind', 'idea dump', 'let me get this out of my head', 'I need to organize my thoughts', 'here's what I'm thinking', or any variation where someone is unloading a messy stream of ideas, tasks, thoughts, and plans wanting them turned into something coherent. Also trigger when the user pastes or dictates a long, unstructured block of mixed ideas — even without the exact phrase — the intent is the same. Fast-to-action by design: no upfront intake. Output is four sections (Projects/Ideas, Tasks, Connections, How I Can Help) ending with a directive question. Asks at most one mid-organization clarifying question when a single item is genuinely ambiguous between task and project.

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

Generate diagrams as valid Excalidraw JSON — flowcharts, architecture, ER diagrams, mind maps, sequence diagrams, wireframes, C4 models, and more. Don't use for draw.io/Mermaid output, slide decks, or pixel-perfect brand graphics.

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

Generate a diagram and route to the right engine — draw.io XML (precise, editable, C4, swimlanes) or Excalidraw JSON (hand-drawn, sketch, wireframes). One entry for flowcharts, architecture, ER, sequence, mind maps. Don't use for Mermaid or slides.

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

Generate professional diagrams as valid draw.io XML — flowcharts, architecture, C4 models, ER diagrams, sequence diagrams, mind maps, and swimlanes. Don't use for Excalidraw or Mermaid output, hand-drawn sketch styles, or slide decks/presentations.

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

This skill channels the strategic and scientific reasoning of Demis Hassabis, CEO and co-founder of Google DeepMind, AlphaGo and AlphaFold, and 2024 Nobel Prize in Chemistry. Use this skill whenever you are evaluating AI for scientific discovery, tackling "root node" problems, designing reinforcement learning systems, or discussing AGI timelines, safety, and global governance. Reach for it when the user faces massive combinatorial search spaces, wants to apply AI to physical/biological sciences (like digital biology), or needs to balance rapid AI scaling with the rigorous scientific method. Apply these mental models to shift the focus from building consumer apps to using AI as the ultimate meta-solution for understanding reality.

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

Applies the Neoplatonic and mathematical reasoning of Hypatia of Alexandria. Use this skill whenever the user is grappling with the pursuit of truth, foundational logic, the hierarchy of knowledge, or the distraction of superficial and physical desires versus deeper intellectual pursuits. Trigger this when discussing mathematics as a foundation for higher understanding, astronomy, overcoming base impulses, or seeking the ultimate source of truth. It is highly relevant for questions about rigorous intellectual discipline, esoteric philosophy, and elevating one's mind above material distractions.

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

Applies the engineering and research philosophies of Jeff Dean, Chief Scientist at Google DeepMind and Google Research. Reach for this skill whenever you are designing large-scale distributed systems, optimizing latency and energy efficiency, or making architectural decisions about machine learning infrastructure. It should trigger automatically for topics involving hardware-ML co-design, model distillation, sparse activation, massively multi-task models, or scaling systems by 5x to 10x. Use this skill to evaluate system bottlenecks, transition from specialized to unified models, and optimize experimental velocity. Apply his mental models to avoid premature 100x scaling and to treat AI models as reasoning engines rather than memorization databases.

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

Applies the reasoning of David Silver, lead researcher on AlphaGo and AlphaZero at DeepMind, to problems of AI design, reinforcement learning, and open-ended discovery. Use this skill whenever you are designing AI systems, evaluating learning algorithms, balancing exploration vs. exploitation, choosing research problems, or discussing how to break past human performance ceilings. Reach for this whenever the user asks about self-play, Monte-Carlo Tree Search, tabula rasa learning, AGI, or moving from human-curated data to autonomous experience. It helps shift the focus from hardcoding human knowledge to building systems that learn for themselves.

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

Turns open-ended requests into things to think WITH instead of answers to accept. Audits the hidden assumptions inside a topic, inverts them into sharp "what if" provocations, branches each one outward, and delivers a fully-expanded mind map image plus the written wonderings. Fire this when the person signals they want to open up a space and think alongside you — "wonder about X", "what are the weird angles on X", "help me think about what this could be", "I want to explore, not decide yet" — or when they invoke /wonder or /wonderpill. Do NOT fire when the same topic is attached to a request for concrete, usable, or decided output: a named deliverable, a count ("give me 5 names"), a deadline ("ideas I can ship this week"), or a "which / what should I pick" question — those want straight answers, not a wonder pill. When it is genuinely unclear which they want, this skill opens by asking one line rather than branching. Not for factual lookups or executing a plan already chosen.

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

Turns open-ended requests into things to think WITH instead of answers to accept. Audits the hidden assumptions inside a topic, inverts them into sharp "what if" provocations, branches each one outward, and delivers a mind map plus written wonderings. Portable version, no vendor-specific tools required, works on any conversational assistant. Fire this when the person signals they want to open up a space and think alongside the assistant: "wonder about X", "what are the weird angles on X", "help me think about what this could be", "I want to explore, not decide yet". Do NOT fire when the same topic is attached to a request for concrete, usable, or decided output: a named deliverable, a count ("give me 5 names"), a deadline, or a "which / what should I pick" question. When it is genuinely unclear which they want, this skill opens by asking one line rather than branching. Not for factual lookups or executing a plan already chosen.

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

This skill should be used when sending images, files, or notifications back to the user via messaging platforms (Discord, Feishu, Telegram, etc.) through cc-connect. TRIGGER when agent generates a plot/chart/screenshot and wants to show the user; agent creates a report/PDF/file the user should receive; agent needs to proactively notify the user (e.g. task completed, alert, reminder); user asks to "send image", "show me the chart", "notify me", "send the file", "send to Telegram", "show plot in Discord".

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

Analyze startups with Paul Graham mindset (pressure, founder-market fit, brutal validation), Dan Koe discipline (monetization, offer, distribution, sales), and Seth Godin principles (differentiation, narrative, smallest viable audience). Triggers on startup idea, business validation, MVP, first customers, revenue model, GTM, product-market fit, "I have an idea".

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

Onboarding-and-switching playbook for SMB Product-Builder products. Defines the first-run experience that turns a prospect leaving an incumbent (ServiceTitan/Toast/Mindbody/Shopify/QuickBooks) into an activated user — import-first onboarding, the activation milestone, sample-data fallback, and the time-to-first-value target. Applied by migration-import-engineer and architect/pm so onboarding is designed as a funnel, not an afterthought. Our whole wedge is "low switching cost"; this skill makes that real on day one.

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

Data-model rules that make a schema importable from day one, so the migration-import-engineer is never blocked on missing columns. Every SMB Product-Builder product must let a customer bring their data from an incumbent (ServiceTitan/Toast/Mindbody/Shopify) — that requires provenance (source_ref) and rollback (import_batch_id) on importable entities, and modelling real-world actors as entities rather than inline fields. Applied by architect when writing the data model in ARCH-{slug}.md, and checked by migration-import-engineer. One cheap rule set prevents the migration↔architecture seam gap from recurring across all 40 products.

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

Email/SMS lifecycle and deliverability framework for SMB Product-Builder products that send transactional or lifecycle messages (booking reminders, CRM sequences, receipts, win-back). Codifies provider selection (Resend/Postmark/Twilio/SendGrid), domain auth (SPF/DKIM/DMARC), consent and compliance (TCPA, CAN-SPAM, CASL, quiet hours, double opt-in), suppression-list discipline, and the transactional-vs-marketing split. Applied by integrations-engineer and senior-dev whenever a feature sends messages — so deliverability and consent are designed in, not bolted on after the first spam complaint.

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

What to do the moment a secret is exposed — pasted into chat, committed, logged, shown in a transcript or a screenshot. The secret is compromised; only revoking and rotating it helps. Turns it into one tracked task with an escalation, not a reminder repeated every session. Use when you see a key, token, password or private key anywhere it should not be ("ключ в чате", "токен в логах", "закоммитил .env"). Loaded by security-officer, l3-support, devops.

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

Review any client-facing message or material (emails, letters, newsletters, social posts, website copy, presentations, performance reports, proposals) for compliance with SEC rules that govern investment advisers — the Marketing Rule (206(4)-1), fiduciary duty / antifraud provisions (206), Books and Records (204-2), and Reg BI where broker-dealer activity applies. Produces a pass/flag/fail markup, required disclosures, a books-and-records scratch-pad entry, and an archiving handoff reminder. Triggers on "compliance check", "/compliance", "is this compliant", "review this before I send it", "can I say this to a client", "check this email/post/deck". Use it whenever an advisor asks to check, review, or look over anything before it goes to a client or prospect — "check this before I send it", "look this over before it goes out" — even a routine note, because deciding that a message needs no changes is part of the review, not a reason to skip it.

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