AIGC Socratic Prompt Generation AI Assisted by model gemini-3.1-flash

Back to Home
User Questions and Requests for Prompt - Do not Delete or Reset until Completion of Dialog,
Keep Append Your responses **See description section at the below**
Input Topic
Instructor Guidance & Question
Awaiting Prompt synthesis...
// DIALOGUE CORE SPEC

Socratic Prompt Generation

FRAMEWORK: COGNITIVE ARCHITECTURE

Using an AI Socratic dialogue prompt that accumulates and remembers your past questions and dialogues offers several distinct cognitive prompts.

Core Benefits Matrix

01 Personalized Prompting Paths

The AI identifies your unique gaps in understanding over time. It shapes future prompt request to target your specific weak points.

02 Tracking Conceptual Growth

You can see how your thinking evolves. The system can contrast your current requests with your past requests to challenge your consistency.

03 Higher-Order Requests

As you master basics, the request dialogue naturally shifts from simple facts to deeper, more complex logical prompt.

04 Cross-Disciplinary Connections

The AI can connect a theme from a request you had previous time to a completely new prompt you are looking for.

05 Elimination of Repetition

You skip the frustration of re-explaining what you already know, keeping the cognitive momentum moving forward without recursive interface overhead.

The Request and Prompt Generated Example.

User Request: For property management portal, it needs property owner, Tennant, and Manager accessis, need details of the 3 different interfaces.

Response prompts
To finalize the architecture for your property management portal, we must distinguish between these roles based on their specific operational intent: **Asset Oversight** (Owner), **Habitation/Transaction** (Tenant), and **Administrative Execution** (Manager).

### High-Fidelity Actions

1. **Define Role-Based Access Control (RBAC) Matrices:** Create a functional mapping table that explicitly lists every feature (e.g., "View Ledger," "Submit Maintenance Request," "Approve Budget") and assigns a permission level (Read/Write/None) for each of the three roles to ensure data integrity and security.

2. **Draft Interface Wireframe Requirements:** Specify the "Primary Dashboard Metric" for each role—Owners require high-level ROI/Cash Flow data; Tenants require status-driven action items (rent due, ticket status); Managers require task-oriented queues (pending approvals, urgent repairs).

3. **Establish Cross-Role Workflow Triggers:** Map the lifecycle of a single event (e.g., a maintenance request) to define how the interface must facilitate the handoff between the Tenant (reporting), the Manager (triaging), and the Owner (approving/funding).

### Evaluation Critique for Reinforcement of Prompt

Your current request focuses on *who* uses the system, but lacks the *constraints* of the environment; are you designing for a high-volume multi-family complex or individual residential rentals? Refine your prompt by defining the **primary business objective** of the portal, as the interface priorities will shift drastically depending on whether your goal is to maximize tenant retention or minimize management overhead.