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": "Configure path aliases to avoid deep relative imports",
"relevant_when": "Agent creates a TypeScript project with multiple directories or nested imports",
"context": "Deep relative imports (../../..) are fragile and hard to read. Configure a path alias like @/* mapping to src/* in tsconfig paths. The alias needs runtime support: tsx for development, vite resolve.alias for Vite projects, or tsc-alias for production builds. The @/ prefix is the most common convention.",
"sources": [
{
"type": "file",
"filename": "skills/typescript-project-structure/SKILL.md",
"tile": "tessl-labs/typescript-project-structure@0.2.0"
}
],
"checklist": [
{
"name": "path-alias-configured",
"rule": "tsconfig.json has a paths configuration with at least one alias (typically @/* mapping to ./src/*) and a baseUrl set",
"relevant_when": "Agent creates a TypeScript project with nested directory structure"
},
{
"name": "no-deep-relative-imports",
"rule": "Source files do not use deeply nested relative imports (three or more levels like ../../../) when a path alias could be used instead",
"relevant_when": "Agent writes TypeScript imports across directories"
}
]
}evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
skills
typescript-project-structure
verifiers