Hindsight Cloud

1---
2name: hindsight-cloud
3description: Store team knowledge, project conventions, and learnings from tasks. Use to remember what works and recall context before new tasks. Connects to Hindsight Cloud. (user)
4---
5 
6# Hindsight Memory Skill (Cloud)
7 
8You have persistent memory via **Hindsight Cloud**. This memory bank is **shared with the team**, so knowledge stored here benefits everyone working on this codebase.
9 
10**Proactively store team knowledge and recall context** to provide better assistance.
11 
12## Setup Check (First-Time Only)
13 
14Before using memory commands, verify the Hindsight CLI is configured:
15 
16```bash
17cat ~/.hindsight/config
18```
19 
20**If the file doesn't exist or is missing credentials**, help the user set it up:
21 
221. **Install the CLI** (if `hindsight` command not found):
23   ```bash
24   curl -fsSL https://hindsight.vectorize.io/get-cli | bash
25   ```
26 
272. **Create the config file** - ask the user for their **API Key** (get it from https://ui.hindsight.vectorize.io):
28   ```bash
29   mkdir -p ~/.hindsight
30   cat > ~/.hindsight/config << 'EOF'
31   api_url = "https://api.hindsight.vectorize.io"
32   api_key = "<user's API key>"
33   EOF
34   chmod 600 ~/.hindsight/config
35   ```
36 
373. **Get the bank ID** - ask the user for their team's bank ID (e.g., `team-myproject`)
38 
39After setup, use the bank ID in all commands below.
40 
41## Commands
42 
43Replace `<bank-id>` with the user's actual bank ID (e.g., `team-frontend`).
44 
45### Store a memory
46 
47Use `memory retain` to store what you learn:
48 
49```bash
50hindsight memory retain <bank-id> "Project uses ESLint with Airbnb config and Prettier for formatting"
51hindsight memory retain <bank-id> "Running tests requires NODE_ENV=test" --context procedures
52hindsight memory retain <bank-id> "Build failed when using Node 18, works with Node 20" --context learnings
53hindsight memory retain <bank-id> "Alice prefers verbose commit messages with context" --context preferences
54```
55 
56### Recall memories
57 
58Use `memory recall` BEFORE starting tasks to get relevant context:
59 
60```bash
61hindsight memory recall <bank-id> "project conventions and coding standards"
62hindsight memory recall <bank-id> "Alice preferences for this project"
63hindsight memory recall <bank-id> "what issues have we encountered before"
64hindsight memory recall <bank-id> "how does the auth module work"
65```
66 
67### Reflect on memories
68 
69Use `memory reflect` to synthesize context:
70 
71```bash
72hindsight memory reflect <bank-id> "How should I approach this task based on past experience?"
73```
74 
75## IMPORTANT: When to Store Memories
76 
77This is a **shared team bank**. Store knowledge that benefits the team. For individual preferences, include the person's name.
78 
79### Project/Team Conventions (shared)
80- Coding standards ("Project uses 2-space indentation")
81- Required tools and versions ("Project requires Node 20+, PostgreSQL 15+")
82- Linting and formatting rules ("ESLint with Airbnb config")
83- Testing conventions ("Integration tests require Docker running")
84- Branch naming and PR conventions
85 
86### Individual Preferences (attribute to person)
87- Personal coding style ("Alice prefers explicit type annotations")
88- Communication preferences ("Bob prefers detailed PR descriptions")
89- Tool preferences ("Carol uses vim keybindings")
90 
91### Procedure Outcomes
92- Steps that successfully completed a task
93- Commands that worked (or failed) and why
94- Workarounds discovered
95- Configuration that resolved issues
96 
97### Learnings from Tasks
98- Bugs encountered and their solutions
99- Performance optimizations that worked
100- Architecture decisions and rationale
101- Dependencies or version requirements
102 
103### Team Knowledge
104- Onboarding information for new team members
105- Common pitfalls and how to avoid them
106- Architecture decisions and their rationale
107- Integration points with external systems
108- Domain knowledge and business logic explanations
109 
110## IMPORTANT: When to Recall Memories
111 
112**Always recall** before:
113- Starting any non-trivial task
114- Making decisions about implementation
115- Suggesting tools, libraries, or approaches
116- Writing code in a new area of the project
117- When answering questions about the codebase
118- When a team member asks how something works
119 
120## Best Practices
121 
1221. **Store immediately**: When you discover something, store it right away
1232. **Be specific**: Store "npm test requires --experimental-vm-modules flag" not "tests need a flag"
1243. **Include outcomes**: Store what worked AND what did not work
1254. **Recall first**: Always check for relevant context before starting work
1265. **Think team-first**: Store knowledge that would help other team members
1276. **Attribute individual preferences**: Store "Alice prefers X" not just "User prefers X"
1287. **Distinguish project vs personal**: Project conventions apply to everyone; personal preferences are per-person
129