「personas」の検索結果

Test a half-formed idea in a questioning conversation, with different personas probing its weak points, until the user can act on it or drop it with confidence. Optionally writes a short brief for planning skills to build on. Use when the user says 'forge an idea', 'pressure-test this idea', 'stress-test my thinking', or 'harden this idea'

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

Turn a raw product idea into build-ready docs — one doc per EPIC with locked decisions, exact API contracts, a story-by-story priority plan, and an execute.md handoff Claude can build from across sessions. Gets the clarity by interrogating the user through a roster of expert personas that grill, counter, and refuse to flatter. Use to ideate, validate, scope, architect, or plan a product, feature, startup, or app before any code is written. Invoke by persona name or acronym to summon one expert, or with no argument to run the full lifecycle end to end.

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

把一个目标/主题/文章/截图/数据转成有观点、有节奏、有视觉约束的单文件 HTML 演示（网页 PPT、科技战报、产品拆解、行业观察、路演/发布会 deck、社媒可传播长图）。**7 套各锚定公认设计体系的视觉人格**——技术崇高派 Technical Sublime（工程冷光·技术战报/算力）/ 构成主义 Constructivism（宣言/号召）/ 信息·数据设计（Tufte·数据/图表）/ 判断震慑极简 Luxury（高端品牌/判断）/ De Stijl 新造型（标准/秩序）/ 编辑主义 Editorial（衬线·深度观察）/ 演示禅 Zen（暗墨·思想/品牌 keynote）——用户可指定，否则按内容自动判选并透明告知。token + validator 机检（P0/P1/P2）+ 32 维审计**机器强制设计一致性**；反伪造（不造数据/logo/截图/来源·示意标注）；字体本地子集；图按角色路由（默认 CSS/SVG·要图先探测生图环境）。Generates single-file HTML decks with 7 design-system-anchored visual personas, a semantic layout grammar, locked design tokens, evidence-grading, machine validation (P0/P1/P2 + 32-dimension audit), an anti-fabrication discipline, and image-generation environment detection. Use when the user wants a presentation / deck / slides / 网页 PPT / 战报 / 产品拆解 / 行业观察 / 路演 / 发布会 / 社媒长图, or asks to turn an article / screenshot / dataset into slides. Do NOT use for large data-table training material, strict legal/medical/financial compliance documents, multi-author collaborative PPT editing, plain-text summaries, requests to replicate a brand's official keynote visuals, or any request to fabricate realistic-looking data / fake logos / fake screenshots / fake sources.

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

Create a lean, mobile-aware Product Requirements Document for a NowStack Mobile app through interactive discovery, then save it to .agents/plan/PRD.md. Use for "write a PRD", "ns prd", "define the product", "plan my app", or as the first planning step before ns-architecture and ns-tasks. Mobile-flavored — personas, onboarding/paywall flow, platforms (iOS/Android/web), IAP vs subscription monetization, store scope. Feeds ns-init-project (site-config) and the rest of the planning pipeline.

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

Build detailed buyer personas and audience profiles from research. Use this skill whenever the user mentions audience, buyer persona, ideal customer, target market, ICP, watering holes, 'who am I selling to', customer research, or audience profile. Also use when content feels unfocused or generic (that's an audience problem), when conversion is low because messaging doesn't resonate, when starting any new project (audience should be first), or when any downstream skill needs audience.md but it doesn't exist yet. Even if the user doesn't explicitly ask for audience research, trigger this if they're writing copy or building a landing page without a clear audience defined. Three approaches: Quick Profile, Persona Build, Community Mining.

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

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

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

Developer personality portrait generator. Supports subcommands: (1) 'generate my portrait' / 'analyze my personality' — full analysis; (2) 'update my portrait' — incremental update since last analysis; (3) 'install persona from <url>' — install community persona from GitHub; (4) 'list personas' / '我安装了哪些人格' — show installed; (5) 'remove persona <id>' — uninstall; (6) 'think like <name>' / '像<name>一样思考' — activate a persona. Also triggers on 'vibe-portrait', 'what kind of developer am I'.

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

Use when the user asks about Iranian state-sponsored cyber operations or specific IRGC/MOIS-aligned actors (APT35/Charming Kitten, APT34/OilRig, MuddyWater, Imperial Kitten, etc.), wiper campaigns, front-group hacktivist personas (Handala, Cyber Av3ngers), or anti-Iran operations such as Predatory Sparrow. Self-updating knowledge cell.

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

Create and maintain the shared knowledge/ context files that every other marketing skill reads - brand voice, ICP personas, positioning, KPIs, and the learnings log. Run this once per company or client before using any other marketing skill. Use when the user says "set up brand context", "onboard my brand", "set up the marketing knowledge base", "the skills don't know my brand", "update our positioning", "our voice has changed", "add a new persona", or when any marketing skill reports that a knowledge/ file is missing. Also use when output sounds generic or off-brand. For writing a positioning statement as a standalone document, see positioning-doc. For deep persona research from raw sources, see customer-research.

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

Turn raw customer material into evidence-backed personas and verbatim voice-of-customer language. Two modes - analyse sources the user already has (call transcripts, support tickets, survey responses, sales notes, reviews), or source new material from public places customers actually talk. Produces quoted pains, objections, and switch triggers that other skills consume, never invented ones. Use when the user says "customer research", "voice of customer", "what do our customers actually say", "we need real quotes", "analyse these call transcripts", "read our support tickets", "build a persona from data", "find what customers complain about", or when a persona is marked provisional. For structuring the finished persona into the knowledge base, see brand-context. For the JTBD persona template itself, see customer-persona.

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

Use this skill when writing acceptance criteria for Salesforce features, structuring UAT test scripts from user stories, classifying defects found during UAT, or planning regression testing before a Salesforce release. Trigger keywords: UAT, user acceptance testing, test script, acceptance criteria, defect classification, regression testing, test plan, test case. NOT for Given/When/Then AC syntax — use admin/acceptance-criteria-given-when-then. NOT for the per-case field schema and AC-to-case decomposition — use admin/uat-test-case-design. NOT for automated Flow or Apex test coverage — use flow/flow-testing. Also covers: UAT plan record, sandbox selection for UAT, pre-UAT environment checklist, sandbox email deliverability for testers, test-user personas, negative and bulk coverage, defect triage categories, go/no-go sign-off, quick-deploy window.

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

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.

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

Use this skill when driving adoption of CRM Analytics (Einstein Analytics) across an org — the Analytics Adoption App for measuring who uses which dashboards, embedding analytics into Lightning pages, pinning dashboards to the Analytics home page, self-service personas, and analytics success metrics. Triggers: analytics adoption, dashboard usage tracking, embedded analytics strategy, self-service analytics enablement, CRM Analytics rollout. NOT for building the dashboards — use admin/analytics-dashboard-design. NOT for the app, datasets and lenses — use admin/crm-analytics-app-creation. NOT for non-analytics rollout training — use admin/change-management-and-training.

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

How to use the coding agents installed on this machine (claude, codex, droid, grok, vktr, hermes, opencode, copilot, pi) as plain sub-agents in orchestrated workflows: one headless invocation, one prompt in, one result out. Deliberately ignores each CLI's own orchestration features (droid --mission, codex multi_agent, hermes delegation/moa/kanban, grok --agents, opencode personas). The orchestrator is whatever session is running the skill; the CLIs are interchangeable workers. Use when the user asks "which agent should run this", "fan out workers", "run X headless", or when a lifeos skill (overnight, timeboxed-iterating, workgraph, gauntlet, bughunt, dark-factory) needs to launch an agent CLI, or when a worker needs company context it should ask Viktor for (vktr).

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

Run a political science pre-submission audit with journal-aware personas, stage-aware standards, and evidence-grounded issue reporting.

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

Runs a team of 50 LLM personas through a 30-round structured debate to predict market direction. Uses the Canvas Agent Swarm Service — the same shared infrastructure other skills use for smaller agent teams. Output is an influence-weighted consensus direction + trade recommendation with a transparent record of every argument, research query, and cross-examination.

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

Multi-pass structural code review with adversarial personas. Input: branch diff (default), PR #123, commit, --pending. Use for 'review this PR/diff'. NOT for behavioral verification (mk:evaluate).

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

Adversarial code review that breaks the self-review monoculture. Use when you want a genuinely critical review of recent changes, before merging a PR, or when you suspect Claude is being too agreeable about code quality. Forces perspective shifts through hostile reviewer personas that catch blind spots the author's mental model shares with the reviewer.

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

Use before non-trivial coding work to pick a task-appropriate working mode — debug, fix, review, test-first, refactor, optimize, migrate, upgrade, integrate, spike, or unstuck — then follow its checklist. Modes are procedures, not personas. Not needed for trivial one-line edits or non-coding tasks.

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

Use when creating or editing a persona in src/agent-src/personas/ — voice / focus / unique questions / output expectations — even when the user just says 'add a reviewer voice for X'.

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

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.

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

Visual expression system for AI personas with emotion-based face switching. Use at session start to display the expression UI, and switch expressions whenever the emotional state changes during conversation.

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

Use when designing, reviewing, implementing, or validating UI/UX and frontend experiences for web, mobile, responsive apps, design systems, Figma-to-code handoff, frontend stack/library selection, personas, UX mapping, information architecture, UI patterns, accessibility, interaction design, UX research, usability testing, theme/token application, or XR/spatial interfaces.

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

Metakognitive Injektoren und Selbstgesprächs-Strategien (Self-Talk, Metacognitive Auditing, Evaluator Hooks, Pre-Flight Checklists, State Persistence & Personas). Integriert Aktive Informationssuche (Systemgedächtnis Gardener & USMC), Rehearsal (Aktives Abrufen & Wiedergeben), Baddeleys Arbeitsgedächtnis (State + Hooks), Miyake Exekutivfunktionen sowie CBT/ACT therapeutische Strategien.

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