Francis
I'm not being 'funny' here - but if the information given in the Quest help isn't enough for you to read up on how to make libraries for Quest, then you probably don't have enough coding experience to succeed (as yet).
We all have to start somewhere and Alex does give a trivial little example in the Quest manual. Read the section, actually MAKE the library as Alex suggests and once you get that working, you'll have the groundwork in place to develop your library making skills... take it slow and don't try to run before you can walk.
MadbRiTs golden rule #1 - plan it on paper before you write a line of code!
My "typelib.qlb" (the sixth or seventh Quest lib I've written) was developed from something originally written to suit my particular game making plans (all of my output is non-violent being targeted at a specific audience) and is offered to anyone who has similar needs. Because I-F is such a diverse thing it is unlikely any one library will ever cover all requirements, even to try to do so it would make a huge and unwieldy lib that would (probably) be a pain to use!
Keep your targets modest, especially at first.
I've no desire/intention to build 'combat' routines into typelib - I think CW is covering the bases with that in his 'RPG' library. I'm adding more NPC interaction (talking to them etc) to typelib because that's what I need
Don't re-invent the wheel!
I also don't plan a multi-player version of typelib - I don't have an audience for multi player RPG's and I don't play them myself...
Stick with what you know!
What I probably will add to typelib (because it already exists I just haven't put a QDK interface on it yet) is my 'shopkeeper' module which deals with money and buying and selling things.
I've also got a 'bartering' module - but I doubt that is general purpose enough to gum up typelib with it.
Just because you CAN do it doesn't mean you SHOULD do it...
Al