resolved
Cursor
cursor.com/dashboard
landed in 38msBookSlash for Cursor · AI
AI-first IDE,
flat-namespace shortcuts.
Cursor is where engineering teams ship AI-assisted code. The team settings, the billing dashboard, the rules and docs — each get a flat name BookSlash makes memorable.
cursor
other shortcuts you might save
b/cursorb/cursor-billingb/cursor-teamb/cursor-docs
Suggested slug patterns
Steal these. They work for most teams.
Battle-tested shortcut conventions for Cursor, with notes on why each one survives the URL changes that break personal bookmarks.
- b/cursor
Cursor home / dashboard.
Engineering teams reach it daily; saving as a slug ends the navigation tax.
https://cursor.com/dashboard - b/cursor-billing
Cursor team billing and usage.
Finance and engineering managers reach it monthly.
https://cursor.com/team/billing - b/cursor-team
Team admin and member management.
IT and engineering managers reach it during onboarding.
https://cursor.com/team - b/cursor-docs
Cursor documentation.
New engineers learn it day one.
https://docs.cursor.com - b/cursor-changelog
Cursor changelog / release notes.
Engineering teams check it for new features; saving as a slug skips the search.
https://cursor.com/changelog - b/cursor-rules
Team-level rules / cursorrules conventions.
Engineering leads reach it during code-review setup; the slug carries through every team-onboarding cycle.
https://docs.cursor.com/context/rules
Common workflows
Three patterns that pay back in week one.
01
New engineer Cursor onboarding
Day-one engineers receive b/cursor, b/cursor-team, b/cursor-docs, and b/cursor-rules. They join the workspace, configure their team rules, and read the docs in 30 minutes.
02
Monthly billing review
Finance opens b/cursor-billing for monthly cost review. Pairs with b/cursor-team for the per-seat breakdown.
03
Release-tracking for engineering
Engineering managers reach b/cursor-changelog weekly to track new features. Pairs with b/cursor-docs for the deeper reference.
With and without
Same Cursor. Different team experience.
Without shortcuts
Each engineer has private Cursor bookmarks. Onboarding includes a 30-minute "how to set up Cursor" walkthrough. Finance pings engineering for the billing URL.
With BookSlash
b/cursor, b/cursor-billing, b/cursor-team, b/cursor-docs, b/cursor-changelog, b/cursor-rules. Six slugs cover the engineering Cursor surface end to end.
Frequently asked
BookSlash + Cursor
Yes — both. Slugs are URL → URL; Cursor exposes URLs identically across plans. Most teams namespace by environment: b/cursor-prod vs b/cursor-staging if they have multiple workspaces.
Most teams pair them: b/cursor (the IDE), b/repo (the GitHub source), b/prs (the review queue). One namespace, every tool the engineering team touches.
No. Cursor handles the code; BookSlash routes the navigation. The two systems never exchange code or AI prompts.
Yes — BookSlash ships a Raycast extension. b/cursor resolves from your launcher with the same ergonomic Cursor users already love.
Start with one team. Roll out when it sticks.
Your stack. Your shortcuts.
One keystroke for everyone.
2,400+ teams reach every important destination in their stack with a single keystroke. Save the first slug in 30 seconds.
Free for personal use · No credit card · 14-day team trial