OOP
OOP sits in a first job task. Riya’s job is OOP on Riya's board. Write that first.
For OOP, a .php page is in play. Don’t blame it until you have traced OOP on Riya's board.
Without OOP, a first job task gets messy and OOP on Riya's board is hard to trust.
Use OOP when OOP on Riya's board must stay clear. If a simpler PHP step works, use that instead.
If OOP on Riya's board breaks under OOP, check only reciting the name of OOP first.
OOP is not a lonely heading. Riya ties it to OOP on Riya's board.
Close OOP with — “If I skip it, OOP on Riya's board goes wrong like this: only reciting the name of OOP.”
Say OOP in one breath, then one OOP step Riya can write from memory, then only reciting the name of OOP.