Michael Chihlas
86120423da
The index page had ~12 distinct card surfaces with three places of nested cards-inside-cards, against PRODUCT.md's "elevation = lighter surface + border" + "nested cards are always wrong" rules. Branding appeared twice, Display Code lived in Identity but does invite work, and Preferences got a full card for one dropdown. Single column, max-w-3xl, no card chrome. Sections separated by border-t rules + mono-uppercase section labels (existing house style): - Header: inline-editable name + plan/status/owner/member-count info line. No card. - Plan & usage: renewal date right-aligned in section header, three thin progress rows replace the 4-card usage stat grid, upgrade CTAs right-aligned at bottom. - People (owner-only): invite form, unified members + pending invites list, display code as a quiet "share to invite during signup" line. Non-owners see a one-line "managed by your admin" instead of a card. - Settings: dense route list (icon + title + summary + status pill + chevron). Profile above a thin divider; team-admin rows below, owner-gated. Branding row carries the Included/Plan-gated pill. Support & Feedback as a dim link at the bottom. - Account actions: plain rows. Owner: Transfer + Delete. Non-owner: Leave. Destructive labels colored, no red box-of-doom. Drops: Access & Security card (filler), Preferences card, Settings Areas link grid, billing-card branding-status duplicate, SettingsLinkCard helper. Default export format moves to Profile Settings where it belongs (personal preference, not account). 856 -> 710 lines on the index. tsc, eslint, vite build clean. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
React + TypeScript + Vite
This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.
Currently, two official plugins are available:
- @vitejs/plugin-react uses Babel (or oxc when used in rolldown-vite) for Fast Refresh
- @vitejs/plugin-react-swc uses SWC for Fast Refresh
React Compiler
The React Compiler is not enabled on this template because of its impact on dev & build performances. To add it, see this documentation.
Expanding the ESLint configuration
If you are developing a production application, we recommend updating the configuration to enable type-aware lint rules:
export default defineConfig([
globalIgnores(['dist']),
{
files: ['**/*.{ts,tsx}'],
extends: [
// Other configs...
// Remove tseslint.configs.recommended and replace with this
tseslint.configs.recommendedTypeChecked,
// Alternatively, use this for stricter rules
tseslint.configs.strictTypeChecked,
// Optionally, add this for stylistic rules
tseslint.configs.stylisticTypeChecked,
// Other configs...
],
languageOptions: {
parserOptions: {
project: ['./tsconfig.node.json', './tsconfig.app.json'],
tsconfigRootDir: import.meta.dirname,
},
// other options...
},
},
])
You can also install eslint-plugin-react-x and eslint-plugin-react-dom for React-specific lint rules:
// eslint.config.js
import reactX from 'eslint-plugin-react-x'
import reactDom from 'eslint-plugin-react-dom'
export default defineConfig([
globalIgnores(['dist']),
{
files: ['**/*.{ts,tsx}'],
extends: [
// Other configs...
// Enable lint rules for React
reactX.configs['recommended-typescript'],
// Enable lint rules for React DOM
reactDom.configs.recommended,
],
languageOptions: {
parserOptions: {
project: ['./tsconfig.node.json', './tsconfig.app.json'],
tsconfigRootDir: import.meta.dirname,
},
// other options...
},
},
])