Direct repo inspection, commits, pushes, checks, and deployment commands.
Tech Stack / Developer Tools
Developer Tools
Repo, terminal, browser, validation, and deployment tooling used to turn ideas into shipped artifacts.
Current shape
Local and live UI checks, console checks, overflow probes, and visual review.
Small HTML/CSS pages with canonical URLs, sitemap entries, and no framework unless needed.
Why this belongs in the stack
Developer tools turn ideas into versioned, testable, reviewable artifacts.
It matters when the normal edit/test/deploy workflow changes.
What stays out
List tools because they anchor validation, shipping, or source control; not because they are fashionable.
Detailed runbooks belong in skills or repo docs, not this stack page.
How it earns a place
This layer covers tools that make changes reproducible: terminals, git/GitHub, browser checks, local scripts, package managers, and validation commands.
A dev-tool entry should connect to a real ship path: edit, run checks, inspect browser output, commit, push, or debug a failure.
It matters when the default check, browser-smoke, GitHub workflow, editor/terminal loop, or deployment command changes what proof is expected before shipping.
Concrete example
A browser smoke test belongs here because visual changes are not done until the rendered page, console state, and overflow risk have been checked rather than inferred from HTML.
What stays private
Name the tool category and the proof it enables, but keep private repo names, credentials, unpublished scripts, and local-only paths out of the public stack page.