That approach seems destined to frustrate you in the long run. I usually find it best to try to learn about the tools involved and what options are available. Searching can be useful to find new tools, but then I would suggest switching to learning about the tool itself instead of trying to apply the example(s) found in the search. You have already seen how that has led you astray in the development of this script: In the post you originally found, the writer said that they did not think there was a way to search for different names without using a regex”that was not true (and probably never has been true, I would be very surprised if the regexp option predated the OR option in find’s history).
In the case of find there are many options available for doing a variety of types of searches. The parameters to find are used to write boolean (true/false) expressions. Using the implicit AND, the -o OR, the ! NOT, and the parenthesis you can create very complex searches. It is a (small) language unto itself and it would be worth it to study the manpage if you plan on using it much more.
Both of those are covered in the manpage. The thing about the double backslash, “\”, is that you want find to get an actual parenthesis, “(”, in its argument list. But parentheses are interpreted specially in the shell, so you have to follow the shell’s quoting/escaping rules. To make the shell pass a parenthesis to find, you can add a backslash before it. Then you need to represent “(” in an AppleScript inline string value. AppleScript’s string quoting rules say that backslash is special and needs to be escaped if you want one in an inline string value, so the AppleScript code becomes “\(”. If instead you decide to use single quoting for the shell instead of a backslash, then no special escaping is needed at the AppleScript level and you end up with “‘(’” (single quote, parenthesis, single quote).
I ran across a couple of shell tutorials recently, they may be worth reading: UNIX SHELL Quote Tutorial and Bourne Shell Tutorial. I have only skimmed over them, but they seem reasonable to me. Edit: When these tutorials were converted from “roff” to HTML, it seems that the backslashes were lost. This makes many of the parts about quoting a bit confusing if you do not already know where the backslashes should go. Also, in several places the Bourne shell material is targeted at the version of sh from Solaris, which is often considered to be a bit buggy. The tutorial demonstrates some of these bugs but does not mention that most modern version of the Bourne shell (bash, dash, probably zsh, too) do things more sanely.
Not a bad idea. There you would find more people that know the general tools, so you would probably get faster responses. Here we can all assume you are using Mac OS X and not bother with what might be slightly different if you were running on some other Unix-type system. We can also suggest tools that are specific to Mac OS X if there is a good match to your problem.
For me, the specific examples helped the most. Sometimes we say “a picture is worth a thousand words”, and that applied in this case to the examples. A full and complete English language description of what you wanted would have been fairly long and complicated, but a full example could be as short as 4-6 short lines.
but thanks in advance. If one doesn’t understand my question, I’ll try to explain it a bit more clearly without using to much “name”. 
No need for -prune because if you use that you need to know a folder. In this case the folder I’m talking about is returned of the script and is unknown at the beginning. It’s all in the * I think.