「writer」の検索結果

Korean and French screenwriting practice (韩国/法国编剧方法) — from the international masterclass; Oh Seung-uk (Christmas in August, The Shameless; field research in disguise, "write the emotion", first act and last act first, spaces as skeleton, reading to hostile listeners, surviving producers), Choi Seok-hwan (King and the Clown; genre as promise to the audience, "story = deepening crisis + intensifying desire", two reversals and bittersweet endings, the producer/director/writer trio), and Frédéric Auburtin (Paris je t'aime; dialogue last, Italian-style table reads, "12 lines not 13", dignity for characters, originals born from commissions, editing by emotion). Use when working in a Korean-style commercial drama or genre film, a French auteur/commission context, when planning field research, when a producer relationship is the problem, or when you need the Korean "three live together" development model or the French "emotion first, structure second" editing approach.

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

Writing a Succession-style ensemble series (继承之战群像剧写法) — distilled from Jesse Armstrong's complete shooting scripts for all four seasons, 39 episodes (Faber 2023), with his introductions and footnotes, plus Frank Rich's and Lucy Prebble's essays on the writers' room. Covers the invisible-act three-test for scripts with no ACT marks, container episodes built on a ceremony's running order, pressure chambers, one core question per episode, finales with fewer and longer scenes, the absent protagonist at the climax, humiliation passed downward, stage directions carrying subtext and "maybe", reversals turned on one word, writing long, alts, the mega-chart, and engineering an ending once the plot engine loses pressure. Use when the user wants a dynastic family drama, a media-power ensemble, a wedding/funeral/summit set piece, a streaming hour with no act breaks, a finale that redraws alliances, or asks how to "Succession-ize" a script or kill a lead mid-season.

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

Character creation, protagonist/antagonist design and dramatic conflict for scripts (人物/对手/冲突) — merged from Lajos Egri (three-dimensional character, orchestration, unity of opposites, pivotal character, rising vs static vs jumping conflict, transition), William Indick's Psychology for Screenwriters (Freud, Erikson, Jung archetypes, Campbell/Murdock hero journeys, Adler, Rollo May), Robert McKee (characterization vs true character, dimensions, gap, antagonism principle), Neill Hicks (character invocation, self-concept, cognitive dissonance, five conflict focuses, Maslow), Lisa Cron (desire vs misbelief), and Lu Jun (人物要活八要, 对手要强, 给对手一把刀, 最强的对手是自己, 不许请祥云). Use when building a protagonist, an antagonist or a cast, when a character feels flat or acts out of character, when conflict stalls or jumps, when a villain is too weak, when designing an arc or motive, or when diagnosing melodrama.

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

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.

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

Case studies of American screenwriting (美国电影剧作案例) — Mei Feng's readings of the Hollywood Western (value pairs, four oppositions), screwball comedy (strong heroine, buddy vs adversary two-hander), Billy Wilder (disguise, Lubitsch touch, meet-cute), Hitchcock and his writers, Adaptation, Mildred Pierce (eight drafts, woman's film + noir), Thelma & Louise ("but" method, mirror pair), Fargo (Coen method), Good Will Hunting (five-part structure), American Beauty (POV strategy, genre mix), Eternal Sunshine (1:5:1, image motifs); Walter's American Graffiti; the Hollywood masterclass films (Bourne, Guardians, Zootopia, Thor); Hoxter's Winter's Bone and Jojo Rabbit; Snyder's Miss Congeniality; Field's Chinatown. Use when you want a worked example of how a specific American film's script is built, when analysing a film for structure, character or theme, or when looking for a model to imitate for a Western, screwball, noir, buddy, coming-of-age, black comedy or non-linear romance.

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

公众号长文写作（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.

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

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.

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

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.

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

Draft a defensible construction change order with entitlement basis, scope delta, itemised pricing, and schedule impact. Use when asked to write a change order, price extra work, draft a CO or COR/PCO, respond to a directive for changed work, or paper a field change. Produces a complete change order request with contract-clause entitlement, labour/material/equipment/OH&P breakdown, time impact statement, and reservation of rights.

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

Convert a git log, commit list, or release notes into a polished, user-facing changelog. Use when writing release notes, generating a CHANGELOG.md entry, or documenting what changed in a version. Produces a structured changelog section with version header, categorised changes, and migration notes. For an already-curated change list use changelog-writer instead.

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

Turn a list of changes, commits, or PRs into clean release notes / a changelog entry. Use when asked to write release notes, a changelog, or a version announcement from raw changes. Produces a Keep-a-Changelog-style entry grouped by type (Added/Changed/Fixed/etc.), written for users — surfacing breaking changes and upgrade notes up top. To go straight from a raw git log use changelog-generator instead.

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

Write clear, developer-facing API documentation. Use when asked to document an API endpoint, write API reference docs, create a developer guide, or turn a raw spec/Postman collection into documentation. Produces endpoint documentation with descriptions, parameters, request/response examples, and error codes.

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

Write warm, direct collaboration comments. Trigger: PR feedback, issue replies, reviews, Slack messages, or GitHub comments.

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

Use when reviewing a DataFusion Comet pull request that touches native or JVM columnar shuffle, the shuffle writers and readers, partitioning, the Arrow IPC block format, shuffle compression, or the Celeborn integration. Load alongside review-comet-pr.

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

Use when reviewing a DataFusion Comet pull request that touches Iceberg writes, the split-operator write plan (IcebergWriteStrategy, IcebergWriteExec, IcebergCommitExec), the native Iceberg writer (CometIcebergWriteExec, iceberg_write.rs, iceberg_partition_path.rs), its eligibility gate (CometIcebergNativeWrite), or the iceberg-rust pin. Load alongside review-comet-pr.

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

Edit drafts into sharper, more human writing while preserving the writer's personal voice, or detect AI-slop patterns without rewriting. Use when the user wants a draft clearer, more direct, more opinionated, or less AI-sounding, or asks whether writing reads as AI. Also the default writing standard for all agent output: 80% ASD-STE100 controlled language plus the format ladder (prose, diagram, HTML page, explainer video).

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

Edit drafts into sharper, more human writing while preserving the writer's personal voice, or detect AI-slop patterns without rewriting. Use when the user wants a draft clearer, more direct, more opinionated, or less AI-sounding, or asks whether writing reads as AI.

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

Research LinkedIn profiles and write personalized messages for any LinkedIn message type — connection requests, InMails, DMs, message requests, post comments, and comment replies. Takes LinkedIn URLs as input, researches each person (profile data + recent posts via Apify), and generates messages tailored to each lead's background, interests, and recent activity. Exports tool-ready CSVs for Dripify, Expandi, Botdog, PhantomBuster, or generic format. No LinkedIn cookies or login required.

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

Maintain, debug, and recover MTGA's Trae native custom-model route. Use when Trae native integration fails, Trae updates shift ai_agent.dll hook offsets, errors such as 4028/4054/429 appear, native rewriter or SseOpenPayload URL rewriting needs diagnosis, or Codex needs to avoid repeating prior renderer-JS/private-protocol dead ends.

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

Build Simulink models that co-simulate with Eclipse SUMO traffic simulator. Use when creating SUMO-Simulink co-simulation, traffic simulation, TraCI connection, vehicle-in-the-loop testing, or ADAS scenario validation with SUMO. Covers Server/Client setup, Reader/Writer/Actor block configuration, random traffic generation, ego vehicle control, and SUMO file creation. Also use when the user mentions SumoInterfaceLibrary, .sumocfg files, or wants to connect Simulink to an external traffic simulator.

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

Read and write 3-D point cloud data using Lidar Toolbox file I/O. Covers PLY, PCD, LAS/LAZ, PCAP (Velodyne/Ouster/Hesai), E57, and IDC (Ibeo) formats. Use when loading point clouds from disk, saving to disk, choosing the correct reader or writer for a file format, extracting or preserving lidar point attributes, reading Ibeo IDC sensor recordings, or converting between formats.

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

Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section. Transforms your writing process from solo effort to collaborative partnership.

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