- always update
CLAUDE.mdfile in root dir and subpackage inside monorepo and consider it as a living document - lookout for nextjs update to support
typescript@7natively, because currently we need@typescript/native-preview
- Remember to always use EXACT version for all dependencies
- Run
bun bump:depsto check for outdated dependencies, then runbun installto install it - To upgrade expo app, it's better to follow the steps in "How to upgrade?" section inside it's README
- To upgrade IntentUI components (last updated at "June 30 2026" release or "v3.8.4"), run interactively
bun bump:ui- keep
'use client'directive in components/hooks - copy changes in toast props into
providers/toast/context.tsx, then remove generatedtoast.tsxfile - use
react-statelyinstead of@react-stately/color - use
react-ariainstead of@react-aria/i18n - change
@/hooks/use-mobileinto@/core/hooks/use-mobile @/hooks/use-clipboardinto@/core/hooks/use-clipboard- copy className in
chart.tsxintoglobals.css - do not use
.Providerfor react context because we're using react 19 - all regex should be defined outside of components/hooks for stable reference
- keep
- If there's MINOR upgrade in
playwright, runbun web test:installto install new version of chromium - Run
bun web test,bun spa test, andbun expo test:devto run E2E tests (run the dev server / emulator first) - Run
bun web build,bun spa build, andbun expo build:android:dev:localto build with development env - Run
bun lint-typecheckfor linting and type checking
After changes are checked, invoke the release skill: add writes a changeset for the PR; cut (on clean main) versions all packages together, updates each CHANGELOG.md, commits, tags vX.Y.Z, and pushes (GitHub Release via .github/workflows/release.yml). Manual: bun cs / bun cs:v.
For first timer, you need to create the 2 environments in your github repo. First is dev environment, and second is prod environment (that's why in .github/workflows/ci.yml we stated environment: dev). In both environments, name it SPA_ENV_FILE and WEB_ENV_FILE (that's why in .github/workflows/ci.yml we stated secrets.SPA_ENV_FILE and secrets.WEB_ENV_FILE).
The value for SPA_ENV_FILE in dev environment is .env.dev, and the value for SPA_ENV_FILE in prod environment is .env.prod for @workspace/spa. The value for WEB_ENV_FILE in dev environment is .env.dev, and the value for WEB_ENV_FILE in prod environment is .env.prod for @workspace/web.
Source of truth is local env files. When changing them, update deployment/CI project env too.
grafana/otel-lgtmdocker- Grafana Prometheus for metrics
- Grafana Tempo for traces
- Grafana Loki for logs
- Grafana Pyroscope for profiling
Login to dashboard at http://localhost:3111 with credentials:
- Username:
admin - Password:
admin
- Capo.js enhancing the performance of HTML
<head>by reordering it. - Unlighthouse measuring the performance of all pages.
- Web.dev Performance
- Web Vitals
- Zhead is a
<head>database. Discover new tags to use to improve your SEO, accessibility and performance. - Opengraph Image Playground.
- JSON-LD Playground.
- Rich Results Test for Google or schema.org Validator for general structured data validation.