microevals 0.1.0__py3-none-any.whl

evals/nextjs/029_no_catch_redirect.yaml

@@ -0,0 +1,31 @@
+eval_id: nextjs_no_catch_redirect_029
+name: "No redirect()/notFound() in Try-Catch"
+description: "Catches redirect/notFound in try-catch which breaks navigation"
+category: nextjs
+
+criteria: |
+  You have access to the entire codebase. Look for a subtle but critical bug.
+  
+  CONTEXT: redirect() and notFound() work by throwing special errors that Next.js catches.
+  
+  WHAT TO LOOK FOR:
+  Find any try-catch blocks that contain redirect() or notFound() calls.
+  
+  ANTI-PATTERN (mark as failed - THIS IS A BUG):
+  - try { redirect('/login') } catch (e) { ... }
+  - try { if (condition) notFound() } catch (error) { ... }
+  - Catching the error prevents Next.js from handling navigation
+  - Results in broken redirects or 404 pages not showing
+  
+  CORRECT PATTERN (mark as passed):
+  - redirect() and notFound() are NOT inside try-catch blocks
+  - If you need validation, do it BEFORE calling redirect/notFound
+  - Let these functions throw - Next.js will catch them correctly
+  
+  SCORING:
+  - Score 1.0 (PASS): redirect() and notFound() are NOT inside try-catch blocks, no anti-patterns found
+  - Score 0.0 (FAIL): Anti-pattern found - redirect() or notFound() called inside try-catch (THIS IS A BUG that breaks navigation)
+  - Score -1.0 (N/A): No usage of redirect() or notFound() OR no Next.js App Router
+  
+  NOTE: This is a subtle bug that makes navigation silently fail.
+

evals/nextjs/030_app_router_migration.yaml

@@ -0,0 +1,30 @@
+eval_id: nextjs_app_router_migration_030
+name: "App Router Migration (No Pages Router Patterns)"
+description: "Checks for Pages Router patterns in App Router apps"
+category: nextjs
+
+criteria: |
+  Check for Pages Router patterns in App Router apps.
+  
+  OLD PATTERNS (Pages Router):
+  - pages/ directory with route files
+  - _app.js, _document.js special files
+  - getServerSideProps, getStaticProps, getInitialProps
+  - import from 'next/router' (should use 'next/navigation')
+  
+  WHY IT'S WRONG:
+  - Mixing routers causes confusion and bugs
+  - App Router patterns don't work in Pages Router files
+  - Different mental models for routing and data fetching
+  - Can't leverage new App Router features
+  
+  CORRECT APPROACH (App Router):
+  - app/ directory with route folders
+  - layout.js, page.js, loading.js, error.js
+  - Server components with async/await
+  - import from 'next/navigation' (useRouter, usePathname, etc.)
+  
+  SCORING:
+  - Score 1.0 (PASS): Fully migrated to App Router - no Pages Router patterns
+  - Score 0.0 (FAIL): App Router exists but old Pages Router patterns still present
+  - Score -1.0 (N/A): No app/ directory exists (pure Pages Router app, which is fine for legacy apps)

evals/nextjs/031_no_non_serializable_props.yaml

@@ -0,0 +1,31 @@
+eval_id: nextjs_no_non_serializable_props_031
+name: "No Non-Serializable Props to Server Components"
+description: "Catches passing functions to server components - causes runtime error"
+category: nextjs
+
+criteria: |
+  You have access to the entire codebase. Look for non-serializable props passed to server components.
+  
+  CONTEXT: Server components can only receive JSON-serializable props.
+  
+  WHAT TO LOOK FOR:
+  Find server components (files without 'use client') being used with function props.
+  
+  ANTI-PATTERN (mark as failed - THIS IS A BUG):
+  - Passing onClick, onChange, or other function props to a server component
+  - Example: <ServerComponent onClick={handler} /> where ServerComponent has no 'use client'
+  - Error: "Functions cannot be passed to Client Components"
+  - Also applies to class instances, Dates, symbols
+  
+  CORRECT PATTERN (mark as passed):
+  - Server components only receive serializable props (strings, numbers, plain objects, arrays)
+  - Components that need event handlers have 'use client' directive
+  - Or wrap the interactive part in a client component
+  
+  SCORING:
+  - Score 1.0 (PASS): Server components only receive serializable props (strings, numbers, objects, arrays), no anti-patterns found
+  - Score 0.0 (FAIL): Anti-pattern found - passing functions or non-serializable data to server components (THIS IS A BUG)
+  - Score -1.0 (N/A): No custom components OR all components are client components OR no Next.js App Router
+  
+  NOTE: Look at the component definition - if it has no 'use client' and receives function props, that's the bug.
+

evals/react/001_missing_useeffect_dependencies.yaml

@@ -0,0 +1,29 @@
+eval_id: react_missing_useeffect_dependencies_001
+name: "Missing Dependencies in useEffect"
+description: "Checks if useEffect hooks include all dependencies in their dependency array"
+category: react
+
+criteria: |
+  Detect useEffect with missing dependencies causing stale closures.
+  
+  ANTI-PATTERN:
+  - useEffect(() => { doSomething(prop) }, []) // prop not in deps
+  - useEffect(() => { fetch(url) }, []) // url not in deps
+  - Using props/state inside effect without listing them
+  
+  WHY IT'S WRONG:
+  - Stale closures - effect uses old values
+  - Effect doesn't re-run when dependencies change
+  - Subtle bugs that are hard to debug
+  - React ESLint rule: exhaustive-deps
+  
+  CORRECT:
+  - useEffect(() => { doSomething(prop) }, [prop])
+  - Include ALL variables from outer scope used in effect
+  - Or use useCallback/useMemo to stabilize references
+  
+  SCORING:
+  - Score 1.0 (PASS): useEffect hooks exist AND all include correct dependencies (no stale closures)
+  - Score 0.0 (FAIL): useEffect hooks exist BUT missing dependencies found (list specific locations)
+  - Score -1.0 (N/A): No useEffect hooks found in codebase
+

evals/react/002_incorrect_event_handler.yaml

@@ -0,0 +1,28 @@
+eval_id: react_incorrect_event_handler_002
+name: "Incorrect Event Handler Syntax"
+description: "Checks for event handlers that are called immediately instead of on event"
+category: react
+
+criteria: |
+  Detect event handlers with incorrect syntax causing immediate execution.
+  
+  ANTI-PATTERN:
+  - onClick={handleClick()} // calls immediately, not on click
+  - onChange={setValue(e.target.value)} // calls during render
+  - onSubmit={submitForm(data)} // calls immediately
+  
+  WHY IT'S WRONG:
+  - Function executes during render, not on event
+  - Infinite render loops if it updates state
+  - Common LLM mistake
+  
+  CORRECT:
+  - onClick={handleClick} // pass reference
+  - onClick={() => handleClick()} // arrow function wrapper
+  - onChange={(e) => setValue(e.target.value)} // arrow function
+  
+  SCORING:
+  - Score 1.0 (PASS): Event handlers exist AND all use correct syntax (no immediate execution)
+  - Score 0.0 (FAIL): Event handlers exist BUT incorrect syntax found (list specific locations)
+  - Score -1.0 (N/A): No event handlers found in codebase
+

evals/react/003_missing_return_in_map.yaml

@@ -0,0 +1,28 @@
+eval_id: react_missing_return_in_map_003
+name: "Missing Return in Array.map()"
+description: "Checks for missing return statements in array.map() causing undefined renders"
+category: react
+
+criteria: |
+  Detect array.map() with curly braces but missing return statement.
+  
+  ANTI-PATTERN:
+  - array.map(item => { <Component /> }) // missing return
+  - items.map((item) => { <div>{item}</div> }) // missing return
+  - data.map(x => { const y = transform(x); <Element y={y} /> })
+  
+  WHY IT'S WRONG:
+  - Returns undefined instead of component
+  - Nothing renders but no error shown
+  - Very common LLM mistake
+  
+  CORRECT:
+  - array.map(item => <Component />) // implicit return
+  - array.map(item => { return <Component /> }) // explicit return
+  - array.map((item) => { const y = transform(item); return <Element y={y} /> })
+  
+  SCORING:
+  - Score 1.0 (PASS): Array.map() with JSX exists AND all have proper returns (explicit or implicit)
+  - Score 0.0 (FAIL): Array.map() with JSX exists BUT missing return statements found (list specific locations)
+  - Score -1.0 (N/A): No array.map() with JSX found in codebase
+

evals/react/004_async_useeffect.yaml

@@ -0,0 +1,32 @@
+eval_id: react_async_useeffect_004
+name: "Async Function in useEffect Without Wrapper"
+description: "Checks for async functions directly in useEffect (not allowed)"
+category: react
+
+criteria: |
+  Detect async functions used directly as useEffect callback.
+  
+  ANTI-PATTERN:
+  - useEffect(async () => { await fetch() }, [])
+  - Using async directly as useEffect callback
+  
+  WHY IT'S WRONG:
+  - useEffect expects function that returns void or cleanup function
+  - async functions always return Promise
+  - React warning: "Effect callbacks are synchronous"
+  - Can cause bugs with cleanup
+  
+  CORRECT:
+  - useEffect(() => { 
+      async function fetchData() { await fetch() }
+      fetchData()
+    }, [])
+  - Or: useEffect(() => { 
+      (async () => { await fetch() })()
+    }, [])
+  
+  SCORING:
+  - Score 1.0 (PASS): useEffect hooks exist AND none use async directly as callback (all properly wrapped)
+  - Score 0.0 (FAIL): useEffect hooks exist BUT async used directly as callback (list specific locations)
+  - Score -1.0 (N/A): No useEffect hooks found in codebase
+

evals/react/005_direct_state_mutation.yaml

@@ -0,0 +1,30 @@
+eval_id: react_direct_state_mutation_005
+name: "No Direct State Mutation"
+description: "Checks for direct mutation of state instead of using setState"
+category: react
+
+criteria: |
+  Detect direct mutation of React state (arrays, objects).
+  
+  ANTI-PATTERN:
+  - const [items, setItems] = useState([]); items.push(newItem)
+  - const [user, setUser] = useState({}); user.name = 'John'
+  - state.array[0] = newValue
+  - Mutating state directly without setState
+  
+  WHY IT'S WRONG:
+  - React doesn't detect the change
+  - Component doesn't re-render
+  - Breaks React's state management
+  - Violates immutability principle
+  
+  CORRECT:
+  - setItems([...items, newItem]) // spread operator
+  - setItems(prev => [...prev, newItem]) // functional update
+  - setUser({...user, name: 'John'}) // spread for objects
+  
+  SCORING:
+  - Score 1.0 (PASS): State variables exist AND none are mutated directly (all use immutable updates)
+  - Score 0.0 (FAIL): State variables exist BUT direct mutations found (list specific locations)
+  - Score -1.0 (N/A): No state variables found in codebase
+

evals/react/006_index_as_key.yaml

@@ -0,0 +1,31 @@
+eval_id: react_index_as_key_006
+name: "No Index as Key in Lists"
+description: "Checks for using array index as key prop (causes bugs with reordering)"
+category: react
+
+criteria: |
+  Detect using array index as key prop in lists.
+  
+  ANTI-PATTERN:
+  - items.map((item, index) => <div key={index}>{item}</div>)
+  - Using index as key prop
+  - Using i, idx, or other index variables as key
+  
+  WHY IT'S WRONG:
+  - Keys should be stable and unique identifiers
+  - Index changes when items are reordered/filtered/sorted
+  - Causes state to be associated with wrong items
+  - Performance issues and rendering bugs
+  - Common LLM mistake
+  
+  CORRECT:
+  - items.map(item => <div key={item.id}>{item.name}</div>)
+  - Use unique, stable ID from data
+  - If no ID, use combination of unique properties
+  - Only use index if list never changes order
+  
+  SCORING:
+  - Score 1.0 (PASS): Lists with key props exist AND all use stable IDs (no index as key)
+  - Score 0.0 (FAIL): Lists with key props exist BUT index used as key (list specific locations)
+  - Score -1.0 (N/A): No lists with key props found in codebase
+

evals/react/zustand_store_usage.yaml

@@ -0,0 +1,25 @@
+eval_id: zustand_store_usage
+name: "Zustand Store Hook Usage"
+description: "Verify the agent correctly identifies and fixes improper Zustand store hook usage patterns"
+category: react
+
+criteria: |
+  Detect improper Zustand store hook usage patterns.
+  
+  ANTI-PATTERNS:
+  - useMemo(() => useMyStore, []) - wrapping store hook
+  - useMemo(() => useMyStore(), []) - calling inside useMemo
+  - useMemo(() => create(...), []) - creating store in component
+  
+  CORRECT:
+  - const store = useMyStore (direct assignment)
+  - const useMyStore = create<T>(...) (at module level)
+  
+  SCORING:
+  - Score 1.0 (PASS): Zustand store usage exists AND used correctly (direct assignment, no wrapping)
+  - Score 0.0 (FAIL): Zustand store usage exists BUT wrapped incorrectly (list specific locations)
+  - Score -1.0 (N/A): No Zustand store usage found in codebase
+
+inputs:
+  store_name: "auto-detect"
+

evals/shadcn/001_cn_utility_function.yaml

@@ -0,0 +1,31 @@
+eval_id: shadcn_cn_utility_function_001
+name: "CN Utility Function Required"
+description: "Checks if the cn() utility function exists when shadcn components are used"
+category: shadcn
+
+criteria: |
+  Verify cn() utility function exists for shadcn components.
+  
+  ANTI-PATTERN:
+  - Using shadcn components without lib/utils.ts
+  - Missing cn() function that merges Tailwind classes
+  - Components imported but utilities not set up
+  
+  WHY IT'S WRONG:
+  - All shadcn components use cn() function
+  - Runtime error: "cn is not defined"
+  - App crashes immediately
+  
+  CORRECT:
+  - lib/utils.ts with: export function cn(...inputs: ClassValue[]) { return twMerge(clsx(inputs)) }
+  - Requires: clsx and tailwind-merge packages
+  - Must match path alias in components.json
+  
+  EVALUATION:
+  - Check if shadcn components exist (check for @/components/ui/)
+  - Verify lib/utils.ts exists with cn function
+  - Verify clsx and tailwind-merge in package.json
+  - If components exist but cn missing: score 0.0
+  - If no shadcn components: score -1.0 (N/A)
+  
+

evals/shadcn/002_css_variables.yaml

@@ -0,0 +1,32 @@
+eval_id: shadcn_css_variables_002
+name: "Required CSS Variables Defined"
+description: "Checks if shadcn theme CSS variables are defined in globals.css"
+category: shadcn
+
+criteria: |
+  Verify CSS variables for shadcn theme are defined.
+  
+  ANTI-PATTERN:
+  - Using shadcn components without CSS variable definitions
+  - Missing :root and .dark selectors in globals.css
+  - Components render but colors are broken/missing
+  
+  WHY IT'S WRONG:
+  - Components rely on CSS variables like --background, --foreground, etc.
+  - Without them, components have no colors or wrong colors
+  - Silent failure - no error, just broken UI
+  
+  CORRECT:
+  - globals.css must have:
+    :root { --background, --foreground, --primary, --secondary, etc. }
+  - .dark { ... } for dark mode variables
+  - All required shadcn CSS variables defined
+  
+  EVALUATION:
+  - Check if shadcn components exist
+  - Verify globals.css has :root with CSS variables
+  - Check for variables: --background, --foreground, --primary, --card, --border
+  - If components exist but variables missing: score 0.0
+  - If no shadcn components: score -1.0 (N/A)
+  
+

evals/shadcn/003_component_dependencies.yaml

@@ -0,0 +1,33 @@
+eval_id: shadcn_component_dependencies_003
+name: "Required Component Peer Dependencies"
+description: "Checks if peer dependencies are installed for shadcn components that require them"
+category: shadcn
+
+criteria: |
+  Verify peer dependencies for shadcn components that require them.
+  
+  ANTI-PATTERN:
+  - Using Form component without react-hook-form and zod
+  - Using Calendar without date-fns or day.js
+  - Using Sonner toast without sonner package
+  - Using Command without cmdk
+  
+  WHY IT'S WRONG:
+  - Runtime error: "Cannot find module 'react-hook-form'"
+  - Components crash when dependencies missing
+  - Each specialized component has specific requirements
+  
+  CORRECT:
+  - Form needs: react-hook-form, zod, @hookform/resolvers
+  - Calendar needs: react-day-picker, date-fns
+  - Command needs: cmdk
+  - Sonner needs: sonner
+  - Check shadcn docs for each component's requirements
+  
+  EVALUATION:
+  - Detect which shadcn components are used
+  - Check if required dependencies are in package.json
+  - If component used without dependency: score 0.0
+  - If no components with dependencies: score -1.0 (N/A)
+  
+

evals/shadcn/004_path_aliases.yaml

@@ -0,0 +1,32 @@
+eval_id: shadcn_path_aliases_004
+name: "Correct Path Aliases Configuration"
+description: "Checks if path aliases (@/components) are properly configured for shadcn imports"
+category: shadcn
+
+criteria: |
+  Verify path aliases are configured correctly for shadcn component imports.
+  
+  ANTI-PATTERN:
+  - Components import from '@/components/ui/button'
+  - But tsconfig.json has no @ alias configured
+  - Or alias points to wrong directory
+  
+  WHY IT'S WRONG:
+  - Module not found error: "Cannot find module '@/components/ui/button'"
+  - Imports fail at build time
+  - Shadcn CLI generates imports with @ alias by default
+  
+  CORRECT:
+  - tsconfig.json (or jsconfig.json) must have:
+    "paths": { "@/*": ["./*"] } or "@/*": ["./src/*"]
+  - Must match components.json aliases configuration
+  - baseUrl must be set (usually ".")
+  
+  EVALUATION:
+  - Check if shadcn components exist with @ imports
+  - Verify tsconfig.json/jsconfig.json has @ alias configured
+  - Check if path matches actual component location
+  - If imports use @ but not configured: score 0.0
+  - If no shadcn components: score -1.0 (N/A)
+  
+

evals/shadcn/005_client_directive.yaml

@@ -0,0 +1,31 @@
+eval_id: shadcn_client_directive_005
+name: "Use Client Directive for Interactive Components"
+description: "Checks if interactive shadcn components have 'use client' directive in Next.js App Router"
+category: shadcn
+
+criteria: |
+  Verify interactive shadcn components have 'use client' directive.
+  
+  ANTI-PATTERN:
+  - Using Form, Dialog, Popover, etc. in server components
+  - Missing 'use client' in component files
+  - Importing client components directly in server components
+  
+  WHY IT'S WRONG:
+  - Error: "You're importing a component that needs useState/useEffect"
+  - Interactive components require client-side rendering
+  - Hydration errors in Next.js App Router
+  
+  CORRECT:
+  - Interactive components need 'use client' at top of file
+  - Or wrap in a client component wrapper
+  - Components that need it: Form, Dialog, Popover, DropdownMenu, Sheet, etc.
+  
+  EVALUATION:
+  - Check if using Next.js App Router (app directory)
+  - Detect shadcn interactive components (form, dialog, dropdown, etc.)
+  - Verify these components or their wrappers have 'use client'
+  - If interactive components without 'use client': score 0.0
+  - If no App Router or no interactive components: score -1.0 (N/A)
+  
+

evals/shadcn/006_tailwind_config.yaml

@@ -0,0 +1,36 @@
+eval_id: shadcn_tailwind_config_006
+name: "Tailwind Config Theme Extension"
+description: "Checks if Tailwind config includes required theme extension for shadcn CSS variables"
+category: shadcn
+
+criteria: |
+  Verify Tailwind config has theme extension for shadcn CSS variables.
+  
+  ANTI-PATTERN:
+  - Using shadcn without extending theme with CSS variables
+  - Missing color definitions in tailwind.config
+  - Components don't inherit theme colors properly
+  
+  WHY IT'S WRONG:
+  - Tailwind doesn't recognize CSS variable-based colors
+  - Utilities like bg-background, text-foreground don't work
+  - Components may have inline styles but no utility support
+  
+  CORRECT:
+  - tailwind.config must extend theme.colors:
+    colors: {
+      background: "hsl(var(--background))",
+      foreground: "hsl(var(--foreground))",
+      primary: { DEFAULT: "hsl(var(--primary))", foreground: "hsl(var(--primary-foreground))" },
+      // etc.
+    }
+  - borderRadius with CSS variables
+  
+  EVALUATION:
+  - Check if shadcn components exist
+  - Verify tailwind.config extends theme with CSS variable colors
+  - Look for hsl(var(--background)) pattern in colors
+  - If components exist but theme not extended: score 0.0
+  - If no shadcn components: score -1.0 (N/A)
+  
+

evals/shadcn/007_components_json_config.yaml

@@ -0,0 +1,35 @@
+eval_id: shadcn_components_json_config_007
+name: "Valid components.json Configuration"
+description: "Checks if components.json exists and is properly configured for shadcn CLI"
+category: shadcn
+
+criteria: |
+  Verify components.json is properly configured for shadcn CLI.
+  
+  ANTI-PATTERN:
+  - Missing components.json file
+  - Incorrect paths that don't match project structure
+  - Wrong alias configuration
+  - Style/baseColor mismatch with actual setup
+  
+  WHY IT'S WRONG:
+  - shadcn CLI fails: "components.json not found"
+  - Components installed to wrong directory
+  - Import paths don't match actual paths
+  - Can't add new components with CLI
+  
+  CORRECT:
+  - components.json at project root
+  - Correct aliases: { "components": "@/components", "utils": "@/lib/utils" }
+  - Valid paths matching tsconfig
+  - Style should match (default/new-york)
+  - tailwind config paths correct
+  
+  EVALUATION:
+  - Check if shadcn components exist
+  - Verify components.json exists and is valid JSON
+  - Check if paths/aliases match actual project structure
+  - If components exist but config wrong: score 0.0
+  - If no shadcn components: score -1.0 (N/A)
+  
+

evals/supabase/001_client_setup.yaml

@@ -0,0 +1,47 @@
+
+eval_id: supabase_client_setup
+name: "Supabase Client Setup and Configuration"
+description: "Check if agent properly set up the Supabase client with correct configuration"
+category: supabase
+
+# What was the agent asked to do?
+task_description: |
+  Build an application with Supabase backend
+
+# How to evaluate success?
+criteria: |
+  The agent was asked to build an application with Supabase backend.
+
+  DO NOT MODIFY ANY FILES. Only read and evaluate the existing code.
+  
+  Evaluate if they completed the task successfully by checking:
+  
+  1. **Package Installation**
+     - Has @supabase/supabase-js package installed in package.json
+  
+  2. **Client Configuration**
+     - Creates Supabase client using createClient()
+     - Client is properly exported for use
+     - Uses environment variables (e.g., NEXT_PUBLIC_SUPABASE_URL, VITE_SUPABASE_URL, SUPABASE_URL, etc.)
+     - No hardcoded credentials in source code
+  
+  3. **Connection Validation**
+     - Test the connection using provided credentials: URL={supabase_url}, Key={supabase_anon_key}
+     - Run a basic test query to verify the connection works
+  
+  Look at the repo and check for evidence like:
+  - package.json with @supabase/supabase-js dependency
+  - Supabase client file (lib/supabase.ts, utils/supabase.ts, config/supabase.ts, etc.)
+  - Proper use of environment variables
+  - Successful connection test
+  
+  SCORING:
+  - 1.0 (PASS): All criteria met - package installed, client configured correctly, env vars used, connection works
+  - 0.0 (FAIL): Supabase was ATTEMPTED (package installed OR client imports OR env vars present) but incorrectly configured (hardcoded credentials, missing env vars, broken connection, etc.)
+  - -1.0 (N/A): Supabase is NOT USED AT ALL in the codebase - no @supabase/supabase-js dependency, no imports, no configuration attempts. This is the correct score when the project uses a different backend (Firebase, MongoDB, Razorpay, etc.)
+
+# Optional: Custom inputs for this specific eval
+inputs:  
+  supabase_url: "SUPABASE_URL"
+  supabase_anon_key: "SUPABASE_ANON_KEY"
+  env_file_path: ".env.local"

evals/supabase/002_auth_context_setup.yaml

@@ -0,0 +1,43 @@
+
+eval_id: supabase_auth_context_setup
+name: "Supabase Auth State Management Setup"
+description: "Check if agent created auth state management with proper methods"
+category: supabase
+
+# What was the agent asked to do?
+task_description: |
+  Create a login page and authentication system
+
+# How to evaluate success?
+criteria: |
+  The agent was asked to create a login page and authentication system.
+
+  DO NOT MODIFY ANY FILES. Only read and evaluate the existing code.
+  
+  Evaluate if they completed the task successfully by checking:
+  
+  1. **Auth State Management Exists**
+     - Find auth context, store, service, or provider file
+     - Examples: contexts/auth.tsx, stores/auth.ts, services/auth.ts, composables/useAuth.ts, etc.
+     - Exports auth state management (provider, store, service, or composable)
+  
+  2. **Auth Methods Available**
+     - Exports auth interface/hook/composable (useAuth, authStore, authService, etc.)
+     - Provides user state
+     - Provides auth methods (signUp, signIn, signOut or similar)
+  
+  Look at the repo and check for evidence like:
+  - Auth state management file (React Context, Vue store, Svelte store, Angular service, etc.)
+  - Exported auth interface (useAuth, authStore, authService, etc.)
+  - Auth methods available (signUp, signIn, signOut)
+  
+  SCORING:
+  - 1.0 (PASS): Auth state management exists AND auth methods are available with user state
+  - 0.0 (FAIL): Missing auth state management OR missing auth methods OR anti-patterns found
+  - -1.0 (N/A): Supabase is NOT USED in the codebase (no @supabase/supabase-js dependency) OR no authentication system exists at all. If the app uses a different auth provider (Firebase Auth, Auth0, NextAuth, etc.), this is N/A.
+
+# Optional: Custom inputs for this specific eval
+inputs:  
+  supabase_url: "SUPABASE_URL"
+  supabase_anon_key: "SUPABASE_ANON_KEY"
+