microevals 0.1.0__py3-none-any.whl

config/judge_system_prompt.yaml

@@ -0,0 +1,113 @@
+# System prompt for code evaluation judge
+
+judge_prompt:
+  instruction_template: |
+    ROLE: You are an objective code evaluation judge.
+    
+    Your sole responsibility is to evaluate code against specific criteria provided below.
+    You are NOT a code reviewer, bug finder, or general critic.
+    You ONLY assess whether the code meets the exact criteria specified.
+    
+    Think of yourself as a judge in a competition who scores based on a rubric.
+    Your judgment must be fair, consistent, and based solely on the criteria given.
+    
+    CRITICAL INSTRUCTIONS:
+    1. DO NOT MODIFY ANY CODE FILES. Only read and analyze them.
+    2. ONLY evaluate the SPECIFIC criteria below. DO NOT report other issues.
+    3. Even if you find critical bugs or problems, IGNORE them unless they match the criteria below.
+    4. Your ONLY job is to evaluate what is asked, nothing else.
+    
+    EVALUATION CRITERIA TO CHECK:
+    {criteria}
+    
+    {inputs_section}
+    
+    SCORING RULES:
+    - Score 1.0: All criteria met successfully (PASS)
+      * The code implements what the criteria asks for
+      * No anti-patterns described in criteria are present
+      * All "must have" requirements are satisfied
+    
+    - Score 0.0: Criteria not met or anti-pattern found (FAIL)
+      * The code does NOT implement what criteria asks for
+      * Anti-patterns described in criteria ARE present
+      * Any "must have" requirement is missing
+    
+    - Score -1.0: Criteria NOT APPLICABLE (pattern/feature not present in codebase)
+      * Use this when the feature/pattern being evaluated doesn't exist in the codebase at all
+      * For example: evaluating Next.js patterns in a pure React app
+      * Or: evaluating authentication when no auth system exists
+    
+    IMPORTANT SCORING GUIDANCE:
+    - Be strict but fair
+    - If criteria lists multiple requirements, ALL must be met for 1.0
+    - If even ONE anti-pattern is found, score is 0.0
+    - When in doubt between 0.0 and -1.0: if the code attempts the pattern (even badly), score 0.0; if pattern doesn't exist at all, score -1.0
+    
+    REQUIRED OUTPUT:
+    You MUST use the write tool to create a file named "eval_result.json" in the current directory.
+    
+    The JSON file must contain exactly these fields:
+    {{
+      "passed": true/false,
+      "score": 1.0 | 0.0 | -1.0,
+      "summary": "Brief explanation of what you found",
+      "evidence": ["Specific findings with line numbers"],
+      "issues": ["List of issues found or empty array"]
+    }}
+    
+    CRITICAL: Use the write tool to create eval_result.json - do not just output JSON to console.
+
+batch_judge_prompt:
+  instruction_template: |
+    ROLE: You are an objective code evaluation judge conducting BATCH evaluations.
+    
+    Your sole responsibility is to evaluate code against MULTIPLE criteria provided below.
+    You are NOT a code reviewer, bug finder, or general critic.
+    You ONLY assess whether the code meets each exact criteria specified.
+    
+    CRITICAL INSTRUCTIONS:
+    1. DO NOT MODIFY ANY CODE FILES. Only read and analyze them.
+    2. Run ALL {eval_count} evaluations listed below.
+    3. Complete EVERY evaluation, even if some fail or error.
+    4. Save EACH result to its specified filename.
+    5. Use the SAME scoring rules for each evaluation.
+    
+    SCORING RULES (apply to EVERY evaluation):
+    - Score 1.0: All criteria met successfully (PASS)
+      * The code implements what the criteria asks for
+      * No anti-patterns described in criteria are present
+      * All "must have" requirements are satisfied
+    
+    - Score 0.0: Criteria not met or anti-pattern found (FAIL)
+      * The code does NOT implement what criteria asks for
+      * Anti-patterns described in criteria ARE present
+      * Any "must have" requirement is missing
+    
+    - Score -1.0: Criteria NOT APPLICABLE (pattern/feature not present in codebase)
+      * Use this when the feature/pattern being evaluated doesn't exist in the codebase at all
+      * For example: evaluating Next.js patterns in a pure React app
+      * Or: evaluating authentication when no auth system exists
+    
+    IMPORTANT SCORING GUIDANCE:
+    - Be strict but fair for each evaluation
+    - If criteria lists multiple requirements, ALL must be met for 1.0
+    - If even ONE anti-pattern is found, score is 0.0
+    - When in doubt between 0.0 and -1.0: if the code attempts the pattern (even badly), score 0.0; if pattern doesn't exist at all, score -1.0
+    
+    EVALUATIONS TO RUN:
+    {batch_criteria}
+    
+    REQUIRED OUTPUT FOR EACH EVALUATION:
+    You MUST use the write tool to create a separate JSON file for EACH evaluation using the exact filename specified.
+    
+    Each JSON file must contain exactly these fields:
+    {{
+      "passed": true/false,
+      "score": 1.0 | 0.0 | -1.0,
+      "summary": "Brief explanation of what you found",
+      "evidence": ["Specific findings with line numbers"],
+      "issues": ["List of issues found or empty array"]
+    }}
+    
+    CRITICAL: Create a SEPARATE file for each evaluation. Do not combine results into one file.

evals/nextjs/001-server-component.yaml

@@ -0,0 +1,28 @@
+eval_id: nextjs_server_component_001
+name: "Server Component Data Fetching"
+description: "Validates proper async server component implementation for data fetching"
+category: nextjs
+
+criteria: |
+  You have access to the entire codebase. Evaluate if server components properly fetch data.
+  
+  CONTEXT: This eval applies to Next.js App Router codebases with data fetching.
+  
+  WHAT TO LOOK FOR:
+  Look for page components (page.tsx/jsx files) or server components that fetch data.
+  
+  ANTI-PATTERN (mark as failed):
+  - Server component uses 'use client' directive just to use useState/useEffect for data fetching
+  - Async function fetch but missing 'await' on fetch() or response.json()
+  - Component should be async but isn't declared as async
+  
+  CORRECT PATTERN (mark as passed):
+  - Page/server component is async function
+  - Uses 'await fetch()' and 'await response.json()' 
+  - No 'use client' directive for data fetching components
+  
+  SCORING:
+  - Score 1.0 (PASS): Server components properly fetch data with async/await, no anti-patterns found
+  - Score 0.0 (FAIL): Anti-patterns found (using 'use client' for data fetching, missing await, non-async)
+  - Score -1.0 (N/A): No Next.js App Router OR no server components doing data fetching
+

evals/nextjs/002-client-component.yaml

@@ -0,0 +1,26 @@
+eval_id: nextjs_client_component_002
+name: "Client Component with State"
+description: "Validates proper client component implementation with React state management"
+category: nextjs
+
+criteria: |
+  You have access to the entire codebase. Evaluate if components using React hooks have the 'use client' directive.
+  
+  CONTEXT: This eval applies to Next.js App Router codebases using React hooks.
+  
+  WHAT TO LOOK FOR:
+  Find any files that import and use React hooks (useState, useEffect, useReducer, etc.)
+  
+  ANTI-PATTERN (mark as failed):
+  - File uses useState, useEffect, or other React hooks but is missing 'use client' directive at top
+  - Component in app/ directory uses hooks without 'use client'
+  
+  CORRECT PATTERN (mark as passed):
+  - All components using hooks have 'use client' at the top of the file
+  - Or they properly import client components that handle the hooks
+  
+  SCORING:
+  - Score 1.0 (PASS): All components using React hooks have 'use client' directive, no anti-patterns found
+  - Score 0.0 (FAIL): Components use React hooks without 'use client' directive
+  - Score -1.0 (N/A): No Next.js App Router OR no components use React hooks OR using Pages Router
+

evals/nextjs/003-cookies.yaml

@@ -0,0 +1,28 @@
+eval_id: nextjs_server_actions_cookies_003
+name: "Server Actions Cookie Management"
+description: "Validates server actions properly handle cookies using Next.js APIs"
+category: nextjs
+
+criteria: |
+  You have access to the entire codebase. Evaluate if cookie management uses the correct APIs.
+  
+  CONTEXT: This eval applies to Next.js App Router codebases that set/read cookies.
+  
+  WHAT TO LOOK FOR:
+  Find any code that sets or reads cookies. Check where and how cookies are used.
+  
+  ANTI-PATTERN (mark as failed):
+  - Server actions or server components use document.cookie (browser API)
+  - Setting cookies without importing cookies() from 'next/headers'
+  - Using cookies() in client components (has 'use client')
+  
+  CORRECT PATTERN (mark as passed):
+  - Server actions use 'use server' and cookies() from 'next/headers'
+  - Server components import { cookies } from 'next/headers'
+  - Client-side uses fetch/server actions to set cookies server-side
+  
+  SCORING:
+  - Score 1.0 (PASS): Cookie management uses correct Next.js APIs (cookies() from 'next/headers'), no anti-patterns found
+  - Score 0.0 (FAIL): Anti-patterns found (using document.cookie in server context, cookies() in client components, etc.)
+  - Score -1.0 (N/A): No Next.js App Router OR no cookie management in codebase OR using Pages Router only
+

evals/nextjs/010-route-handlers.yaml

@@ -0,0 +1,30 @@
+eval_id: nextjs_route_handlers_010
+name: "Route Handlers API Routes"
+description: "Validates proper Next.js App Router route handler implementation"
+category: nextjs
+
+criteria: |
+  You have access to the entire codebase. Evaluate if API routes use correct Next.js App Router patterns.
+  
+  CONTEXT: This eval applies to Next.js App Router codebases with API routes.
+  
+  WHAT TO LOOK FOR:
+  Find route.ts/route.js files in the app/ directory (API routes).
+  
+  ANTI-PATTERN (mark as failed):
+  - route.ts file uses Pages Router API (export default function handler(req, res))
+  - Using Node.js req/res objects instead of Next.js Request/Response
+  - API route not named route.ts/route.js
+  - Missing Response.json() for JSON responses
+  
+  CORRECT PATTERN (mark as passed):
+  - Files named route.ts in app/api/[endpoint]/ structure
+  - Exports named functions: GET, POST, PUT, DELETE, etc.
+  - Uses Next.js Request/Response: new Response(), Response.json()
+  - Async functions when doing async operations
+  
+  SCORING:
+  - Score 1.0 (PASS): API routes use correct App Router patterns (route.ts files with named exports GET/POST/etc.), no anti-patterns found
+  - Score 0.0 (FAIL): Anti-patterns found (Pages Router patterns in App Router, wrong file names, missing Response.json(), etc.)
+  - Score -1.0 (N/A): No API routes in codebase OR using Pages Router only OR no Next.js App Router
+

evals/nextjs/013-pathname-server.yaml

@@ -0,0 +1,29 @@
+eval_id: nextjs_pathname_server_013
+name: "Dynamic Route Parameters in Server Components"
+description: "Validates using params prop in dynamic route server components"
+category: nextjs
+
+criteria: |
+  You have access to the entire codebase. Evaluate if dynamic routes properly use params.
+  
+  CONTEXT: This eval applies to Next.js App Router with dynamic routes.
+  
+  WHAT TO LOOK FOR:
+  Find dynamic route folders (app/[id], app/posts/[slug], etc.) and check their page.tsx files.
+  
+  ANTI-PATTERN (mark as failed):
+  - Dynamic route page component tries to use useRouter() or useParams() in server component
+  - Server component doesn't accept params prop but needs route parameters
+  - Component is marked 'use client' just to access route params
+  
+  CORRECT PATTERN (mark as passed):
+  - Server component accepts params prop: async function Page({ params })
+  - Uses params.id or params.slug etc. to fetch data
+  - Component is async and awaits data fetching
+  - No 'use client' needed just for route params
+  
+  SCORING:
+  - Score 1.0 (PASS): Dynamic route server components properly use params prop, no anti-patterns found
+  - Score 0.0 (FAIL): Anti-patterns found (using useRouter/useParams in server components, missing params prop, 'use client' just for route params)
+  - Score -1.0 (N/A): No dynamic routes in codebase OR using Pages Router only OR no Next.js App Router
+

evals/nextjs/014-server-routing.yaml

@@ -0,0 +1,28 @@
+eval_id: nextjs_server_routing_014
+name: "Server-Side Routing and Redirects"
+description: "Validates proper server-side redirect() usage vs client-side navigation"
+category: nextjs
+
+criteria: |
+  You have access to the entire codebase. Evaluate if redirects are done correctly based on context.
+  
+  CONTEXT: This eval applies to redirects in Next.js App Router.
+  
+  WHAT TO LOOK FOR:
+  Find redirect() calls and check if they're used in the right context (server vs client).
+  
+  ANTI-PATTERN (mark as failed):
+  - Server component (no 'use client') tries to use useRouter().push() for redirects
+  - Using window.location.href in server components or server actions
+  - Auth redirects done client-side when user data is only available server-side
+  
+  CORRECT PATTERN (mark as passed):
+  - Server-side redirects use redirect() from 'next/navigation' in server components
+  - Client-side navigation uses useRouter().push() in 'use client' components
+  - Auth checks done server-side with redirect() if unauthorized
+  
+  SCORING:
+  - Score 1.0 (PASS): Redirects use correct APIs based on context (redirect() in server, useRouter in client), no anti-patterns found
+  - Score 0.0 (FAIL): Anti-patterns found (useRouter in server components, window.location in server, client-side auth redirects with server data)
+  - Score -1.0 (N/A): No redirects in codebase OR no Next.js App Router OR using Pages Router
+

evals/nextjs/018-use-router.yaml

@@ -0,0 +1,28 @@
+eval_id: nextjs_use_router_018
+name: "useRouter Programmatic Navigation"
+description: "Validates proper useRouter import from next/navigation (App Router)"
+category: nextjs
+
+criteria: |
+  You have access to the entire codebase. Evaluate if useRouter is imported from the correct package.
+  
+  CONTEXT: This eval applies to Next.js App Router codebases using programmatic navigation.
+  
+  WHAT TO LOOK FOR:
+  Find any imports of useRouter hook.
+  
+  ANTI-PATTERN (mark as failed):
+  - Importing useRouter from 'next/router' in App Router app/ directory
+  - Using window.location.href = '...' for Next.js navigation
+  - Missing 'use client' in file that uses useRouter
+  
+  CORRECT PATTERN (mark as passed):
+  - Imports useRouter from 'next/navigation' (App Router)
+  - File has 'use client' directive
+  - Uses router.push(), router.back(), router.refresh() correctly
+  
+  SCORING:
+  - Score 1.0 (PASS): useRouter imported from 'next/navigation' with 'use client' directive, no anti-patterns found
+  - Score 0.0 (FAIL): Anti-patterns found (importing from 'next/router' in App Router, window.location, missing 'use client')
+  - Score -1.0 (N/A): No programmatic navigation OR using Pages Router only OR only using Link components
+

evals/nextjs/020_no_use_effect.yaml

@@ -0,0 +1,30 @@
+eval_id: nextjs_no_use_effect_020
+name: "Avoid Unnecessary useEffect"
+description: "Checks for unnecessary useEffect usage that can be replaced with direct code execution"
+category: nextjs
+
+criteria: |
+  Detect unnecessary useEffect hooks that can be replaced with direct code execution.
+  
+  ANTI-PATTERNS:
+  - useEffect for browser/navigator detection (can be done directly in component body)
+  - useEffect for setting derived state (should compute during render)
+  - useEffect with empty deps for one-time calculations (can be done at module level or during render)
+  - useEffect just to call a function once (can call directly in component)
+  
+  WHY IT'S WRONG:
+  - Adds unnecessary complexity and indirection
+  - Can cause extra re-renders
+  - Makes code harder to understand and maintain
+  - May cause timing issues (effect runs after paint)
+  
+  CORRECT APPROACH:
+  - Compute values directly in component body
+  - Use useMemo for expensive derived computations
+  - Call functions directly if they don't need side effects
+  - Only use useEffect for actual side effects (subscriptions, DOM manipulation, etc.)
+  
+  SCORING:
+  - Score 1.0 (PASS): No unnecessary useEffect found - all effects are for legitimate side effects
+  - Score 0.0 (FAIL): Unnecessary useEffect detected - code that doesn't need side effects
+  - Score -1.0 (N/A): No React/Next.js code found in project

evals/nextjs/021-avoid-fetch-in-effect.yaml

@@ -0,0 +1,28 @@
+eval_id: nextjs_avoid_fetch_in_effect_021
+name: "Avoid Fetch in useEffect"
+description: "Detects unnecessary client-side data fetching that should be server-side"
+category: nextjs
+
+criteria: |
+  You have access to the entire codebase. Evaluate if data fetching is done server-side when possible.
+  
+  CONTEXT: This eval applies to Next.js App Router codebases with data fetching.
+  
+  WHAT TO LOOK FOR:
+  Find components that fetch data on mount. Check if they could be server components instead.
+  
+  ANTI-PATTERN (mark as failed):
+  - Page component has 'use client' and uses useEffect(() => { fetch(...) }, []) for initial data
+  - Component marked 'use client' solely to use useState/useEffect for non-interactive data fetching
+  - Loading data that doesn't depend on user interaction or client-side state
+  
+  CORRECT PATTERN (mark as passed):
+  - Page components are async server components that await fetch()
+  - Client components only fetch data in response to user interaction
+  - useEffect fetch is for real-time updates, polling, or client-specific needs
+  
+  SCORING:
+  - Score 1.0 (PASS): Data fetching done server-side when possible, client-side fetch only for valid reasons (user interaction, real-time), no anti-patterns found
+  - Score 0.0 (FAIL): Anti-patterns found (useEffect fetch for initial data that should be server-side, 'use client' solely for non-interactive data)
+  - Score -1.0 (N/A): No data fetching OR all client-side fetching is legitimate OR using Pages Router
+

evals/nextjs/022_prefer_server_actions.yaml

@@ -0,0 +1,29 @@
+eval_id: nextjs_prefer_server_actions_022
+name: "Prefer Server Actions Over API Routes"
+description: "Checks if forms use server actions instead of client-side fetch to API routes"
+category: nextjs
+
+criteria: |
+  Check if forms use server actions instead of client-side fetch to API routes.
+  
+  ANTI-PATTERN:
+  - Forms with onSubmit + fetch/axios calls to API routes
+  - Creating API routes just for simple form mutations
+  - Client-side data fetching for form submissions
+  
+  BEST PRACTICE (Next.js 13+ App Router):
+  - Forms with action={serverAction} prop
+  - 'use server' directive in server action functions
+  - Direct FormData usage in server actions
+  - No intermediate API route needed
+  
+  WHY IT'S BETTER:
+  - Simpler code - no API route + fetch boilerplate
+  - Better performance - direct server execution
+  - Type safety - server actions are type-safe
+  - Progressive enhancement - works without JavaScript
+  
+  SCORING:
+  - Score 1.0 (PASS): Forms use server actions (or no forms exist but should score 1.0 if using App Router best practices)
+  - Score 0.0 (FAIL): Forms use old pattern (onSubmit + fetch to API routes)
+  - Score -1.0 (N/A): No forms found, or using Pages Router (where API routes are appropriate)

evals/nextjs/023_avoid_getserversideprops.yaml

@@ -0,0 +1,27 @@
+eval_id: nextjs_avoid_getserversideprops_023
+name: "Avoid Pages Router Patterns (getServerSideProps)"
+description: "Detects old Pages Router patterns like getServerSideProps in App Router apps"
+category: nextjs
+
+criteria: |
+  Detect old Pages Router patterns (getServerSideProps, getStaticProps, getInitialProps).
+  
+  OLD PATTERNS (Pages Router - deprecated in App Router):
+  - export function getServerSideProps
+  - export function getStaticProps
+  - export function getInitialProps
+  
+  WHY IT'S WRONG:
+  - These functions only work in Pages Router (pages/ directory)
+  - App Router uses server components and async functions instead
+  - Mixing routers causes confusion and errors
+  
+  CORRECT APPROACH (App Router):
+  - Use server components for data fetching
+  - Use async/await directly in components
+  - Use server actions for mutations
+  
+  SCORING:
+  - Score 1.0 (PASS): No Pages Router patterns found - using App Router correctly
+  - Score 0.0 (FAIL): Old Pages Router patterns detected (getServerSideProps, getStaticProps, getInitialProps)
+  - Score -1.0 (N/A): Using Pages Router exclusively (pages/ directory exists, app/ doesn't)

evals/nextjs/024_avoid_redundant_usestate.yaml

@@ -0,0 +1,29 @@
+eval_id: nextjs_avoid_redundant_usestate_024
+name: "Avoid Redundant useState"
+description: "Checks for unnecessary useState for derived values that can be computed directly"
+category: nextjs
+
+criteria: |
+  Detect useState storing derived values that could be computed directly.
+  
+  ANTI-PATTERN:
+  - useState for values completely derived from other state
+  - useEffect updating state based on other state changes
+  - Example: `const [showResult, setShowResult] = useState(false)` that mirrors `selected !== null`
+  - Example: total price from items array (should compute, not store)
+  
+  WHY IT'S WRONG:
+  - Unnecessary complexity and state management overhead
+  - Can lead to synchronization bugs if derived state gets out of sync
+  - Extra re-renders when both states update
+  - Harder to maintain and understand
+  
+  CORRECT APPROACH:
+  - Compute derived values directly: `const showResult = selected !== null`
+  - Use useMemo for expensive computations
+  - Keep state minimal and derive everything else
+  
+  SCORING:
+  - Score 1.0 (PASS): No redundant useState found - all state is minimal and necessary
+  - Score 0.0 (FAIL): Redundant useState detected - state storing derived values
+  - Score -1.0 (N/A): No React/Next.js code found in project

evals/nextjs/025_no_async_client_components.yaml

@@ -0,0 +1,29 @@
+eval_id: nextjs_no_async_client_components_025
+name: "No Async Client Components"
+description: "Catches async client components which cause runtime errors"
+category: nextjs
+
+criteria: |
+  You have access to the entire codebase. Look for a specific runtime error pattern.
+  
+  CONTEXT: This catches a common mistake that causes immediate runtime errors.
+  
+  WHAT TO LOOK FOR:
+  Find any file that has BOTH 'use client' directive AND an async component function.
+  
+  ANTI-PATTERN (mark as failed - THIS IS A BUG):
+  - File has 'use client' at the top
+  - AND exports an async function component: export default async function MyComponent()
+  - This causes error: "Client components cannot be async"
+  
+  CORRECT PATTERN (mark as passed):
+  - Client components ('use client') are NOT async
+  - Async components do NOT have 'use client' (they're server components)
+  
+  SCORING:
+  - Score 1.0 (PASS): No async client components found, all async components are server components, no anti-patterns found
+  - Score 0.0 (FAIL): Anti-pattern found - file has 'use client' AND async component function (THIS IS A BUG that breaks the app)
+  - Score -1.0 (N/A): No Next.js App Router OR no async component functions in codebase
+  
+  NOTE: This is a critical error. If found, this breaks the app immediately.
+

evals/nextjs/026_no_serial_await.yaml

@@ -0,0 +1,26 @@
+eval_id: nextjs_no_serial_await_026
+name: "Avoid Serial Await (Use Parallel Fetching)"
+description: "Checks for serial await pattern that should be parallelized with Promise.all"
+category: nextjs
+
+criteria: |
+  Detect serial await for independent requests (should use Promise.all).
+  
+  ANTI-PATTERN:
+  - const data1 = await fetch1();
+  - const data2 = await fetch2(); // Independent of data1 - should be parallel!
+  - Serial awaiting when requests don't depend on each other
+  
+  WHY IT'S WRONG:
+  - Wastes time - second request waits unnecessarily for first to complete
+  - Poor performance - doubles the total wait time
+  - Example: 2 serial 1s requests = 2s total, parallel = 1s total
+  
+  CORRECT APPROACH:
+  - const [data1, data2] = await Promise.all([fetch1(), fetch2()])
+  - Only use serial await when requests are dependent
+  
+  SCORING:
+  - Score 1.0 (PASS): No serial await for independent requests - using Promise.all appropriately
+  - Score 0.0 (FAIL): Serial await detected for independent requests
+  - Score -1.0 (N/A): No multiple async operations found, or all serial awaits are legitimately dependent

evals/nextjs/027-prefer-next-image.yaml

@@ -0,0 +1,30 @@
+eval_id: nextjs_prefer_next_image_027
+name: "Prefer Next.js Image Component"
+description: "Validates using Next.js Image instead of img tags for image optimization"
+category: nextjs
+
+criteria: |
+  You have access to the entire codebase. Evaluate if images are using Next.js optimization.
+  
+  CONTEXT: This eval applies to Next.js projects displaying images.
+  
+  WHAT TO LOOK FOR:
+  Find <img> tags or Image components in the codebase.
+  
+  ANTI-PATTERN (mark as failed):
+  - Using <img> tags instead of Next.js Image component
+  - Hardcoded image paths without optimization
+  - Missing required props (width, height, alt) on Image component
+  
+  CORRECT PATTERN (mark as passed):
+  - Import Image from 'next/image'
+  - Use <Image src="..." alt="..." width={X} height={Y} />
+  - All images have proper alt text for accessibility
+  
+  SCORING:
+  - Score 1.0 (PASS): All images use Next.js Image component with proper props, no anti-patterns found
+  - Score 0.0 (FAIL): Anti-patterns found (using <img> tags, missing required props on Image, no alt text)
+  - Score -1.0 (N/A): No images displayed OR images are only SVGs OR not using Next.js
+  
+  NOTE: This is an optimization, not a bug. <img> works but misses Next.js optimizations.
+

evals/nextjs/027_no_hooks_in_server_components.yaml

@@ -0,0 +1,29 @@
+eval_id: nextjs_no_hooks_in_server_components_027
+name: "No React Hooks in Server Components"
+description: "Catches React hooks used without 'use client' - causes runtime error"
+category: nextjs
+
+criteria: |
+  You have access to the entire codebase. Look for hooks used in server components.
+  
+  CONTEXT: This catches a very common mistake that causes runtime errors.
+  
+  WHAT TO LOOK FOR:
+  Find files that use React hooks (useState, useEffect, useReducer, useContext, etc.) but DON'T have 'use client' directive.
+  
+  ANTI-PATTERN (mark as failed - THIS IS A BUG):
+  - File in app/ directory uses useState, useEffect, etc.
+  - File is missing 'use client' at the top
+  - Error: "You're importing a component that needs useState. This only works in a Client Component"
+  
+  CORRECT PATTERN (mark as passed):
+  - All files using hooks have 'use client' directive
+  - Server components don't use hooks
+  
+  SCORING:
+  - Score 1.0 (PASS): All files using React hooks have 'use client' directive, no anti-patterns found
+  - Score 0.0 (FAIL): Anti-pattern found - React hooks used without 'use client' directive (THIS IS A BUG that breaks the app)
+  - Score -1.0 (N/A): No Next.js App Router OR using Pages Router OR no React hooks used in codebase
+  
+  NOTE: This is one of the most common Next.js App Router mistakes.
+

evals/nextjs/028-prefer-next-font.yaml

@@ -0,0 +1,30 @@
+eval_id: nextjs_prefer_next_font_028
+name: "Prefer Next.js Font Optimization"
+description: "Validates using next/font instead of external font CDN or CSS imports"
+category: nextjs
+
+criteria: |
+  You have access to the entire codebase. Evaluate if custom fonts are using Next.js optimization.
+  
+  CONTEXT: This eval applies to Next.js projects using custom fonts.
+  
+  WHAT TO LOOK FOR:
+  Find font loading patterns - check HTML head, CSS @import, or next/font imports.
+  
+  ANTI-PATTERN (mark as failed):
+  - Google Fonts loaded via CDN link in HTML: <link href="https://fonts.googleapis.com/...">
+  - @import url('https://fonts.googleapis.com/...') in CSS
+  - External stylesheet for fonts instead of next/font
+  
+  CORRECT PATTERN (mark as passed):
+  - Import fonts from next/font/google: import { Inter } from 'next/font/google'
+  - Configure with options: const inter = Inter({ subsets: ['latin'] })
+  - Apply className: <body className={inter.className}>
+  
+  SCORING:
+  - Score 1.0 (PASS): Custom fonts use next/font optimization, no anti-patterns found
+  - Score 0.0 (FAIL): Anti-patterns found (loading fonts via CDN links, @import in CSS, external stylesheets)
+  - Score -1.0 (N/A): No custom fonts used OR not using Next.js OR no Next.js App Router
+  
+  NOTE: This is an optimization, not a bug. CDN fonts work but are slower.
+

evals/nextjs/028_cookies_headers_context.yaml

@@ -0,0 +1,29 @@
+eval_id: nextjs_cookies_headers_context_028
+name: "Cookies/Headers Only in Server Context"
+description: "Catches cookies() or headers() used in client components - causes runtime error"
+category: nextjs
+
+criteria: |
+  You have access to the entire codebase. Look for cookies() or headers() in wrong contexts.
+  
+  CONTEXT: This catches a mistake that causes runtime errors.
+  
+  WHAT TO LOOK FOR:
+  Find imports of cookies or headers from 'next/headers' and check where they're used.
+  
+  ANTI-PATTERN (mark as failed - THIS IS A BUG):
+  - File has 'use client' directive AND uses cookies() or headers()
+  - Error: "cookies() only works in Server Components"
+  - These APIs only work in server components, server actions, and route handlers
+  
+  CORRECT PATTERN (mark as passed):
+  - cookies() and headers() only used in files WITHOUT 'use client'
+  - Used in server components, server actions (use server), or route.ts files
+  
+  SCORING:
+  - Score 1.0 (PASS): cookies() and headers() only used in server context (no 'use client'), no anti-patterns found
+  - Score 0.0 (FAIL): Anti-pattern found - cookies() or headers() used in client components with 'use client' (THIS IS A BUG)
+  - Score -1.0 (N/A): No usage of cookies() or headers() from 'next/headers' OR no Next.js App Router
+  
+  NOTE: If you need cookies in client component, pass them as props from server component.
+