「iter」の検索結果

Mainland-Chinese TV-series craft, documents and production chain (国产剧创作体系与制片链) — the China layer parallel to the Japanese and Korean/French skills. Distilled from Yao Kougen 姚扣根《电视剧写作概论》(2016; series taxonomy, four Chinese script formats, the 3-minute/15-minute/episode-end suspense law, 36 situations), Zhang Wei 张巍《电视剧改编教程》(2014; five source types, sell-point migration, six case studies), Zhang Mingzhi & Song Peiyi《电视剧出品人与制片人教程》(2016; running-time rules, two-stage censorship, scene-breakdown sheet, contracts), Zhao Binbin《影视剧片段改编教程》(2016; film to stage fragment), plus official Chinese renderings of US TV terms from the translated Douglas and Blum textbooks. Use when writing or judging a 国产剧, turning a novel or IP into a 30–50 episode drama, writing a 策划书 / 分集梗概 / 人物小传, formatting a Chinese teleplay, sizing episode count and word count, checking content red lines and the 立项/备案/审查 chain, reading a Chinese screenwriter contract, or mapping US series vocabulary onto Chinese usage.

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

Draft a structured preregistration document (OSF, AsPredicted, or AEA RCT Registry style) from a research spec or free-form study description. Output is a Markdown file with hypotheses, design, sampling plan, analysis plan, exclusions, and inference criteria — annotated with MUST / SHOULD / MAY clarity flags. Use when user says "preregister", "draft a preregistration", "OSF preregistration", "AsPredicted", "AEA RCT registry", "PAP", "preanalysis plan", or before launching an experiment / data collection / analysis on data the analyst has not yet seen. NOT a registry submission tool — produces a document the user uploads to OSF / AsPredicted / AEA themselves.

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

公众号长文写作（1500–4000 字）。先诊断作者手上已有什么（一个念头 / 一堆素材 / 半篇草稿 / 一份大纲 / 一篇不满意的成稿），再路由到对应的六种写法之一，产出成稿并过公众号专属质检。当用户说"写篇公众号""帮我写文章""这个主题怎么写""我有一堆素材不知道怎么组织""帮我扩写""这篇改一下""写不下去了""长文""深度文"时触发。

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

小红书笔记正文撰写。输入主题/产品/经历/素材，产出可直接发布的小红书正文（含开头 3 行、分段骨架、结尾互动、标签组合、合规自检）。覆盖种草测评、干货教程、个人故事、合集清单、避雷拔草、好物分享、经验复盘 7 种笔记类型。当用户说"写小红书""小红书文案""发笔记""笔记正文""种草文""种草笔记""避雷帖""干货笔记""帮我写篇小红书""这个怎么发小红书""小红书怎么写""笔记体检""改成小红书风格"时触发。标题批量生成交给 space-xhs-title，封面/配图交给 xhs-html。

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

AI DevKit · Review and improve documentation for novice users. Use when users ask to review docs, improve documentation, audit README files, evaluate API docs, review guides, or improve technical writing.

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

Transform photos, film stills, or new scene descriptions into the observed visual grammar of the 2026 animated film 《牛来》. Use when the user asks for 牛来风格、牛来正片风格、粗粝低模动物 3D、把真人画面改成牛来式动画，or requests iterative comparison against 《牛来》 references. Default to the rough film-3D mode; use the separate ink-poster mode only when the user explicitly asks for the movie poster look.

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

Edit any video by conversation. Transcribe, cut, color grade, generate overlay animations, burn subtitles — for talking heads, montages, tutorials, travel, interviews. No presets, no menus. Ask questions, confirm the plan, execute, iterate, persist. Production-correctness rules are hard; everything else is artistic freedom.

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

Analyze branch commits and consolidate iterative modifications.

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

Use when preserving product intent, acceptance criteria, decision memory, open loops, roadmap context, or the product-manager continuity layer of an agent team.

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

Recover source-bound buyer jobs, struggling moments, desired progress, forces, workarounds, information acts, journey states, criteria, constraints, roles, locales, and authentic language. Use on approved ICP hypotheses plus customer, search, review, forum, procurement, support, or public-market evidence before designing an AI-visibility prompt architecture.

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

Creates explicit validation checkpoints (verification gates) between project phases to catch errors early and ensure quality before proceeding. Use when the user asks about quality gates, milestone checks, phase transitions, approval steps, go/no-go decision points, or preventing cascading errors across a multi-step workflow. Produces acceptance criteria checklists, automated CI gate configurations, manual sign-off requirements, and conditional review rules for scenarios such as security changes, API changes, or database migrations.

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

Build a playable prototype in about an hour to answer one question — is it fun? — with greybox primitives, a hard timebox, and explicit keep/kill criteria. Use when prototyping a mechanic, making a vertical slice or MVP, greyboxing/blockout, or judging throwaway vs keep.

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

Build, refresh, report, or probe an accessibility coverage matrix across criteria, surfaces, and evidence methods. Use when assessing coverage with the accessibility runtime harness and generated evidence bundle.

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

Design LLM-as-Judge evaluators for subjective criteria that code-based checks cannot handle. Use when a failure mode requires interpretation (tone, faithfulness, relevance, completeness). Do NOT use when the failure mode can be checked with code (regex, schema validation, execution tests); use `write-code-eval`. To validate an existing judge, use `validate-evaluator`.

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

Confirm a change before merge. `/check verify` drives the real app to prove behavior against the spec (every acceptance criterion met, every surface built). `/check review` runs a senior code review on a fresh model, one that did not write the code. Verify after /develop, review before a PR. Writes to docs/reviews/, never edits code.

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

Drive structured autoresearch iteration after evo:discover and the baseline commit. Use when the user invokes /evo:optimize or asks to try ideas, try variants, run experiments, use available GPUs, improve the current best/frontier, continue an evo search, or compare candidate changes in an evo workspace. The orchestrator plans and spawns optimization subagents; candidate edits/runs belong to those subagents. Width is set via subagents=N (1 for serial workloads, larger for parallel); the loop's structural value applies at any width.

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

Creates reusable, source-traced research reports and coordinates provider/mode lanes with original exports. Use for 深度研究, 调研报告, literature reviews, market or company research, and ChatGPT/Kimi/UniFuncs research routes. Technology choice uses tech-selection; competitor code uses competitors-analysis.

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

Writes educational Teams channel posts about Claude Code features and best practices, using templates emphasizing concrete examples and underlying principles (e.g. context engineering). Use when writing a Teams post or announcement to teach colleagues Claude Code usage, announce a feature, share a tip, or document a lesson learned.

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

Prepare a promotion defence (晋升答辩) for a level-based promotion process common at Chinese technology companies: the materials, the presentation structure, the evidence for the next level, and a rehearsal of the committee's questions. Use when asked 帮我准备晋升答辩, 晋升述职, 晋升 PPT, how do I prepare for my promotion committee, or 答辩问题. Produces a level-gap analysis against the target level's criteria, the defence presentation outline in Chinese, a timed talk track, and a question bank with answer points, then a mock committee round.

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

Use when asked 写作业指导书, SOP 作业指导书, 工序作业标准, 标准作业书, 新员工看得懂的操作说明, WI 怎么写, or write a shop-floor work instruction for a production or inspection step in a Chinese factory. Produces a one-station 作业指导书 in Chinese with the header block (文件编号, 版本, 工序, 产品, 标准工时), materials and tools, numbered steps with key points (要点) and the reasons, quality checks and limits, safety notes and PPE, photo or diagram placeholders, abnormal-situation handling, and a revision record, written for a new operator.

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

Compare job levels (职级) across Chinese technology companies and against international ladders, to judge an offer, a job move or a promotion target: what a level usually means in scope and expectations, how levels roughly line up, and what to ask the recruiter. Use when asked P7 相当于什么级别, 跳槽职级怎么对标, 字节 2-2 对应阿里什么, 这个 offer 的职级合理吗, compare Chinese tech levels, or how does Alibaba P-level map to Google levels. Produces a level comparison built from the person's own ladders and offer details, a scope-and-expectation profile for each level, the negotiation questions to ask, and a clear note on what is approximate.

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

Use when asked 帮我写开题报告, 开题答辩怎么准备, 文献综述怎么写, 技术路线图, 研究内容和创新点, or write a thesis proposal for a Chinese university. Produces a 开题报告 in the section order Chinese universities use (选题背景与意义, 国内外研究现状, 研究内容与目标, 研究方法与技术路线, 创新点, 研究基础, 进度安排, 预期成果, 参考文献), a literature review plan, a technical route diagram in text, and the questions the 开题答辩 panel is likely to ask.

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

Use when asked 5S 检查表, 6S 管理, 现场管理检查, 5S 评分标准, 车间 6S 稽核, 做一份 5S 推行计划, or design a 5S or 6S audit for a workshop, warehouse or office in a Chinese factory. Produces an audit checklist for the area with scored criteria for 整理, 整顿, 清扫, 清洁, 素养 (and 安全 for 6S), a scoring guide with photo evidence rules, a results summary and red-tag list, a corrective-action tracker with owners and dates, and an audit rota, in Chinese.

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

Run a consulting client discovery session — uncover the real problem, scope, and decision process. Use when asked to prepare for a client discovery call, qualify a consulting lead, scope an engagement, or run a kickoff. Produces a discovery plan — the questions that surface the real problem (not the stated one), budget/authority/timeline qualifiers, success criteria, red flags, and a follow-up that leads to a proposal.

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