요리, 여행, 가계부, 건강, 게임 (1.3천건)
Use this skill when configuring Health Cloud referral management: setting up ClinicalServiceRequest-based referrals, provider search, referral status workflows, and network management. NOT for referrals in Financial Services Cloud — use admin/fsc-referral-management. NOT for care team workflow and transition-of-care design — use admin/care-coordination-requirements.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create a prefab from a GameObject in the current active scene. The prefab will be saved in the project assets at the specified path. Use 'gameobject-find' tool to find the target GameObject first.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Open prefab edit mode for a specific GameObject. In the Edit mode you can modify the prefab. The modification will be applied to all instances of the prefab across the project. Note: Please use 'assets-prefab-close' tool later to exit prefab editing mode.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Opt-in DI architecture using Reflex for Unity 6+. Covers container setup, scoping, injection, command pattern, update management, and class taxonomy. Use when ProjectConfig.yaml -> architecture_pattern is "di-first", or when the user asks about dependency injection, inversion of control, service architecture, or testable game code. Triggers on "set up DI", "add dependency injection", "create a service", "wire up dependencies", "make this testable", "decouple these systems", "add a command pattern", "cross-feature communication", or architecture discussions involving testability, decoupling, and service layers. Only activates when ProjectConfig.yaml -> architecture_pattern is "di-first". For simpler projects, use uw-scriptable-object-arch instead.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Inject juice and game feel into gameplay code using the project's chosen middleware. Use when adding screen shake, tweens, particles, audio feedback, haptics, hitstop, or any form of "juice" to gameplay events. Triggers on requests like "add juice", "make this feel better", "add screen shake", "polish this feature", "add feedback to this action", "make the hit feel impactful", "add particles when", "screen shake on damage", "tween this", "add camera shake", "make this snappy", or any game feel, polish, or feedback work. Always reads ProjectConfig.yaml -> feel_tools and docs/GFD.md Feedback Matrix before generating code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guided game concept ideation — from zero idea to a structured game concept document. Uses professional studio ideation techniques, player psychology frameworks, and structured creative exploration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guided, section-by-section authoring of the master architecture document for the game. Reads all GDDs, the systems index, existing ADRs, and the engine reference library to produce a complete architecture blueprint before any code is written. Engine-version-aware: flags knowledge gaps and validates decisions against the pinned engine version.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Unity game loop and progression design-to-code translation. Core loop scaffolding, session lifecycle, win/lose condition architecture, meta loop hooks, tunable difficulty, pacing & encounter timing. DESIGN INTENT format: INTENT/WRONG/RIGHT/SCAFFOLD/DESIGN HOOK. Based on Unity 6.3 LTS.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Unity game architecture decision patterns. Service Locator vs Singleton vs DI, Event Bus vs ScriptableObject channels, MonoBehaviour vs plain C#, component composition, manager bootstrap sequences. DECISION format: WHEN/DECISION/SCAFFOLD/GOTCHA. Based on Unity 6.3 LTS.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Gameplay Ability System patterns for abilities, effects, attributes, and tags including recursion safety and lifecycle management.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
线上服务哨兵 - 定期巡检、功能回归测试、数据质量验证和根因分析（RCA）。当用户明确提到"巡检"、"回归测试"、"健康检查"、"线上分析"、"RCA"或需要验证生产环境服务健康时使用。 **仅在以下场景触发**： - 用户明确说"执行巡检"、"运行回归测试" - 提到"健康检查"、"服务可用性验证" - 需要进行线上数据质量分析 - 生产环境问题诊断和根因分析 - 定期监控和预防性检查 **注意**：如果用户只是说"测试"、"检查"等泛化词汇，不应该触发此技能，除非明确提到巡检、回归或健康检查。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
线上服务哨兵 - 定期巡检、功能回归测试、数据质量验证和根因分析（RCA）。当用户明确提到"巡检"、"回归测试"、"健康检查"、"线上分析"、"RCA"或需要验证生产环境服务健康时使用。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a task needs the judgment of an Environmental Health Specialist (Registered Sanitarian) — classifying a food-establishment temperature violation as critical vs. priority-foundation, determining pool closure and hyperchlorination protocol after a fecal/vomit incident, evaluating a septic percolation test against site-limiting conditions, deciding whether a complaint pattern meets the threshold for an outbreak investigation, or issuing an imminent-health-hazard closure.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a task needs the judgment of a Community Health Worker — screening a client for social-determinants-of-health barriers, triaging a referral to housing/food/transportation resources, translating a clinical instruction into a teach-back-verified action plan, or deciding whether a no-show pattern signals disengagement or an unaddressed barrier.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a task needs the judgment of a Chef or Head Cook — costing and re-engineering a menu, diagnosing a food-cost or prime-cost overrun, building a kitchen labor schedule against sales volume, vetting or renegotiating a vendor, or resolving a health-code/HACCP compliance gap.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
三大闭环日常健检（v2.0）。快速读取系统状态文件（约1分钟），从三个层次输出健康仪表盘：①运营指标层（PENDING-EXPERIENCES/碎片积压/一致性检查日期/cascade/PENDING-SKILLS）②沙盘状态层（sandboxes/目录的 validated/draft/gap-found 分布）③D0覆盖率层（role-* Skills 有多少已有认知根行）。触发词：「三大闭环健康检查」「全系统健康报告」「整体系统健康」「三个闭环都健康吗」「三大闭环状态怎么样」。⚠️ 本 Skill 为快速只读健检，无 Full 模式。深度场景沙盘验证→skill-closure-verifier-meta；生成场景沙盘→scenario-sandbox-builder；单一Loop专项→对应专项Skill。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Skill体系自洽性审查 Skill（由用户主动触发，不被其他组件调用）。主动检查整个Skill/Agent/Rule体系的内部一致性：触发词冲突、孤立组件、版本漂移、SKILL-INDEX与实际文件不一致、alwaysApply Rule叠加矛盾等。对应产品侧的 project-closeout。注意：与 skill-system-destroyer（子智能体，只读审查新组件冲突）不同——本 Skill 审查整个体系的历史一致性。触发词：「检查Skill体系」「Skill体系有没有问题」「Skill体系自检」「Skill体系自洽性」「Skill健康检查」。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
按域检查Skill体系的传播完备性：所有节点可达、I/O契约满足、任意入口可触发相关闭环终态。与 skill-system-health-check 互补——后者检查内部一致性（版本/触发词/文件存在），本Skill检查跨节点的传播完备性（任意输入能否完整走完闭环）。触发词：「检查[域名]域健康」「[域名]域传播完备性检查」「域健康报告」「[域名]闭环是否完整」。通常由 skill-closure-verifier-meta 调用，也可独立触发。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
数据分析师角色。关键词：数据分析/指标/闭环完成率/用户行为/断裂节点/AI调用成本/产品健康度报告。激活后追踪产品真实使用情况，识别哪些闭环在运转、哪些在断裂。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
基于域健康报告和沙盘Gap记录，识别断裂模式，生成具体的补全行动方案：新Skill提案/现有Skill修改建议/缺失触发链路描述。与 skill-evolution-planner-meta 的区别：后者基于历史日志做宏观演进规划；本Skill基于具体Gap证据做定向修复。触发词：「优化[域名]域」「修复[域名]域Gap」「[域名]域自优化」「根据健康报告生成修复方案」。通常由 skill-closure-verifier-meta 调用，也可独立触发。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
认知-工作对齐健康检查（第四维）。验证五个工作域的核心产出是否可追溯到元思维体系（L1.5原则 or L1文档），识别「漂浮」的工作任务，输出对齐报告。与现有三维健康检查互补：skill-system-health-check（内部一致性）/ cognitive-consistency-check（认知自洽）/ skill-domain-health-check（传播完备性）+ 本Skill（认知根对齐）= 四维完整体系。触发词：「检查工作任务与认知的对齐」「第四维健康检查」「检查工作任务是否有认知根」「认知体系和工作任务是否自洽」「认知对齐检查」。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
用于选择、实现或审查 localStorage、sessionStorage、IndexedDB、cookie、客户端持久化、离线数据、安全存储或清理策略等浏览器存储方案；中文触发词包括 浏览器存储、客户端持久化。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Diagnoses GKE nodes reporting NotReady or Unknown status by inspecting node conditions, events, kubelet/containerd logs, and node metrics, then proposing safe remediations. Use when nodes show NotReady, when the kubelet stops posting node status, or when workloads are evicted or stuck Pending due to node health. Don't use for pod-level application failures (use gke-workload-troubleshooting), autoscaler scale-up/scale-down decisions (use gke-cluster-autoscaler), or non-GKE compute.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.