The new Star Trek Voyager game is such a thorough simulation that I think it's convinced me to abandon my dreams of joining Starfleet when I grow up. Being a captain is no fun at all!
Topics:
star trek
voyager game
captain
starfleet
space exploration
Originally appeared on Robby on Rails.One of my priorities this quarter was running a few AI pilot experiments. This was one of them.
When I mentioned the project to a teammate, he said, “You shou...
Originally appeared on Robby on Rails.One of my priorities this quarter was running a few AI pilot experiments. This was one of them.
When I mentioned the project to a teammate, he said, “You should write this up.” So here we are.
Others on our team had already been exploring embeddings, vector databases, and RAG. I’d been watching from the sidelines… until it was time to roll up my sleeves and build something myself.
The Problem
At Planet Argon, we manage several client projects. We live in Jira (I know… I know…). We keep decisions in Confluence. We ship code from GitHub. Over years a lot of institutional knowledge piles up across those systems… past bugs, old tradeoffs, and the “we tried that once” stories.
The problem…
If you’ve been using Claude Code for a while, you’ve probably accumulated a decent amount of configuration: settings, skills, custom agents, CLAUDE.md instructions. Losing all of that would be anno...
If you’ve been using Claude Code for a while, you’ve probably accumulated a decent amount of configuration: settings, skills, custom agents, CLAUDE.md instructions. Losing all of that would be annoying.
The fix: git init inside ~/.claude, with some caveats.
What lives in ~/.claude
Based on the official docs, here’s what’s worth versioning:
CLAUDE.md
settings.json
skills/**/SKILL.md
agents/<name>.md
commands/<name>.md
statusline.sh
What to ignore
Claude Code generates transient data that you should ignore. Add this to your .gitignore.
# Credentials
.credentials.json
credentials.json
# Internal state
.claude.json
.claude.json.backup.*
security_warnings_*.json
stats-cache.json
mcp-needs-auth-cache.json
# Session data
history.jsonl
backups
cache
debug
file-history
paste-cache
session-env
shell-snapshots
# Agent and team state
plans
plugins
tasks
teams
todos
# Telemetry
statsig
telemetry
usage-data
# IDE integration
ide/
Note about projects
The projects/ directory contains per-project auto-memory and conversation logs. Claude Code recently enabled memory per project, which is worth adding to git. The easiest approach is to ignore the log files instead:
projects/**/*.jsonl
projects/**/*.txt
Quick setup
Remember to push it to GitHub or GitLab, below is an example with GitHub:
cd ~/.claude
git init
git add .gitignore CLAUDE.md settings.json
git add skills/ agents/ commands/ statusline.sh 2>/dev/null
git commit -m "feat: initial claude config"
gh repo create claude-config --private --source=. --push
That’s it.
Originally appeared on Ruby Central.We're excited to announce that Ruby will participate in Google Summer of Code (GSoC) 2026! This program offers new open source contributors the chance to work on...
Originally appeared on Ruby Central.We're excited to announce that Ruby will participate in Google Summer of Code (GSoC) 2026! This program offers new open source contributors the chance to work on impactful projects supporting the Ruby ecosystem, such as RubyGems.org, RubyGems, and Bundler, with guidance from experienced mentors.Google Summer of Code is an annual program run by Google that pairs open source organizations with new contributors (18+ years old with less than two years of open source experience). Contributors receive a stipend from Google to work on a defined project over roughly 12 weeks.How to get involvedOur contributor wiki has everything you need to get started: project ideas, guidance on writing a strong…
Topics:
google summer of code
open source
rubygems
bundler
Originally appeared on Robby on Rails.I had never personally worked with embeddings, vector databases, or retrieval-augmented generation before this project. I knew the words. I did not know where ...
Originally appeared on Robby on Rails.I had never personally worked with embeddings, vector databases, or retrieval-augmented generation before this project. I knew the words. I did not know where the sharp edges were. Folks on our team do… but I felt it was time to wrap my own head around it.
What I did have was a real problem, a team that loves Ruby, and enough curiosity to see where things broke.
This is the story of that experiment… what worked, what surprised me, and what I’d tell another Ruby developer who’s considering something similar.
The Problem
At Planet Argon, we manage several client projects. We live in Jira (I know… I know…). We keep decisions in Confluence. We ship code from GitHub. Over years a lot of…