Three questions before a long coding-agent run

Lydia Hallie’s AI Engineer talk follows a coding session as it goes from a developer watching each step to running on its own. We asked an agent to turn three parts of the talk into a checklist we could try on our own projects.

What belongs in the project notes?

Keep

  • Constraints the code does not reveal
  • Dependencies a future edit could break

Revisit after an upgrade

  • Directions the model can infer from the repo
  • Reminders written for an older model

3:14 in the talk. Hallie uses a legacy dependency as an example. A developer can know it still matters even when the current project gives the agent few clues.

What can an allowed command do?

At approval

  • Decide whether the proposed command may start

During the run

  • Limit what the process can read, write or reach

7:16 in the talk. A test runner can start other code. Approval and the execution environment answer different questions.

How will we know it worked?

  • Pick the behavior the team needs to preserve.
  • Exercise it with a realistic example.
  • Make failure visible before the job can finish.

10:47 in the talk. For a login migration, Hallie checks an existing session. A new sign-in alone would miss a regression that signs current users out.

Source: Lydia Hallie, Rethinking Claude Code Best Practices, AI Engineer.


Make an analysis like this

This document was made with an AI agent in SmallDocs. SmallDocs turns Markdown into shareable documents with charts, diagrams, working tables and interactive explanations.

To make your own, get started with SmallDocs, set it up for your agent, and ask: “Make a SmallDoc exploring this question. Check the original sources, show the calculations, and explain it visually.” You can open a local Markdown file with sdoc your-analysis.md and ask your agent to refine it as new questions come up.

Format document
General
px
Colors
▶ Headings
▶ Blocks

Default for code blocks, blockquotes, and charts. Override individually below.

▶ Code
▶ Blockquote
▶ Charts
▶ Tables
Headers
▶ General h1–h4
em
▶ H1 h1
em
▶ H2 h2
em
▶ H3 h3
em
▶ H4 h4
em
Paragraph
em
Lists
em
em
Links
Code
Blockquote
px
em
Save as default styles
  • Requires sdocs-dev CLI
    • Install: npm link from project root
  • Saves to ~/.sdocs/styles.yaml
  • Paste the command below in your terminal

        
      
Export document

Download as PDF document

Download as Word document

Plain markdown, no styles

Markdown with YAML front matter styles

100% private Open source: verify server CLI for you & your agents: Copy install promptcurl -fsSL https://smalldocs.org/install | sh Discord GitHub For business You agree to our Terms