---
name: tsconfig-configuration-assistant
description: Specialized skill for assisting with TypeScript configuration setup, optimization, and troubleshooting in the DWP Hours Tracker project.
title: tsconfig-configuration-assistant
canonical_url: https://skilld.dev/gh/corey-alix/dwp-hours/tsconfig-configuration-assistant
last_updated: 2026-10-07T01:30:59.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install corey-alix/dwp-hours/tsconfig-configuration-assistant`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/tsconfig-configuration-assistant`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/corey-alix/dwp-hours/tsconfig-configuration-assistant) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/tsconfig-configuration-assistant`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/tsconfig-configuration-assistant --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/tsconfig-configuration-assistant --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# TSConfig Configuration Assistant

## Description

Specialized skill for assisting with TypeScript configuration (tsconfig.json) setup, optimization, and troubleshooting in the DWP Hours Tracker project. Provides guidance based on official TypeScript documentation and project-specific requirements.

## Trigger

Activate when users ask about:

- TypeScript compiler options and configuration
- tsconfig.json settings and best practices
- TypeScript build errors related to configuration
- Module resolution, paths, or strict mode settings
- Integrating TypeScript with project build tools

## Response Pattern

1. **Analyze Current Configuration**: Review the existing tsconfig.json and related files (tsconfig.build.json, etc.)
2. **Reference Official Documentation**: Consult https://www.typescriptlang.org/tsconfig/ for accurate option details
3. **Assess Project Context**: Consider DWP Hours Tracker's Node.js/Express backend and vanilla TypeScript frontend architecture
4. **Provide Targeted Recommendations**: Suggest specific compiler options with explanations
5. **Validate Changes**: Ensure suggestions align with project quality gates (strict mode, error handling, etc.)
6. **Test Configuration**: Recommend running `npm run build` and `npm test` to validate changes

## Examples

- "How should I configure the 'paths' option for module resolution?"
- "What's causing this TypeScript compilation error in my config?"
- "Help me set up strict TypeScript checking for better code quality"
- "How do I configure TypeScript for both development and production builds?"
- "What's the best way to handle type declarations for external libraries?"

## Additional Context

- Prioritizes TypeScript strict mode and modern ES modules
- Integrates with project's build system (npm scripts, Vitest testing)
- References TASKS/database-schema.md and TASKS/api-endpoints.md for type-related requirements
- Ensures compatibility with sql.js for database operations
- Supports both server-side (Node.js) and client-side (browser) compilation targets
