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
{
"instruction": "Enable strict mode and noUncheckedIndexedAccess in tsconfig.json",
"relevant_when": "Agent creates or configures a TypeScript project",
"context": "Every tsconfig.json must have strict: true (never cherry-pick individual strict options) and noUncheckedIndexedAccess: true. Without strict mode, TypeScript misses null/undefined bugs, implicit any types, and incorrect function types. Without noUncheckedIndexedAccess, Record and array index access hides potential undefined values.",
"sources": [
{
"type": "file",
"filename": "skills/typescript-project-structure/SKILL.md",
"tile": "tessl-labs/typescript-project-structure@0.2.0"
}
],
"checklist": [
{
"name": "strict-true",
"rule": "tsconfig.json (or the base tsconfig) has \"strict\": true in compilerOptions — not individual strict flags cherry-picked",
"relevant_when": "Agent creates any tsconfig.json file"
},
{
"name": "no-unchecked-indexed-access",
"rule": "tsconfig.json has \"noUncheckedIndexedAccess\": true in compilerOptions",
"relevant_when": "Agent creates any tsconfig.json file"
},
{
"name": "no-strict-false",
"rule": "No tsconfig in the project sets \"strict\": false or disables individual strict checks like \"strictNullChecks\": false",
"relevant_when": "Agent creates any tsconfig.json file"
}
]
}evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
skills
typescript-project-structure
verifiers