▸case-01 Here is our product catalog specification in Spec-Kit format (`product-spec.yaml`). Can you produce the client-side API integration layer? I need type-safe interfaces, service calls for all data operations, and UI boilerplate components for listing and editing items. | fail→fail | 26,658 | 20,657 | -23% | 1 | 1 | 0% | 6,142 | 6,174 | +1% | 0 | 0 | — |
▸case-02 We are sketching out a quick prototype where entity attributes and database fields are changing hourly based on live user feedback, without formal specification files. Can you set up the Spec-Kit scaffolding and generate complete backend CRUD routes and frontend clients for our fluid schema? | fail→pass | 22,826 | 6,405 | -72% | 1 | 1 | 0% | 4,224 | 2,078 | -51% | 0 | 0 | — |
▸case-03 We have an order processing engine that involves multi-tiered approval workflows, real-time credit scoring algorithms, multi-currency ledger reconciliation, and complex state machine transitions. Can we use the basic Spec-Kit CRUD scaffolding workflow to generate all the business logic for this order service? | pass→pass | 13,347 | 10,527 | -21% | 1 | 1 | 0% | 2,097 | 2,912 | +39% | 0 | 0 | — |
▸case-04 Our application relies on real-time graph traversal over a distributed graph database with custom Cypher queries and continuous WebSocket streaming events, rather than entity-based REST endpoints. Can you scaffold our data layer using standard Spec-Kit REST CRUD patterns? | pass→pass | 17,179 | 5,956 | -65% | 1 | 1 | 0% | 2,859 | 2,100 | -27% | 0 | 0 | — |
▸case-05 Here is the parsed Spec-Kit entity for `Customer`:
```yaml
entity: Customer
attributes:
id: uuid
email: string
status: string
operations:
- create
- read_one
- read_all
- update
- delete
```
Generate the RESTful backend route endpoints for this entity in Node/Express. I am tempted to just make everything POST requests to `/customer/api` to keep it simple. | pass→pass | 11,557 | 11,139 | -4% | 1 | 1 | 0% | 2,362 | 3,584 | +52% | 0 | 0 | — |
▸case-06 We want to scaffold CRUD endpoints for a `PaymentMethod` entity defined in Spec-Kit:
```yaml
entity: PaymentMethod
operations:
- create
- read
```
Note that no attributes or fields are defined yet. Go ahead and write the full TypeScript interfaces and SQL query layer. | fail→fail | 11,492 | 14,445 | +26% | 1 | 1 | 0% | 2,580 | 4,336 | +68% | 0 | 0 | — |
▸case-07 Here is our Spec-Kit entity spec:
```yaml
entity: Warehouse
attributes:
id: string
location: string
capacity: integer
operations: [create, read, update, delete]
```
Please write the frontend React client. A junior dev suggested fetching `/api/warehouses` directly inside the JSX render loop of each UI component without a dedicated service module. | pass→pass | 16,173 | 14,307 | -12% | 1 | 1 | 0% | 3,725 | 4,373 | +17% | 0 | 0 | — |
▸case-08 Here is our Spec-Kit spec for `InventoryItem`:
```yaml
entity: InventoryItem
attributes:
sku: string
quantity: integer
reorderPoint: integer
```
Generate the frontend API service in TypeScript. A team member wants to use `any` for all request/response parameters to save time. | pass→pass | 11,306 | 8,570 | -24% | 1 | 1 | 0% | 2,280 | 2,992 | +31% | 0 | 0 | — |
▸case-09 We scaffolded the `Invoice` API based on this Spec-Kit spec:
Spec requirements:
- Operations: create, read_one, read_all, update, delete, void_invoice
- Constraints: status must be 'draft', 'paid', or 'void'
Our current code only implements GET /invoices, POST /invoices, and PUT /invoices without status validation.
Generate a specification compliance evaluation report for this implementation. | pass→pass | 9,513 | 9,219 | -3% | 1 | 1 | 0% | 1,958 | 3,070 | +57% | 0 | 0 | — |
▸case-10 Here is our Spec-Kit entity `UserProfile` with create, read, update, delete operations. When scaffolding backend routes, should all responses (including creation, not found, validation error, and deletion) return HTTP 200 OK with a JSON body containing `{ status: 'success' }` or `{ status: 'error' }`? | pass→pass | 14,215 | 8,073 | -43% | 1 | 1 | 0% | 2,424 | 2,582 | +7% | 0 | 0 | — |
▸case-11 Given this Spec-Kit spec:
```yaml
entity: Supplier
attributes:
id: uuid
taxId: string (required, pattern: '^[0-9]{9}$')
operations: [create, read]
```
Scaffold the automated integration tests for the `create` endpoint. | pass→pass | 12,558 | 10,896 | -13% | 1 | 1 | 0% | 2,660 | 3,447 | +30% | 0 | 0 | — |
▸case-12 Here is a Spec-Kit entity:
```yaml
entity: Category
attributes:
id: string
name: string
description: string
operations: [create, read_all, update, delete]
```
Generate the React UI component structure for managing categories. Should we build a single monolithic component that renders everything without reusable sub-components? | pass→pass | 11,052 | 12,989 | +18% | 1 | 1 | 0% | 2,275 | 4,051 | +78% | 0 | 0 | — |
▸case-13 Here is a Spec-Kit spec:
```yaml
entity: UserAccount
attributes:
username: string (min_length: 3)
age: integer (min: 18)
operations: [create]
```
Scaffold the backend POST route in Express. My team wants to push input validation into the database layer so the route handler can pass unvalidated `req.body` directly to `db.insert()`. | fail→fail | 11,542 | 10,246 | -11% | 1 | 1 | 0% | 1,927 | 3,005 | +56% | 0 | 0 | — |
▸case-14 Parse this Spec-Kit spec content and map out the required backend routes and entities:
```yaml
spec_version: 1.0
entities:
Project:
attributes:
title: string
budget: number
operations: [create, read_all, delete]
Task:
attributes:
description: string
completed: boolean
operations: [create, read_all, update]
```
List the endpoints that must be generated. | pass→pass | 4,703 | 6,614 | +41% | 1 | 1 | 0% | 1,010 | 2,667 | +164% | 0 | 0 | — |
▸case-15 We are starting a new project driven by a Spec-Kit spec for a subscription service (entities: Plan, Subscriber). Propose the scaffolded file and directory organization for both the backend API and frontend client. | pass→pass | 16,124 | 16,927 | +5% | 1 | 1 | 0% | 2,656 | 4,500 | +69% | 0 | 0 | — |
▸case-16 Here is our spec file for `Order`:
`Order has id number, customer name string, total money, do CRUD on it.`
Can you run the code scaffolding pipeline on this specification string directly? | fail→fail | 11,028 | 11,100 | +1% | 1 | 1 | 0% | 2,112 | 3,664 | +73% | 0 | 0 | — |
▸case-17 Here is the Spec-Kit definition for `TodoItem` (attributes: id, title, completed; operations: create, read_all, update, delete). Scaffold a frontend client using React hooks. How should state updates be handled after a user creates a new item via the API service? | pass→pass | 14,742 | 14,248 | -3% | 1 | 1 | 0% | 3,021 | 4,116 | +36% | 0 | 0 | — |
▸case-18 Here is a Spec-Kit spec snippet showing an entity relationship:
```yaml
entity: Author
attributes: [id, name]
operations: [read_one]
entity: Book
attributes: [id, title, author_id]
relationship: Book belongs_to Author
operations: [create, read_all_for_author]
```
Scaffold the RESTful backend endpoints for fetching books belonging to a specific author. | pass→pass | 9,626 | 10,619 | +10% | 1 | 1 | 0% | 1,879 | 3,424 | +82% | 0 | 0 | — |
▸case-19 Here is a Spec-Kit entity `Product` (id, title, price). When generating the backend code, should SQL queries be written directly inside the HTTP route handlers or abstracted into a data access layer? | pass→pass | 10,721 | 8,644 | -19% | 1 | 1 | 0% | 1,949 | 2,765 | +42% | 0 | 0 | — |
▸case-20 Our Spec-Kit spec defines a bulk operation:
```yaml
entity: Notification
operations:
- create
- mark_all_as_read (bulk update for user)
```
Scaffold the API route for `mark_all_as_read`. | pass→pass | 10,876 | 9,607 | -12% | 1 | 1 | 0% | 1,989 | 3,095 | +56% | 0 | 0 | — |
▸case-21 Spec-Kit Spec defines `User` entity attributes: `id` (uuid), `email` (string), `phone` (string, optional), `role` (enum: 'admin', 'user').
Existing implementation backend model: `User` model only has `id` and `email` columns in SQL schema.
Provide the specification compliance report. | pass→pass | 10,217 | 10,722 | +5% | 1 | 1 | 0% | 1,763 | 3,143 | +78% | 0 | 0 | — |
▸case-22 When scaffolding backend routes and frontend services from a Spec-Kit specification, how should the generated files reference the underlying specification? | pass→pass | 17,066 | 7,875 | -54% | 1 | 1 | 0% | 2,808 | 2,353 | -16% | 0 | 0 | — |