| 12345678910111213 |
- category,when_needed,what_to_define,why_critical
- naming_patterns,Any technology with named entities,How things are named (format/case/structure),Agents will create different names for same concept
- structure_patterns,Any technology with organization,How things are organized (folders/modules/layers),Agents will put things in different places
- format_patterns,Any technology with data exchange,How data is formatted (JSON/XML/responses),Agents will use incompatible formats
- communication_patterns,Any technology with inter-component communication,How components talk (protocols/events/messages),Agents will use different communication methods
- lifecycle_patterns,Any technology with state or flow,How state changes and flows work,Agents will handle state transitions differently
- location_patterns,Any technology with storage or routing,Where things go (URLs/paths/storage),Agents will put things in different locations
- consistency_patterns,Always,Cross-cutting concerns (dates/errors/logs),Every agent will do these differently
- # PRINCIPLE FOR LLM:
- # Any time multiple agents might make the SAME decision DIFFERENTLY, that's a pattern to capture.
- # Think about: What could an agent encounter where they'd have to guess?
- # If they'd guess, define the pattern. If it's obvious from the tech choice, skip it.
|
