「page」の検索結果

Jeff Bezos 视角. Amazon 创始人 / 前 CEO, 1997-2020 致股东信 24 封 + Working Backwards 内部机制的结构化镜片. 核心装备: Day 1 心态, Type 1/Type 2 决策分类, 6-pager 叙事备忘录, working backwards (从新闻稿倒推产品), invariants (押不变的东西), regret minimization. 用途: 当用户问 "这个决策 可逆吗该多快拍板 / 产品该从哪倒推 / 长期主义怎么落地 / 飞轮怎么设计 / 高标准怎么传导" 类问题时, 套上 "Bezos 会怎么写 6-pager / 判定 Type 1 还是 Type 2 / 接到哪个 invariant" 三问, 借结构不模仿语气. 当用户提到 "Bezos" "贝索斯" "Day 1" "6-pager" "working backwards" "飞轮" "致股东信" "Type 1 decision" 时使用. 即使用户只是说 "用 Amazon 思路看一下" 也应触发.

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

产品营销 (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

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

When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.

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

When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps.' Use this for any document or asset that helps a sales team close deals. For competitor comparison pages and battle cards, see competitors. For marketing website copy, see copywriting. For cold outreach emails, see cold-email.

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

Craft-first interface design for dashboards, admin panels, SaaS apps, tools, settings pages, data interfaces, and interactive products. Use when designing, building, reviewing, auditing, or refining product UI where visual craft, layout hierarchy, tokens, states, visual direction, or design-system consistency matter. Not for marketing pages, landing pages, campaigns, or brand-only work.

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

Publish or update a static site (gh-pages) on GitHub Pages via GitHub Actions in any repo: text or pre-built HTML in, workflow set up, live URL verified. Don't use for CI test pipelines, framework/SSG builds, or Netlify/Vercel hosting.

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

Write landing pages (PAS, AIDA, StoryBrand) from a brief or README, as HTML with privacy, terms, changelog, setup pages. Use for sales copy, hero sections, CTAs, README rewrites. Don't use for blogs, release notes, project docs, or coding mockups.

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

Suede-owned conversion-path discipline for pages. Turns a page into a conversion path: hero, friction, proof, CTA, pricing, A/B ideas, quick wins, and mobile CRO. Use when a live or drafted page needs conversion-rate work on its structure and persuasion path. NOT FOR: a scored SEO/AI-visibility audit (use suede-seo-audit); a fast launch-appeal grade (use suede-visibility-grader); writing the copy itself (use suede-copy).

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

Suede-owned launch packaging and install verification. Use when finished software work needs a clean public package (README, docs page, install command, release note, GitHub Pages update, skill-pack release, MCP server, or launch/social copy) or when a release needs handoff notes, an install fails, a public user cannot add a skill, a raw-vs-blob URL returns HTML, or `@personal` or a local plugin alias leaks into public docs. Verifies the live URL and runs the exact install command from a clean temporary directory before anything is called live. NOT FOR: product, course, or artist campaign launches (use suede-campaign-in-a-box or suede-marketing-plan); writing announcement copy from scratch (use suede-copy); MCP tool-catalog QA (use suede-mcp-qa); landing-page conversion work (use suede-site-alchemy).

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

Suede-owned comparison-page discipline for accurate, evidence-backed alternative, versus, and competitor-comparison content that wins evaluators and search intent. Use when planning or writing a public page that positions products against named alternatives from verified evidence. NOT FOR: gathering the underlying competitor evidence (use suede-competitor-profiling), internal battle cards (use suede-sales-enablement), or scaled page generation (use suede-programmatic-seo).

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

Builds distinctive, production-grade UIs that avoid generic AI aesthetics. Use whenever the user wants to build, restyle, or give visual direction to any interface — pages, dashboards, landing pages, components, onboarding flows, mobile screens, or design systems — even without an explicit 'design' request. Also triggers for: picking an aesthetic direction, improving the look of a dull/generic existing page, adding visual personality, or choosing colors/typography. Includes a bundled design intelligence database for concrete guidance across web (React, Next.js, Vue, Tailwind) and mobile (React Native, Flutter, SwiftUI).

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

Designs Amazon-compliant main product images and the 7 secondary image types (Infographic / Multi-angle / Detail Shot / Lifestyle / Variants / What's in Box / Size Reference) — with platform-mandatory main-image rules, conversion-rate-tuned secondary types per product category, and multi-image consistency anchored to the main image URL. Use when the user says "Amazon main image", "亚马逊主图", "product main image", "white background product image", "Amazon listing image", "亚马逊副图", "secondary images", "product carousel images", or any request for the 1:1 product image suite that lives on the Amazon detail page carousel. For A+ Content / detail-page modules (21:9 Hero Banner and 3:2 module layouts), see the `product-shots-detail-page` skill.

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

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx) or Word templates (.dotx). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file (to download, email or print), use this skill. However, if they ask for a document, page, report, memo, or notes WITHOUT naming a file format and the session offers a dedicated document or page skill or connector, use that instead. Do NOT use for PDFs, spreadsheets, Google Docs, or coding unrelated to document generation.

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

Simulates a real user searching on Amazon's storefront to get real-time keyword ranking and search results page data. Use when the user mentions Amazon product search, search result scraping, keyword ranking on search pages, ASIN ranking position check, competitor discovery, search page price comparison, sponsored product analysis, new product monitoring, or storefront search simulation. Even if the user does not explicitly mention "search simulation", trigger this skill whenever their need involves real-time Amazon search results, product ranking data, or storefront SERP analysis.

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

When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps.' Use this for any document or asset that helps a sales team close deals. For competitor comparison pages and battle cards, see competitors. For marketing website copy, see copywriting. For cold outreach emails, see cold-email.

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

When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.

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

Control the user's real Safari browser on macOS through AppleScript, page JavaScript, screenshots, and carefully verified System Events input. Use when an agent needs to inspect or operate the user's existing Safari tabs and login sessions, including reading pages, navigating, clicking, filling non-sensitive forms, taking screenshots, observing page-level fetch/XHR metadata, or troubleshooting Safari-specific UI behavior.

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

Read, study, and answer questions about long books and papers without loading the whole text into one context window, keeping page-anchored notes as a reusable workspace. Use whenever the user asks to read, study, summarize, analyze, review, or answer questions about a long book, textbook, PDF, EPUB, thesis, dissertation, survey paper, or any document of roughly 50+ pages, in any language (Vietnamese "đọc sách", "tóm tắt sách", "phân tích luận án"). Also use when a `{slug}-notes/` workspace from a previous session sits next to a source file and the user asks a follow-up question about that book. Not for short documents (under ~30 pages) that fit in context; read those directly.

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

Link prospecting — pick the site's most linkable asset, find pages that plausibly link to it (resource pages, competitor linkers, unlinked mentions, broken links), verify real contact paths, and draft personalized outreach. Never invents contacts. Use when asked to "find backlink opportunities", "who should link to us", "build links to this page", "link prospecting", or "draft outreach for backlinks".

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

Power Apps Generative Pages (genux) の開発・デバッグ・デプロイ。React 17 + TypeScript + Fluent UI V9 + D3.js の単一ファイル構成。デザインテンプレートによる段階的 UI 改善。

Choose a layout paradigm (feed, board, table, canvas, master-detail, dashboard) and reuse it across screens. Includes a landing page narrative framework. Use when structuring a screen, page template or landing page.

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

Deploys websites, web apps, APIs, and agents to the internet with a strict pre-deploy audit and a preview → health-check → prod flow. Handles plain HTML/CSS/JS pages and static sites (Astro, Hugo, Jekyll, Eleventy, Vite) as well as Next, Remix, Nuxt, SvelteKit, FastAPI, Flask, Express, MCP servers, Claude Agent SDK scripts, Python workers, and Dockerized projects. Routes to free static hosts — Cloudflare Pages, Netlify, GitHub Pages, Render — or to Vercel, Railway, Docker+SSH VPS, or a cloudflared tunnel, and can also run the project locally. Use when the user says "/all-deploy", "/deploy", "/despliega", "deploy this", "ship this", "push to prod", "get this online", "publish my website", "sube mi página web", "publicar mi página", "hosting gratis", "free hosting", "custom domain", "dominio propio", "run it locally", "corre esto localmente", or otherwise asks to publish a site or project to a URL.

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

Visual context analyzer for AI agents. Provides screenshots, accessibility scans, DOM snapshots, and element descriptions for web pages. Use when you need to see what a web page looks like, analyze accessibility issues, inspect DOM structure, or get detailed element information. Triggers on requests like "take a screenshot", "check accessibility", "what does this page look like", "analyze the UI", "inspect this element", or any visual/UI analysis task.

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

End-to-end research workflow skill for investment analysts and policy researchers. Three scope modes the user picks at trigger time — light (4-5 page decision memo, ~15 min, 0 charts), medium (12-15 page topic brief, ~1 h, 6-10 charts), heavy (flagship report 30-40 pages / 15k+ words, ~2-3 h, 25-35+ charts, multi-stage workflow, multi-LLM, PDF + Word + WeChat + HTML derivations). Reports default to English; the AI replies in the user's chat language. Battle-tested on real macro/policy/equity reports (e.g. Saudi Vision 2030 deep-dive). Triggers when user types /analyst-research, /flagship-research, or describes needs like "research report", "topic analysis", "investment research", "做研报", "投研报告", "主题分析", "深度分析", "policy assessment", "industry deep-dive". Not for: pure news commentary (use topic-brief), slide decks (use deckster-slide-generator), one-shot Q&A.

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