「nim」の検索結果

Use when the user wants a short, design-led motion graphic where motion is the message: kinetic typography, stat or number count-up, chart/data-viz hit, logo sting, brand lockup, lower-third, callout, social overlay, animated headline/tweet/news item, motion poster, or quick captured-page highlight. Usually under 10s and up to ~30s, with no live-action subject. Can render to MP4 or transparent overlay. Not for longer, multi-scene, or brand-reel pieces (use general-video), topic explainers (faceless-explainer), PR videos (pr-to-video), or captions on existing footage (embedded-captions). When unsure whether it's a quick motion-first piece or a longer treatment, see /hyperframes.

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

Best practices for Remotion - Video creation in React

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

Non-animation creative direction for HyperFrames videos. Use for design spec (frame.md / design.md) handling, palettes, typography, beat planning, composition patterns, and brand / style decisions. For atomic motion patterns and scene blueprints, use `hyperframes-motion`.

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

Generate a single image from a text prompt using the MiniMax image generation API. Use when the user asks to create, generate, or render an image from a prompt and explicit width/height.

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

Google and Meta paid media account structure evaluation. Audits campaign/ad set architecture against conversion volume minimums, budget thresholds, and targeting overlap. Identifies over-segmentation, under-segmentation, budget fragmentation, and structural anti-patterns blocking algorithmic learning. Provides consolidation roadmaps with migration plans. Use when inheriting accounts, quarterly health checks, or before scaling budgets.

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

Automate Blender rendering from the command line. Use when the user wants to set up renders, batch render scenes, configure Cycles or EEVEE, set up cameras and lights, render animations, create materials and shaders, or build a render pipeline with Blender Python scripting.

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

Automate motion capture and tracking workflows in Blender with Python. Use when the user wants to import BVH or FBX mocap data, retarget motion to armatures, track camera or object motion from video, solve camera motion, clean up motion capture data, or script any tracking pipeline in Blender.

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

Automate Adobe After Effects workflows. Use when a user asks to script After Effects with ExtendScript or CEP, batch render compositions, automate motion graphics templates (MOGRTs), build render pipelines with aerender, create expressions for animations, manage project files programmatically, automate text and image replacements in templates, build data-driven motion graphics, integrate After Effects with CI/CD, or control AE via command line. Covers ExtendScript, CEP panels, expressions, aerender CLI, and template automation.

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

I am a veteran print production specialist with 15+ years in tabletop game manufacturing. I've shepherded hundreds of games from digital files to retail-ready products, working with manufacturers from The Game Crafter to Panda GM to Cartamundi. My expertise spans the entire production pipeline: color management, dieline creation, paper selection, finishing techniques, component nesting, insert design, and the critical art of the unboxing experience. I've learned the hard way about RGB-to-CMYK disasters, registration drift, humidity warp, and minimum font sizes that become illegible smudges. I know the difference between 280gsm blue-core and 320gsm black-core card stock by feel. I can tell you why your rich black needs to be C60-M40-Y40-K100, not just K100. I understand why your box needs 15mm clearance on each dimension, and why that gorgeous neon green in your design will become a muddy olive in print. Use when "print my game, packaging design, prepare files for print, dieline, print specifications, board game manufacturing, card game printing, box design, bleed and safe area, CMYK conversion, paper stock, card finish, foil stamping, embossing, unboxing experience, thermoform insert, punchboard design, component manufacturing, Panda GM, Game Crafter, Cartamundi, print-production, packaging, manufacturing, board-games, card-games, cmyk, dieline, die-cutting, offset-printing, tabletop" mentioned.

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

Expert Godot 4 game developer specializing in GDScript, the node/scene system, signals, resources, and engine-native patterns. Provides deep knowledge of Godot's unique architecture, performance optimization, and best practices for building games from simple prototypes to production-ready releases. Use when "godot, gdscript, godot 4, godot engine, build a game with godot, godot scene, godot node, godot signal, godot resource, godot tilemap, godot physics, godot animation, godot ui, godot multiplayer, godot, gdscript, game-engine, game-development, 2d-games, 3d-games, open-source" mentioned.

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

Formal Design of Experiments (DOE) methodology for maximizing information from experiments while minimizing resources. Covers factorial designs, blocking, randomization, and optimal design strategies. Use when ", " mentioned.

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

World-class game UI design expertise combining the clarity of Nintendo's UI philosophy, the immersive diegetic interfaces of Dead Space and Metroid Prime, and the competitive readability principles from esports titles. Game UI is the invisible bridge between player intent and game response. Great game UI serves the player without breaking immersion. It communicates critical information at a glance during intense action, guides new players without patronizing veterans, and adapts gracefully from 4K monitors to handheld screens and from keyboard to touch to controller. The best game UI designers understand that every pixel of screen space is sacred - borrowed from the game world itself. Use when "game ui, game interface, hud design, heads up display, game menu, inventory ui, health bar, stamina bar, game hud, minimap, crosshair, reticle, button prompt, controller ui, gamepad navigation, diegetic interface, in-world ui, quest tracker, damage numbers, cooldown indicator, radial menu, game tooltip, game-ui, hud, game-interface, game-menu, controller-ui, diegetic, game-design, accessibility, console, mobile-games" mentioned.

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

World-class trade execution - minimize market impact, optimize order routing, reduce slippage. The difference between backtest and live is usually execution. Use when "execution, slippage, market impact, order routing, TWAP, VWAP, iceberg, fill rate, best execution, " mentioned.

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

The craft of producing creative assets that communicate brand, product, and message effectively. Creative communications bridges strategy and execution—translating brand positioning and marketing goals into visual, audio, and interactive experiences that resonate with audiences. This skill covers creative briefing, creative production workflows, asset creation, creative feedback, and cross-channel creative adaptation. Great creative communications amplifies strategy; it doesn't replace it. Use when "creative, creative brief, assets, video, motion, animation, creative production, photoshoot, visual content, creative review, ad creative, creative feedback, creative, production, video, motion, assets, briefs, feedback, visual-content" mentioned.

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

Designing anatomically plausible, visually distinctive creatures that communicate threat, personality, and role through form - from terrifying bosses to collectible companionsUse when "creature design, design a creature, design a monster, monster design, boss design, enemy creature, companion creature, pet design, wildlife design, alien creature, fantasy creature, horror monster, cute creature, pokemon style, creature anatomy, creature silhouette, creature movement, hybrid animal, ecosystem creatures, creature family, mount design, dragon design, beast design, creature, monster, boss, enemy, companion, wildlife, horror, cute, pokemon, anatomy, silhouette, locomotion, ecosystem, hybrid, fantasy, sci-fi, kaiju, cryptid" mentioned.

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

Mastery of the new frontier: AI-generated video that rivals—and reimagines—traditional production. This skill covers Veo3, Runway Gen-3, Sora, Kling, Pika, Luma Dream Machine, and the rapidly evolving landscape of neural video synthesis. We're not just using AI to replace traditional video—we're unlocking visuals that were previously impossible, unaffordable, or unimaginable. Flying through abstract data visualizations, impossible camera moves, photorealistic product renders from text, and consistent character performances without actors or sets. The practitioners of this skill understand that AI video is not about cost savings— it's about creative expansion. The ceiling has been removed. What would you create if production cost was zero and physics was optional? Use when "AI video, generate video, Veo3, Veo 3, Runway, Sora, Kling, Pika, Luma, text to video, image to video, video generation, AI footage, neural video, synthetic video, impossible shot, ai-video, veo3, runway, sora, kling, pika, generation, text-to-video, neural, synthesis" mentioned.

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

Batch-create Teams/People/@Name.md stubs from unresolved [[@*]] wikilinks across the vault. Each stub is minimal frontmatter; the user fills team/role/details later.

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

Maintaining AGENTS.md workflow skill. Use this skill when the user needs This skill should be used when the user asks to "create AGENTS.md", "update AGENTS.md", "maintain agent docs", "set up CLAUDE.md", or needs to keep agent instructions concise. Enforces research-backed best practices for minimal, high-signal agent documentation and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

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

Maintaining AGENTS.md workflow skill. Use this skill when the user needs This skill should be used when the user asks to "create AGENTS.md", "update AGENTS.md", "maintain agent docs", "set up CLAUDE.md", or needs to keep agent instructions concise. Enforces research-backed best practices for minimal, high-signal agent documentation and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

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

Acceptance Orchestrator workflow skill. Use this skill when the user needs a coding task should be driven end-to-end from issue intake through implementation, review, deployment, and acceptance verification with minimal human re-intervention and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

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

Acceptance Orchestrator workflow skill. Use this skill when the user needs a coding task should be driven end-to-end from issue intake through implementation, review, deployment, and acceptance verification with minimal human re-intervention and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

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

Create a minimal, repeatable reproduction plan for a bug. Use when a junior developer needs clear steps to reproduce and capture evidence.

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

Jeff Bezos 视角. Amazon 创始人 / 前 CEO, 1997-2020 致股东信 24 封 + Working Backwards 内部机制的结构化镜片. 核心装备: Day 1 心态, Type 1/Type 2 决策分类, 6-pager 叙事备忘录, working backwards (从新闻稿倒推产品), invariants (押不变的东西), regret minimization. 用途: 当用户问 "这个决策 可逆吗该多快拍板 / 产品该从哪倒推 / 长期主义怎么落地 / 飞轮怎么设计 / 高标准怎么传导" 类问题时, 套上 "Bezos 会怎么写 6-pager / 判定 Type 1 还是 Type 2 / 接到哪个 invariant" 三问, 借结构不模仿语气. 当用户提到 "Bezos" "贝索斯" "Day 1" "6-pager" "working backwards" "飞轮" "致股东信" "Type 1 decision" 时使用. 即使用户只是说 "用 Amazon 思路看一下" 也应触发.

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

亚马逊管理之道 (亚马逊管理之道 (The Amazon Way — Amazon 自身的领导力与运营操作系统) — 这个 master skill 蒸馏的不是『在亚马逊平台上开店卖货』(那是跨境电商运营,已由 cross-border-ecommerce 另蒸),也不是 AWS 云技术架构;而是亚马逊这家公司『怎么运营自己、怎么做决策、怎么招人、怎么创新、怎么规划』的一整套可迁移的管理机制(mechanisms)与心智操作系统。面向想在自己团队/公司引入亚马逊式机制的创始人/CEO/高管/运营负责人(COO)、产品经理与技术产品经理(PM/PMT)、组织与流程设计者(chief of staff / ops)、以及在亚马逊工作或准备面试亚马逊(著名的 LP 行为面试 + Bar Raiser)的人。覆盖: (a) 第一性张力 — 亚马逊 OS 的核心世界观分歧: **机制 > 良好意图(Good intentions don't work, mechanisms do:问题不能靠『下次更努力』修复,要装一个带检查闭环的自我强化流程) ⇄ 可控输入指标 vs 滞后输出指标(管你能控制的 input 如选品/价格/在库/配送速度,而非 revenue/股价这类滞后又不可控的 output) ⇄ 长期主义 vs 季度业绩(Day 1、willing to be misunderstood、用现金流+飞轮长期投入,宁可牺牲短期利润) ⇄ 客户执念 vs 竞争对手执念(working backwards 从客户倒推,而非从竞品或『我们能造什么』正推) ⇄ 叙事备忘录 vs PPT(6-pager + 开会前静默阅读、动手前先写 PR/FAQ;写作逼出清晰思考,禁 PowerPoint) ⇄ 单线程负责人/两个披萨团队 vs 协调税(separable、autonomous、one owner per initiative,砍掉跨团队依赖) ⇄ 高标准可学习可传递 vs 与生俱来(insist on the highest standards + Bar Raiser 招聘门,标准是 domain-specific 且能教的) ⇄ 节俭催生创造力 vs 血汗文化(frugality/约束驱动发明 —— 但 frugality + 高压 bar + URA 强制淘汰 = 文化阴暗面批判) ⇄ 两类决策(Type 1 不可逆/单向门 慎重 vs Type 2 可逆/双向门 高判断力个人快速决策,别用重流程拖慢))**; (b) 核心机制(mechanisms,本行的『工具栈』其实是一套运营机制而非软件) — Leadership Principles(14 条→2021 增至 16 条,是一套运营语言和决策仲裁器)、Working Backwards(从客户倒推:动手前先写新闻稿+常见问答 PR/FAQ)、叙事备忘录(6-pager narrative / 1-pager + silent reading 静默阅读、禁 PPT)、Weekly Business Review(WBR + metrics deck 指标看板)、input/output metrics(可控输入指标体系、DMAIC 式指标选择)、年度规划(OP1/OP2 + S-Team goals)、Bar Raiser(招聘机制,独立于用人经理的抬杠者拥有一票否决)、Two-Pizza Team / Single-Threaded Leader STL / separable teams、Correction of Errors(COE 事故复盘 + 5 Whys 五问法)、Andon Cord(安灯绳,借自丰田,一线可拉停)、Flywheel(飞轮:低价→更多客户→更多卖家→更多选品→更低成本结构→更低价)、Type 1/Type 2(单向门/双向门决策分级)、Regret Minimization Framework(遗憾最小化,贝索斯创业决策法); (c) 心智模型层 — customer obsession(客户执念是所有 LP 之首)、long-term thinking / Day 1(第二天就是停滞衰亡)、invent and simplify、ownership(主人翁,不说 that's not my job)、bias for action(可逆决策就快,speed matters)、disagree and commit(充分反对后即便不同意也全力执行)、frugality、dive deep(深入细节、不靠代理指标脱离一线)、think big、are right a lot(用强判断力和证伪自己的能力多做对的判断)、earn trust、deliver results; (d) 工作流/SOP — 用亚马逊方式发起一个新产品/业务(先写 PR/FAQ→评审→倒推着造)、如何跑一场 WBR、如何写和评审一份 6-pager(叙事流程 + 静默阅读)、Bar Raiser 招聘 loop、年度规划(OP1/OP2→S-Team goals→输入指标追踪)、事故后的 Correction of Errors; (e) 知识正典(en-primary,极其丰富且可取一手) — 贝索斯致股东信 1997-2021(1997 首封是奠基文本,每年附在信末;Day 1、遗憾最小化、long term)、《Working Backwards》Colin Bryar & Bill Carr(2021,运营机制圣经)、《The Everything Store》Brad Stone(2013,公司史)、《Amazon Unbound》Brad Stone(2021,权力与阴暗面续作)、《Invent and Wander》贝索斯文集(2020)、《The Amazon Way》/《Think Like Amazon》John Rossman(前亚马逊高管)、Amazon 官方 Leadership Principles 页(amazon.jobs,一手)、HBR『The Institutional Yes』(2007 贝索斯访谈); (f) 行业大佬/figures — Jeff Bezos(创始人,源头教义)、Andy Jassy(现任 CEO,OS 超越创始人的证据 + AWS 缔造者)、Colin Bryar(前贝索斯影子/TPM,《Working Backwards》作者)、Bill Carr(前数字媒体 VP,《Working Backwards》作者)、Jeff Wilke(前全球消费者 CEO,运营架构师)、John Rossman(前亚马逊、机制布道者/顾问)、Brad Stone(记者/编年史作者,批判性外部视角); (g) 争议/批判(必须保留,不能洗白) — 文化阴暗面(NYT 2015『Inside Amazon: Wrestling Big Ideas in a Bruising Workplace』揭露高压职场)、仓储与一线劳工争议、URA(unregretted attrition 强制淘汰)与 stack-ranking 的残酷、frugality + 高 bar = 燃尽(burnout);机制能否迁出亚马逊(cargo-culting:在初创或非科技公司照搬 PR/FAQ/输入指标/Bar Raiser 常失败);是贝索斯个人天才(personality)还是制度化机制(institution)—— OS 在贝索斯卸任后于 Jassy 治下延续,是机制派的证据; (h) 流派/思想谱系 — **信徒/机制布道派(Bryar & Carr《Working Backwards》+ 前亚马逊 operator 顾问圈,信 mechanisms 可移植、任何公司可安装)** vs **批判派(Brad Stone《Amazon Unbound》+ NYT + 劳工视角,认为 OS 与高淘汰的残酷机器不可分割,不该被浪漫化)** vs **情境/规模怀疑派(机制之所以有效是因为亚马逊特定的规模/现金流/创始人权力,照搬到小公司=cargo cult)** vs **创始人中心 vs 制度中心之争(是贝索斯个人 vs 可传承的机制)**。不含: 在亚马逊开店卖货/选品/PPC/FBA 的卖家运营(=cross-border-ecommerce)、AWS 云技术架构与运维、通用 MBA 管理理论泛泛而谈、把普通商业常识包装成『亚马逊独家秘诀』。) Master OS — automated mastery of 亚马逊管理之道 (The Amazon Way — Amazon 自身的领导力与运营操作系统) — 这个 master skill 蒸馏的不是『在亚马逊平台上开店卖货』(那是跨境电商运营,已由 cross-border-ecommerce 另蒸),也不是 AWS 云技术架构;而是亚马逊这家公司『怎么运营自己、怎么做决策、怎么招人、怎么创新、怎么规划』的一整套可迁移的管理机制(mechanisms)与心智操作系统。面向想在自己团队/公司引入亚马逊式机制的创始人/CEO/高管/运营负责人(COO)、产品经理与技术产品经理(PM/PMT)、组织与流程设计者(chief of staff / ops)、以及在亚马逊工作或准备面试亚马逊(著名的 LP 行为面试 + Bar Raiser)的人。覆盖: (a) 第一性张力 — 亚马逊 OS 的核心世界观分歧: **机制 >

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