Cinematography 180 Degree Rule logo

Cinematography 180 Degree Rule

Community
geegl
cinematography-180-degree-rule

用户提到180度法则、轴线、画面方向、分割线、摄影机放哪边

Overview

Publishergeegl
Repositorydirectorskills
Skill namecinematography-180-degree-rule
Stars
68
Forks
7
Bundled files
1
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by geegl on GitHub. Read the source before you install it.

Installation

Install the Cinematography 180 Degree Rule AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/geegl/directorskills/tree/main/output/books/cinematography-brown/cinematography-180-degree-rule
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/geegl/directorskills.git /tmp/directorskills
mkdir -p .claude/skills
cp -r /tmp/directorskills/output/books/cinematography-brown/cinematography-180-degree-rule .claude/skills/cinematography-180-degree-rule
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Cinematography 180 Degree Rule in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Cinematography 180 Degree Rule on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Cinematography 180 Degree Rule is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

180度法则(分割线原则)

R — 原文 (Reading)

观众的位置(或者说摄影机的位置)划下了这条线,有时叫作180度线或运动轴线。如果两个女人在车的同一侧观察车的运动,她们所见车的移动方向将会是一致的。 — Brown, 第6章, p.g_0026

I — 方法论骨架 (Interpretation)

180度法则是连续性的核心原则:

基本规则:两个角色之间定义一条轴线(分割线),摄影机必须始终在轴线的同一侧拍摄。违反此法则会导致画面方向反转,观众会困惑角色的位置关系。

为什么这条法则存在:不能让观众产生混淆。这是这条原则存在的唯一理由——它不是不可撼动的铁律,而是服务于观众理解的工具。

合法的打破方式:

  1. 中轴镜头:物体运动方向正对或远离摄影机(如车笔直开来),可用于过渡到另一侧
  2. 空间布局清晰:法庭、会议室等布局众所周知的场景,可以更灵活地打破分割线
  3. 摄影机移动:在镜头拍摄过程中摄影机移动越过轴线,观众能理解空间关系的改变
  4. 切到完全不同的画面:如果切到一个完全不同的画面再切回来,可以改变分割线
  5. 故意反转:当需要引入新人物从门口进入时,可以故意跳到另一侧

移动动作中的分割线:在打斗场景中,分割线会一直变化。导演和剪辑人员会想无视分割线增加运动感和迷失感,但要小心观众可能把两人弄混。

A1 — 书中的应用 (Past Application)

案例:沙发场景的分割线反转

  • 问题:一对夫妻坐在沙发上,摄影机在沙发前面拍摄。新人物需要从门口进入,但门口在沙发后面(分割线的另一侧)。
  • 方法论的使用:将摄影机移到沙发后面(打破分割线),这样沙发上的两人在前景,也能拍到第三人走进房间。虽然打破了分割线,但观众不会混淆,因为沙发的位置是已知的。
  • 结论:分割线可以被打破,前提是观众不会产生混淆。

案例:《正午》的连续性处理

  • 问题:多个人物在不同位置的复杂场景中如何保持画面方向?
  • 方法论的使用:影片中人物位置十分清晰,各归各位。连续性的某些规则可以放宽松一些,因为空间布局足够清晰。
  • 结论:当空间布局清晰时,可以更灵活地处理分割线。

A2 — 触发场景 (Future Trigger) ★

用户会在什么情境下需要这个 skill?

  1. 用户在设计多机位对话场景——"摄影机应该放哪边?"
  2. 用户遇到画面方向问题——"为什么我的镜头看起来角色位置反了?"
  3. 用户需要在分割线另一侧加入新机位——"怎么从另一侧拍?"

语言信号

  • "180度法则"、"轴线"、"分割线"、"不要越线"
  • "画面方向"、"角色位置反了"、"观众会搞混"
  • "摄影机放哪边"、"从哪一侧拍"
  • "中轴镜头"、"反转"

与相邻 skill 的区分

  • 与 master-scene 的区别:主场景法解决"先拍什么"的顺序问题,180度法则解决"从哪个方向拍"的方向问题。
  • 与 back-lighting 的区别:从后场打光是灯光方向原则,180度法则是摄影机位置原则。

E — 可执行步骤 (Execution)

  1. 建立轴线

    • 在两个角色之间画一条假想线
    • 确定摄影机始终在线的同一侧
    • 完成标准:所有机位都在轴线的同一侧
  2. 检查画面方向

    • 如果A从左看向右,B必须从右看向左
    • 如果车辆从左往右开,切换镜头后必须保持从左往右
    • 完成标准:所有画面方向一致且不令人困惑
  3. 需要打破分割线时使用合法方法

    • 先切到中轴镜头(物体正对摄影机),再切到另一侧

    • 或在摄影机移动过程中越过轴线

    • 或切到完全不同的画面再切回来

    • 完成标准:观众能理解空间关系的变化

    • 🔴 判停条件: 若观众在观看连续镜头时感到空间方向混乱("谁在左边?"),说明跳轴了——立即回到主镜头确认轴线位置,用中轴镜头或摄影机跨线运动过渡

B — 边界 (Boundary) ★

不要在以下情况使用此 skill

  • 用户在拍摄单人场景(没有轴线问题)
  • 用户在拍摄纪录片风格的自由镜头(连续性规则可以放宽)
  • 用户在讨论灯光问题而非摄影机位置

作者在书中警告的失败模式

  • 将法则当成铁律:180度法则不是不可打破的,关键是不让观众产生混淆。
  • 忽略移动动作的分割线变化:在打斗场景中,分割线会随人物移动而变化。
  • 打破分割线时没有过渡:直接跳到另一侧会让观众困惑,需要中轴镜头或摄影机移动来过渡。

反模式与常见错误

  • 跳轴无过渡:直接从轴线一侧切到另一侧,没有中轴镜头或摄影机移动作为过渡,观众瞬间失去空间方向感
  • 忽略移动场景的轴线变化:打斗/追逐中轴线随人物移动不断变化,仍按静态轴线处理导致画面方向混乱
  • 将180度法则与灯光方向混淆:法则是摄影机位置原则,不是灯光方向原则,两者独立运作

作者的盲点 / 时代局限

Blain Brown 的分析框架源自传统胶片摄影,对数字传感器的特性(如动态范围、高光滚降、暗部噪声)讨论不足。他假设摄影团队有充足的设备和时间,独立制作或低预算场景的应对策略覆盖较少。案例库以好莱坞和欧洲艺术片为主,对亚洲、拉美等非西方电影传统的摄影风格涉及有限。

此外,180度法则基于观众的空间认知模型,但现代观众经过 MTV 和短视频的视觉训练后,对跳轴的容忍度已显著提高。此外,该法则假设场景中有明确的两人对话轴线,对多人场景、运动场景或虚拟场景(如绿幕合成)的轴线处理讨论不足。

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Cinematography 180 Degree Rule AI skill do?

用户提到180度法则、轴线、画面方向、分割线、摄影机放哪边

Why use Cinematography 180 Degree Rule on TypingMind?

Because you install it once and use it with any model. Cinematography 180 Degree Rule is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Cinematography 180 Degree Rule in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/geegl/directorskills/tree/main/output/books/cinematography-brown/cinematography-180-degree-rule. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Cinematography 180 Degree Rule?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Cinematography 180 Degree Rule?

As many as you like. As long as a model supports skills, you can use Cinematography 180 Degree Rule with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Cinematography 180 Degree Rule AI skill free?

Yes. It is published on GitHub by geegl under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇