bladecoderbladecoder/narrative-skills/skills/if/if-init-project/SKILL.md

if-init-project

Skill0 starsChanged 7 months agoMITView on GitHub

Create or normalize the canonical project structure for an Ink interactive fiction story with free map exploration and free-order character conversations.

In this repository27 other files it gives its agents.
- beta-reader-passSkill
- build-distributionSkill
- chapter-reviewSkill
- continuity-checkSkill
- create-character-bibleSkill
- define-style-bibleSkill
- draft-chapterSkill
- generate-high-level-outlineSkill
- if-design-dialogueSkill
- if-design-mapSkill
- if-design-progressionSkill
- if-design-structureSkill
- if-draft-inkSkill
- if-load-contextSkill
- if-plan-ink-sliceSkill
- if-playtest-reviewSkill
- if-sync-stateSkill
- ink-docSkill
- init-story-projectSkill
- load-story-contextSkill
- manuscript-reviewSkill
- plan-chapterSkill
- prepare-exportSkill
- rewrite-chapterSkill
- sync-story-bibleSkill
- update-character-stateSkill
- update-timelineSkill

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
Use this skill to initialize the current directory as an Ink interactive fiction project.
line 10
Very specific:
Ask only for missing information that blocks initialization, especially story.language.
line 24
Distinctive:
Use normal Unicode and correct orthography for the selected language.
line 104
Distinctive:
Create missing folders and files from the canonical IF structure.
line 109
Very specific:
Create 05_ink/main.ink as a minimal entrypoint with includes/placeholders only if no Ink source exists.
line 113
Distinctive:
Do not draft a full game here.
line 118
Distinctive:
Do not invent confirmed locations, characters, objects, or unlocks.
line 119
Distinctive:
Do not rename canonical files away from English names.
line 120

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

IF Init Project

Overview

Use this skill to initialize the current directory as an Ink interactive fiction project. It extends the traditional narrative project contract with design files for locations, dialogue, progression, state, Ink source, and playtest review.

Required Inputs

Collect or infer:

provisional title;
story language;
genre, tone, audience, POV, and tense;
premise and playable fantasy;
expected scope;
free exploration constraints;
known locations, characters, obstacles, inventory, knowledge, or skills.

Ask only for missing information that blocks initialization, especially story.language.

Files To Create Or Update

Create or normalize:

README.md
story.yaml

00_meta/
01_style/
02_story/
03_characters/

04_design/
  map.md
  locations.yaml
  dialogue_matrix.md
  progression.yaml
  state_model.md
  story_beats.md
  critical_path.md
  slices/

05_ink/
  main.ink
  locations/
  dialogues/
  systems/

06_playtest/
  route_matrix.md
  playability.review.md

07_continuity/
  canon_facts.yaml
  entities.yaml
  locations.yaml
  unresolved_threads.yaml

08_exports/

Metadata Contract

Persist this minimum contract in story.yaml:

project:
  title: ""
  format: "interactive_fiction_ink"
  status: "initialized"
story:
  genre: ""
  subgenre: ""
  language: ""
  audience: ""
  estimated_length: ""
  premise_status: "provisional"
narrative:
  tone: ""
  voice: ""
  pov: ""
  tense: ""
interactive:
  engine: "ink"
  entrypoint: "05_ink/main.ink"
  navigation_model: "free_2d_map"
  conversation_model: "free_order_dialogues"
workflow:
  canonical_root: "."
  initialized_at: ""
  next_skill: "if-design-structure"

Language Rules

Skill text, folder names, filenames, and YAML keys stay in English.
Human-readable project content is written in story.language.
Use normal Unicode and correct orthography for the selected language.

Procedure

Inspect the current directory and preserve useful existing material.
Create missing folders and files from the canonical IF structure.
Initialize story.yaml without overwriting confirmed metadata.
Seed design files with concise operational prompts in story.language.
Seed YAML files as valid structured empty data where no facts are known.
Create 05_ink/main.ink as a minimal entrypoint with includes/placeholders only if no Ink source exists.
Recommend if-design-structure next.

Restrictions

Do not draft a full game here.
Do not invent confirmed locations, characters, objects, or unlocks.
Do not rename canonical files away from English names.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free