TypeScript project structure, strict tsconfig, module resolution, path aliases, shared types, and monorepo patterns
90
84%
Does it follow best practices?
Impact
100%
1.09xAverage score across 5 eval scenarios
Passed
No known issues
A developer needs to build a command-line tool in TypeScript that processes CSV files and generates JSON reports. The tool will be published as an npm package, so it needs proper build output, declaration files for consumers, and a clean project structure.
The CLI should accept a CSV file path as input and output a summary report. It needs to handle errors gracefully (file not found, malformed CSV).
Produce a complete project structure with:
package.json — with bin entry, type: module, scripts (build, dev, start, typecheck, lint, test), and appropriate dependenciestsconfig.json — strict config with NodeNext resolution, declaration output, path aliasestsconfig.test.json — test config extending base, including test directory.gitignore — ignoring dist/, node_modules/, and other generated filessrc/index.ts — CLI entry point (parses command-line args)src/parser.ts — CSV parsing logicsrc/reporter.ts — Report generationsrc/types/index.ts — Type definitions (CSVRow, ReportConfig, ReportOutput)src/lib/errors.ts — Custom error types (FileNotFoundError, ParseError)tests/parser.test.ts — Test file for the parser (using vitest or similar)Focus on project structure, tsconfig configuration, type-only imports, and proper TypeScript patterns. The CSV parsing itself can be simplified.
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
skills
typescript-project-structure
verifiers