Hard Sci Fi Visual Director logo

Hard Sci Fi Visual Director

Community
62656456
hard-sci-fi-visual-director

Script-first visual design for original hard-science-fiction worlds, scenes, film stills, visual bibles, nonhuman life and ecology, mecha and combat-mecha families, future equipment, cockpits and UI/HMI. Use for 硬科幻视觉、科幻场景与世界观、外星生命、原创机甲与巨兽、未来界面与装备、摄影质感、提示词优化诊断 and requested images. Match source facts, evidence, physics and visual authorship to the current task; exclude franchise copying and actionable weapon construction.

Overview

Publisher62656456
Repositoryai-film-skills
Skill namehard-sci-fi-visual-director
Stars
101
Forks
19
Bundled files
20
LicenseApache-2.0
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.

  • 20 bundled files

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

  • Open source

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

Installation

Install the Hard Sci Fi Visual Director 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/62656456/ai-film-skills/tree/main/experimental/hard-sci-fi-visual-director
  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/62656456/ai-film-skills.git /tmp/ai-film-skills
mkdir -p .claude/skills
cp -r /tmp/ai-film-skills/experimental/hard-sci-fi-visual-director .claude/skills/hard-sci-fi-visual-director
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Hard Sci Fi Visual Director 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 Hard Sci Fi Visual Director 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 Hard Sci Fi Visual Director 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.

Hard Sci-Fi Visual Director

Preserve the current story and approved identity while making the selected science, world, behavior, camera and light visible. There is no cross-project palette, era, weather, protagonist, lens, body plan or industrial silhouette. Engineering explains the selected form; it does not replace visual authorship.

Choose the actual task before loading

TaskRead and deliver
A bounded question, known parameter or one visible defectRead the relevant topic below; answer that question with the needed evidence or one causal correction. Do not create a world bible, research report or full checklist.
A local prompt/image correction within an approved designRead the current target, affected source passage and locks. Reuse valid evidence, change only the named variables and check their consequences. Load only the relevant topic; research a newly introduced mechanism or unsupported claim, not the whole world again.
A new bounded scene, asset or visual proposalRead source-to-visual derivation, identify the open decisions, then load only the affected professional topics. Use the research engine for design-changing gaps; do not inflate one scene into every system or output card.
A complete world, visual bible, system/family or substantial redesignRead full design workflow, source derivation and research engine, then the applicable topics below. Retain the complete method and evidence gates; do not substitute a shallow summary.
Generate from an already decided design, or inspect an existing imagePreserve the design; read aesthetic audit and the relevant image/continuity topic. Generation requires the user's request and actual available tools. A new design still follows its design route before generation.

A diagnosis alone does not request rewriting or generation. Current “continue” inherits the active medium and stage. Same-context references already read and unchanged can be reused; task changes load the gap. Do not reopen accepted choices merely to populate a template.

Professional topics: load only the applicable contract

  • Source authority, dramatic function, facts versus open gaps and single-frame capacity: script-to-visual-derivation.md.
  • New design-changing inference, evidence search, speculative amplitude and no-copy mechanism transfer: inspiration-engine.md. Reuse current approved evidence within its scope; actual new gaps still require opened sources before final design claims.
  • Affected gravity, medium, energy, heat, load, motion or failure: physics-and-engineering.md.
  • Location, inhabited world or multi-shot geography: scene-world-design.md; add scene-routes.md only for matching environmental constraints. A neutral isolated asset needs no invented geography.
  • New or changed style, light, color and exposure: style-color-system.md. Photographed live-action/hybrid routes also use live-action-cinematography.md; illustration and UI do not inherit practical-set requirements.
  • Reference alignment, composition or visible image diagnosis: cinematic-image-direction.md.
  • People, materials, tools, vehicles, habitats or equipment: relevant parts of production-design.md.
  • Nonhuman organism, ecology or biological environment: organism-and-ecology.md. Giant organisms add mecha-and-megafauna.md; giant machines use the latter without inventing biology.
  • Combat-mecha identity, body rhythm, silhouette or repair: combat-mecha-form-direction.md after the mecha route. Form and two or three cooperating identity anchors precede engineering detail; preserve the current stage's single-author or family contract.
  • Visible cockpit, indicator, alarm, control, FUI/HMI or interaction: future-interface-systems.md. Only applicable task, body/system relation and feedback enter the design.
  • Weapon, defense or rescue/hazard equipment defined by effect/protection/logistics: future-weapon-systems.md. Ordinary civilian equipment uses production design; no automatic military subsystem.
  • Related frames, approved-frame derivation, bible continuity or CONTACT-SHEET: visual-continuity.md.
  • Actual direct images and image diagnosis: aesthetic-audit.md. Examples or validation sets: prompt-examples.md, only when requested.

All professional references stay inside this package. Names and examples are aids, not a hidden scene menu or instruction to read every topic.

Constraints that remain in every mode

  1. Current user corrections, the named source/beat and approved locks outrank research, proposals and examples. Keep FACT, necessary DERIVATION, reversible PROPOSAL and LOCKED decisions distinct. Generated images and internal scores do not become canon or approval.
  2. Research concerns a real open decision. Separate verified fact, constrained extrapolation and explicit hypothesis; open authoritative sources for new design-changing evidence. Reuse only still-applicable approved evidence. If a source cannot be checked, preserve the unresolved boundary and the existing offline-preliminary rule; do not invent verification.
  3. A scientific constraint conflicting with story is an explicit choice for the user, not silent script repair. Fictional rules have visible costs and consequences; real weapons guidance stays non-actionable.
  4. A single still holds one compatible moment. Put the selected action, discovery, relation, place, aftermath or asset function in visible evidence at the intended scale; UI text and lore cannot rescue missing composition. Do not force a crisis, person, operator, crowd or sacrifice into an unrelated task.
  5. Keep world geometry, light, identity, contact and entering/exit states continuous. Form, material and detail follow current purpose and history, not automatic grime, LEDs, fog or franchise silhouettes. Strong color, silence, wonder, intimate scale and visual extremity remain available.
  6. Preserve approved bodies and user-directed camera decisions. New combat-mecha form is judged first by readable silhouette and body rhythm; family divergence cannot be cosmetic recoloring. Referenced designs supply relationships and mechanisms, not recognizable parts to collage.

Deliver, check and repair at the requested scope

Lead with the requested answer, design, prompt or actual image. A prompt request gets one complete copy-ready prompt and only scene-specific necessary constraints; a diagnosis gets dominant failure, visible evidence and one causal correction. A full design package uses the full-workflow output contract. Mecha form repair stays at the form stage until its contract permits expansion; related multi-image work keeps its actual bible and stable identities.

Keep the source/gap cards and checks internal unless requested or needed to explain an unresolved choice. Apply affected professional gates once, repair concrete failures and recheck affected consequences. Do not rerun the entire twenty-step world workflow for wording, crop, exposure or a local material change that leaves its evidence and identity intact.

Text consistency, source verification, actual generation, visible inspection and user acceptance are separate states. A missing tool or unverified hard constraint stays explicit. Do not claim reduced reading, a successful image or an internal score proves speed, semantic accuracy or the user's taste.

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 Hard Sci Fi Visual Director AI skill do?

Script-first visual design for original hard-science-fiction worlds, scenes, film stills, visual bibles, nonhuman life and ecology, mecha and combat-mecha families, future equipment, cockpits and UI/HMI. Use for 硬科幻视觉、科幻场景与世界观、外星生命、原创机甲与巨兽、未来界面与装备、摄影质感、提示词优化诊断 and requested images. Match source facts, evidence, physics and visual authorship to the current task; exclude franchise copying and actionable weapon construction.

Why use Hard Sci Fi Visual Director on TypingMind?

Because you install it once and use it with any model. Hard Sci Fi Visual Director 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 Hard Sci Fi Visual Director in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/62656456/ai-film-skills/tree/main/experimental/hard-sci-fi-visual-director. 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 Hard Sci Fi Visual Director?

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 Hard Sci Fi Visual Director?

As many as you like. As long as a model supports skills, you can use Hard Sci Fi Visual Director with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Hard Sci Fi Visual Director AI skill free?

Yes. It is published on GitHub by 62656456 under the Apache-2.0 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 👇