STARTING POINTS
Decide before choosing a tool.
Short frameworks for naming the business task, the available information, the person responsible, and the result worth measuring.
In preparationPublic resources should do a real job.
This will be the home for practical AI starting points, field tools, and build notes I can stand behind. Each asset will explain the task it solves, what it assumes, how it was tested, and where its limits begin.
What will live here.
The resource set will stay small enough to maintain. The goal is not a giant vault. It is a clear set of materials that help an owner or builder make one useful move without guessing what the author meant.
FIELD TOOLS
Use a repeatable working path.
Practical checklists and templates that make an AI workflow easier to run, review, and hand to another person.
In preparationBUILD NOTES
See how a system was assembled.
Plain-language notes about architecture, tradeoffs, failure points, and the lessons that remain useful after a specific tool changes.
In preparationReady means usable end to end.
A public asset is ready only when someone outside the build can understand its purpose, follow the path, and recognize when it does not fit their situation.
- Name the jobState the decision, handoff, or operating task the resource is meant to improve.
- State the prerequisitesList the information, access, tools, and judgment a person needs before starting.
- Show the working pathProvide a complete example and the point where a human reviews or takes over.
- Mark the limitsRecord the tested version, known failure modes, and conditions that require a different approach.