updated MCP mermaid diagram to show confirmation

added prompt engineering slide

TO-DO. start on demo slides and notes
This commit is contained in:
2026-01-19 18:56:19 +11:00
parent 5791a2261d
commit a4d9138f01
3 changed files with 27 additions and 4 deletions

View File

@@ -42,7 +42,7 @@ What is MCP?
<!-- new_line -->
<!-- alignment: center -->
<!-- font_size: 2 -->
**MCP gives tools to AI**
MCP gives tools to AI
===
![image](robot.png)
<!-- no_footer -->
@@ -123,9 +123,11 @@ sequenceDiagram
LLM->>ArgoCD: Get GitOps application
LLM->>Git: Get Git repo
LLM->>LLM: Plan fix
LLM->>You: Here is the plan. Requesting Approval
You->>LLM: Approved
LLM->>Git: Push fix to Git
LLM->>OCP: Verify change applied
LLM->>You: The issue was X. I resolved by doing Y
LLM->>You: Applied Succesfully
```
<!-- pause -->
<!-- column: 1 -->
@@ -135,6 +137,9 @@ sequenceDiagram
<!-- new_line -->
<!-- new_line -->
<!-- new_line -->
<!-- new_line -->
<!-- new_line -->
<!-- new_line -->
![image:width:100%](homerspin.gif)
@@ -176,14 +181,32 @@ Tools for the demo
<!-- new_line -->
* `argocd-mcp-server` - ArgoCD (aka Openshift GitOps) application management
<!-- new_line -->
* `minio-mcp-server` - S3-Compatible Object storage operations
<!-- no_footer -->
<!-- speaker_note: Explain the tools in the wider context -->
<!-- speaker_note: openshift - complete CRUD access -->
<!-- speaker_note: gitea - ability to read and commit, create repos etc. -->
<!-- speaker_note: ArgoCD - add and keep deployments in a specified state -->
<!-- speaker_note: MinIO - self-hosted S3 -->
<!-- end_slide -->
<!-- font_size: 4 -->
Prompt Engineering
===
<!-- font_size: 2 -->
Intent vs. Instruction
===
<!-- font_size: 2 -->
![image:width:100%](table.png)
<!-- pause -->
<!-- new_line -->
<!-- new_line -->
<!-- font_size: 2 -->
Ambiguity is the enemy of automation. If you dont define safe… the AI will.
<!-- end_slide -->