1Welcome

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

This documentation kit comes in two complementary forms: a paper binder and a website. Both hold the same reference documentation, each in the format that suits its use — the binder for reading on its own and handing on without any computer access, the website for quick access from any device, with clickable navigation and documents you can copy in one move.

The two forms were designed together. Neither is the main version of the other.

This guide helps you find your bearings — whether you are opening the kit for the first time, picking up a project already under way, or simply want to understand how the whole thing works.

2Finding your way

The documentation is organised into themed sections, each with its own colour. It is a simple visual cue — no need to memorise numbers, the colour alone is enough to find a section at a glance. In the binder these are the physical dividers; on the website, the coloured blocks of the home page. The same logic in both forms.

The reading order was set by the author, and it is not arbitrary. Start with the first section and work through in order. Each step gives you what you need for the next.

3How the content is laid out

The binder's cover sheet and the website's home page show the same sections with their colours, and the same documents. That is where you start when looking for a particular document. The stylesheets and the working files appear in neither: they are in the downloadable archive.

Their granularity differs slightly, and that is deliberate: the binder lists everything you are holding, the website aggregates what is published online. It is not an inconsistency.

4The documents, section by section

Here is what you will find in each section of this binder, and why each document is worth having. The sections appear in the order they sit behind the coloured dividers.

4.1Before you begin

The entry documents. How to document your projects covers the decisions that come before the first line is written: what you want to obtain, for whom, and the organisational choices that determine the rest. The reading guide, the one in your hands, explains how to use the binder and in what order to approach the sections.

4.2Working with Claude AI

Every document in this binder was produced with the help of an artificial intelligence. The Kit depends on no particular supplier: it sets formatting rules and a production chain, and each engine applies them in its own environment. One section per documented engine follows: Claude AI, Grok AI, ChatGPT AI.

Each section gathers what belongs to its engine. The manual introduces it and details its particularities; the practical guide gives the session reflexes; the environment report says what its chain offers and what it lacks; the dialogue commands, where the engine supplies them, add what is its own.

Read the section of the engine you use. The environment contract itself names no engine: it lives with the files and the structure, §4.7.

Claude AI: manual, practical guide and environment report.

4.3Working with Grok AI

Grok AI: manual, practical guide, environment report and engine-specific dialogue commands.

4.4Working with ChatGPT AI

ChatGPT AI: practical guide and environment report.

4.5Starting and maintaining a project

This section holds the kit's operational guides. The initialisation guide describes the steps to start a new project in a few minutes. The update guide explains how to inject an evolved version of the kit into an existing project without affecting work in progress. The naming convention sets the naming rules for every file. To consult at launch or at any evolution of the system.

4.6Steering the AI and adapting the Kit to your needs

Two ways of taking the lead. The dialogue commands are pasted into the chat to frame a session or bring it back when it drifts; they act on the assistant, mid-work.

Extending the Kit acts on the kit itself: how to add your own layouts without modifying the kit's, where your files belong, and what breaks when the kit evolves. To read when the kit does not cover a need.

4.7Files and structure

The project prompt opens this section. A prompt, here, is not a question asked in the chat: it is a document of permanent rules, placed once in the workspace and reread by the assistant at the start of each session. It carries what must never be repeated — the stylesheet to use, the naming convention, the language, the author, the checking chain mandatory before any delivery. It is the piece that makes the result reproducible from one session to the next.

The execution environment contract joins this section. It states what the chain requires, what falls away when a capability is missing, and the check to replay at the start of every session. It names no engine: each engine's report lives in its own section.

The rest of the section gathers the formal description of the kit — its files, their roles and their interdependencies. You will find the common structure document listing every file of a project with its contract, the documentation of the web publishing pipeline, and that of quality control. To consult if you want to understand how the kit is built.

The glossary closes the section: the kit's technical terms, defined in plain language, with an example where useful. The terms appear in coloured italics in the body of the other documents, signalling that a definition exists here.

4.8Publishing and sharing a project

The last divider covers what follows the documentation: presenting it online and making it possible to take over. Publishing and reuse describes what a sub-site shows its readers, what it keeps outside that presentation, and on what condition that second part becomes public.

5Going further

This binder is the printed form of a digital documentation system. The documents it holds were produced from the files of a dedicated workspace, with the help of artificial intelligence.

If you want to take this system in hand yourself — to produce new documents, update existing content or develop the project further — the sections after the reading guide describe how to proceed.

If you have no need to go further, this paper binder reads without any access to the computer files.

The complete kit downloads from the site as a single archive: the documents in every language, the stylesheets, the generators and the checking tools. Enough to take the whole thing onto your own machine. The stylesheets come with their reference documents — General, Glossary, YAML and HTML — which illustrate each formatting function with its visual result.

💡The project website comes into its own during a working session: the steering commands can be copied to the clipboard there in one click, ready to paste into the chat — without opening the paper binder.