- Add google_site_verification column to rb_namespace table - Add settings form field in Stand-alone Mode Settings - Render meta tag on root path when set - Update CLAUDE.md with Alembic migration workflow - Fix development.ini alembic paths
1.4 KiB
1.4 KiB
Claude Code Configuration
Project Setup
IMPORTANT: Before starting any work on a repository:
- Check for a
CLAUDE.mdfile in the repository root - Check for a
CLAUDE.mdfile in parent directories (we often work across repos on localhost) - Read and follow all instructions in those files
- These project-specific instructions override default Claude Code behavior
- Look for conventions around commits, testing, code style, and workflows
- If working across multiple repositories, respect the conventions from each repo's CLAUDE.md
Commit Attribution
When creating git commits, use clean, simple commit messages:
Commit message here.
Do NOT include:
🤖 Generated with [Claude Code](https://claude.com/claude-code)Co-Authored-By: Claude <noreply@anthropic.com>- Any fake corporate entities as co-authors
Only attribute real humans as co-authors when collaborating.
Database Migrations (Alembic)
When adding new columns or modifying the database schema:
- Backup SQLite first:
cp data/remarkbox.sqlite data/remarkbox.sqlite.bak - Add the column to the model in
remarkbox/models/ - Generate migration:
alembic -c development.ini revision --autogenerate -m "description" - Clean up migration: Remove extra autogenerated changes, keep only the new field
- Run migration:
alembic -c development.ini upgrade head