Inferential guide

Where a practice acts when an agent writes the code: what the agent reads before it acts. One cell of Böckeler's grid.

Examples

  • Principles Böckeler
  • Cross-functional requirements Böckeler
  • Rules Böckeler
  • Reference docs Böckeler
  • How-tos Böckeler
  • Coding conventions in AGENTS.md or a skill Böckeler
  • A spec and a plan, approved by a person before the work starts
  • Architecture named in the literature's words, such as DDD, hexagonal or MVVM, in prompts and skills

The ones marked Böckeler are from Harness engineering for coding agent users; the others are added by this library.

Practices that act here

  • Domain-driven design: The code is shaped on a model of the business, written in the words its experts use, and kept apart from the technical concerns around it.
  • Hexagonal architecture (ports and adapters): The application talks to the outside only through ports, each served by an adapter, so its core depends on nothing outside it.
  • Make illegal states unrepresentable: Types are shaped so that a state the program must never reach cannot be written, and the compiler refuses it.
  • Model-View-ViewModel (MVVM): A view binds to a view model that holds its state and commands, so the interface's logic can be tested without the interface.
+ Propose a practice