Hi,
If it's not a completely asinine idea, I'd like to experiment with making post flop decisions based on my HUD.

For instance, if I am raised or re-raised by a villain with a VPIP of 0-15, then I'd fold TPTK and two pair, possibly even an over pair. Conversely, if I'm raised or re-raised by a VPIP of 50 or greater, then i'll call any pair, re-raise any top pair and shove with TPTK or greater.

Obviously the extreme ends of the spectrum are sort of easy to figure out, but I'm looking for perhaps a chart or something that can break it down further, like what to do vs. a 20 to 30, or a 40 to 50 or something to that effect.

I can guess at it, but I'd rather get it from someone with more knowledge than my pure imagination.

That is, provided its a good idea. If its a horrible one, then I'll just forget about it.

FWIW this is in regards to micro stakes online.

thanks

Making decisions which include information you obtain from one's HUD is good. Making post-flop decisions based solely upon hand strength and opponents' pre-flop stats is bad.

First...HUDs are just part of the equation as stated.

Second and more importantly, you should do the work yourself. The thought process to develop such a system will pay you many many buckets of gold. no joke.

Great second point from KS above.
Although there is certainly a correlation between pre-flop and post-flop tendencies (loose passives pre tend to be caling stations post, for example) if you want to use HUD stats to make decisions based on statistical facts, then you need to look at particular stats. For example, when a someone raises your flop bet (and you have TPTK), look at their "raise c-bet %" stat, not their PFR stat. Generally speaking, a nitty set-miner with pre-flop stats like 11/4 is only raising on the flop when he hits his set (hence the name "nitty set-miner"). A laggier player will raise more often with flush draws and OESDs, and sometimes with complete airballs or bottom pair. These two types of players will often have completely different "raise flop c-bet %" stats, so that is the stat you need to look at.

2 pair>overpair