init

.agents/skills/kiranism-shadcn-dashboard/evals/evals.json

@@ -0,0 +1,35 @@
+{
+  "skill_name": "kiranism-shadcn-dashboard",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Migrate the products feature in this dashboard starter away from the mock API. Keep the existing React Query and table flow, but make the default architecture Drizzle-backed route handlers under src/app/api/products and a service.ts that calls those local endpoints.",
+      "expected_output": "Guidance defaults to route handlers plus Drizzle, keeps the feature API layering, and treats mock data as legacy to be replaced.",
+      "files": [
+        "src/features/products/api/service.ts",
+        "src/app/api/products/route.ts",
+        "src/app/api/products/[id]/route.ts"
+      ]
+    },
+    {
+      "id": 2,
+      "prompt": "Replace the Clerk-based protection on a dashboard page with Auth.js session checks and an app-owned organization membership model. I need the plan to cover middleware or protected routes, page-level guards, and how nav visibility should work without useOrganization/useUser.",
+      "expected_output": "Guidance defaults to Auth.js, explains user-organization-membership-role vocabulary, and avoids Clerk-specific hooks or components.",
+      "files": [
+        "src/proxy.ts",
+        "src/hooks/use-nav.ts",
+        "src/components/layout/providers.tsx"
+      ]
+    },
+    {
+      "id": 3,
+      "prompt": "Add a new orders page to this repo. I want it built the way the project should look after migration: Drizzle schema first, route handlers for CRUD, feature api/types-service-queries-mutations, and dashboard UI with table filters.",
+      "expected_output": "Guidance uses the new build order from schema to UI, includes route handlers and Auth.js-aware server checks, and does not recommend mock-api files.",
+      "files": [
+        "src/app/dashboard/orders/page.tsx",
+        "src/features/orders/api/types.ts",
+        "src/app/api/orders/route.ts"
+      ]
+    }
+  ]
+}