Getting Started
Installation - Storyline Docs
Install Storyline in under 2 minutes. One-line installer for Linux, macOS, and WSL.
Getting started with Storyline takes just a couple of minutes. This guide covers installation, verification, and troubleshooting.
Requirements
Linux, macOS, or WSL (Windows Subsystem for Linux) is required.
- Windows users: Please use WSL (Windows Subsystem for Linux). It’s easy to set up and provides a seamless Linux environment.
- Native Windows PowerShell is not currently supported due to line ending compatibility issues.
Before you begin, make sure you have:
- Git installed and configured
- Claude Code installed (claude.com/claude-code)
One-Line Install (Recommended)
Run this command in your terminal:
curl -fsSL https://raw.githubusercontent.com/prillcode/storyline/main/remote-install.sh | bash
This will:
- Clone Storyline with all dependencies (using git submodules)
- Install everything to
~/.local/share/storyline - Copy skills and commands to
~/.claude/
The installer completes in seconds and requires no additional configuration.
Manual Installation
If you prefer to clone and install manually:
git clone --recurse-submodules https://github.com/prillcode/storyline.git
cd storyline
chmod +x install.sh
./install.sh
The --recurse-submodules flag automatically includes the cc-resources dependency. If you forget the flag, the installer will offer to initialize submodules for you.
Advanced: Windows Native (Manual File Copy)
While WSL is strongly recommended, advanced users can manually install on native Windows by copying files:
Step 1: Clone the repository with submodules
git clone --recurse-submodules https://github.com/prillcode/storyline.git
cd storyline
Step 2: Create Claude directories (if they don’t exist)
New-Item -ItemType Directory -Force -Path "$HOME\.claude\skills"
New-Item -ItemType Directory -Force -Path "$HOME\.claude\commands"
New-Item -ItemType Directory -Force -Path "$HOME\.claude\agents"
Step 3: Copy dependency files
Copy-Item -Path ".\dependencies\cc-resources\skills\*" -Destination "$HOME\.claude\skills\" -Recurse -Force
Copy-Item -Path ".\dependencies\cc-resources\commands\*" -Destination "$HOME\.claude\commands\" -Recurse -Force
Copy-Item -Path ".\dependencies\cc-resources\agents\*" -Destination "$HOME\.claude\agents\" -Recurse -Force
Step 4: Copy Storyline files
Copy-Item -Path ".\skills\*" -Destination "$HOME\.claude\skills\" -Recurse -Force
Copy-Item -Path ".\commands\*" -Destination "$HOME\.claude\commands\" -Recurse -Force
Note: This approach bypasses installation scripts and directly copies skill/command files. No compilation or line-ending issues involved - just file copying.
Verify Installation
Start a new Claude Code session and run:
/sl-setup check
This verifies all Storyline components are installed correctly. You should see:
✅ All Storyline skills installed
✅ All Storyline commands installed
✅ All dependencies installed
Updating Storyline
To update to the latest version, re-run the one-line installer:
curl -fsSL https://raw.githubusercontent.com/prillcode/storyline/main/remote-install.sh | bash
Or if you cloned manually:
cd storyline
git pull origin main
git submodule update --init --recursive
./install.sh
Next Steps
Now that Storyline is installed:
- Initialize your first project: Quick Start guide
- Learn the workflow: Workflow documentation
- Explore available commands: Run
/sl-setupin Claude Code
Troubleshooting
”Command not found: /sl-setup”
Make sure you started a new Claude Code session after installation. Skills and commands are loaded when Claude Code starts.
Skills not found
Check that files were copied correctly:
ls ~/.claude/skills/storyline*
ls ~/.claude/commands/sl-*
You should see multiple Storyline-related files in each directory.
Permission issues
If you get permission errors during installation:
chmod +x install.sh
./install.sh
WSL Installation Issues
If you’re on Windows and having trouble with WSL:
- Ensure WSL 2 is installed:
wsl --version - Install a Linux distro:
wsl --install -d Ubuntu - Update WSL:
wsl --update
Still stuck? Open an issue on GitHub or ask in Discussions.
Next: Quick Start →