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:problem-solving

Unstick hard problems

Break stuck problems open with targeted reframing techniques for complexity spirals, innovation blocks, recurring patterns, forced assumptions, and scale uncertainty.

01

Name stuckness

02

Dispatch technique

03

Load reference

04

Apply method

Rule 01

Match technique to symptom, not preference

Rule 02

A good reframing removes constraints or reveals a next action

Rule 03

Document what worked and what failed

Rule 04

Combine techniques only when the problem truly needs it

Execution Map

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

01

Start

Input, scope, route

  1. 1 Name stuckness Identify whether the symptom is complexity spiral, innovation block, repeated pattern, forced assumption, scale uncertainty, or general stuckness.
  2. 2 Dispatch technique Match the symptom to simplification cascades, collision-zone thinking, meta-pattern recognition, inversion exercise, scale game, or when-stuck guide.
02

Work

Agent / skill execution

  1. 3 Load reference Read the detailed guide for the chosen technique instead of applying a generic brainstorming pattern.
  2. 4 Apply method Run the technique systematically: eliminate special cases, collide metaphors, abstract patterns, invert rules, or test extremes.
03

Verify

Gate, review, validation

  1. 5 Extract insight Document what changed, which assumption broke, what generalized, or what became unnecessary.
  2. 6 Combine if needed Blend simplification with meta-pattern, collision with inversion, or scale with simplification when one method is not enough.
04

Close

Report, handoff, artifact

  1. 7 Produce unblock path Return a concrete next-action path, residual unknowns, and why the chosen reframing fits the symptom.
  2. 8 Ultra verifier When --ultra is present, assemble one evidence packet, run five independent candidates, and let one verifier select or reject.

Syntax, arguments, subcommands

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

Syntax

/ak:problem-solving [problem description]

Arguments

[problem description]

Problem description

Describes the stuck problem, visible symptom, forced assumption, repeated pattern, or scale uncertainty so the skill can choose the matching reframing technique.

/ak:problem-solving "We keep adding one more special case to checkout"

Output / publish flags

Only flags that change the artifact or publish it. Not the full option set.

--ultra

Ultra verifier

Run five independent reframing candidates and a verifier selection pass.

Example

/ak:problem-solving "We keep adding one more special case to checkout" --ultra

Modes / Routes

--ultra

Best-of-5 verifier pass over a fixed evidence packet; one winner is selected unchanged or all are rejected.

Research:
5 read-only candidates
Review:
strong verifier
Validate:
reject-all gate

Sample Prompt

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

Simplify cases Recommended 
/ak:problem-solving "The settings page has five implementations and every new option needs another branch"
Use when:
Use for complexity spirals and repeated special cases.
Expected:
The skill names a technique, then returns a simplification path that removes extra branches instead of adding more.
Question premise 
/ak:problem-solving "We think this must be solved with a database migration"
Use when:
Use when a solution feels forced by an unquestioned premise.
Expected:
Identifies conditional rules through inversion, then names safer options and the premise to revisit.
Production scale 
/ak:problem-solving "This queue design should scale but edge cases are unclear"
Use when:
Use when readiness changes across scale extremes.
Expected:
Maps scale extremes to failure signals, boundary tests, and concrete next actions.
Ultra pass 
/ak:problem-solving "We are stuck choosing a sync model" --ultra
Use when:
Use when a high-value stuck problem deserves independent candidates and verifier selection.
Expected:
Returns one winning reframing unchanged, or stops with reject-all reasons and no false consensus.

Handled Scope

  • Name stuckness
  • Dispatch technique
  • Load reference
  • Apply method
  • Extract insight
  • Combine if needed

Artifacts Produced

Reframing Output

Pattern

Symptom → technique → insight → unblock path

The answer should explain why the technique matched, what changed in the framing, and what concrete action to take next.

Next