---
title: "TeqFW Guide: JSDoc — onboarding around JSDoc in TeqFW"
description: "I launched a custom GPT chat for the TeqFW team so JSDoc stays part of the project’s daily workflow and VSCode can read package types more reliably."
date: 2026-02-20
display_date: "February 20, 2026"
image: "/img/brand/teqfw.webp"
image_alt: "TeqFW Guide: JSDoc — onboarding around JSDoc in TeqFW"
---

# TeqFW Guide: JSDoc — onboarding around JSDoc in TeqFW

<zoom-img src="/img/brand/teqfw.webp" alt="TeqFW Guide: JSDoc — onboarding around JSDoc in TeqFW"
        width="100px"></zoom-img>

In TeqFW, JSDoc helps the team work productively in a regular JavaScript codebase without TypeScript. It gives
        VSCode and `tsserver` enough structure to understand modules, contracts, and types, so developers get useful
        navigation and hints while staying in the TeqFW way of working.

[TeqFW Guide: JSDoc](https://fly.wiredgeese.com/flancer/gpt/teqfw/guide/jsdoc/) is a custom GPT chat for the TeqFW team. It helps keep JSDoc aligned with the project’s
        documents and makes package types easier for VSCode to read.

The useful part is the dialogue. The chat turns project rules into something practical: what to put into
        JSDoc, how to describe types in an npm package, and how to avoid unnecessary rebuilds in an isomorphic JS app
        when the front end and the back end already share the same code.

For TeqFW, this matters because the codebase stays in JS without TS while still keeping editor support,
        readable signatures, and sane navigation through the code. TeqFW Guide: JSDoc helps keep that workflow in
        place.