Cloud Parts

Developer tools

The editors, agents and toolchains code is written and checked with.

7 concepts · 29 technologies

  1. Editors and terminals6 technologiesThe editor where code is written and the terminal where it runs: two old tools that now reach language servers, debuggers and coding agents through open protocols.
  2. AI coding agents14 technologiesA language model in a loop with tools: it reads files, runs commands and edits code, sees each result, and decides the next step until the task is done.
  3. Package managers3 technologiesTools that choose versions for a project’s dependencies, record the exact choice in a lockfile and install that same set on every machine.
  4. Linters, formatters and type checkers5 technologiesTools that read source code without running it: linters flag likely bugs, formatters reprint the layout, and type checkers check that values have the types the code claims.
  5. Automated testing4 technologiesCode that checks other code: a runner finds the tests, runs them and reports what failed, so every change is checked in seconds instead of by hand.
  6. Bundlers and dev servers3 technologiesFollow every `import` from an entry file to build a module graph, serve it quickly while you code, and pack it into a few small files for production.
  7. Documentation sites1 technologyDocs written as Markdown files in a repository, built into a searchable website on every merge, with API reference generated from the API’s own description and plain-text copies for AI agents.

Technologies

Grouped by the concept each one mainly implements

Worth exploring

All resources →
Video· August 2025Advanced Context Engineering for AgentsDex Horthy (HumanLayer), YC Root AccessA talk on getting coding agents to work in large, existing codebases by keeping their context small and correct: split work into research, plan and implement, compact each step into a Markdown file, keep context use around 40–60%, and spend human review on the research and plan rather than every line of code. Summarised here from the written version in HumanLayer’s GitHub repository, which also notes where the approach failed; HumanLayer builds tools for this workflow.