Notebook session ended
This session ended after eight hours.
Sign in again to continue from where you left off.
Notebook gate offline
The sign-in service is not responding right now.
Wait a minute and try again, or read what is already public from the hub.
Foundational walk through the smo1 project. Read top to bottom if you're new; no prior context assumed.
More about this project on the Smo1 hub.
Use when: onboarding a new developer to the SMO1 codebase; explaining the architecture to a non-technical stakeholder; understanding the relationship between the six projects
Use when: debugging why a slug returns 404 instead of redirecting; understanding how the edge worker decides between redirect, proxy, and landing; explaining the request path to an infrastructure engineer
Use when: adding a new feature to purr-api; tracing a bug through the call stack; explaining the Go project structure to a new backend engineer
Use when: designing a new feature that touches users, links, or achievements; understanding the API response shape for the dashboard; debugging why a link shows the wrong status or score
Use when: debugging 401 errors across different clients; adding a new auth mechanism to purr-api; auditing the security surface of the API
Use when: debugging login loops or session expiry; understanding how meow-web authenticates without its own user database; implementing SSO with Airlock in another project
Use when: debugging why a slug does not redirect; understanding the edge worker's internal flow; optimising redirect latency
Use when: investigating inflated click counts; adding a new bot pattern to the edge worker; understanding how unique visitors are counted
Use when: debugging missing or duplicate click counts; understanding how analytics data flows from edge to warehouse; explaining the async tracking design to a product manager
Use when: debugging stale link data; designing cache invalidation for a new feature; explaining why the same slug resolves differently on different devices
Use when: implementing password-protected links; debugging why a protected link shows a prompt instead of redirecting; understanding the edge vs. API split for protection
Use when: debugging 429 errors for specific users; adjusting rate limits for a new subscription tier; understanding how Redis enforces sliding windows
Use when: explaining link health scores to a user; debugging why a link's pawprintz dropped suddenly; designing new gamification mechanics
Use when: designing new achievement rewards; understanding why a user is level 7 instead of level 8; explaining the progression curve to a product designer
Use when: debugging why a user's tier did not update after payment; adding a new subscription plan; understanding webhook idempotency
Use when: debugging why a new link is not immediately resolvable at the edge; understanding the async write pattern for edge cache; designing bulk operations that affect many links
Use when: implementing a white-label short link; debugging why a proxied page shows broken assets; understanding path rewriting at the edge
Use when: designing a query that spans transactional and analytical data; troubleshooting slow analytics dashboards; explaining the three-database strategy to a DevOps engineer
Use when: setting up a new environment (kitten/cat/lion); debugging why the landing page is not loading; understanding the Cloudflare → Vercel routing
Use when: adding a new UI label that needs both cat and professional versions; understanding why the dashboard uses words like 'Pawprintz'; explaining the dual-mode design to a designer
Use when: writing the smo1.io tagline or homepage hero; answering 'what category is smo1 in?' in one sentence
Use when: deciding which audience a campaign or page speaks to; writing copy that has to land for more than one segment at once
Use when: drafting the homepage hero or first-time visitor flow; writing an empty state, a decay message, or an error
Use when: writing a launch post or status update for smo1 V1-ALPHA; explaining what 'live' actually means for smo1
Use when: reviewing a smo1 design comp or marketing draft for drift; explaining why smo1 looks different from other shorteners