Skip to main content

​
Setup

Run the CLI tool in your project directory: 
npx rippletide-code
This walks you through authentication, rule selection, and hook installation. Once complete, every Claude Code session in this project will have access to your rules.

​
What happens during setup

​
1. Authentication

If you’re not logged in, the CLI prompts for your email and sends a one-time password (OTP). After verification, your credentials are stored locally at ~/.config/rippletide/config.json.

​
2. Repository scan

The CLI scans your project to detect:
  • Tech stacks — TypeScript, Python, Rust, Go, Java, Ruby, and more
  • Existing CLAUDE.md — if present, existing rules are parsed and checked for contradictions
  • Project structure — source file count, test file count, MCP tools in .mcp.json

​
3. Rule generation

Based on your existing Claude Code sessions and CLAUDE.md, Rippletide generates rule candidates. Rules come from three sources:
  • Inferred — extracted from your past Claude Code sessions via the Context Graph
  • Generic — best practices for your detected tech stack
  • Default — general coding conventions

​
4. Rule selection

An interactive multi-select prompt lets you pick which rules to adopt. You can also type custom rules when prompted: 
Type to add your rule (or press Enter to finish):
> All API endpoints must return structured error responses
Selected rules are saved to the Rippletide backend and locally to .rippletide/selected-rules.md.

​
5. Hook installation

The CLI installs Claude Code hooks into your project: 
your-project/
├── .claude/
│   ├── hooks/
│   │   ├── fetch-rules.sh      # Injects rules into every prompt
│   │   ├── check-code.sh       # Blocks code that violates rules
│   │   ├── manage-rule.sh      # Handles add/edit/delete operations
│   │   ├── invite-rules.sh     # Sends rule shares to teammates
│   │   └── receive-rules.sh    # Receives shared rules
│   ├── settings.json           # Hook configuration
│   ├── settings.local.json     # Command permissions
│   └── commands/
│       ├── plan.md             # /plan command definition
│       └── review-plan-command.sh
├── CLAUDE.md                   # Agent instructions (auto-generated)
└── .rippletide/
    └── selected-rules.md       # Your selected rules
After installation, Claude Code launches automatically with the hooks active.

​
Logout

To remove stored credentials: 
npx rippletide-code logout

​
Read-only mode

To connect without write access to the rule set (useful for team members who should follow but not modify conventions): 
npx rippletide-code --read-only
See Team Governance for details.

​
Data privacy

Rippletide only relies on the context available inside your local Claude Code workflow to identify reusable engineering rules:
  • the current Claude Code chat session for the active project
  • your CLAUDE.md
Your codebase is analyzed through your own local Claude Code environment, not centrally ingested. Rippletide only stores the extracted rules and conventions, not project content or unrelated session context.