How I Built the santi020k Developer Tool Ecosystem
How Lumen, ESLint Config Basic, Quality, Astro Doctor, Commitprompt, Dep Beacon, OG, Theme, and Auth form one practical system for my projects.
- Developer experience
- Developer tools
16 artículos
Herramientas y prácticas para tener estándares más claros, recibir retroalimentación antes y facilitar el desarrollo diario.
Más recientes primero · Página 1 de 2
Volver al blogArtículos 1–12 de 16
How Lumen, ESLint Config Basic, Quality, Astro Doctor, Commitprompt, Dep Beacon, OG, Theme, and Auth form one practical system for my projects.
Why Zed became my editor of choice: responsive work across multiple projects, flexible AI integrations, and Dep Beacon now available as a Zed extension.
Why I separated social-image generation mechanics from project-owned visuals, then built caching, safe cleanup, worker concurrency, and CI checks around that boundary.
How I built a native CLI that coordinates existing analyzers across Rust, Swift, Android, Kotlin, JavaScript, and Astro without flattening their ecosystem-specific strengths.
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.
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.
Explore @santi020k/eslint-config-basic v2 with ESLint 10, one-package setup, lazy framework support, monorepo tooling, lite mode, and CLI checks.
Measure developer experience with cycle time, feedback speed, onboarding time, recovery time, and tooling interruptions. Start with a baseline.
Run tested Playwright and axe examples for page scans, dialog focus, and skip links, then use a keyboard checklist to review what automation cannot prove.
Temas relacionados
Los 112 temasMás allá de este tema
Sigue otro tema o vuelve al archivo completo de artículos.