- avoid "in place" mates, make the part then add it to the assy and mate it

- never use incontext on library / catalog items or parts that will be reused in other assemblies

- avoid incontext relationships between parts that may move relative to one another (dynamic assembly motion)

- avoid combining incontext relations with assembly configs that change the geometry the incontext refers to

- avoid using the "multiple context" switch

- avoid combining incontext with flexible subassemblies (for both relative motion and configs reasons)

- for complex incontext scenarios, use assembly layout sketches, an envelope or a single part used only for layout sketches to drive the parts in the assembly.

- always be concious of the circular reference problem.  If you don't use the layout part/sketch scenario above, then organize your assembly tree so the driving parts are clearly identified and at the top of the tree.  Make sure that the relationships always go up the tree.

- avoid making incontext relations to a part that already has incontext relations

- make good use of subassemblies to organize and simplify incontext relations

- incontext relations are best used to automate change.

- use Lock relations rather than Break.

- do not use Break wholesale unless to solve or avoid a problem (I think it is not a good idea to delete/break incontext relations at the end of a project as a matter of policy - you can acheive the same broken associativity with a Parasolid round trip)

- remember that incontext sketch planes are sometimes overlooked when manually removing incontext features

- be very careful about renaming, save as or save as copy when parts are incontext.

- use Display/Delete relations to find all the incontext references in a sketch

- use List external references to find the assembly (or part for mirror/base/split) where the the incontext reference was made

- do not use incontext relations when assembly mates are more appropriate (to position a part)

- don't get carried away with incontext relations, if every feature is incontext, maybe you should examine your approach

- if someone else is going to use your assembly, try to make the relationships simple to understand or include design intent documentation (notes, custom props, sketch/feature names)