1Why the Kit is injected in full

This document is a translation in substance. The reference is the original document in French; extensions and changes are always made there.

This guide is for you, not for the AI. It describes how to start a new project from the Kit.

Before the procedure, one important point: the Kit is a coherent system. Its files are not independent bricks to be picked one by one — they depend on each other. Each stylesheet has an associated reference document describing how to use it. The Registry declares the active versions. The technical prompt and the common structure set the normative contract that all your project files apply.

Injecting the Kit partially — forgetting a Reference, replacing a stylesheet without its Registry declaration, leaving an old prompt in place — produces silent inconsistencies that only show when a document is generated. The symptom is then a broken layout or, worse, lost content.

Simple rule: the Kit is uploaded in full, as delivered. Every file listed in §3 goes into the working tree in one go. No picking and choosing, no file-by-file replacement. This rule holds for initialisation as for later updates.

2The information to prepare

Before opening a session, prepare the following pieces of information.

3Creating the project and injecting the Kit

Create a new project. The name is up to you. Then upload into its context every Kit file listed below, without exception.

These files will not be modified by your project — they are the same for every project using this Kit. They provide the formatting rules, the permanent instructions and the visual references.

Your project's own files — Registry, project prompt, glossary, customised cover sheet, any data modules — are not uploaded at this stage: they are created from scratch during the first session, from the normative skeletons in Common Structure.

4Starting the first session

Once every Kit file is in the working tree, open a conversation and paste the text below as the first message.

That text is an enabler: it forces every source of truth to be read in the right order, an explicit reading report, confirmation of your configuration, and a wait for your go-ahead before a single file is created. The result is coherent because no step can be skipped.

SETTING UP A NEW PROJECT — FULL KIT INJECTION
==============================
 
PROJECT CONFIGURATION :
------------------------------
 
Project prefix : [YOUR PREFIX]
Full name : [PROJECT NAME]
My name : [YOUR NAME]
Language : [FR / EN / DE / LU]
 
MANDATORY READING — STRICT ORDER :
------------------------------
 
Before creating any project file, read in this order :
 
1. Kit - Projet - Prompt (TS).docx
   — permanent technical instructions.
2. Kit - Stylesheet - General - Code.js + Reference.docx
   — formatting engine for all documents.
3. Kit - Stylesheet - Glossary - Code.js + Reference.docx
   — stylesheet of the project glossary.
4. Kit - Stylesheet - YAML - Code.js + Reference.docx
   — code and YAML blocks in the documentation.
5. Kit - Stylesheet - HTML - Code.js + Reference.docx
   — mirror HTML stylesheet.
6. Kit - Projet - Structure commune (TS).docx
   — normative contract of the project files and skeletons.
7. Kit - Projet - Convention de nommage (TS).docx
   — naming rules.
8. Kit - Documentation - Quality Control (TS).docx
   — mandatory validation chain and session prerequisites.
9. Kit - Projet - Guide d'initialisation (TS).docx
   — this guide.
 
READING REPORT — ANSWER BEFORE GOING ON :
------------------------------
 
For each document in the list above :
− read in full : yes / no
− version or timestamp recorded
 
Then confirm :
− the four configuration items
− the list of optional data modules wanted
  (brands, variable names, home-automation entities,
  Reading Guide, project cover sheet) and their value
 
STOP CONDITIONS :
------------------------------
 
If any of these is met, full stop and explicit report
before any creation :
 
− a Kit file is missing from the working tree
− a version number declared in the Registry does not
  match the actual version of the file
− two files of the same pair carry different timestamps
− a configuration item is missing or ambiguous
 
AFTER REPORT AND CONFIRMATIONS — WAIT FOR THE GO :
------------------------------
 
Create no project file before an explicit « go » has been
received in the chat. Announce the full plan first : order
of the files to produce, intended content, sequential
delivery per Kit - Projet - Prompt §9.

After the reading report and the confirmation of your optional modules, simply answer “go” in the chat to trigger the creation of the project files.

5What happens next

All the technical work is taken care of. You have nothing technical to decide beyond the four pieces of information in §2 and the optional modules confirmed at step 2.

6Working day to day

6.1Start of session

Each conversation stands alone — nothing is retained from the previous session. Continuity comes from the project's files. At the start of each session the AI checks that everything is in order before beginning.

If a file is missing, it will tell you. Upload it and carry on.

6.2End of session

To end a session, simply say:

And now to the end of session, please.

You will automatically receive a session summary, a file inventory and, if needed, an updated project prompt. The list of files to upload before the next session is given as well.

6.3Keeping files current

The most important rule: after each session, upload the updated files delivered to you into the project. Without that step, the next session starts from old files.

Depending on the flags enabled in your Registry, not every file in the table below is necessarily present in your project. Upload only those that actually exist.

7The cover page in your documents

Every document this Kit generates begins with a cover page carrying the title, subtitle and date. The header and footer are automatically suppressed on that first page for a clean result — they appear only from page 2.

The Kit handles this automatically, with no action from you.