ClaudeKit usage guide - just type naturally
Think harder. All-in-one ClaudeKit guide. Run the script and present output based on type markers.
IMPORTANT: Always translate $ARGUMENTS to English before passing to script.
The Python script only understands English keywords. If $ARGUMENTS is in another language:
$ARGUMENTS to Englishpython .claude/scripts/ck-help.py "$ARGUMENTS"
The script outputs a type marker on the first line: @CK_OUTPUT_TYPE:<type>
Read this marker and adjust your presentation accordingly:
@CK_OUTPUT_TYPE:comprehensive-docsFull documentation (config, schema, setup guides).
Presentation:
Example enhancement after showing full output:
## Additional Tips
**When to use global vs local config:**
- Use global (~/.claude/.ck.json) for personal preferences like language, issue prefix style
- Use local (./.claude/.ck.json) for project-specific paths, naming conventions
**Common setup for teams:**
Each team member sets their locale globally, but projects share local config via git.
Need help setting up a specific configuration?
@CK_OUTPUT_TYPE:category-guideWorkflow guides for command categories (fix, plan, cook, etc.).
Presentation:
@CK_OUTPUT_TYPE:command-detailsSingle command documentation.
Presentation:
@CK_OUTPUT_TYPE:search-resultsSearch matches for a keyword.
Presentation:
@CK_OUTPUT_TYPE:task-recommendationsTask-based command suggestions.
Presentation:
Script output = foundation. Your additions = value-add.
Never replace or summarize the script output. Always show it fully, then enhance with your knowledge and context.
/plan → /code: Plan first, then execute the plan/cook: Standalone - plans internally, no separate /plan needed/plan → /cook (cook has its own planning)