island-state
Island State
State management in this project follows a strict pattern: Nanostores for simple reactive state, React Context for complex domain state. Components are purely reactive — they never own or initialize state themselves.
This matters especially in a static site with React islands. Islands are independent — there is no shared React tree. Nanostores solves this by living outside React entirely, making state accessible to any island.
Two Patterns in Use
1. Nanostores — Simple reactive state
Use for UI state, flags, or simple values that multiple components need to react to.
// src/stores/animationStore.ts
import { atom } from 'nanostores'
export const $appStore = atom<AppState>(getInitialState())
More from augurproject/augur-reboot-website
astro-dev
Comprehensive Astro development with React, Tailwind v4, and Cloudflare Workers deployment
13blogging
This skill should be used when the user asks to "add a blog post", "create a new post", "write a learn article", "publish an update", "add content to the learn section", "update the blog", or needs help with MDX content, frontmatter, or the content collection structure.
1fork-gauge
This skill should be used when the user asks to "update the fork gauge", "change risk colors", "modify the gauge animation", "add a risk level", "update the SVG visualization", "fix the needle", "change the arc", or needs help with the fork risk visualization component and its data pipeline.
1