Act as a senior no-code developer and AI workflow automation specialist. Task: Client intake questionnaire.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to client intake questionnaire and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Problem and outcome framing.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to problem and outcome framing and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Process inventory.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to process inventory and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: No-code feasibility review.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to no-code feasibility review and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Requirements specification.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to requirements specification and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Stakeholder map.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to stakeholder map and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Scope and exclusions.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to scope and exclusions and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Success metrics.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to success metrics and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Tool selection matrix.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to tool selection matrix and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Implementation roadmap.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to implementation roadmap and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: App specification.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to app specification and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Database types and fields.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to database types and fields and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Privacy rules review.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to privacy rules review and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Page architecture.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to page architecture and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Reusable elements.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to reusable elements and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Workflow logic.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to workflow logic and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Authentication plan.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to authentication plan and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Search and filtering.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to search and filtering and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Responsive QA.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to responsive qa and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Bubble launch checklist.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to bubble launch checklist and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Site architecture.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to site architecture and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: CMS collection schema.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to cms collection schema and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Responsive layout brief.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to responsive layout brief and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Component naming.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to component naming and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: CMS template plan.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to cms template plan and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Form handling workflow.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to form handling workflow and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: SEO implementation audit.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to seo implementation audit and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Accessibility review.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to accessibility review and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Performance audit.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to performance audit and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Client editor guide.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to client editor guide and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Base schema design.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to base schema design and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Field type review.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to field type review and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Relations and linked records.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to relations and linked records and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Views and filters.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to views and filters and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Formula design.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to formula design and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Data import mapping.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to data import mapping and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Duplicate prevention.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to duplicate prevention and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Permissions matrix.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to permissions matrix and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Automation triggers.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to automation triggers and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Data quality audit.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to data quality audit and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Workspace architecture.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to workspace architecture and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Project tracking database.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to project tracking database and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Knowledge base design.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to knowledge base design and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Team wiki template.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to team wiki template and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Meeting notes system.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to meeting notes system and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Client portal plan.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to client portal plan and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Relations and rollups.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to relations and rollups and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Status reporting view.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to status reporting view and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Permissions audit.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to permissions audit and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Workspace onboarding.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to workspace onboarding and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Trigger action blueprint.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to trigger action blueprint and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Zapier workflow design.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to zapier workflow design and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Make scenario design.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to make scenario design and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Field mapping.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to field mapping and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Router and branch logic.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to router and branch logic and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Conditional filter design.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to conditional filter design and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Deduplication logic.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to deduplication logic and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Rate limit strategy.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to rate limit strategy and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Retry and error handling.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to retry and error handling and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Automation test matrix.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to automation test matrix and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: n8n workflow architecture.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to n8n workflow architecture and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Node selection.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to node selection and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Webhook input validation.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to webhook input validation and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: HTTP request configuration.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to http request configuration and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Expression mapping.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to expression mapping and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: AI node orchestration.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to ai node orchestration and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Batch processing.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to batch processing and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Error workflow.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to error workflow and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Credential security review.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to credential security review and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Self-hosting checklist.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to self-hosting checklist and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Integration requirements.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to integration requirements and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: API documentation digest.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to api documentation digest and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Authentication selection.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to authentication selection and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Webhook payload schema.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to webhook payload schema and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Pagination strategy.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to pagination strategy and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Idempotency plan.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to idempotency plan and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Error code mapping.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to error code mapping and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: JSON transform mapping.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to json transform mapping and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Integration contract tests.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to integration contract tests and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Integration runbook.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to integration runbook and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: AI use case screening.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to ai use case screening and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Prompt specification.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to prompt specification and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Structured JSON output.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to structured json output and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Retrieval workflow.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to retrieval workflow and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Human approval checkpoints.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to human approval checkpoints and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Sensitive data controls.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to sensitive data controls and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Fallback and escalation.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to fallback and escalation and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Output evaluation rubric.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to output evaluation rubric and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Cost and latency budget.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to cost and latency budget and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: AI feature acceptance tests.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to ai feature acceptance tests and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: End-to-end test plan.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to end-to-end test plan and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: User acceptance scenarios.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to user acceptance scenarios and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Permission boundary tests.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to permission boundary tests and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Input validation checklist.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to input validation checklist and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Failure injection plan.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to failure injection plan and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Monitoring dashboard.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to monitoring dashboard and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Backup and recovery plan.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to backup and recovery plan and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Change management checklist.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to change management checklist and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Accessibility test plan.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to accessibility test plan and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Release go no-go review.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to release go no-go review and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: SOP authoring.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to sop authoring and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Training walkthrough.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to training walkthrough and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Handover checklist.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to handover checklist and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Change request template.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to change request template and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Maintenance agreement outline.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to maintenance agreement outline and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Issue intake form.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to issue intake form and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Incident status update.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to incident status update and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Monthly performance report.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to monthly performance report and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Cost optimization review.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to cost optimization review and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Offboarding and ownership transfer.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to offboarding and ownership transfer and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Portfolio case study.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to portfolio case study and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Demo project concept.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to demo project concept and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Before after workflow story.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to before after workflow story and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Technical architecture explanation.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to technical architecture explanation and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Freelance service packages.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to freelance service packages and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Proposal tailored to brief.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to proposal tailored to brief and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Discovery call agenda.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to discovery call agenda and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Estimate assumptions.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to estimate assumptions and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: Remote interview practice.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to remote interview practice and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.

Act as a senior no-code developer and AI workflow automation specialist. Task: 30-day skill development plan.

PROJECT CONTEXT
Business / client: [CLIENT_AND_INDUSTRY]
Current workflow or product: [CURRENT_STATE]
Target users and permissions: [USERS_AND_ROLES]
Tools and platforms: [TOOLS e.g. Bubble/Webflow/Airtable/Notion/Zapier/Make/n8n]
Available data and example records (redacted): [DATA_SCHEMA_OR_SAMPLES]
Constraints (budget, timeline, privacy, integrations): [CONSTRAINTS]
Desired outcome: [MEASURABLE_GOAL]

INSTRUCTIONS
1. Tailor the solution specifically to 30-day skill development plan and distinguish confirmed facts from assumptions.
2. Ask up to five blocking clarification questions only if needed; otherwise state reasonable assumptions.
3. Produce a practical step-by-step plan with exact fields, screens, nodes, rules or settings where relevant; explain platform-specific variations and do not invent unavailable features.
4. Include a small realistic example, edge cases, permissions/data-protection checks, failure handling, and a validation/test checklist.
5. Identify human approvals for irreversible actions, customer communications, data deletion and AI-generated decisions. Never request or expose credentials.
6. Finish with expected deliverables, acceptance criteria, dependencies and next action.

OUTPUT FORMAT
A. Objective and assumptions; B. Recommended design; C. Implementation steps; D. Example/configuration; E. QA/security checklist; F. Delivery and handoff.
If current vendor capabilities or pricing matter, mark them for verification against official documentation rather than guessing.