Function Deployment & Validation Flow:
When deploying cloud functions with recognized lifecycle hook names (e.g., beforeCreate, beforeSignin), the system should:

Detect Blocking Function Patterns
Check if the deployed function's name matches known blocking trigger conventions.

Assignment Validation
Verify whether the detected function is registered as a blocking trigger in the system configuration.

Interactive Guidance
If unassigned, display CLI prompt:
"Seems like you want to deploy a 'Blocking' function named <FUNCTION_NAME> but no blocking trigger is assigned. Would you like to configure this function now? (y/N)"

Key Function Patterns:
```
beforeCreate | beforeSignin | afterSignout | customBeforeHook

(Additional supported hooks)

Why This Matters:
Proactively addresses common configuration gaps through contextual prompts, reducing deployment errors and cognitive load for developers while maintaining automation compatibility.