TypeScript strict patterns and best practices
Opinionated strict-TypeScript discipline — const object + extracted type instead of unions, flat interfaces, never any (unknown/generics/type guards), utility types, and import-type conventions
- What
- Opinionated strict-TypeScript discipline — const object + extracted type instead of unions, flat interfaces, never any (unknown/generics/type guards), utility types, and import-type conventions
- Cost
- Free
- Needs
- a TypeScript project the agent can read and refactor (ideally strict mode) — the skill is a pattern guide, not software to install
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @gentleman-programming's strict TypeScript patterns skill: opinionated discipline for the agent writing TypeScript. Const object created first with `as const`, type extracted via `(typeof X)[keyof typeof X]` — direct union types forbidden; interfaces kept one level deep with nested objects promoted to dedicated interfaces; `any` never used (use `unknown` for truly unknown data, generics for flexible functions); the full utility-type kit (`Pick`, `Omit`, `Partial`, `Required`, `Readonly`, `Record`, `Extract`, `Exclude`, `NonNullable`, `ReturnType`, `Parameters`); type guards with `value is User` narrowing; and `import type` conventions. Every rule is shown as ✅ always / ❌ never with code. Honest caveats: methodology only — the agent needs a TypeScript project (ideally strict mode) to apply it to; license is MIT per the catalog (the file's frontmatter also mentions Apache-2.0). Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Quick answer
TypeScript strict patterns is a free Muse skill, an opinionated strict-TypeScript discipline: create a const object first with as const, then extract the type, since direct unions are forbidden; keep interfaces one level deep, promoting nested objects to dedicated interfaces; never use any, using unknown for unknown data and generics for flexible functions, with utility types and import-type conventions.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit c8036a3Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a TypeScript project the agent can read and refactor (ideally strict mode) — the skill is a pattern guide, not software to install Install "TypeScript strict patterns and best practices" for me. It gives my agent @gentleman-programming's strict TypeScript discipline: const object first with as const, type extracted from it (no direct union types), flat interfaces with nested objects as dedicated interfaces, never any (unknown/generics/type guards instead), the full utility-type kit (Pick, Omit, Partial, Required, Readonly, Record, Extract, Exclude, NonNullable, ReturnType, Parameters), and import type conventions — every rule shown as always/never with code. MIT-licensed. Repository: https://raw.githubusercontent.com/gentleman-programming/gentleman-skills/c8036a37893679dc5e942484975405d39689c63b/curated/typescript/SKILL.md Pinned version: install the code at commit c8036a37893679dc5e942484975405d39689c63b exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 2. Safety check: review the SKILL.md for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "typescript". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. point the agent at my TypeScript project or file; nothing else — it's a pattern guide). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- c8036a3 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.