VividKit Crystal clear AI coding
VI
Choose Your Setup Get Started with AgentKit Continue with ClaudeKit Migrate from ClaudeKit to AgentKit Clean cutover from ClaudeKit What Is AgentKit? How AgentKit Works AgentKit Kits, Skills, Agents & Hooks AgentKit Runtime Support AgentKit Desktop App AgentKit Configuration AgentKit CLI Quick Reference AgentKit Skills Cheatsheet AgentKit Workflows AgentKit Statusline Update AgentKit CLI & Kits AgentKit Helper Clean reinstall of AgentKit AgentKit Troubleshooting What is ClaudeKit? ClaudeKit CLI Guide Command Finder Commands Cheat Sheet Workflow Recipes CLI Quick Reference Claude Mechanics Permission Modes ClaudeKit Hooks Coexistence ClaudeKit x Codex CK → Other coding tools How ClaudeKit Works Inside ClaudeKit Finding Your Unknowns Session Recovery Fix from Logs UI/UX Guide Accounts Switcher IDE Config Remote Control Codex App System Diagramming UI Review Gate Promotions Support VividKit

Quick Ref / Command

Engineer Kit

/ak:journal

Technical Session Journal

Persist chronological technical journals under plans/journals using the first-class CLI, preserving work history without replacing current docs, ADRs, or product decision sources.

01

Gather events

02

Draft concise entry

03

Persist with CLI

04

Validate when needed

Rule 01

Prefer concrete errors, paths, outcomes, and decisions over vague retrospectives.

Rule 02

Persist through ak journal create; do not leave the journal only in chat.

Rule 03

Automatic journal steps are controlled by explicit flags and config precedence.

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Gather events Collect root cause, key changes, impacts, decisions, next steps, concrete errors, paths, and outcomes from the session.
  2. 2 Draft concise entry Write a short title and markdown body with concrete evidence instead of vague summaries.
02

Work

Agent / skill execution

  1. 3 Persist with CLI Use ak journal create with title, summary, and stdin so no interactive editor is required.
  2. 4 Validate when needed Run ak journal validate <slug-or-filename-stem> for entries that need checking.
03

Verify

Gate, review, validation

  1. 5 Skip AgentWiki publish Report “AgentWiki publish skipped” because publishing from this skill is deferred and the local file remains source of truth.
  2. 6 Browse history Use ak journal list, ak journal show <slug>, or the Journals page to inspect existing entries.
04

Close

Report, handoff, artifact

  1. 7 Respect auto policy When run automatically after other workflows, honor --skip-journal, journal.auto config, and precedence: flag > project config > user config > default true.
  2. 8 Publish socially only when configured For social posts, resolve config, draft per-channel bodies, dry-run post-social first, then publish only after inspecting dry-run output.

Syntax, arguments, subcommands

How to invoke the skill: syntax, positional arguments, shared options, then each subcommand with its own syntax and outcome.

Syntax

/ak:journal [topic or reflection]

Arguments

[topic or reflection] Required

Journal topic

Natural-language session topic, reflection, or record request. Include concrete errors, paths, outcomes, decisions, and remaining work; the Skill has no published mode flag.

/ak:journal "Record today's session-cache repair: duplicate invalidation root cause, rejected timer workaround, affected API behavior, regression evidence, and follow-up monitoring."

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Session reflection Recommended 
/ak:journal after fixing the OAuth callback race condition
Use when:
You want a concise chronological work record after implementation or debugging.
Expected:
Gathers root cause, key changes, impacts, decisions, and next steps; drafts a concrete markdown entry; persists it with ak journal create under plans/journals; reports AgentWiki publish skipped.
Failure archaeology 
/ak:journal why the deployment rollback was necessary
Use when:
The entry should emphasize honest root cause, impact, and lessons from a failure.
Expected:
May invoke the journal-writer subagent when emotional honesty is the point, then still writes the journal through ak journal create and keeps it as local work history rather than a decision authority.
Backdated project entry 
/ak:journal record yesterday's API migration notes dated 2026-08-29 for project vividkit-web
Use when:
You need the journal file tied to a specific date or AgentKit project registry name.
Expected:
Uses the optional ak journal create --date and --project inputs while preserving the same gather, draft, validate-when-needed, and AgentWiki-skipped workflow.
Configured social post 
/ak:journal turn today's release journal into configured social posts with image ./release-card.png
Use when:
You have journal social channels configured and want per-channel copy after the local journal exists.
Expected:
Creates the journal first, resolves .agentkit journal/config settings and writing style, drafts per-channel bodies, runs post-social with --dry-run --json for inspection, then publishes only after the dry-run output is accepted.

Handled Scope

  • Session reflection
  • Chronological work records
  • Journal CLI persistence
  • Auto-journal preferences
  • Social-publishing dry runs

Artifacts Produced

Journal result

Pattern

Created file path, one-line summary, validation status when run, AgentWiki publish skipped.

The journal preserves work history; it should not be cited as the durable product spec.

Next