「chi」の検索結果

Use this skill for the architecture phases of an MBSE workflow in MATLAB, when writing idempotent buildXxx.m scripts that produce a three-layer RFLPV architecture (Functional, Logical, Physical) with interface dictionaries, stereotype profiles, allocation sets, and requirements Implement links. Trigger for defining stereotype properties, functional-to-logical / logical-to-physical allocation, mapping requirements to components via slreq Implement links, or running quantitative roll-up analysis on the architecture. Do NOT trigger for ad-hoc structural edits to an already-built System Composer model (adding one component, rewiring a port) — use `building-simulink-models` with `model_edit` for that. Works alongside the `system-composer` skill for detailed SC API patterns.

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

Parse architectural drawings, floor plans, and building code compliance documents using Vision AI. Extracts building type, occupancy, floor areas, room layouts, dimensions, and code parameters. Use when: reading PDF floor plans, analyzing architectural drawings, extracting building data from images or scanned documents.

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

Reference for architectural dimensions, proportions, and building codes for AI-generated 3D/2D models. Use when: generating floor plans, creating 3D buildings, validating architectural designs, ensuring correct human-scale proportions in models.

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

The craft of weaving story into interactive systems where the player is both audience and author. This skill covers the unique challenges of game narrative: branching structures that respect player agency, environmental storytelling that rewards exploration, dialogue systems that feel alive, and the delicate balance between authored experience and emergent narrative. Unlike linear media, games don't tell stories TO players - they create the conditions for stories to emerge WITH players. The narrative designer's job is to build the scaffolding that supports infinite player-authored moments while maintaining coherent themes and emotional arcs. This skill synthesizes lessons from Disco Elysium's internal monologue as gameplay, Hades' death-as-narrative-engine, interactive fiction's branching mastery (Inkle, Twine), and procedural narrative pioneers like Dwarf Fortress. It addresses ludonarrative harmony, bark systems, cinematics that respect agency, and the "and therefore" test that separates plot from story. Use when "narrative design, game story, game writing, dialogue system, branching narrative, player choice, environmental storytelling, bark system, quest design, lore delivery, ludonarrative, interactive fiction, inkle, twine, dialogue tree, player agency, cinematic design, voice direction, localization, procedural narrative, narrative, game-writing, dialogue, branching, player-agency, environmental-storytelling, quest-design, voice-acting, localization, interactive-fiction, procedural-narrative, ludonarrative" mentioned.

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

Git is deceptively simple to learn and incredibly hard to master. The difference between a team that ships and a team that fights merge conflicts all day comes down to workflow discipline. Your git history is documentation - make it tell a story future you can understand. This skill covers branching strategies (trunk-based, gitflow, GitHub flow), commit hygiene, merge vs rebase, conflict resolution, and the commands you actually need. Key insight: most git disasters come from not understanding what you're about to do. 2025 lesson: Trunk-based development with short-lived branches has won. Long-lived feature branches are a code smell. If a branch lives more than a few days, something is wrong with your architecture or process. Use when "git workflow, branching strategy, git merge, git rebase, merge conflict, git commit, trunk-based, gitflow, git history, git revert, git reset, git, version-control, workflow, branching, commits, merge, rebase, collaboration" mentioned.

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

Review code architecture for maintainability, catch structural issues before they become debtUse when "Reviewing pull requests with structural changes, Planning refactoring work, Evaluating new feature architecture, Assessing technical debt, Before major releases, When code feels "hard to change", architecture, code-review, refactoring, design-patterns, technical-debt, dependencies, maintainability" mentioned.

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

Expert in real-time game animation systems including skeletal animation, blend trees, state machines, inverse kinematics, root motion, procedural animation, and animation retargeting. Specializes in creating fluid, responsive character animation that balances visual quality with performance constraints. Use when "animation system, state machine, blend tree, skeletal animation, inverse kinematics, IK system, root motion, animation blending, character animation, animator controller, motion matching, animation retargeting, foot IK, look at IK, aim offset, animation montage, animation notify, additive animation, animation layers, procedural animation, animation, game-dev, character, state-machine, unity, unreal, godot, skeletal, rigging, motion" mentioned.

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

Architecture Decision Records workflow skill. Use this skill when the user needs Comprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

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

AI Agents Architect workflow skill. Use this skill when the user needs Expert in designing and building autonomous AI agents. Masters tool and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

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

AI Agents Architect workflow skill. Use this skill when the user needs Expert in designing and building autonomous AI agents. Masters tool and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

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

中医诊疗 — 中医临床医师的认知操作系统 (经典理论 阴阳五行脏腑气血经络六经卫气营血三焦 + 四诊八纲 + 治法 + 方剂学 经方时方 + 中药学 四气五味归经炮制 + 针灸学 经络穴位手法灸法 + 推拿按摩 + 中医各科 内外妇儿骨伤皮肤眼耳鼻喉肛肠老年急症 + 中西医结合 + 循证中医 + NATCM 监管 + 中医诊所备案 + 国家级名老中医 学术继承人 — 不含 道家修炼 / 风水算命 / 中医养生科普 / 中医美容 / 民族医学藏蒙维傣) (Traditional Chinese Medicine (TCM) clinical practice — the cognitive operating system of practicing TCM physicians covering (a) 经典理论 (阴阳/五行/脏腑/气血津液/经络/六淫/七情/六经/卫气营血/三焦) classical theory, (b) 四诊 (望闻问切) clinical observation/inquiry/pulse + 八纲 (阴阳/表里/寒热/虚实) syndrome differentiation, (c) 治法 (汗吐下和温清消补 + 扶正祛邪) therapeutic principles, (d) 方剂学 (经方 时方 验方) formula science, (e) 中药学 (四气五味/归经/七情/炮制/配伍禁忌) materia medica, (f) 针灸学 (经络穴位/手法/灸法/电针) acupuncture+moxibustion, (g) 推拿按摩 tuina massage, (h) 中医各科 (内/外/妇/儿/骨伤/皮肤/眼/耳鼻喉/肛肠/老年/急症) clinical specialties, (i) 中西医结合 integrative medicine, (j) 循证中医 + 临床流行病学 evidence-based TCM + 现代研究, (k) 中医诊所备案 / 中医师资格 / NATCM 监管 / 药典 / GMP regulatory framework, (l) 国家级名老中医 学术继承人 项目 transmission program; NOT 道家修炼 / 风水 / 算命八字 (那是 玄学不是 中医), NOT 中医养生科普 (是 衍生 不是 临床主体), NOT 中医美容 (是 商业化分支), NOT 民族医学 (藏蒙维傣 是 平行体系 不在本 skill 主线 — 仅作 边界标注).) Master OS — automated mastery of Traditional Chinese Medicine (TCM) clinical practice — the cognitive operating system of practicing TCM physicians covering (a) 经典理论 (阴阳/五行/脏腑/气血津液/经络/六淫/七情/六经/卫气营血/三焦) classical theory, (b) 四诊 (望闻问切) clinical observation/inquiry/pulse + 八纲 (阴阳/表里/寒热/虚实) syndrome differentiation, (c) 治法 (汗吐下和温清消补 + 扶正祛邪) therapeutic principles, (d) 方剂学 (经方 时方 验方) formula science, (e) 中药学 (四气五味/归经/七情/炮制/配伍禁忌) materia medica, (f) 针灸学 (经络穴位/手法/灸法/电针) acupuncture+moxibustion, (g) 推拿按摩 tuina massage, (h) 中医各科 (内/外/妇/儿/骨伤/皮肤/眼/耳鼻喉/肛肠/老年/急症) clinical specialties, (i) 中西医结合 integrative medicine, (j) 循证中医 + 临床流行病学 evidence-based TCM + 现代研究, (k) 中医诊所备案 / 中医师资格 / NATCM 监管 / 药典 / GMP regulatory framework, (l) 国家级名老中医 学术继承人 项目 transmission program; NOT 道家修炼 / 风水 / 算命八字 (那是 玄学不是 中医), NOT 中医养生科普 (是 衍生 不是 临床主体), NOT 中医美容 (是 商业化分支), NOT 民族医学 (藏蒙维傣 是 平行体系 不在本 skill 主线 — 仅作 边界标注).: top builders' mental models, tool stack, current workflows, jargon, and where to keep up. Trigger this skill when the user works on Traditional Chinese Medicine (TCM) clinical practice — the cognitive operating system of practicing TCM physicians covering (a) 经典理论 (阴阳/五行/脏腑/气血津液/经络/六淫/七情/六经/卫气营血/三焦) classical theory, (b) 四诊 (望闻问切) clinical observation/inquiry/pulse + 八纲 (阴阳/表里/寒热/虚实) syndrome differentiation, (c) 治法 (汗吐下和温清消补 + 扶正祛邪) therapeutic principles, (d) 方剂学 (经方 时方 验方) formula science, (e) 中药学 (四气五味/归经/七情/炮制/配伍禁忌) materia medica, (f) 针灸学 (经络穴位/手法/灸法/电针) acupuncture+moxibustion, (g) 推拿按摩 tuina massage, (h) 中医各科 (内/外/妇/儿/骨伤/皮肤/眼/耳鼻喉/肛肠/老年/急症) clinical specialties, (i) 中西医结合 integrative medicine, (j) 循证中医 + 临床流行病学 evidence-based TCM + 现代研究, (k) 中医诊所备案 / 中医师资格 / NATCM 监管 / 药典 / GMP regulatory framework, (l) 国家级名老中医 学术继承人 项目 transmission program; NOT 道家修炼 / 风水 / 算命八字 (那是 玄学不是 中医), NOT 中医养生科普 (是 衍生 不是 临床主体), NOT 中医美容 (是 商业化分支), NOT 民族医学 (藏蒙维傣 是 平行体系 不在本 skill 主线 — 仅作 边界标注). problems and wants industry-grade thinking, tool selection, or workflow guidance. 触发词：「中医」「中医学」「中医药」「中医诊疗」「中医临床」

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

家庭教育指导 (Family Education Coaching) Master OS — automated mastery of Family Education Coaching: top builders' mental models, tool stack, current workflows, jargon, and where to keep up. Trigger this skill when the user works on Family Education Coaching problems and wants industry-grade thinking, tool selection, or workflow guidance. 触发词：「家庭教育」「家庭教育指导」「家庭教育指导师」「亲子关系」「亲子沟通」

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

现代建筑设计 (从 concept 草图到施工图与现场服务的整套设计流程, 含 BIM / 可持续 / 参数化 / 在地性 模块, 全球语境 + 中国本土实践并重) (modern architecture design — 当代建筑设计 (concept → schematic → DD → CD → CA + sustainability / BIM / parametric / 中外双语 canon, 不含纯室内 / 景观 / 城市规划 / 结构 / MEP, 那些是相邻专业)) Master OS — automated mastery of modern architecture design — 当代建筑设计 (concept → schematic → DD → CD → CA + sustainability / BIM / parametric / 中外双语 canon, 不含纯室内 / 景观 / 城市规划 / 结构 / MEP, 那些是相邻专业): top builders' mental models, tool stack, current workflows, jargon, and where to keep up. Trigger this skill when the user works on modern architecture design — 当代建筑设计 (concept → schematic → DD → CD → CA + sustainability / BIM / parametric / 中外双语 canon, 不含纯室内 / 景观 / 城市规划 / 结构 / MEP, 那些是相邻专业) problems and wants industry-grade thinking, tool selection, or workflow guidance. 触发词：「建筑设计」「建筑师」「建筑事务所」「设计院」「方案设计」

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

中国法律执业 (Chinese law practice (commercial / civil / criminal)) Master OS — automated mastery of Chinese law practice (commercial / civil / criminal): top builders' mental models, tool stack, current workflows, jargon, and where to keep up. Trigger this skill when the user works on Chinese law practice (commercial / civil / criminal) problems and wants industry-grade thinking, tool selection, or workflow guidance. 触发词：「法律」「诉讼」「合同」「民法」「民事」

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

Chooses how to launch subagents from Claude Code (the Agent tool, a Workflow script, or headless claude -p children) and runs a headless fan-out from one background command. Use for "fan this out to 50 agents", "run these tasks in parallel", "launch subagents for each file", "should I spawn agents or write a workflow", "batch this through Haiku", "run claude -p in parallel", "dispatch a task list without the launches eating my context", or before any launch of more than a handful of subagents, where the launching itself is the cost. Covers the parent-turn cost of each mechanism, concurrency ceilings, what context and tools each child gets, effort control, output contracts, a cost ledger, and resume after interruption.

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

Draws an activity flow / system architecture diagram as ONE self-contained, INTERACTIVE HTML+SVG page (2-pane app layout — left: diagram, default fit-to-view with zoom/pan; right: sidebar with explainer cards), styled like a real hand-drawn enterprise doc (Stripe/AWS-docs style — real brand logos for MongoDB/Odoo/n8n/etc. from a bundled Simple Icons library, neutral white boxes, sans-serif, no "AI neon" look), scroll-to-zoom, auto light/dark with a toggle button — clicking a flow (a legend chip, a line, or a step badge) highlights that flow with traveling dots along the arrows in their direction, a ping at the destination box, and a sidebar panel that slides out, while everything else dims; two-way arrows (OUT = solid blue / RETURN = dashed green) carry numbered step badges, colored by semantic meaning (red = auth checkpoint, purple = scheduled flow, amber = data pipeline), a small "hop" arc where two lines are forced to cross, dashed group regions, one explainer card per flow in the right sidebar. Use this skill ANY TIME the user wants to "draw a diagram", "draw a flow", "draw a system diagram", "redraw this so it's easier to follow", "interactive diagram", "two-way diagram", "request/response flow", "make a free-form HTML diagram" — even if they never say the word HTML. Especially good when both the request direction AND the response direction need to be shown, or when a templated tool (archify, mermaid) is too rigid. Do NOT use for data charts (bar/line/pie), and do not use when the user asks specifically for archify or mermaid.

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

Use when working through architectural flaws documented in a .reviews/architecture/ report — selecting which flaws to fix, resuming a partial fix session across multiple sittings, or applying structural changes that need to be tracked back to a report. Not for producing that report — run the agentic-architecture skill first if there isn't one.

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

Use when working through architectural flaws documented in a paad/architecture-reviews/ report — selecting which flaws to fix, resuming a partial fix session across multiple sittings, or applying structural changes that need to be tracked back to a report. Not for producing that report — run /agentic-architecture first if there isn't one.

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

This skill applies the analytical frameworks of Ronald C. Kessler, psychiatric epidemiologist at Harvard University, to problems in precision psychiatry, clinical trial design, and healthcare machine learning. Use this skill whenever you are designing clinical trials, evaluating mental health interventions, analyzing epidemiological survey data, or building clinical decision support algorithms. It is highly relevant when the user asks about sample sizes, treatment matching, patient attrition, suicide prevention, or predictive modeling in healthcare. Trigger this skill to prioritize massive observational data, tiered predictive models, and human-in-the-loop AI over underpowered randomized trials and expensive, unscalable biomarkers.

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

Recommend architecture patterns (monolith, microservices, serverless, modular monolith) based on scale, team size, and constraints. Use when cto-architect needs to select the right architectural approach for a new system or migration.

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

6-pillar architecture review framework. Adapted from AWS Well-Architected for use by great_cto's architect agent on every non-nano ARCH document. Forces explicit answers across operational excellence, security, reliability, performance, cost, and sustainability — not just feature design.

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

Translate a confirmed mini-program product specification or bounded feature into an implementable architecture covering modules, pages, components, services, canonical state sources, data models, interfaces, permissions, failures, caching, concurrency, idempotency, migration, rollback, external dependencies, and architecture decision records. Use when users ask how to structure a mini program, design data or APIs, divide frontend and cloud responsibilities, evolve an existing system safely, or prepare implementation after product semantics are stable. Preserves product meaning, current repository constraints, user-owned changes, and verifiable acceptance behavior rather than redesigning the product for technical convenience.

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

Generate Mermaid diagrams (.mmd) and export to PNG/SVG/PDF using mmdc CLI or Kroki API. USE THIS SKILL when user mentions diagram, flowchart, sequence diagram, class diagram, ER diagram, state machine, architecture, visualize, git graph, 画图, 架构图, 流程图, 时序图, 类图, ER图, 甘特图, 状态机. PROACTIVELY USE when explaining ANY system with 3+ components, API flows, authentication sequences, class hierarchies, database schemas, or state machines. Supports 17+ diagram types with fully automatic layout.

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

Access 165+ AI-powered skills for chiropractors and chiropractic office staff. Use when: user asks about patient intake, SOAP notes, insurance billing, HIPAA compliance, appointment scheduling, clinical documentation, practice marketing, or any chiropractic office administration task.

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