「archetype」の検索結果

架构师工作技能 - 架构设计、文档管理、语义化版本控制、设计审查。当用户提到架构、设计文档、版本管理、技术选型、系统设计、数据模型、API设计、文档审查、设计规范、架构决策、或需要创建/更新设计文档时，必须使用此技能。确保所有设计文档遵循语义化版本规范和命名约定。

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

前端 UED 开发工作流——数据先行、分步实施、迭代精化。当你需要设计或修改前端页面、组件、交互流程时使用此 skill，包括新页面开发、现有页面重构、可视化图表、Bug 调试、交互优化。即使用户只是说'改一下首页'或'这个图显示不对'，也应参考此工作流。覆盖 Vue / React / Svelte 等主流前端框架。

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

四路交叉验证工具 - 检查 Design Spec ↔ Scrum ↔ Code ↔ Tests 对齐一致性。当用户需要验证代码实现是否符合设计文档、Story AC 是否完整、测试覆盖率是否达标、Story 开发完成检查、MR 前验证、代码审查一致性验证时，必须使用此技能。适用于开发阶段的质量保证，防止设计文档与实现不一致的事故。⚠️ 实验性质技能，建议结合人工审查使用。

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

Simple Admin 完整开发工作流指导技能,涵盖从 Ent Schema 定义到 RPC 服务、API 网关、前端页面的全链路开发。当用户进行以下操作时使用此技能:(1) 开发新功能、新增字段、修改数据模型,(2) 创建或修改微服务的任何环节(Ent/RPC/API/前端),(3) 进行 CRUD 开发、接口开发、页面开发,(4) 需要使用 m-goctls 工具生成代码,(5) 在 Simple Admin 项目中进行任何开发工作。此技能提供完整的工作流指导,包括命令使用、文件修改规则、常见问题排查等。

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

开发工作流程指导 - 编码、测试、代码质量、MR/PR 创建和 CI/CD。用于开发任务、编码、功能实现、Bug 修复、单元测试、代码覆盖率、代码审查、CI/CD 流水线和 Git 操作。

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

代码提交与 MR 创建技能 - 自动生成语义化 commit message、创建符合规范的 GitLab Merge Request、验证飞书工作项关联。当用户提到 Git 提交、commit、push、推送代码、创建 MR、创建 PR、合并请求、或需要提交代码、推送代码、创建 MR/PR 时，必须使用此技能。支持交互式（对话）和非交互式（参数）两种模式。

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

PM 编排技能 — 具备意图识别与动态路由能力的项目管理中枢。除了 pm 的全部 Story/Epic/Sprint 管理能力外，pm 能分析用户 prompt 的多领域意图，动态匹配所需的专业 skill（arch/dev/ued/qa/devops 等），生成编排计划并在用户确认后依次唤起各 skill 协同工作。当用户的请求涉及多个专业领域、需要跨 skill 协调、或者用户希望用一个 prompt 驱动完整的「设计→实现→验证」流程时，使用此技能。纯 Story 管理/迭代规划等单领域任务，pm 会直接处理而不路由。

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

线上服务哨兵 - 定期巡检、功能回归测试、数据质量验证和根因分析（RCA）。当用户明确提到"巡检"、"回归测试"、"健康检查"、"线上分析"、"RCA"或需要验证生产环境服务健康时使用。

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

安全重构代码技能。当用户明确提到"重构"、"代码异味"或需要在TDD循环的Refactor阶段改进代码内部结构时使用。

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

Comparative mythology expert covering world mythologies, archetypal patterns, and Joseph Campbell's monomyth

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

Brand strategist AI — identity, archetype, positioning, voice, brand book สำหรับธุรกิจไทย

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

Design and build cohesive web pages with custom visual identity — landing pages and portfolios get rich anatomy + section archetypes; any other page type (blog, about, pricing, contact, coming-soon, dashboard, admin, e-commerce, custom) is supported through generic anatomy + skeleton. Use this skill whenever the user mentions: landing page, portfolio, personal site, hero section, marketing page, product page, sales page, splash page, blog page, about page, pricing page, contact page, coming-soon, waitlist, dashboard, admin panel, e-commerce store, redesign my site, design my portfolio, build a portfolio, work showcase, hire-me page, perfect-ui, perfect landing, or asks to create any web page surface. Two tiers: special (landing | portfolio — rich treatment) and generic (everything else — universal craft toolkit). Self-contained 8-phase pipeline: vibe discovery → visual direction (color/typography/mood) → custom icon set (NO emoji, NO icon library) → AI-generated visuals → optional shader effects layer → inline plan + implement on Next.js + Tailwind + shadcn. Always proposes effect layer as optional. No refusals; outputs distinctive sites, not AI slop.

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

Apply the four published expert-consensus clinical scenarios to manage GI adverse events in complex GLP-1 receptor agonist patients — persistent nausea mid-titration, GERD/heartburn after up-titration, elderly with sarcopenia risk, and insulin-treated elderly with CKD plus diarrhoea. Use when a clinician describes a patient resembling one of these archetypes, or asks "how to manage GLP-1 in an elderly patient with CKD", "patient on liraglutide developed reflux", "sarcopenia worry on semaglutide in 80-year-old", or "persistent nausea on semaglutide despite escalation". Grounded in Gorgojo-Martínez 2023 Table 4.

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

Ground a brand strategy from the corpus — archetype, opposable positioning, voice and tone, messaging framework. Use to decide who a brand is for, what it stands for, and how it sounds.

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

Guidelines and instructions for maintaining, extending, and debugging the Konoha MCP Tools Orchestrator, MCP middleware, and multi-archetype website builder across 7 coding clients (Antigravity IDE/CLI, Cursor, Claude Code, OpenCode, Command Code, Codex, Pi/pi.dev).

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

Builds a slide-by-slide presentation draft on the user's own slide template and checks every slide against written brand rules (colours with hex codes, fonts, logo placement, slide archetypes, tone, banned visuals), returning the approved outline, the DRAFT deck content and a compliance report as Markdown. Use when the user asks to "build this deck on our template", "make these slides on-brand", "check this presentation against our brand guidelines", "rebuild these slides to corporate identity (CI)" or asks for a CI-compliant or corporate-template presentation. Do not use for an accessibility review of slides, use document-accessibility-check instead. Drafts for human review; never approves, authorises or signs off.

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

Pre-tests one message (email, announcement, intranet post, town hall script, customer notice or slide) against two to six role personas the user supplies and returns a DRAFT panel report: each persona's likely first reaction, objections, unanswered questions, misreadings and what they would do next, every point tied to the passage that triggers it, plus suggested edits that add no fact the message does not already hold. Use when the user asks to "pre-test this message", "how will the team read this", "run this past the personas", "what objections will this raise", "find the holes before I send" or "check this lands with managers and field staff". Do not use for an in-character review of a proposal or business case by one executive archetype, use the executive-review family (cfo-reviewer, frontline-skeptic-reviewer and siblings) instead; to write the message in the first place, use announcement-drafter. Drafts for human review; never approves, authorises or signs off.

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

Reviews a proposal, business case, deck or product plan in character as a Chief Product Officer archetype and returns a DRAFT review in the chat with a verdict, findings that cite the exact passage, product and adoption risks, what would change the verdict and five interrogation questions. Use when the user asks to "run a CPO review", "pressure-test this product plan", "what would a CPO say about this", "challenge the user evidence" or "check the roadmap opportunity cost". Do not use for positioning, messaging or launch marketing, use cmo-reviewer instead; for internal staff adoption of a rollout, use frontline-skeptic-reviewer; for what a change asks of paying customers, use customer-advocate-reviewer. Drafts for human review; never approves, authorises or signs off.

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

Reviews a proposal, business case, deck, pricing plan, go-to-market plan or forecast in character as a Chief Revenue Officer archetype and returns a DRAFT review in the chat with a verdict, findings cited to exact passages, revenue risks, what would change the verdict and five interrogation questions. Use when the user asks to "run a CRO review", "pressure-test the revenue plan", "what would sales leadership say about this" or "challenge this forecast". Do not use for partnership, deal-structure or market-positioning reviews, use cbo-reviewer instead; for the finance seat use cfo-reviewer. Drafts for human review; never approves, authorises or signs off.

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

Reviews a proposal, business case, deck or plan in character as a Chief Technology Officer archetype and returns a DRAFT review in the chat with a verdict, findings cited to the exact passage, technology risks (architecture, build versus buy, vendor lock-in, security of design, engineering capacity), what would change the verdict and five interrogation questions. Use when the user asks to "run a CTO review", "pressure-test the technical side of this plan", "what would a CTO ask about this" or "rehearse the technology seat before the review". Do not use for cash, payback or budget questions, use cfo-reviewer instead; for capacity and timeline questions, use coo-reviewer; for security controls, privacy or compliance, use ciso-reviewer. Drafts for human review; never approves, authorises or signs off.

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

Reviews a proposal, business case, deck or rollout plan in character as a Frontline Sceptic archetype, the experienced staff member who will live with the change, and returns a DRAFT review in the chat with a verdict, findings that cite the exact passage, adoption risks, what would change the verdict and five interrogation questions. Use when the user asks to "run a frontline review", "give me the shop-floor view of this rollout", "pressure-test adoption of this plan" or "what will the team actually say about this". Do not use for employee consultation, monitoring or works council preparation, use works-council-reviewer instead; for people strategy or restructuring, use chro-reviewer; for product evidence, use cpo-reviewer. Drafts for human review; never approves, authorises or signs off.

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

Reviews a proposal, business case, deck, plan or contract summary in character as a General Counsel archetype and returns a DRAFT review in the chat with a verdict, findings that cite the exact passage or clause, legal risks, what would change the verdict and five interrogation questions. Meeting preparation, not legal advice. Use when the user asks to "run a general counsel review", "what would legal say about this", "pressure-test the legal exposure in this deal" or "prepare me for the deal committee". Do not use for price, term, renewal or vendor leverage, use procurement-reviewer instead; for lawful basis and data flows, use cdo-reviewer; for security controls, use ciso-reviewer. Drafts for human review; never approves, authorises or signs off.

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

Reviews a proposal, business case, deck or plan in character as an Investor archetype and returns a DRAFT review in the chat with a verdict whose conditions read as terms, findings that cite the exact passage, capital-allocation risks, what would change the verdict and five interrogation questions. Use when the user asks to "run an investor review", "what would an investor say about this", "pressure-test the capital case" or "prepare me for the investment committee". Do not use for internal budget, cost or finance-function review, use cfo-reviewer instead; for revenue forecast and pipeline, use cro-reviewer. Drafts for human review; never approves, authorises or signs off.

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

Reviews a proposal, business case, deck or vendor contract in character as a Head of Procurement archetype and returns a DRAFT review in the chat with a verdict, findings that cite the exact passage or clause, commercial risks, what would change the verdict and five interrogation questions. Use when the user asks to "review this from a procurement angle", "what would procurement say about this proposal", "pressure-test this vendor contract commercially", "find the holes before the sourcing committee" or "check the renewal terms like a Head of Procurement would". Do not use for liability, IP, regulatory or signing-authority questions, use general-counsel-reviewer instead; for whether the spend fits the budget, use cfo-reviewer; for vendor security, use ciso-reviewer. Drafts for human review; never approves, authorises or signs off.

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