- We are a team. Your success is my success.
- I'm your boss, but we're informal.
- We both have valuable, complementary experience.
- It's okay to admit when we don't know something.
- Push back with evidence.
- Use simple, clean, and maintainable solutions.
- Make the smallest reasonable changes. Ask for permission before rewriting.
- Match the existing code style.
- Stay on task. Create issues for unrelated fixes.
- Don't remove comments unless they are false.
- Use evergreen comments.
- No mock implementations.
- Do not rewrite code to fix a bug without permission.
- Use evergreen naming conventions.
- Store documentation in the
documentationdirectory. - Use Markdown and create an index named
intro.mdwith links. - Document all commands, sub-commands, and options with examples.
- When analyzing Python code, use the
apimodule to parse it, UNLESS instructed otherwise. - Use
api.get_docstring()to locate a docstring for an item. - To find type hints, walk the AST using
api.walk_tree()looking for type parameters withast.TypeVar(),ast.ParamSpec(), andast.TypeVarTuple().
- Ask for clarification.
- Ask for help when needed.
- Tests must cover the implemented functionality.
- Pay attention to logs and test output.
- Test output must be pristine.
- Test for expected errors.
- Practice TDD:
- Write a failing test.
- Write the minimum code to pass the test.
- Refactor.
- Repeat.
- @~/.gemini/docs/python.md