diff --git a/README.md b/README.md index f18fe5e..9c58978 100644 --- a/README.md +++ b/README.md @@ -37,7 +37,7 @@

- A CodeCraft session in the Gruvbox dark theme: a diff of the fix, the task list, and a permission card asking before the test suite runs; the sidebar shows pinned chats, a folder and the archive + A CodeCraft session in the Gruvbox dark theme: the agent's task list and a permission card with the diff of a one-line fix; the sidebar shows a pinned chat, a folder and today's chats, and the chip in the top bar shows an active skill
A session: the agent works through its task list, shows diffs, and asks before anything outside the rules.

@@ -130,7 +130,7 @@ opens the command palette, and prompt templates with placeholders save typing.
- CodeCraft on a phone in a light theme: the agent asks where coupon codes should be stored and offers three options plus free text
+ CodeCraft on a phone in a dark theme: the task list and a permission card with the diff, with Allow once, Always allow and Reject buttons
Mobile: answer questions and approve changes from your phone. Share links and text from other apps into a chat.
@@ -154,6 +154,19 @@ slash commands in `.claude/commands` and skills in `.claude/skills` are picked u The agent keeps notes about a project in `.codecraft/memory.md`; your personal memory applies to every project. +

+ Settings, Skills tab: the user's own skills with description and file count, buttons for a new skill and the import from GitHub +

+ +**Skills** are packaged instructions for a kind of task: a folder with a `SKILL.md` (name, description, +instructions) and further files. Create them in *Settings → Skills* with a small editor, or import them +from a GitHub repository or folder (every folder with a `SKILL.md` is offered; filter and select several). +They are stored per user and work next to the skills of your projects and the built-in ones. To keep the +context small, you switch skills on **per chat** (menu ⋯ → *Skills for this chat*): only those are part of +every turn. All others cost nothing – up to 12 are listed by name, a larger library is not listed at all and +the agent finds a skill by keyword and loads it, with its further files, when it needs it. In the +[code factory](#code-factory) each phase can have its own skills. + ## Models Every provider is an endpoint with a list of models. Each model can have a context size, @@ -204,7 +217,7 @@ platforms: `cargo install --locked --git https://git.familie-zink.org/zink/codec ## Automations

- Creating an automation from a template: schedule chips, cron expression, mode, permission mode, model and the task for the agent + The automation editor: schedule chips with the next runs, mode, approval mode, model, time limit and the instructions file next to an assistant chat

An automation is an agent that starts on a schedule. Its instructions are a Markdown file @@ -226,6 +239,12 @@ The factory turns issues on your Git forge (Gitea, GitHub or GitLab) into review merged changes – with agents doing the work and you deciding at the points that matter. It is the **Factory** page in the sidebar; all chats it creates live in the sidebar folder *Factory*. +

+ The factory board: columns for review, questions, approved, build, acceptance, failed and done with issue cards, the repository tile with its version, and buttons to plan a feature, cut a milestone and start a release +
+ The factory page: every issue sits in the column of its phase; the repository shows its current version. +

+ ``` issue + label "factory" │ @@ -291,8 +310,8 @@ the files attached (Gitea and GitHub). **Settings per repository** (*Factory → Repositories*, *New repository*): forge connection and token, label (default `factory`), parallel runs, allowed issue authors (default: the token's owner), and per -phase the model, agent (CodeCraft or Claude Code), permission mode, timeout and tries on -technical failures, plus the number of rework rounds (default 2). Failed or rejected issues +phase the model, agent (CodeCraft or Claude Code), permission mode, timeout, tries on +technical failures, the skills that are switched on for it, plus the number of rework rounds (default 2). Failed or rejected issues can be restarted from the board, finished ones are closed with a comment. **Files in the repository** (all optional, kept in `.factory/`): diff --git a/docs/images/automations.png b/docs/images/automations.png index dccf694..2e38a6e 100644 Binary files a/docs/images/automations.png and b/docs/images/automations.png differ diff --git a/docs/images/chat.png b/docs/images/chat.png index f922105..6683b70 100644 Binary files a/docs/images/chat.png and b/docs/images/chat.png differ diff --git a/docs/images/factory.png b/docs/images/factory.png new file mode 100644 index 0000000..25fda4c Binary files /dev/null and b/docs/images/factory.png differ diff --git a/docs/images/mobile.png b/docs/images/mobile.png index 3a32bd3..d4f6b07 100644 Binary files a/docs/images/mobile.png and b/docs/images/mobile.png differ diff --git a/docs/images/settings.png b/docs/images/settings.png index 29bcaa6..69017da 100644 Binary files a/docs/images/settings.png and b/docs/images/settings.png differ diff --git a/docs/images/skills.png b/docs/images/skills.png new file mode 100644 index 0000000..566a728 Binary files /dev/null and b/docs/images/skills.png differ diff --git a/docs/images/stats.png b/docs/images/stats.png index ffeada9..e4537d2 100644 Binary files a/docs/images/stats.png and b/docs/images/stats.png differ