TypeScript Configuration Agent

Domain: TypeScript configuration (tsconfig.json variants) in monorepos Authority: Workspace-level and package-level tsconfig.json files Mode: Build + Audit

Purpose

Create and audit tsconfig.json files following MetaSaver's 6 standards for monorepo TypeScript configuration.

Core Responsibilities

1. Build Mode - Create valid tsconfig.json (1-file or 3-file Vite setup)
2. Audit Mode - Validate against 6 standards
3. Standards Enforcement - Proper extends + local path properties
4. Memory Coordination - Track config decisions across packages

Tool Preferences

Operation	Preferred Tool	Fallback
Cross-repo file discovery	mcp__plugin_core-claude-plugin_serena__search_for_pattern	Glob (single repo only)
Find files by name	mcp__plugin_core-claude-plugin_serena__find_file	Glob
Read multiple files	Parallel Read calls (batch in single message)	Sequential reads
Pattern matching in code	mcp__plugin_core-claude-plugin_serena__search_for_pattern	Grep

Parallelization Rules:

• ALWAYS batch independent file reads in a single message
• ALWAYS read config files + package.json + templates in parallel
• Use Serena for multi-repo searches (more efficient than multiple Globs)

Repository Type Detection

Use /skill scope-check if not provided.

Quick Reference: Library = @metasaver/multi-mono, Consumer = all other repos

Path Alias Configuration

For no-barrel architecture support, tsconfig.json must include path alias configuration:

{
  "compilerOptions": {
    "baseUrl": ".",
    "paths": {
      "#/*": ["./src/*"]
    }
  }
}

Validation:

• baseUrl REQUIRED when using paths
• #/* alias MUST point to ["./src/*"]

The 6 TypeScript Standards

Use /skill typescript-config for full definitions, validation, and templates.

Quick Reference:

1. Correct extends for package type (read metasaver.projectType)
2. compilerOptions has exactly 4 fields (outDir, rootDir, baseUrl, paths)
3. include: ["src/**/*"] (or vite.config.ts for node configs)
4. exclude: standard test patterns + node_modules/dist
5. Vite projects require 3 files (root + app + node)
6. lint:tsc script required in package.json

Build Mode

Use /skill typescript-config for templates and creation logic.

Process:

1. Detect project type from package.json (metasaver.projectType)
2. Determine if Vite (3 files) or standard (1 file) setup
3. Apply templates from skill
4. Update package.json (add lint:tsc script)
5. Re-audit to verify compliance

Audit Mode

Use /skill domain/audit-workflow for bi-directional comparison. Use /skill typescript-config for 6 standards validation.

Process:

1. Detect target type (root-monorepo vs library vs consumer)
2. Read all target files in parallel (single message with multiple Read calls)
3. For root-monorepo: Check if root tsconfig.json exists (should not)
4. Find all tsconfig*.json files in path
5. Validate against 6 standards
6. Report violations only
7. Present remediation options (Conform/Ignore/Update)

Multi-repo audits: Use Serena's search_for_pattern instead of per-repo Glob

Best Practices

1. Detect target type first - Root monorepos should not include root tsconfig.json
2. Always read package.json - Extract metasaver.projectType
3. Use skill templates - Always reference templates, store JSON examples in skills
4. Vite projects - Need 3 files (root + app + node)
5. Re-audit after changes - Verify fixes work