ltk
Your personal development toolkit for Claude Code - extensible, per-project, and smart.
┌─────────────────────────────────────────────────────────────────┐
│ ltk │
│ ─── │
│ 35 Skills · 16 Commands · 7 Agents · 4 Hooks · 3 MCP Servers │
└─────────────────────────────────────────────────────────────────┘
What is this?
A Claude Code plugin that gives you:
- Skills - Domain knowledge that loads automatically when relevant
- Commands - Actions you invoke with
/ltk:command-name
- Agents - Autonomous helpers that trigger after you write code
- Hooks - Automation that runs on events (session start, before/after edits)
Understanding the Components
┌─────────────────────────────────────────────────────────────────────────────┐
│ HOW COMPONENTS DIFFER │
├─────────────────────────────────────────────────────────────────────────────┤
│ │
│ SKILLS = Knowledge that loads automatically │
│ COMMANDS = Actions you trigger manually │
│ AGENTS = Autonomous helpers that run after you code │
│ HOOKS = Automation that runs on system events │
│ │
└─────────────────────────────────────────────────────────────────────────────┘
Skills - Passive Knowledge
What: Domain expertise that Claude learns from when relevant
When: Loads automatically based on what you're asking about
Trigger: Your questions/context match the skill description
You do: Nothing - just ask questions naturally
You: "How do I test my FastAPI endpoints?"
↓
Claude: [fastapi + pytest skills auto-load into my knowledge]
"Here's how to test FastAPI endpoints..."
Think of it as: A reference book that opens to the right page automatically
Commands - Manual Actions
What: Specific tasks you explicitly request
When: Only when you type the command
Trigger: You type /ltk:command-name
You do: Invoke it manually when you want that action
You: /ltk:scan-security
↓
Claude: [Runs security scan on codebase]
"Found 2 vulnerabilities..."
Think of it as: Buttons you press to do specific things
Agents - Proactive Helpers
What: Specialized assistants that watch what you're doing
When: After you write or edit code (automatically)
Trigger: Tool events (Write, Edit) + matching context
You do: Nothing - they activate on their own
You: *writes Python code with SQL query*
↓
Claude: [security-analyzer agent activates]
"Note: This SQL query might be vulnerable to injection.
Consider using parameterized queries."
Think of it as: A team of experts looking over your shoulder
Hooks - System Automation
What: Scripts/prompts that run on specific system events
When: Triggered by system events (session start, before/after edits)
Trigger: Events like SessionStart, PreToolUse, PostToolUse
You do: Nothing - happens automatically in the background
[Session starts]
↓
Hook: [Loads git status, project structure, TODOs]
↓
Claude: [Has project context ready]
Think of it as: Automatic setup and cleanup routines
Side-by-Side Comparison
| Aspect | Skills | Commands | Agents | Hooks |
|---|
| Activation | Automatic (context) | Manual (/ltk:...) | Automatic (after code) | Automatic (events) |
| Purpose | Provide knowledge | Execute actions | Analyze & advise | Automate workflows |
| User action | Just ask questions | Type command | Write code | Nothing |
| Output | Better answers | Task results | Suggestions/warnings | Background setup |
Visual Flow