{
  "version": 1,
  "tests": true,          // generate test files for every new component
  "codeLocale": "en",     // language for identifiers, comments, variable names
  "uiLocale": "pt-BR",    // language for user-facing strings in templates
  "i18n": false,          // set up internationalization support
  "css": "tailwind"       // plain | modules | tailwind | unocss | none
}

# My App

## Stack
- PraxisJS 1.x + @praxisjs/core, @praxisjs/decorators, @praxisjs/runtime, @praxisjs/jsx
- Build: Vite 7 + @praxisjs/vite-plugin
- Routing: @praxisjs/router
- State: @praxisjs/store

## Architecture
SPA. Entry: src/main.ts. Pages in src/pages/, components in src/components/.

## Conventions
Stores are singletons injected via @Store. All forms extend FormBase.

## Known constraints
JWT stored in memory only. Targets Chrome 100+.

I just scaffolded a PraxisJS project with the router template. Create CLAUDE.md
with the current stack and architecture, then show me the entry point setup.

Set up a PraxisJS todo app from scratch — stateful component, add/complete/delete
tasks, filter by status. Create CLAUDE.md first, then fetch the relevant docs
before writing any components.

Create a UserCard component that receives a user object as a prop and displays
name, avatar, and role. It's stateless — no internal state needed.

I need a SearchInput component with debounced input (300ms) that emits a search
event to the parent. Check the decorators/timing docs before implementing.

Add a UserProfile component that fetches /api/users/:id on mount, shows a
skeleton while loading, the profile on success, and a retry button on error.
The userId comes in as a prop.

Our ProductList currently fetches on mount. Refetch automatically whenever the
categoryId signal changes. Check the async-data docs first.

Add a CartStore to manage items, quantities, and total. Inject it into the
Header and ProductCard components. Update CLAUDE.md with the store pattern.

We need authentication state shared across the app — logged-in user, JWT token,
and a hasRole() helper. What's the right approach with PraxisJS store and DI?

Set up client-side routing with three pages: Home, Dashboard (requires auth),
and Profile. Redirect unauthenticated users to /login using a beforeEnter guard.

Add a /products/:id route that lazy-loads the ProductDetail component and
reads the id from route params. Fetch the router docs before implementing.

This computed value is updating too often — it re-derives even when unrelated
signals change. Read the reactivity docs and explain why, then fix it.

Extract the authentication logic from UserPage into a reusable composable.
Check the custom-composables docs for the right pattern.

Add @praxisjs/motion to the project and animate the sidebar width when it
toggles open and closed. Install the package first, then fetch the motion docs.