Expanding Santi020k Theme from editor to terminal
How a VS Code palette became a generated terminal system with six application formats, three Starship styles, managed shells, validation, and Homebrew releases.
Related topics
Latest
Start with the latest post tagged #developer-experience, then browse the rest.
How a VS Code palette became a generated terminal system with six application formats, three Starship styles, managed shells, validation, and Homebrew releases.
How I separated product code from distribution metadata and turned signed terminal releases into familiar Homebrew install and upgrade commands.
What separates ESLint configurations that spread across a codebase from ones that get removed after the first sprint.
In series: ESLint in Practice · Part 4
Why I built Dep Beacon, a VS Code extension that keeps npm update paths, pnpm catalog context, and OSV security warnings inside manifests.
Why I built Astro Doctor: a CLI, ESLint plugin, editor extension, GitHub Action, and agent skill system for catching Astro anti-patterns early.
A practical tour of the shipped @santi020k/eslint-config-basic v2.0 release: ESLint 10, one main install, lazy frameworks, lite mode, monorepos, CLI checks, and AI standards.
In series: ESLint in Practice · Part 5
DX improvements that cannot be measured rarely survive long enough to compound. Treating them like product work changes that.
In series: The santi020k way · Part 12
How to add accessibility automation to your Playwright suite in a way that is fast enough to stay in the workflow and specific enough to actually catch problems.
In series: Building a Production Next.js App · Part 8
AI agents rerun checks constantly. Quiet logs, compact reporters, and parallel verification reduce token waste without lowering the quality bar.
In series: The santi020k way · Part 11
Posts connected by this topic in the archive.
Distinct topics across the full writing archive.
Pagination for this topic archive.