Peeled
Suppose we have a situation where the player is in darkness, but is allowed to feel and interact with (except for examining) any large objects. In that case, we write a scope rule that puts those large objects into scope all the time, and trust the "requires light" aspect of verbs like examining to prevent the player from doing any actions that he shouldn't:
Test me with "feel floor / feel rug / eat rug / examine rug / get grape".
It is pitch dark, and you can't see a thing.
>(Testing.)
>[1] feel floor
You try feeling your way around and reach a bearskin rug.
>[2] feel rug
You grope for the bearskin rug...
It feels furry!
>[3] eat rug
That's plainly inedible.
>[4] examine rug
It is pitch dark, and you can't see a thing.
>[5] get grape
You can't see any such thing.
Sadly, because the grape is small, the player will never encounter this horror.
Alternatively, suppose we have a situation in which the player can use one command to interact with a kind of thing that isn't normally in scope. It's usually most convenient to write the "understand" rule appropriately rather than use the scope activity.
(Note that we define "inquiring about" as applying to one *visible* thing; otherwise we would be required to be able to touch the catsuit in order to inquire about it. More on this restriction may be found in the Advanced Actions chapter on the topic of visible, touchable, and carried things.)
Test me with "ask about catsuit / x catsuit".
>(Testing.)
>[1] ask about catsuit
"What can you tell me about the skintight catsuit?" you demand. Mr Steed raises his eyebrows, but does not reply.
>[2] x catsuit
You can't see any such thing.
All this said, there do arise certain complex situations when we want an activity-specific scoping.