principles-of-coding-with-geb
Principles of Coding
Do not rely on descriptions of the implementation
Docs may lie; implementations do not.
When working, you may use only the following four types of information as authoritative:
- The implemented source code
- Coding conventions or guidelines that do not describe the implementation
- Any content outside descriptions of the implementation
- Your prior knowledge and information outside this repository (e.g., public documentation)
Documents that describe the implementation—including specifications, design docs, and implementation descriptions—may be used only as guidance to help you understand the implementation or guidelines. They must never be treated as authoritative.
After reading any implementation description, you must verify that the actual implementation matches the description. If it does not, treat the description as false and ignore it.
More from geb-algebra/geb-agent-skills
react-router-route-module-patterns
How to implement Route Modules for React Router. Use when you implement any page or component using React Router Framework Mode.
5ui-components
Implement React components in maintainable, effortless and consistent way. Use when you implement React components for your application.
4domain-driven-development
Implement the entire application with domain-driven development (DDD) architecture. Use when you design and implement the overall architecture of the application, define domain objects and their relationships, implement business logic in services, and create APIs and UI components for the domain objects and logic.
3impl-pad
Implement following your Pad (a markdown file named `pad.md`). Use When the user instructs you to implement something, specifying pad.md.
1write-pad
Write your Pad (a markdown file named `pad.md` in this repository). Use when the user instructs you to write a pad.md.
1