mberman84

OpenClaw Prompts - Build Your Own AI Assistant

Prompts to recreate each piece of the OpenClaw system. Use these with any AI coding assistant.

---

1. Personal CRM "Build a personal CRM that automatically scans my Gmail and Google Calendar to discover contacts from the past year. Store them in a SQLite database with vector embeddings so I can query in natural language ('who do I know at NVIDIA?' or 'who haven't I talked to in a while?'). Auto-filter noise senders like marketing emails and newsletters. Build profiles for each contact with their company, role, how I know them, and our interaction history. Add relationship health scores that flag stale relationships, follow-up reminders I can create, snooze, or mark done, and duplicate contact detection with merge suggestions. Link relevant documents from Box to contacts so when I look up a person, I also see related docs."

2. Meeting Action Items (Fathom)

mberman84

# OpenClaw Prompts - Build Your Own AI Assistant

Prompts to recreate each piece of the OpenClaw system. Use these with any AI coding assistant.

---

**1. Personal CRM**
"Build a personal CRM that automatically scans my Gmail and Google Calendar to discover contacts from the past year. Store them in a SQLite database with vector embeddings so I can query in natural language ('who do I know at NVIDIA?' or 'who haven't I talked to in a while?'). Auto-filter noise senders like marketing emails and newsletters. Build profiles for each contact with their company, role, how I know them, and our interaction history. Add relationship health scores that flag stale relationships, follow-up reminders I can create, snooze, or mark done, and duplicate contact detection with merge suggestions. Link relevant documents from Box to contacts so when I look up a person, I also see related docs."

**2. Meeting Action Items (Fathom)**

mberman84

# OpenClaw Implementation Prompts

Each prompt below is a self-contained brief you can hand to an AI coding assistant (or use as a project spec) to build that use case from scratch. Adapt the specific services to whatever you already use — the patterns are what matter.

---

## 1) Personal CRM Intelligence

```
Build me a personal CRM system that automatically tracks everyone I interact with, with smart filtering so it only adds real people — not newsletters, bots, or cold outreach.

mberman84

{"conversationTurns": [{"prompt": {"content": [{"text": "I'll be arriving late tomorrow night around 11pm. What's your check-in process and will there still be someone at the desk to help me?"}]}, "referenceResponses": [{"content": [{"text": "Yes, our front desk is staffed 24 hours to assist with check-in regardless of your arrival time. According to our check-in policy, you'll need to communicate with our staff upon arrival to complete the check-in process. You'll be required to provide your personal information including name and contact details, and if you're a foreign national, additional information like passport number and date of entry into the country. We may request identification documents to verify this information. You might also be asked to provide a security deposit. Once check-in is complete, we'll assign and inform you of your room number."}]}]}]}
{"conversationTurns": [{"prompt": {"content": [{"text": "We need to cancel our reservation due to a family emergency. We were supposed to arrive tom

mberman84

[
    {
        "AllowedHeaders": [
            "*"
        ],
        "AllowedMethods": [
            "GET",
            "PUT",
            "POST",
            "DELETE"

mberman84

total 0
drwxr-xr-x@ 7 matthewberman  admin   224B Mar 21 22:44 app-mlx-generate-mac-arm64@25
drwxr-xr-x@ 8 matthewberman  admin   256B Mar 21 22:45 app-mlx-generate-mac-arm64@26
drwxr-xr-x@ 8 matthewberman  admin   256B Apr 18 10:30 app-mlx-generate-mac-arm64@32
drwxr-xr-x@ 7 matthewberman  admin   224B Apr 29 09:22 app-mlx-generate-mac-arm64@34
drwxr-xr-x@ 8 matthewberman  admin   256B Apr 29 09:22 app-mlx-generate-mac-arm64@36
drwxr-xr-x@ 7 matthewberman  admin   224B Mar 13 12:32 cpython3.11-mac-arm64@5
drwxr-xr-x@ 7 matthewberman  admin   224B Mar 21 22:45 cpython3.11-mac-arm64@6
drwxr-xr-x@ 7 matthewberman  admin   224B Apr 29 09:08 cpython3.11-mac-arm64@8
drwxr-xr-x@ 8 matthewberman  admin   256B Apr 18 10:30 framework-unified-mac-arm64@10

mberman84

TBBmalloc: skip allocation functions replacement in ucrtbase.dll: unknown prologue for function _msize
[SDN-INF]: Launch Time: 0.00s
[SDN-INF]: UnregNode Time: 0.00s
register_class(...):
Warning: 'MLTWords_UL_UIList' doesn't have upper case alpha-numeric prefix
register_class(...):
Warning: 'MLTText_UL_UIList' doesn't have upper case alpha-numeric prefix
[SDN-WRN]: Parsing Node Start
[SDN-WRN]: Parsing Node Finished!
[SDN-INF]: ParseNode Time: 0.63s

mberman84

Write a complete HTML/JavaScript program using Three.js that renders a fully interactive Rubik's Cube simulation of any size up to 20x20x20. The user should be able to specify the cube size dynamically (e.g., via an input or a variable), and the cube should be constructed accordingly with proper color-coded faces (standard Rubik's Cube colors: white, yellow, red, orange, blue, green).
Include camera controls for rotating the view, and allow for basic user interaction such as rotating layers of the cube via mouse or UI buttons.
Additionally, implement a "Solve" button that, when clicked, animates the cube being solved step-by-step visually. You can use a simplified solving algorithm (you do not need to match real Rubik’s solving logic) — the goal is just to animate the cube returning to its original solved state, one move at a time, with clear transitions.
Requirements:
Use Three.js for all 3D rendering.


Cube size should be adjustable up to 20x20x20.

mberman84

* Always check for a PRD (Product Requirements Document) before starting a new task and follow it closely
* Look for comprehensive project documentation to understand requirements before making changes
* Focus only on code areas relevant to the assigned task
* Prefer iterating on existing code rather than creating new solutions
* Keep solutions simple and avoid introducing unnecessary complexity
* If you run into issues that take multiple iterations to fix. After you fix it, write up a description of the problem and how we fixed it and store it in a folder called "fixes", in an individual .md file with the name of the issue. Only do this for major issues and solutions.
* For issues that are taking multiple iterations to fix, check the fixes folder for previous fixes and see if the same issue has been fixed before.
* Keep a running list of patterns and technology used in the README.md file
* Reference the README.md file for patterns and technology used in the project
* If you run into the same persistent error

mberman84

**Project Approach**

* Always check for a PRD (Product Requirements Document) before starting a new task and follow it closely
* Look for comprehensive project documentation to understand requirements before making changes
* Focus only on code areas relevant to the assigned task
* Prefer iterating on existing code rather than creating new solutions
* Keep solutions simple and avoid introducing unnecessary complexity

**Code Quality**