kimal3 0.2.10 → 0.3.1

package/skill/en/commands/k3context.md

@@ -0,0 +1,92 @@
+---
+description: Answer the open questions about your company in conversation
+---
+
+<!-- kimal3:erzeugt — this file is maintained by `kimal3 skill install` and
+     overwritten on every update. Your own changes will be lost; if you want
+     to keep them, copy the file under a different name. -->
+# Filling in the company context
+
+## 1. Read the rules first
+
+Read **`~/.claude/skills/kimal3/SKILL.md`**, “Keeping the company context up to date” and
+“Filling in the company context — the steps”. This file deliberately does not repeat the rules —
+otherwise there would be two truths that drift apart.
+
+## 2. See what is open
+
+```
+kimal3 context questions
+```
+
+It only reads and needs neither network nor sign-in. **Nothing open?** Say so in one sentence and
+stop.
+
+🔴 **The line `AI Workplace: …` is the most important one in the whole output — the paths below it
+are relative to that folder, not to your working directory.** The normal case is that the two
+differ: `workplace new` explicitly advises changing into the **workbench** and starting Claude
+there; the files are then one level up. **Prefix every path with the named AI Workplace folder
+before you write.**
+⚠️ Whoever skips this creates a **new** file in the wrong place. `kimal3 context upload` goes on
+reading the real files and uploads empty answers — both sides report success, and the work is
+gone all the same.
+
+**No AI Workplace found?** The message means “I found none from here upwards” — **not** “there is
+none”. Ask first: *Do you already have an AI Workplace folder?* (In a German company it is called `KI-Arbeitsplatz`.) Yes → change into it
+and try again. No → `kimal3 workplace new`. ⚠️ Guess wrong here and you create a second, empty
+workplace.
+
+## 3. Ask the questions — one at a time
+
+🔴 **One question, wait for the answer, then the next.** No questionnaire in one go.
+🔑 These are questions about a person's company — whoever gets them all at once answers none of
+them well. That is exactly why this is a conversation and not a form.
+
+Write the answer into the file that `kimal3 context questions` named, under its `## ` heading. The
+`>` hint lines are ours: **leave them in place, write below them.**
+**What the answer looks like** (never break a line in the middle of a sentence, no bold) is in
+`SKILL.md`, step 3 of “Filling in the company context — the steps” — stick to it, otherwise it is hard to read in the app.
+
+🔴 **Never make anything up**, and do not suggest anything that looks like an answer either. If the
+person doesn't know something, **the question stays open** and is back the next time.
+
+⚠️ **Stopping halfway is not a special case:** the answers given so far are already in the files;
+at the next `/k3context` simply fewer questions are open. **Do not keep track of an interim state** —
+the files *are* the state.
+
+## 4. Upload — show first, then ask
+
+Show the person **what goes to the company**, and wait for their explicit yes. Only then:
+
+```
+kimal3 context upload
+```
+
+🔑 The five files belong to the **company** — every colleague sees them at their next
+`kimal3 context download`.
+⚠️ `kimal3 context upload --overwrite` **only when explicitly asked**: it throws away whatever
+someone else has changed at the company in the meantime.
+
+## 5. When it doesn't work
+
+🔴 **With `context upload` the number `1` on its own says NOTHING AT ALL — read the message.** It is
+the shared exit for at least six different situations, and they call for opposite things:
+
+| What the message says | What it means |
+|---|---|
+| “Only the company admin can edit the company context.” | A second attempt changes nothing about the role. Name the admin — if `kimal3 context download` ran before, their name is in its output. |
+| “There's no AI Workplace here” | Do **not** guess `workplace new`! See section 2 — the folder usually exists, the person is just standing somewhere else. |
+| “The context was changed in the meantime …” | The way out is in the same message: `--overwrite`. Only suggest it if the person really wants to throw away the other change — it is a colleague's work. |
+| several companies / ambiguous | The way out is `--company "…"`. **You do not choose** — show the person the list. |
+| a file can't be read or no longer has any questions | Rename the file (for example `company-old.md`), then `kimal3 context download` fetches the company's version fresh. Otherwise `download` does **not** touch a file that was edited. |
+| **“You don't belong to a company.”** | 🔴 **Do NOT send them to an admin — there isn't one.** This hits the fresh Pro buyer of all people: they get their workplace with every question open, dutifully answer them, and here there is no one the answers could be sent to. Tell them that their answers **are in their files and stay there**, and that they can be uploaded as soon as there is a company. Nothing is lost. |
+| **“The company has saved your changes — only the local tracking file …”** | 🔴 **This is a SUCCESS.** Everything has arrived at the company; only one file on disk couldn't be written. Say exactly that — **never** “that didn't work”. (from 0.2.8: exit code 0) |
+
+⚠️ **Why this is spelled out here at such length:** up to 0.2.7 the last row was the most costly
+case. Whoever read the `1` as “not an admin” told a person who had just answered every question
+and uploaded them successfully to go to their admin. *A success, read out as a refusal.* From
+0.2.8 the exit code itself (`0` instead of `1`) separates this case from a real refusal — with an
+older CLI the old reading still applies, which is why the message remains the more reliable route.
+
+**Exit code `4`**: signed in, but no Pro access — show the message, do **not** repeat the
+command. Interpret everything else according to `SKILL.md`, section “Exit codes”.

package/skill/en/commands/k3course.md

@@ -0,0 +1,54 @@
+---
+description: Back into the Mini course — pick up where you left off
+---
+
+<!-- kimal3:erzeugt — this file is maintained by `kimal3 skill install` and
+     overwritten on every update. Your own changes will be lost; if you want
+     to keep them, copy the file under a different name. -->
+# Course
+
+> Back into the Mini course: “Where was I again?” — picks up where you left off.
+> (Most of the time you won't need this: your coach takes you through the course on its own
+> when you run `/k3start`. This is the deliberate way back in if you got sidetracked along the way.)
+
+Carry out the steps in order. Stay in the coaching tone: English, friendly, one step at a
+time, the why before the how, no prior knowledge assumed.
+
+## 1. Look up the course
+- **Is there a `course-parts.md` (or `kurs-beats.md`) next to you? If not, stop here.** Then this person does not have the
+  Mini course — tell them kindly in one sentence that this command belongs to the course and
+  isn't needed here, and ask, with a suggestion, what they would like to work on instead.
+  **Do not start retelling the course from memory**, and do not look for the file
+  anywhere else. *Since 0.2.5 the command comes with every kimal3, but the course does not.*
+- If it is there: read `course-parts.md` (or `kurs-beats.md`) — it holds the 3 parts of the course the person
+  comes from. That is your knowledge of it; the file is generated automatically, never change it by hand.
+- If only `kurs-beats.md` is there (a German course folder): carry on in English with the content of that file — the course text in the browser is in English for this person, and a “Beat” there is a “Part” here.
+
+## 2. See how far you have got
+- Read `NEXT-STEPS.md` (if it exists) — it holds the course status, for example “Part 2 in progress”.
+- **The status file is called `NEXT-STEPS.md` — or `WEITER-HIER.md` if the folder was created in German.** If one exists, use it. If both exist, ask which one applies and write to neither until you have the answer. If one has to be created: inside `workbench-…` it is `NEXT-STEPS.md`, inside `werkbank-…` it is `WEITER-HIER.md`, anywhere else `NEXT-STEPS.md`.
+- If the file doesn't exist yet, this is the first session: Part 1 is then done (the person
+  has just started you, after all), and it carries on at **Part 2**. **Create it straight away** —
+  see `START-HERE.md` (or `START-HIER.md`).
+
+## 3. Say where you stand in one sentence
+- Say in **one** sentence where you are in the course — no lecture, no repeat of the whole course.
+
+## 4. Carry on — until Part 2 is done
+- Lead on **one** step at a time: show, let them do it, make sure they understand. Never the
+  whole list at once. Update `NEXT-STEPS.md` (or `WEITER-HIER.md`) as soon as a part is finished.
+- **Part 1** (app, account, plan, Start-Workspace, **Git**) happens in the browser, **before** you
+  exist — you can't lead it. It is done as soon as you are running.
+
+## 5. After Part 2: build the move & hand over
+- The end of Part 2 is the **move**: suggest a folder name + location for the first real
+  project (for example `Documents\Claude-Projects\my-first-project` — the real folder is called `Documents` in the file system, even if Explorer shows it under a translated name; have them open the folder once in Explorer before closing Claude), create the folder
+  and put a short **`NEXT-STEPS.md`** there (if there is already a `WEITER-HIER.md`, use that) as a handover note — what has been done
+  and what comes next (pick a small real task, `git init` + first
+  commit, rhythm: think it through → build → check → save, a visible result; tick off the steps
+  in the course in the browser as you go). Then ask them to close Claude completely and reopen it in the
+  new folder (`/k3start`).
+- **You don't lead Part 3 from here.** In the new folder you are simply their coach —
+  the note tells you where you stand. The celebrating happens in the browser.
+- If they are already that far (or even finished), say so briefly and kindly — and ask, with a
+  suggestion, what they would like to work on here instead. No more course talk.

package/skill/en/commands/k3list.md

@@ -0,0 +1,26 @@
+---
+description: Show the projects you have added
+---
+
+<!-- kimal3:erzeugt — this file is maintained by `kimal3 skill install` and
+     overwritten on every update. Your own changes will be lost; if you want
+     to keep them, copy the file under a different name. -->
+# Showing projects
+
+```
+kimal3 project list
+```
+
+Give the list back in a **readable** form, not as raw output: title, the date it went live,
+and the numbers attached to it. Name what is missing as missing — don't make anything up.
+
+Three states occur, and they mean different things: **live since …** is running today,
+**planned for …** is still in the future, **not live yet** has no date at all. Don't lump them
+together — “planned” says nothing about today.
+
+If the list is empty, that is not an error: then there is nothing in the success profile yet, and
+the next step is `/k3project <what you built>`.
+
+If fetching it doesn't work, interpret the exit code according to
+**`~/.claude/skills/kimal3/SKILL.md`, section “Exit codes”** — above all: on `4`, do **not** retry
+and do **not** suggest `login`.

package/skill/en/commands/k3project.md

@@ -0,0 +1,50 @@
+---
+description: Add a finished project to the success profile
+argument-hint: <what you built>
+---
+
+<!-- kimal3:erzeugt — this file is maintained by `kimal3 skill install` and
+     overwritten on every update. Your own changes will be lost; if you want
+     to keep them, copy the file under a different name. -->
+# Adding a project
+
+## 1. Read the rules first
+
+Read **`~/.claude/skills/kimal3/SKILL.md`** — above all “Look first, then write”,
+“Adding a project” and “Never make up numbers”. This file deliberately does not repeat the rules.
+
+## 2. Check whether it is already there
+
+```
+kimal3 project list
+```
+
+If the project is already there: do **not** add it again. Tell the person it is already in, and
+ask whether they want to change it.
+
+## 3. Add it
+
+The project in question:
+
+$ARGUMENTS
+
+⚠️ **If it literally says the placeholder** (`<what you built>`), someone copied the line in the
+Pro area and sent it unchanged. Then **nothing** has been given: ask which project it is, instead
+of taking the placeholder as the title.
+
+Build `kimal3 project new --title "…" [--company "Name" | --no-company]` from it with the matching
+options (`kimal3 project new --help` lists them all, for example `--hours …` and `--result …`).
+Anyone who belongs to exactly one company doesn't need `--company` — the project goes to that company.
+With two companies the refusal lists both as ready-made commands.
+
+🔴 **Never estimate time saved, revenue or net result.** These numbers then appear **publicly** on a
+page with the person's name. If a number was not given: **ask for it** or leave the field out. A
+plausible number is worse than none here.
+
+Show the person **before** running it what you are going to add, and let them confirm — the
+result is public and can't be taken back with one keystroke.
+
+## 4. Afterwards
+
+If it didn't work, explain the exit code as `SKILL.md` describes it. If it worked, briefly show
+what the profile now says.

package/skill/en/commands/k3start.md

@@ -0,0 +1,47 @@
+---
+description: Start a session — where you stand and what comes next
+---
+
+<!-- kimal3:erzeugt — this file is maintained by `kimal3 skill install` and
+     overwritten on every update. Your own changes will be lost; if you want
+     to keep them, copy the file under a different name. -->
+# Start
+
+> Your way into a session: arrive, see where you stand, find the next step —
+> so you never sit staring at a blank page wondering “now what?”.
+> (The counterpart to `/k3wrapup`, which you use to finish cleanly at the end.)
+
+Carry out the steps in order. Stay in the coaching tone: English, friendly, one step at a
+time, the why before the how, no prior knowledge assumed. If a step isn't relevant here,
+say so briefly and skip it — no filler.
+
+## 1. Arrive
+- Greet briefly and warmly. No long introduction — just be there like a patient colleague.
+
+## 2. See where you stand
+- **Is there a `START-HERE.md` (or `START-HIER.md`) next to it? Then read it and follow it.** It is the instruction to
+  you for exactly this project and **takes priority** over everything below.
+- Is there a status file (`NEXT-STEPS.md` or `ROADMAP.md`) — a small file in which the
+  latest status and the next step are written down? Then read it.
+- **The status file is called `NEXT-STEPS.md` — or `WEITER-HIER.md` if the folder was created in German.** If one exists, use it. If both exist, ask which one applies and write to neither until you have the answer. If one has to be created: inside `workbench-…` it is `NEXT-STEPS.md`, inside `werkbank-…` it is `WEITER-HIER.md`, anywhere else `NEXT-STEPS.md`.
+- No status file? **First check whether there is a `.git` folder next to it.** If there is, this
+  project keeps a version history, and `git log --oneline -10` plus `git status` show you the
+  latest state.
+  ⚠️ **If there is no `.git` next to it, leave both commands out.** They then answer with
+  `fatal: not a git repository` — and an error message as a greeting looks as if the
+  person did something wrong. In a freshly started project where nothing has been saved
+  yet, `git log` fails on its own; `git status` runs there and reports “nothing to commit”.
+- None of these (for example in the very first session)? Completely normal — then there is no
+  “status” yet. Go straight to step 4 and help find a first real task.
+
+## 3. Summarise the status (if there is one)
+- Summarise in **2–3 lines without jargon** where you stand and what was done last.
+
+## 4. Find the next step
+- Are there open next steps? Name them and **recommend one** (the smallest sensible one).
+- Nothing open? Then ask: “Which real task in your working day annoys you, keeps coming back
+  or eats up your time?” — and carve out of it something you can get done *today*.
+
+## 5. One question with a suggestion
+- End with **one** question that carries your suggestion: “Where shall we start? I'd
+  suggest X — does that work, or would you rather do Y?” Never leave the person facing a blank page.

package/skill/en/commands/k3wrapup.md

@@ -0,0 +1,99 @@
+---
+description: End a session cleanly — save the status, tidy up, summarise
+---
+
+<!-- kimal3:erzeugt — this file is maintained by `kimal3 skill install` and
+     overwritten on every update. Your own changes will be lost; if you want
+     to keep them, copy the file under a different name. -->
+# Wrap-up
+
+> A clean end to the session: save the status, tidy up, summarise — so that the next
+> start (in this project or another one) carries on smoothly.
+
+Carry out the steps in order. Stay in the coaching tone: briefly explain what you are doing, and get
+my OK **before publishing (push)**. If a step isn't relevant here, say so briefly
+and skip it — no filler.
+
+## 1. Review the status
+- Is it a Git repo? Then `git status` + `git diff --stat`: what was changed in this
+  session? Summarise it in 1–2 sentences.
+- Not a Git repo? Say so briefly and offer to set one up (a safety net) — don't force anything.
+
+## 2. Update the status file — and tidy it up
+The status file (`NEXT-STEPS.md` or `ROADMAP.md`) is the note for the next start. It is only
+useful as long as it can be read in one go. **Every wrap-up adds something to it —
+so every wrap-up also has to clear something out**, otherwise it grows until nobody reads it any more.
+
+**The status file is called `NEXT-STEPS.md` — or `WEITER-HIER.md` if the folder was created in German.** If one exists, use it. If both exist, ask which one applies and write to neither until you have the answer. If one has to be created: inside `workbench-…` it is `NEXT-STEPS.md`, inside `werkbank-…` it is `WEITER-HIER.md`, anywhere else `NEXT-STEPS.md`.
+
+If there is no status file and the work is growing beyond one session: suggest one,
+then carry on with step 3.
+
+1. **Update:** set “Where we stand” and “next step” to what happened today.
+2. **Clear out what no longer applies.** Into the archive goes:
+   - what is **done** (finished tasks, ticked-off items),
+   - the stories of **earlier sessions** (“Before that …”, “Status as of …”) — “Where we stand” keeps
+     only today's status,
+   - whatever in the text has been **disproved or superseded**.
+   What stays: the current status, the next step, the open items, and for each idea for later
+   **at most two sentences** — anything longer gets its own file, which the status file links to.
+3. **Into the archive means: move, not delete.** If there is already an archive (usually named in the head of
+   the status file — the AI Workplace template uses `archive/next-steps-archive.md`), use it; otherwise create next to `NEXT-STEPS.md` a `NEXT-STEPS-archive.md`, next to `WEITER-HIER.md` a `WEITER-HIER-archiv.md`. Append at the bottom, with
+   today's date as the heading, **word for word** — the why behind earlier decisions should
+   stay findable.
+4. **Measure, don't estimate:** count the lines of the status file **before and after**. If its
+   head states a target length, that applies, otherwise **150 lines**. If it is still over that afterwards, clear out
+   more — or say out loud why the rest has to stay. Then check in the archive that what was
+   moved is really there (search for one line from it) before you report it as done.
+5. **Say out loud what you changed:** what is new in it, what went into the archive, lines before → after.
+
+## 3. Learned rules — does something need to be written down?
+**Only when there is a real reason**, not as a chore. A reason is: I corrected you today,
+explicitly asked for a way of working, or gave the same kind of answer to the same kind of question for the third time.
+No reason? Say so in half a sentence and move on.
+
+If there is one, **suggest the rule** — one sentence on what you will do differently from now on, plus the date and
+the reason in one sentence — and only add it to the file after my OK. Where it goes depends on what it is:
+
+| What is it? | Where it goes |
+|---|---|
+| **A working rule** — how you should work, ask, check, explain | `~/.claude/rules/kimal3-coach.md`, at the **bottom** of the section “Learned rules” (in a German coach it is called “Gelernte Regeln”) (newest at the bottom) |
+| **Something about me** — who I am, my roles, my tools | my `~/.claude/CLAUDE.md` |
+| **Something about this project** — structure, tools, pitfalls | the `CLAUDE.md` in the project folder |
+
+🔬 **Check first whether the rule already exists** — in the coach and in the CLAUDE.md files. If it
+is already there, do **not** add it twice: tell me where it is and that it was not
+followed today. A rule that is written down twice is not followed any better.
+⚠️ **If `~/.claude/rules/kimal3-coach.md` does not exist**, a working rule also goes into my
+`~/.claude/CLAUDE.md`. Do **not** create the coach file yourself — it belongs to kimal3.
+🔴 **In the coach you change ONLY the section “Learned rules” (in a German coach it is called “Gelernte Regeln”)** and only add at the bottom. Everything
+above it is the kimal3 template — you change nothing there.
+
+Afterwards say out loud **which sentence is in which file** (full path). The folder
+`~/.claude` is usually not a Git repo — the file is then not backed up by Git; say so too.
+
+## 4. Tidy up the project (lightweight)
+- Remove obvious rubbish (`.DS_Store`, `*.tmp`, `*.log`, `__pycache__`).
+- With anything unclear: do **not** delete — list it and ask me.
+
+## 5. Save (with my OK)
+- Stage the relevant changes **file by file** — **never** secrets or `.env*`, and no
+  `git add -A`, which sweeps in work from elsewhere.
+- Show me briefly what goes into the commit — **and what deliberately stays out**: files Git does not
+  know yet and that do not come from this session appear by name in the same list, with one sentence on what
+  they are. (They often come from another session and would otherwise go unnoticed.)
+  My OK to the commit covers the whole list; if I want one of them included after all, I'll say so.
+- Suggest a commit message.
+- After my OK: commit.
+- **Pushing, depending on the project:** check with `git remote` whether there is a destination at all.
+  - No destination: say so briefly — the commit is then the backup, done.
+  - A destination: **ask whether you should push** (the step “to the outside”). If the
+    project `CLAUDE.md` says a push triggers something (for example, redeploys the live site),
+    say so too. Only run `git push` after I confirm.
+
+## 6. Summary & goodbye
+- 2–3 sentences **without jargon**: what did we get done today, what did I learn — and in
+  one sentence, what was tidied up.
+- **One** concrete, small next step for next time (the cliffhanger — keep it small).
+- A short, friendly goodbye like a good colleague finishing for the day. Wait for my
+  reply before the session ends.

package/dist/zz-kaputt.js

@@ -1 +0,0 @@
-export const x = "das ist keine Zahl";