cinematic-story-architecture

nolanx-ai/nolanx.ai · Agent Skill

Creates script structure for films, trailers, and short dramas, focusing on narrative, escalation, and production-ready scenes.

Jump to install ↓

Overview

Publishernolanx-aiOrganization
Repositorynolanx-ai/nolanx.ai ↗
Skill foldercinematic-story-architecture
Stars1,747
Bundled files1
LicenseMIT
Last updatedMay 12, 2026
LinksSkill source ↗ · Repository ↗

Mozgi check

What we found in the skill files. Details come with a subscription.

Security
low risk · no obvious risks found — the full report shows the details
Compatibility
instructions only — works with most agents
Similar skills
72 similar skills found
Also with subscription

Installation

A skill is a folder with a SKILL.md file. Pick your agent and run the commands in a terminal (macOS, Linux or Git Bash on Windows) from your project root.

Copy the prompt into Claude, Codex or another assistant: it will review the skill and install it for you.

Install the “cinematic-story-architecture” skill from mozgi.io (https://mozgi.io/skills/cinematic-story-architecture/) for me.

1. Download the archive: https://mozgi.io/skills/cinematic-story-architecture/download
   If it fails, take the skill folder from the source: https://github.com/nolanx-ai/nolanx.ai/tree/main/.nolanx/skills/cinematic-story-architecture
2. Read SKILL.md and the other files. Check the skill is safe: no hidden commands, no sending data elsewhere, no scripts doing something other than described. If anything looks suspicious, stop and tell me.
3. Put the “cinematic-story-architecture” folder into your agent's skills folder: .claude/skills/ for Claude Code, .agents/skills/ for Codex, .cursor/skills/ for Cursor, .gemini/skills/ for Gemini CLI. Inside the project if we are in one, otherwise in the home folder (~/.claude/skills/ etc.).
4. Make sure <skills folder>/cinematic-story-architecture/SKILL.md exists.
5. Briefly tell me what this skill does and offer to try it on my task.

If you cannot do a step yourself, tell me what to click or type.

Review the source files

1 file Download Zip

Read SKILL.md and any companion files before deciding whether to install. Click a file to preview it.

SKILL.md contents

Original author text · read-only

Cinematic Story Architecture

Apply this skill when the request is narrative, dramatic, episodic, trailer-like, or adaptation-driven.

Goals

  • Build a clear dramatic spine before visual generation.
  • Turn loose prompts into production-ready scene beats.
  • Preserve user-provided IP, names, locations, lore, and emotional intent exactly.
  • Prioritize a strong first 3 seconds and meaningful escalation every beat.

Workflow

1. Identify story mode: short drama, film scene, trailer, ad narrative, adaptation, or action vignette.

2. Lock the narrative engine:

  • protagonist desire
  • obstacle / pressure
  • turning point
  • payoff or cliffhanger

3. Break output into playable beats, not exposition blocks.

4. For each beat, define:

  • action
  • emotional turn
  • visual revelation
  • camera intention
  • dialogue or silence function

5. Ensure each successive beat either raises stakes, reveals new information, or reverses power.

Structural Rules

  • Start from conflict, pressure, mystery, or impact. Do not warm up slowly.
  • Prefer 3-7 dense beats for short-form scenes.
  • Every beat must justify its screen time visually.
  • Dialogue should change the power balance or emotional state, not merely explain background.
  • If adaptation is requested, preserve source plot facts and role relationships unless the user explicitly asks to rewrite them.

Beat Design Heuristics

  • Hook: shock, threat, reversal, desire, countdown, or emotional rupture.
  • Middle: pursuit, confrontation, discovery, transformation, or worsening trap.
  • End: twist, unresolved danger, emotional slam, or irreversible action.

Output Requirements

When producing script or storyboard-facing planning:

  • Name beats clearly.
  • Keep recurring world elements stable.
  • Specify why each beat exists.
  • Carry aspect ratio and format intent across all beats.

Guardrails

  • Do not flatten everything into generic cinematic prose.
  • Do not redesign the world every shot.
  • Do not rename canon entities.
  • Do not rely on narration to do the work of staging.

Frequently asked questions

What does the cinematic-story-architecture skill do?

Creates script structure for films, trailers, and short dramas, focusing on narrative, escalation, and production-ready scenes.

How do I install cinematic-story-architecture?

Open the “Installation” block on this page and pick your agent — Claude Code, Codex, Cursor or Gemini CLI — for ready-made commands that copy the skill folder to the right place. Or copy the prompt from the “Via assistant” tab and let the assistant review and install the skill.

Which AI models work with cinematic-story-architecture?

Skills are plain Markdown instructions (the Agent Skills format), so cinematic-story-architecture works with any agent that reads SKILL.md: Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and more. The model loads the instructions only when a task matches the skill's description.

Is cinematic-story-architecture free?

The skill is published openly by nolanx-ai under the MIT license. The skill itself costs nothing — you only pay your AI provider for the tokens you use.

Is it safe to install skills?

A skill is a set of instructions your agent will follow, so read SKILL.md and its companion files before installing. Scripts in the skill folder only run if your agent runs them — keep an eye on what it does and do not grant unnecessary permissions.

How is a skill different from an MCP server or a plugin?

An MCP server or plugin gives the model new tools — code that runs and returns a result. A skill gives it knowledge and process: how to approach a task, which steps to follow and what good output looks like. It needs no server or API key.

Related skills

All skills →