I think this sort of thing would work better as a list of common problems that you encounter when doing iOS dev and the possible frameworks with example projects.
Having one massive Xcode project with all of these things already integrated is just begging for abuse. Novice devs who make this their goto Xcode project template and not really understand what these frameworks do are going to hurt themselves in the long run.
I have written my own version of basically all of these frameworks (except for JSONKit because JSON parsing is incredibly complex and efficiency is very important) and I am a better iOS dev now because of it.
If every time I needed to do a HTTP requeste I just included ASI I would not have learned as much as I did about network connections and iOS.
Explaining why these frameworks are useful in certain scenarios and how they work are more important in my opinion.
Also including frameworks like MapKit in a boilerplate project is just wrong. Why not add every Apple framework to the build phase so that novice devs will never by accident and an #import and get a compile error because the framework wasn't added to the project?