---
name: sql-js-database-assistant
description: Provides guidance for working with sql.js database operations, including query optimization, prepared statements, and schema management.
title: sql-js-database-assistant
canonical_url: https://skilld.dev/gh/corey-alix/dwp-hours/sql-js-database-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/sql-js-database-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/sql-js-database-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/sql-js-database-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/sql-js-database-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/sql-js-database-assistant --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/sql-js-database-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.

# SQL.js Database Assistant

## Description

Provides guidance for working with sql.js database operations, including query optimization, prepared statements, schema management, and SQLite best practices. Helps implement efficient database interactions for the DWP Hours Tracker application.

## Trigger

Activated when users mention database operations, SQL queries, SQLite, prepared statements, schema changes, or ask about database performance, data persistence, or sql.js usage.

## Response Pattern

1. Analyze the database operation requirements and current schema structure
2. Recommend appropriate sql.js patterns (prepared statements, transactions, proper error handling)
3. Guide implementation of SQL queries with proper parameterization and indexing
4. Suggest database optimization techniques and data integrity practices
5. Ensure database operations align with project quality gates and TASKS/database-schema.md standards

## Examples

- "How do I write a prepared statement for inserting PTO entries?"
- "What's the best way to query employee data with sql.js?"
- "How do I handle database transactions safely?"
- "My database query is slow, how can I optimize it?"
- "How do I add a new table to the schema?"

## Additional Context

This skill integrates with the completed TASKS/database-schema.md and follows sql.js official documentation best practices. Focuses on SQLite-specific optimizations, proper resource management, and reliable data persistence. Complements the existing database schema while ensuring all operations follow TypeScript strict mode and proper error handling patterns.
