I'm going to suggest the obvious, but this helps in the long run.
Document, document, document.
Set up a document of coding standards.
Create a document describing your framework and approach so others can follow it.
comment you code, do this well, remember some one with little experience might have to work with the things you have done and if they understand why you did it a certain way the more likely their code will fit into the automation suite with out breaking.
Well considering what I've seen so far... it might not be that obvious.
Additionally, I'd suggest to sit down with the people involved, and discuss this project, make designs, etc. before starting to actually implement it.
This starts with naming conventions and continues with interfaces for common functions everyone might need to use. Treat it like a development project. You might also want to consider a data driven approach. But that very much depends on the application you are going to test.
Use the object oriented functionality SilkTest offers. It will make the code much more readable and scripts much easier to write.
Convenience is the first step to enslave yourself. Freedom is inconvenient.
[This message has been edited by KlausK (edited 04-09-2003).]