Enhance droid documentation and coding rules:

- Update coder and reviewer descriptions to clarify subagent roles.
- Improve coding rules for modularity and project structure.
- Add new semantic code search skill documentation for ColGREP.
- Introduce rules skill for accessing project coding conventions.

.factory/rules/code.md

@@ -3,4 +3,4 @@
 1. Never use emojis in the code. Use ASCII characters as much as possible.
 Kaomojis are also fine to make it fun but do not use emojis.
 
-2. Keep files under 300 lines. Create nested folders/files for modularity.
+2. Keep files under 300 lines. Create nested folders/files for modularity. If someone runs `tree --gitignore` they should see a well structured project. And it should be self explanatory about where to find what.

.factory/rules/python.md

@@ -13,6 +13,7 @@ Do not try to use comments to work around the linter (ruff) or type checker (ty)
 Chances are Makefiles are present read and use them. If doesn't exist then create it.
 Run formatting after done with changes.
 Never use `sys.path` or `pathlib` for resources. Use `importlib.resources`.
+Fetch version from pyproject.toml using `importlib.metadata`.
 
 ## Some rules to configure in ruff