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:sumup

Implementation Recap

Summarizes completed engineering work, evidence, failures, trade-offs, behavior, architecture, usage, and follow-ups without replaying the full session.

01

Gather evidence

02

Separate evidence states

03

Highlight relevant substance

04

Add a clarifying visual

Rule 01

Evidence first, narrative second

Rule 02

Verified is not the same as proposed

Rule 03

Use visuals only when they clarify

Rule 04

Keep unresolved work last and actionable

Execution Map

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

01

Start

Input, scope, route

  1. 1 Gather evidence Use the conversation, accepted decisions, current diff, tests, and relevant issue or plan state as the strongest available evidence.
  2. 2 Separate evidence states Separate implemented and verified work from proposed, inferred, untested, unshipped, or still-unresolved work.
02

Work

Agent / skill execution

  1. 3 Highlight relevant substance Summarize outcomes, high-value changes, failures and workarounds, decisions, how the result works, practical usage, follow-ups, and next steps.
  2. 4 Add a clarifying visual Use a compact table, chart, Mermaid diagram, or ASCII flow when it clarifies behavior, user flow, architecture, database, or UI/UX; otherwise briefly say why no visual helps.
03

Verify

Gate, review, validation

  1. 5 Keep unresolved work last Keep the recap concise, use the user's language, omit empty sections, and put unresolved items last.

Syntax, arguments, subcommands

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

Syntax

/ak:sumup [recap request]

Arguments

[recap request]

Recap focus

Natural-language implementation period, feature, or question to recap. Include the evidence boundary or emphasis you want; it does not trigger implementation, deployment, or a live status check.

/ak:sumup "Recap the implementation we just completed. Separate verified work from untested or unresolved work, explain the main flow, and keep next steps last."

Sample Prompt

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

Implementation recap Recommended 
/ak:sumup summarize the auth refactor and remaining blockers
Use when:
Use after implementation when a human needs the outcome without replaying the work session.
Expected:
Produces a concise recap with outcome, strongest evidence, key implemented changes, verification boundaries, unresolved blockers, and actionable next steps.
Failure and workaround recap 
/ak:sumup recap what failed during the queue worker implementation and what remains
Use when:
Use when failed attempts, workaround choices, or unresolved blockers need to be preserved clearly.
Expected:
Separates resolved recovery steps from unresolved failures, names the evidence for each result, and keeps remaining blockers last.
Behavior or architecture recap 
/ak:sumup explain how the new queue worker works and how to use it
Use when:
Use when changed behavior, user flow, architecture, database, or UI/UX benefits from a compact explanation.
Expected:
Explains only applicable operation details, includes a compact clarifying visual when useful, and adds minimal usage steps or commands.

Handled Scope

  • implementation recap
  • verification summary
  • failure recovery
  • architecture explanation
  • follow-up prioritization

Next