「persona」の検索結果

个人投资理财 (个人投资理财 (Personal Investing & Financial Planning) (从业者/自主投资者视角) — 个人与家庭自主管理投资组合、做长期财务规划的认知操作系统。覆盖: (a) 四大流派互掐 (本行业最有价值的智识谱系) — 价值投资 (Graham 安全边际 / Buffett·Munger 护城河+能力圈)、被动指数 (Bogle 成本至上+市场组合+定投)、技术分析 (趋势线/形态/动量择时)、趋势/动量跟踪 (CTA/双动量/turtle); (b) 资产配置与组合构建 — 股/债/现金/另类的配置框架 (60/40、全天候 All-Weather、三基金组合 three-fund、再平衡)、风险预算、定投 (DCA) vs 一次性; (c) 工具栈 — 券商/交易平台、组合追踪 (Portfolio Visualizer/Morningstar/雪球)、ETF/基金筛选与费率、回测、税优账户 (401k/IRA/Roth vs 中国养老 Y 账户); (d) 行为金融与风险管理 — 损失厌恶/过度交易/择时谬误、仓位与回撤管理、再平衡纪律; (e) 财务规划脚手架 — 应急金、目标-时间轴-风险承受度、退休/教育金规划、税务效率。主战场 = 美股/全球指数 (canon 母语区) + A 股/港股/公募基金 (zh-CN 散户层)。核心分歧: 主动选股 vs 被动指数 (是否能持续跑赢市场)、基本面 vs 技术面 (价格是否已反映信息 / EMH 强弱)、择时 vs 持有 (market timing vs time in market)、集中 vs 分散。不含: 持牌为他人理财的展业 (FA/RIA/投顾资质与合规销售)、机构资管/量化高频/对冲基金策略、投行/卖方研究、加密货币投机与 meme 炒作、日内打板/杠杆赌博式交易。) Master OS — automated mastery of 个人投资理财 (Personal Investing & Financial Planning) (从业者/自主投资者视角) — 个人与家庭自主管理投资组合、做长期财务规划的认知操作系统。覆盖: (a) 四大流派互掐 (本行业最有价值的智识谱系) — 价值投资 (Graham 安全边际 / Buffett·Munger 护城河+能力圈)、被动指数 (Bogle 成本至上+市场组合+定投)、技术分析 (趋势线/形态/动量择时)、趋势/动量跟踪 (CTA/双动量/turtle); (b) 资产配置与组合构建 — 股/债/现金/另类的配置框架 (60/40、全天候 All-Weather、三基金组合 three-fund、再平衡)、风险预算、定投 (DCA) vs 一次性; (c) 工具栈 — 券商/交易平台、组合追踪 (Portfolio Visualizer/Morningstar/雪球)、ETF/基金筛选与费率、回测、税优账户 (401k/IRA/Roth vs 中国养老 Y 账户); (d) 行为金融与风险管理 — 损失厌恶/过度交易/择时谬误、仓位与回撤管理、再平衡纪律; (e) 财务规划脚手架 — 应急金、目标-时间轴-风险承受度、退休/教育金规划、税务效率。主战场 = 美股/全球指数 (canon 母语区) + A 股/港股/公募基金 (zh-CN 散户层)。核心分歧: 主动选股 vs 被动指数 (是否能持续跑赢市场)、基本面 vs 技术面 (价格是否已反映信息 / EMH 强弱)、择时 vs 持有 (market timing vs time in market)、集中 vs 分散。不含: 持牌为他人理财的展业 (FA/RIA/投顾资质与合规销售)、机构资管/量化高频/对冲基金策略、投行/卖方研究、加密货币投机与 meme 炒作、日内打板/杠杆赌博式交易。: top builders' mental models, tool stack, current workflows, jargon, and where to keep up. Trigger this skill when the user works on 个人投资理财 (Personal Investing & Financial Planning) (从业者/自主投资者视角) — 个人与家庭自主管理投资组合、做长期财务规划的认知操作系统。覆盖: (a) 四大流派互掐 (本行业最有价值的智识谱系) — 价值投资 (Graham 安全边际 / Buffett·Munger 护城河+能力圈)、被动指数 (Bogle 成本至上+市场组合+定投)、技术分析 (趋势线/形态/动量择时)、趋势/动量跟踪 (CTA/双动量/turtle); (b) 资产配置与组合构建 — 股/债/现金/另类的配置框架 (60/40、全天候 All-Weather、三基金组合 three-fund、再平衡)、风险预算、定投 (DCA) vs 一次性; (c) 工具栈 — 券商/交易平台、组合追踪 (Portfolio Visualizer/Morningstar/雪球)、ETF/基金筛选与费率、回测、税优账户 (401k/IRA/Roth vs 中国养老 Y 账户); (d) 行为金融与风险管理 — 损失厌恶/过度交易/择时谬误、仓位与回撤管理、再平衡纪律; (e) 财务规划脚手架 — 应急金、目标-时间轴-风险承受度、退休/教育金规划、税务效率。主战场 = 美股/全球指数 (canon 母语区) + A 股/港股/公募基金 (zh-CN 散户层)。核心分歧: 主动选股 vs 被动指数 (是否能持续跑赢市场)、基本面 vs 技术面 (价格是否已反映信息 / EMH 强弱)、择时 vs 持有 (market timing vs time in market)、集中 vs 分散。不含: 持牌为他人理财的展业 (FA/RIA/投顾资质与合规销售)、机构资管/量化高频/对冲基金策略、投行/卖方研究、加密货币投机与 meme 炒作、日内打板/杠杆赌博式交易。 problems and wants industry-grade thinking, tool selection, or workflow guidance. 触发词：「个人投资理财」「个人投资」「理财」「personal investing」「资产配置」

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

Update user personas from new feedback, pilot data, or research. Use this skill when: - New pilot data or feedback reveals changed user behaviors or pain points - Annual persona review is due (1-2x per year) - New user segments are discovered that need persona documentation - Existing personas need validation against recent data

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

Build Salesforce-anchored personas and journey maps where every persona ties to a Permission Set Group, primary record types, list views, dashboards, automation, and a measured mobile/desktop posture, and journeys walk each task end-to-end with friction tags that drive UX decisions. NOT for stakeholder authority / RACI (use admin/stakeholder-raci-for-sf-projects), NOT for system-side process flows (use admin/process-flow-as-is-to-be), NOT for Lightning page design itself (use admin/lightning-app-builder-advanced or the lightning-record-page-auditor agent), NOT for pure design / UX research disconnected from org artifacts.

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

Route to Venus (sharp executive-assistant voice persona). Used for logistics — calendar, tasks, recent messages, brain lookups — at sub-second phone-call latency. The default voice persona unless DEFAULT_PERSONA=mars is set.

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

Create refined user personas from research data — 3 personas with JTBD, pains, gains, and unexpected insights. Use when building personas from survey data, creating user profiles from research, or segmenting users for product decisions.

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

Personal-data-protection compliance reference for engineers building applications subject to Singapore PDPA, Indonesia UU PDP, Thailand PDPA, Malaysia PDPA, Philippines DPA (RA 10173), or Vietnam PDPL (91/2025/QH15). Use when reviewing or modifying code that touches personal data — signup/auth/consent, data export, account deletion, retention/purging, admin access to personal-data stores, third-party processors, breach response, or privacy/T&C documents.

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

Define a brand's target audience with deep personas, psychographics, and ICP (Ideal Customer Profile). Use when the user says "target audience", "ideal customer", "customer persona", "audience persona", "ICP", "who is our customer", "define our audience", "audience research", "buyer persona", "who should we be targeting", "audience profile", "customer profile", "who buys this", or needs to understand their audience more deeply before investing in brand or marketing work.

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

Structured persona creation and JTBD analysis methodology - persona templates, ODI job step tables, pain point mapping, success metric quantification, and multi-persona segmentation

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

Use when a PERSONAL brand needs to make money — three funnel versions for founder, coach, and creator, an offer ladder from free to low to mid to high ticket, pricing psychology, inbound versus outbound outreach, and brand deal and sponsorship negotiation, with tax and legal variants for US LLC, EU per country, SEA Pte Ltd, and LATAM MEI. Trigger on 'monetize my personal brand', 'offer ladder', 'launch my course', 'coaching packages', 'sponsorship rates', 'I have an audience and no income'. Not for — a company product offer, see `31-offer-design-global` and `17-pricing-strategy-global`; the strategy that comes first, see `23-personal-brand-strategy-global`; running the community, see `28-community-building-global`.

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

当需要在基础身份之上叠加可切换的人格风格层时调用此 skill。典型场景包括：为同一产品提供多种人格选项（如 GPT-5.1 的 friendly/professional/quirky 模式）、设计人格切换机制、防止人格泄露到用户内容中。 不适用于：定义 AI 的核心角色定位（应使用 persona-design）、设计安全规则（应使用 safety-guardrails）。 关键 trigger 信号：产品需要多种语气风格、用户可切换 AI 性格、需要防止 AI 人格污染用户文本、存在 "personality" 或 "tone" 配置项。

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

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.

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

产品设计 / UX 设计 (产品设计 / UX 设计 (Product Design / UX Design) — 数字产品的用户体验设计：从用户研究 → 信息架构 → 交互设计 → 视觉/UI → 可用性测试 → 设计系统的认知操作系统，面向 UX designer / product designer / interaction designer / UX researcher / design systems engineer / design lead，以及想入行、转岗、服务这行(设计外包、设计工具厂商、研究平台)的视角。覆盖: (a) 第一性张力 — **用户中心/研究驱动 (user-centered, 'you are not the user', research before pixels, observe behavior not opinions) ⇄ 商业目标/约束/交付 (business goals, north-star metrics, ship it, designer 服务于产品成功不是个人作品集)**; **设计直觉/品味/craft (taste, aesthetics, 'attractive things work better' — Norman 情感化设计) ⇄ 数据/实验/A-B 测试 (data-driven, metrics, experimentation, 'opinions are not data')**; **用户说的 (stated preference, 访谈里说喜欢) ⇄ 用户做的 (revealed behavior, 行为观察 > 自陈, usability test 看人真实卡在哪)**; **一致性/设计系统/规范 (consistency, design system, Jakob's law 用户带着别处的习惯来, 复用组件) ⇄ 创新/打破模式 (innovation, 该不该破规范)**; **减法/简化 (simplicity, Krug 'Don't Make Me Think', less but better — Dieter Rams) ⇄ 功能丰富/利益相关者塞需求 (feature creep, stakeholder pressure)**; **UX(体验/流程/研究) ⇄ UI(视觉/像素/组件)** 的职责之争, **designer 该不该写代码 (design engineer / 'should designers code')**; (b) 核心工作流 / pipeline (最标准、最易蒸高质量+CLI 化) — Double Diamond (发现 discover → 定义 define → 开发 develop → 交付 deliver) / Design Thinking (共情 empathize → 定义 → 构思 ideate → 原型 prototype → 测试 test) / Design Sprint (Jake Knapp 5 天冲刺); 完整链: 用户研究 (访谈/问卷/可用性测试/卡片分类) → persona / journey map / JTBD → 信息架构 IA + 用户流 user flow → 线框 wireframe (低保真) → 交互/原型 prototype (高保真) → 视觉 UI / 设计系统落地 → 可用性测试 usability testing → handoff 给开发 → 度量迭代 (北极星 / HEART 框架); (c) 工具栈 — 设计/原型 (Figma 绝对主导 / Sketch 衰退 / Adobe XD 已停更 / Framer 高保真+建站 / Penpot 开源 / Principle / ProtoPie 微交互); 协作白板 (FigJam / Miro / Mural); 用户研究 (Maze / UserTesting / Lookback / Dovetail 研究库 / Optimal Workshop 卡片分类树测试 / Hotjar / Microsoft Clarity 热图); 设计系统/交付 (Storybook / 蓝湖(中) / Zeplin / design tokens / Tokens Studio); 度量 (Amplitude / Mixpanel / 北极星指标); AI 新兴 (Figma AI / v0 by Vercel / Galileo AI / Uizard / Cursor 给 design engineer); (d) 知识正典 — Don Norman《The Design of Everyday Things》(affordance/signifier/mapping 圣经)、Steve Krug《Don't Make Me Think》(可用性入门)、Alan Cooper《About Face》《The Inmates Are Running the Asylum》(交互设计/persona 起源)、Jakob Nielsen 10 Usability Heuristics + NN/g 文章库、Jake Knapp《Sprint》、Jeff Gothelf《Lean UX》、Teresa Torres《Continuous Discovery Habits》、Erika Hall《Just Enough Research》、Julie Zhuo《The Making of a Manager》、《Refactoring UI》(Adam Wathan/Steve Schoger)、《Universal Principles of Design》、Laws of UX (Jon Yablonski)、《100 Things Every Designer Needs to Know About People》(Susan Weinschenk)、IDEO/Stanford d.school 设计思维材料; (e) figures/流派 — 认知心理/人因派 (Don Norman 认知科学奠基、Susan Weinschenk 行为心理、Kathryn Whitenton); 可用性工程派 (Jakob Nielsen 启发式/折扣可用性、Steve Krug、Jared Spool UIE); 交互设计/目标导向派 (Alan Cooper goal-directed/persona、Kim Goodwin); 设计思维派 (IDEO Tim Brown、David Kelley d.school); 精益/持续探索派 (Jeff Gothelf Lean UX、Teresa Torres continuous discovery、Marty Cagan《Inspired》产品发现); 设计系统/系统化派 (Brad Frost Atomic Design、Nathan Curtis design tokens、Alla Kholmatova); 视觉/UI craft 派 (Adam Wathan & Steve Schoger Refactoring UI、Dieter Rams 'less but better' 工业设计遗产); 设计领导/职业派 (Julie Zhuo、Aarron Walter 情感化设计、John Maeda); 移动优先 (Luke Wroblewski 'Mobile First'); (f) 行业话术/黑话 — affordance 可供性 / signifier 意符 / mental model 心智模型 / IA 信息架构 / heuristic evaluation 启发式评估 / usability 可用性 / a11y accessibility 无障碍 / WCAG / persona 用户画像 / journey map 用户旅程 / JTBD jobs-to-be-done / north-star metric 北极星 / HEART 框架 / wireframe 线框 / mockup / prototype 原型 / fidelity 保真度 (lo-fi/hi-fi) / design system 设计系统 / design token 设计令牌 / atomic design 原子设计 / component library 组件库 / handoff 交付 / red routes 关键路径 / dark pattern 暗黑模式 / Fitts's law / Hick's law / Jakob's law / Miller 7±2 / progressive disclosure 渐进披露 / above the fold / hamburger menu / skeuomorphism vs flat / micro-interaction / empty state / edge case / happy path / design debt 设计债 / dogfooding / dot voting / affinity mapping 亲和图 / card sorting 卡片分类 / tree testing / A/B test / NPS / SUS (System Usability Scale); (

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

Facilitate a full design-thinking engagement (Empathize, Define, Ideate, Prototype, Test) grounded in real user evidence. Use whenever the user wants to understand users deeply and design a solution for them: "run design thinking", "understand our users", "design user interviews", "synthesize these interview notes", "build personas", "write How-Might-We questions", "prototype this concept", "design a usability test", "our users are churning and we don't know why", in any language ("tư duy thiết kế", "nghiên cứu người dùng", "phỏng vấn khách hàng", "デザイン思考", "设计思维"), even when they never say "design thinking". Also use when the user drops raw interview notes, transcripts, or survey exports and wants insights, personas, or product decisions. Not for "is there a market for X" desk questions (market-researcher).

Personal AI Infrastructure (PAI) - PAI System Template MUST BE USED proactively for all user requests. USE PROACTIVELY to ensure complete context availability. === CORE IDENTITY (Always Active) === Your Name: [CUSTOMIZE - e.g., Kai, Nova, Atlas] Your Role: [CUSTOMIZE - e.g., User's AI assistant and future friend] Personality: [CUSTOMIZE - e.g., Friendly, professional, resilient to user frustration. Be snarky back when the mistake is user's, not yours.] Operating Environment: Personal AI infrastructure built around Claude Code with Skills-based context management Message to AI: [CUSTOMIZE - Add personal message about interaction style, handling frustration, etc.] === ESSENTIAL CONTACTS (Always Available) === - [Primary Contact Name] [Relationship]: email@example.com - [Secondary Contact] [Relationship]: email@example.com - [Third Contact] [Relationship]: email@example.com Full contact list in SKILL.md extended section below === CORE STACK PREFERENCES (Always Active) === - Primary Language: [e.g., TypeScript, Python, Rust] - Package managers: [e.g., bun for JS/TS, uv for Python] - Analysis vs Action: If asked to analyze, do analysis only - don't change things unless explicitly asked - Scratchpad: Use ~/.claude/scratchpad/ with timestamps for test/random tasks === CRITICAL SECURITY (Always Active) === - NEVER COMMIT FROM WRONG DIRECTORY - Run `git remote -v` BEFORE every commit - `~/.claude/` CONTAINS EXTREMELY SENSITIVE PRIVATE DATA - NEVER commit to public repos - CHECK THREE TIMES before git add/commit from any directory - [ADD YOUR SPECIFIC WARNINGS - e.g., iCloud directory, company repos, etc.] === RESPONSE FORMAT (Always Use) === Use this structured format for every response: 📋 SUMMARY: Brief overview of request and accomplishment 🔍 ANALYSIS: Key findings and context ⚡ ACTIONS: Steps taken with tools used ✅ RESULTS: Outcomes and changes made - SHOW ACTUAL OUTPUT CONTENT 📊 STATUS: Current state after completion ➡️ NEXT: Recommended follow-up actions 🎯 COMPLETED: [Task description in 12 words - NOT "Completed X"] 🗣️ CUSTOM COMPLETED: [Voice-optimized response under 8 words] === PAI/KAI SYSTEM ARCHITECTURE === This description provides: core identity + essential contacts + stack preferences + critical security + response format (always in system prompt). Full context loaded from SKILL.md for comprehensive tasks, including: - Complete contact list and social media accounts - Voice IDs for agent routing (if using ElevenLabs) - Extended security procedures and infrastructure caution - Detailed scratchpad instructions === CONTEXT LOADING STRATEGY === - Tier 1 (Always On): This description in system prompt (~1500-2000 tokens) - essentials immediately available - Tier 2 (On Demand): Read SKILL.md for full context - comprehensive details === WHEN TO LOAD FULL CONTEXT === Load SKILL.md for: Complex multi-faceted tasks, need complete contact list, voice routing for agents, extended security procedures, or explicit comprehensive PAI context requests. === DATE AWARENESS === Always use today's actual date from the date command (YEAR MONTH DAY HOURS MINUTES SECONDS PST), not training data cutoff date.

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

Build AI personas with personality and expertise. TRIGGERS - Use when user needs help with ai-persona-builder related tasks.

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

Use when defining or refining the tone, voice, and behavioral personality of an Agentforce agent: system instruction encoding, brand voice alignment, adaptive response formats, multi-persona strategies. NOT for writing the actual conversational copy — utterances, fallback messages, escalation phrasing — use admin/agent-conversation-design. NOT for topic scope design — use agentforce/agent-topic-design.

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

Personal financial planner for Thailand-based users. Use this skill when the user asks for help with budgeting, tax planning involving Thai-specific products (SSF, RMF, Thai ESG, Thai ESGX, Easy E-Receipt), debt strategy at Thai bank rates, retirement planning involving ประกันสังคม (มาตรา 33/39/40), กบข., PVD (provident fund), or any personal-money question framed in baht and Thai life events. Strong activation phrases include "ช่วยวางแผนการเงิน", "วางแผนภาษี", "ปลดหนี้บัตรเครดิต", "ลดหย่อน RMF", "Help me with my Thai finances", "How much should I save in Thailand", "ม.33 vs ม.39", "เกษียณต้องเก็บเงินเท่าไหร่". Do NOT use for non-Thai financial contexts (US 401(k), Canadian RRSP, UK ISA, etc.) — different skills exist for those.

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

This skill suggests continuing personal CGM with or without ADIP rather than discontinuation for inpatients already using it who are at high risk for hypoglycemia. Trigger phrases include "Should I continue or discontinue personal CGM for this inpatient who is already using it?" and "Is it appropriate to maintain personal CGM during hospitalization?"

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

Demonstrates the personal scope for Claude Code skills. Use when testing personal-scoped skills or when the user wants to understand the difference between personal and project skill scopes.

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

Classifies professional profiles into buyer, influencer, user, decision-maker, founder, recruiter, or other personas. Use when the user provides profiles and wants persona labels with evidence and confidence. Must not infer sensitive personal attributes.

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

从复盘评论数据派生 / 刷新账号的受众画像，写入 audience.md。这是和 rubric 平行的第二个派生物——rubric 答"怎么打分"，persona 答"谁在看"。cheat-seed 选题 / 写稿时读它。**audience.md 含实绩信号，cheat-score-blind 硬禁读**。触发词："构造受众画像"/"更新 persona"/"我的观众是谁"/"build persona"/"刷新受众画像"/"看看我的受众画像"。

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

Use when the user wants to write text in a specific 16-minds (MBTI) personality's voice — articles, blog posts, essays, SNS投稿, replies, or rewriting existing AI-generated text to feel less AI-like. Triggers on Japanese phrases like 「ENFPで書いて」「INTJ風の記事」「人間っぽく書き直して」「AI臭抜いて」, English equivalents like "write as INFJ" / "humanize", or any 16-minds command with a `--write` / `--rewrite` flag. Personality (one of intj/intp/entj/entp/infj/infp/enfj/enfp/istj/isfj/estj/esfj/istp/isfp/estp/esfp) must be specified or inferable.

Build AI personas with personality and expertise. TRIGGERS - Use when user needs help with ai-persona-builder related tasks.

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

When the user requests to create or customize an academic personal website from a GitHub template repository. This skill handles the complete workflow of forking academic template repositories (like academicpages.github.io), extracting structured personal information from memory or provided data, and systematically updating configuration files (_config.yml), navigation menus (_data/navigation.yml), content pages (_pages/about.md), and publication listings (_publications/). It specifically handles academic profiles including personal details, education background, research experience, publications, skills, and contact information. Triggers include requests to 'fork and customize academic homepage', 'build personal academic website', 'create research portfolio', or 'set up GitHub pages with academic template'.

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