littlepea-claudekit
v1.0.1
Published
CLI to scaffold littlepea configurations
Readme
littlepea-claudekit 🚀
A powerful CLI tool to scaffold your private Claude AI configurations securely across local projects or globally on your system.
It syncs private instruction folders (.claude, docs/, plans/) directly from a secured Git Repository, eliminating the manual task of copying and tweaking context for each AI project.
Installation
This utility allows executing on-the-fly with npx (No installation needed) by temporarily pulling the executable, but installing it globally is highly recommended for the fastest configuration synchronization across the entire PC.
# RECOMMENDED: Make it accessible anywhere as a native OS command
npm install -global littlepea-claudekitUsage
Once installed globally, you can execute the command littlepea-claudekit or its shorthand lpck anywhere.
Alternatively, use npx littlepea-claudekit if you haven't installed it.
1. 🏗️ Local Mode (Project Specific)
Syncs your secret template right into the current working directory of a specific project you are building.
# Navigate to your project
cd my-new-project
# Scaffold local configurations
lpck initThis mode copies [ .claude, docs, plans, CLAUDE.md ] relative to the current working directly to guide Claude AI only for this workspace.
2. 🌍 Global Mode (Recommended for Default Setup)
If you want standard AI commands universally available to all your projects without copy-pasting .claude everywhere, use the --global or -g flag.
lpck init -g- macOS/Linux: Installs seamlessly to
~/.claude/ - Windows: Installs dynamically to
%LOCALAPPDATA%\.claude\
AI Tools like standard Claude Code (claude) will recognize these global system rules.
3. 🧹 Maintenance & Cleanup
Behind the scenes, the CLI optimizes speed by locally fetching your repository exactly once globally at ~/.lpck-cache, then updating lightly via git pull.
Should you encounter cached conflicts, auth token updates, or need a hard reset:
lpck cache:cleanThis forcefully clears the hidden cache repository requiring the next init call to run a fresh Git Clone.
