• There are 10 files with 1,084 lines of code.
• 0 very long files (0 lines of code)
• 1 long files (664 lines of code)
• 0 medium size files (0 lines of code)
• 2 small files (259 lines of code)
• 7 very small files (161 lines of code)

File	# lines	≈ tokens to read	# changes (1y)	≈ lines edited per change	lines read per line changed
App.jsx in src	664	~3k–10k	5	~200	~3
promo-generator.ts in cdk/lib	69	~300–1k	4	~20	~3
riff-raff.yaml in root	31	under 1k	5	~20	~2
index.css in src	101	~700–1.5k	1	~2	~50
vite.config.js in root	6	under 1k	1	~3	~2
mjs eslint.config.mjs in cdk	5	under 1k	1	~5	~1

Tokens are lines × 7 to 14 (analysis.fileReadsForChanges). Lines edited per change are the file's lines added and deleted divided by its commits over the whole history. Agents read about 2,000 lines at a time: when a 17,000-line file was split into modules, the tokens an agent read for the same change fell by 83% (The Economic Benefit of Refactoring, 2026).

There is only one file with lines longer than 120 characters. In total, there are 25 long lines.

File	# lines	# units	# long lines
App.jsx in src	664	-	25

• File size measurements show the distribution of size of files.
• Files are classified in four categories based on their size (lines of code): 1-100 (very small files), 101-200 (small files), 201-500 (medium size files), 501-1000 (long files), 1001+(very long files).
• It is a good practice to keep files small. Long files may become "bloaters", code that have increased to such gargantuan proportions that they are hard to work with.