myceliumail 1.0.3 → 1.0.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.github/workflows/publish.yml +108 -0
- package/CHANGELOG.md +85 -0
- package/README.md +295 -162
- package/mcp-server/package-lock.json +3 -4
- package/mcp-server/package.json +6 -5
- package/package.json +11 -2
- package/COMPLETE.md +0 -51
- package/MYCELIUMAIL_STARTER_KIT.md +0 -603
- package/NEXT_STEPS.md +0 -96
- package/docs/20251215_Treebird-Ecosystem_Knowledge-Base_v2.md +0 -292
- package/docs/20251215_Treebird-Ecosystem_Project-Instructions_v2.md +0 -176
- package/docs/AGENT_DELEGATION_WORKFLOW.md +0 -453
- package/docs/ANNOUNCEMENT_DRAFTS.md +0 -55
- package/docs/DASHBOARD_AGENT_HANDOFF.md +0 -429
- package/docs/DASHBOARD_AGENT_PROMPT.md +0 -32
- package/docs/DASHBOARD_BUILD_ROADMAP.md +0 -61
- package/docs/MCP_PUBLISHING_ROADMAP.md +0 -113
- package/docs/SSAN_MESSAGES_SUMMARY.md +0 -92
- package/docs/STORAGE_ARCHITECTURE.md +0 -114
|
@@ -1,453 +0,0 @@
|
|
|
1
|
-
# Agent Delegation Workflow - Meta Documentation
|
|
2
|
-
|
|
3
|
-
> **How to create handoff packages for delegating work to fresh agents**
|
|
4
|
-
|
|
5
|
-
This documents the workflow used to create the Myceliumail Dashboard handoff package (Dec 15, 2025).
|
|
6
|
-
|
|
7
|
-
---
|
|
8
|
-
|
|
9
|
-
## The Workflow Pattern
|
|
10
|
-
|
|
11
|
-
### Step 1: Understand the Request
|
|
12
|
-
|
|
13
|
-
**User asked:** "Can you create a roadmap and everything necessary for a fresh new Gemini agent to build this?"
|
|
14
|
-
|
|
15
|
-
**What this means:**
|
|
16
|
-
- Create complete, self-contained documentation
|
|
17
|
-
- New agent should need ZERO context from this conversation
|
|
18
|
-
- Include code templates, not just descriptions
|
|
19
|
-
- Provide acceptance criteria and testing scenarios
|
|
20
|
-
|
|
21
|
-
### Step 2: Create Task Checklist
|
|
22
|
-
|
|
23
|
-
**File:** `task.md` (artifact)
|
|
24
|
-
|
|
25
|
-
```markdown
|
|
26
|
-
# Agent Handoff Package - [Feature Name]
|
|
27
|
-
|
|
28
|
-
## Documentation
|
|
29
|
-
- [ ] Create [FEATURE]_AGENT_HANDOFF.md
|
|
30
|
-
- [ ] Create [FEATURE]_BUILD_ROADMAP.md
|
|
31
|
-
- [ ] Create folder structure
|
|
32
|
-
- [ ] Add code templates
|
|
33
|
-
|
|
34
|
-
## Context Files
|
|
35
|
-
- [ ] Link to existing modules
|
|
36
|
-
- [ ] Document architecture
|
|
37
|
-
- [ ] List dependencies
|
|
38
|
-
|
|
39
|
-
## Acceptance Criteria
|
|
40
|
-
- [ ] Define success metrics
|
|
41
|
-
- [ ] List test scenarios
|
|
42
|
-
|
|
43
|
-
## Verification
|
|
44
|
-
- [ ] Self-contained
|
|
45
|
-
- [ ] No missing context
|
|
46
|
-
- [ ] Clear next steps
|
|
47
|
-
```
|
|
48
|
-
|
|
49
|
-
**Purpose:** Organize the handoff creation process
|
|
50
|
-
|
|
51
|
-
### Step 3: Create Implementation Plan
|
|
52
|
-
|
|
53
|
-
**File:** `implementation_plan.md` (artifact)
|
|
54
|
-
|
|
55
|
-
**Contents:**
|
|
56
|
-
1. **Complexity Analysis** - Time estimates, difficulty rating
|
|
57
|
-
2. **Tech Stack** - Technologies, why chosen
|
|
58
|
-
3. **Proposed Changes** - File structure, new files
|
|
59
|
-
4. **Implementation Phases** - Step-by-step breakdown
|
|
60
|
-
5. **Verification Plan** - How to test
|
|
61
|
-
|
|
62
|
-
**Key insight:** This becomes the skeleton for the agent handoff doc
|
|
63
|
-
|
|
64
|
-
### Step 4: Create Agent Handoff Brief
|
|
65
|
-
|
|
66
|
-
**File:** `docs/[FEATURE]_AGENT_HANDOFF.md`
|
|
67
|
-
|
|
68
|
-
This is the MAIN document the new agent reads. Structure:
|
|
69
|
-
|
|
70
|
-
```markdown
|
|
71
|
-
# [Feature] - Agent Handoff Brief
|
|
72
|
-
|
|
73
|
-
> For a fresh Gemini agent to build [feature]
|
|
74
|
-
|
|
75
|
-
## Your Mission
|
|
76
|
-
[One-paragraph description of what to build]
|
|
77
|
-
|
|
78
|
-
## What's Already Built (You Can Use)
|
|
79
|
-
[Table of existing modules with paths and descriptions]
|
|
80
|
-
|
|
81
|
-
## Project Structure (Create These)
|
|
82
|
-
[File tree showing what to create]
|
|
83
|
-
|
|
84
|
-
## Roadmap: Step-by-Step
|
|
85
|
-
|
|
86
|
-
### Step 1: [Phase Name] (time)
|
|
87
|
-
[Detailed instructions]
|
|
88
|
-
|
|
89
|
-
**File:** `path/to/file.ts`
|
|
90
|
-
```typescript
|
|
91
|
-
// Complete code template
|
|
92
|
-
```
|
|
93
|
-
|
|
94
|
-
**Test:** How to verify this step
|
|
95
|
-
|
|
96
|
-
### Step 2: ...
|
|
97
|
-
[Repeat for each phase]
|
|
98
|
-
|
|
99
|
-
## Acceptance Criteria
|
|
100
|
-
[Checklist of success criteria]
|
|
101
|
-
|
|
102
|
-
## Testing Scenarios
|
|
103
|
-
[Specific test cases]
|
|
104
|
-
|
|
105
|
-
## Troubleshooting
|
|
106
|
-
[Common issues and fixes]
|
|
107
|
-
|
|
108
|
-
## Resources
|
|
109
|
-
[Links to docs, existing code]
|
|
110
|
-
```
|
|
111
|
-
|
|
112
|
-
**Critical elements:**
|
|
113
|
-
- ✅ **Complete code templates** - copy-paste ready
|
|
114
|
-
- ✅ **Time estimates** for each phase
|
|
115
|
-
- ✅ **Test commands** after each step
|
|
116
|
-
- ✅ **Absolute file paths** not relative
|
|
117
|
-
- ✅ **Existing code references** with exact paths
|
|
118
|
-
|
|
119
|
-
### Step 5: Create Quick Roadmap
|
|
120
|
-
|
|
121
|
-
**File:** `docs/[FEATURE]_BUILD_ROADMAP.md`
|
|
122
|
-
|
|
123
|
-
A condensed checklist version:
|
|
124
|
-
|
|
125
|
-
```markdown
|
|
126
|
-
# [Feature] Build Roadmap
|
|
127
|
-
|
|
128
|
-
## Phase 1: Setup (15 min)
|
|
129
|
-
- [ ] Install dependencies
|
|
130
|
-
- [ ] Create directories
|
|
131
|
-
|
|
132
|
-
## Phase 2: Backend (2 hours)
|
|
133
|
-
- [ ] Create file X
|
|
134
|
-
- [ ] Test Y
|
|
135
|
-
|
|
136
|
-
...
|
|
137
|
-
|
|
138
|
-
## Time Budget
|
|
139
|
-
Setup: 15 min
|
|
140
|
-
Backend: 2 hours
|
|
141
|
-
Total: 6 hours
|
|
142
|
-
|
|
143
|
-
## Success =
|
|
144
|
-
[One-sentence success criterion]
|
|
145
|
-
```
|
|
146
|
-
|
|
147
|
-
**Purpose:** Quick reference, easy to scan
|
|
148
|
-
|
|
149
|
-
### Step 6: Create Agent Prompt
|
|
150
|
-
|
|
151
|
-
**File:** `docs/[FEATURE]_AGENT_PROMPT.md`
|
|
152
|
-
|
|
153
|
-
**The copy-paste prompt** to start a new agent:
|
|
154
|
-
|
|
155
|
-
```markdown
|
|
156
|
-
# Quick Start Prompt for Fresh Agent
|
|
157
|
-
|
|
158
|
-
**Copy-paste this to a new Gemini agent:**
|
|
159
|
-
|
|
160
|
-
---
|
|
161
|
-
|
|
162
|
-
Hi! I need you to build [feature].
|
|
163
|
-
|
|
164
|
-
**Context:**
|
|
165
|
-
- Project: /absolute/path/to/project
|
|
166
|
-
- Read this first: `docs/FEATURE_AGENT_HANDOFF.md`
|
|
167
|
-
- Follow roadmap: `docs/FEATURE_BUILD_ROADMAP.md`
|
|
168
|
-
|
|
169
|
-
**Your mission:**
|
|
170
|
-
[One paragraph]
|
|
171
|
-
|
|
172
|
-
**Key requirements:**
|
|
173
|
-
[Bullet list of 5-6 requirements]
|
|
174
|
-
|
|
175
|
-
**Time estimate:** X hours
|
|
176
|
-
|
|
177
|
-
**Acceptance criteria:** [Success description]
|
|
178
|
-
|
|
179
|
-
Start with Phase 1 in the roadmap!
|
|
180
|
-
|
|
181
|
-
---
|
|
182
|
-
```
|
|
183
|
-
|
|
184
|
-
**Purpose:** Makes delegation effortless
|
|
185
|
-
|
|
186
|
-
---
|
|
187
|
-
|
|
188
|
-
## Key Principles
|
|
189
|
-
|
|
190
|
-
### 1. Self-Contained Documentation
|
|
191
|
-
|
|
192
|
-
The new agent should NOT need:
|
|
193
|
-
- ❌ This conversation history
|
|
194
|
-
- ❌ To ask clarifying questions
|
|
195
|
-
- ❌ To search for other docs
|
|
196
|
-
- ❌ To guess file paths
|
|
197
|
-
|
|
198
|
-
The new agent SHOULD have:
|
|
199
|
-
- ✅ Complete code templates
|
|
200
|
-
- ✅ Exact file paths (absolute)
|
|
201
|
-
- ✅ All dependencies listed
|
|
202
|
-
- ✅ Test commands
|
|
203
|
-
- ✅ Success criteria
|
|
204
|
-
|
|
205
|
-
### 2. Progressive Disclosure
|
|
206
|
-
|
|
207
|
-
**Info density by document:**
|
|
208
|
-
|
|
209
|
-
| Doc | Detail Level | Purpose |
|
|
210
|
-
|-----|-------------|---------|
|
|
211
|
-
| Agent Prompt | Minimal | Start a new agent (30 sec read) |
|
|
212
|
-
| Build Roadmap | Medium | Quick checklist (2 min read) |
|
|
213
|
-
| Agent Handoff | Maximum | Complete implementation (10 min read) |
|
|
214
|
-
| Implementation Plan | Technical | For reviewing agent (5 min read) |
|
|
215
|
-
|
|
216
|
-
### 3. Code > Prose
|
|
217
|
-
|
|
218
|
-
**Bad:**
|
|
219
|
-
> "Create an API endpoint that fetches messages from storage and decrypts them if encrypted."
|
|
220
|
-
|
|
221
|
-
**Good:**
|
|
222
|
-
```typescript
|
|
223
|
-
fastify.get('/api/inbox', async (request, reply) => {
|
|
224
|
-
const messages = await storage.getInbox(agentId);
|
|
225
|
-
const keyPair = loadKeyPair(agentId);
|
|
226
|
-
// ... complete working code
|
|
227
|
-
});
|
|
228
|
-
```
|
|
229
|
-
|
|
230
|
-
**Why:** Copy-paste > interpretation errors
|
|
231
|
-
|
|
232
|
-
### 4. Testable Milestones
|
|
233
|
-
|
|
234
|
-
After each phase, agent should be able to RUN something:
|
|
235
|
-
|
|
236
|
-
```bash
|
|
237
|
-
# Step 1: ✅ Server starts
|
|
238
|
-
node src/dashboard/server.ts
|
|
239
|
-
|
|
240
|
-
# Step 2: ✅ API responds
|
|
241
|
-
curl http://localhost:3737/api/inbox
|
|
242
|
-
|
|
243
|
-
# Step 3: ✅ UI loads
|
|
244
|
-
open http://localhost:3737
|
|
245
|
-
```
|
|
246
|
-
|
|
247
|
-
---
|
|
248
|
-
|
|
249
|
-
## Templates for Startersan
|
|
250
|
-
|
|
251
|
-
### Template: Agent Handoff Brief
|
|
252
|
-
|
|
253
|
-
```markdown
|
|
254
|
-
# {FEATURE_NAME} - Agent Handoff Brief
|
|
255
|
-
|
|
256
|
-
> For a fresh Gemini agent to build {feature_description}
|
|
257
|
-
|
|
258
|
-
## Your Mission
|
|
259
|
-
{one_paragraph_mission}
|
|
260
|
-
|
|
261
|
-
## What's Already Built (You Can Use)
|
|
262
|
-
| Module | Path | What It Does |
|
|
263
|
-
|--------|------|--------------|
|
|
264
|
-
{existing_modules_table}
|
|
265
|
-
|
|
266
|
-
## Project Structure (Create These)
|
|
267
|
-
{file_tree}
|
|
268
|
-
|
|
269
|
-
## Roadmap: Step-by-Step
|
|
270
|
-
|
|
271
|
-
### Step 1: {phase_name} ({time_estimate})
|
|
272
|
-
{detailed_instructions}
|
|
273
|
-
|
|
274
|
-
**File:** `{file_path}`
|
|
275
|
-
```{language}
|
|
276
|
-
{complete_code_template}
|
|
277
|
-
```
|
|
278
|
-
|
|
279
|
-
**Test:** {test_command}
|
|
280
|
-
|
|
281
|
-
{repeat_for_each_step}
|
|
282
|
-
|
|
283
|
-
## Acceptance Criteria
|
|
284
|
-
{checklist}
|
|
285
|
-
|
|
286
|
-
## Testing Scenarios
|
|
287
|
-
{test_cases}
|
|
288
|
-
|
|
289
|
-
## Troubleshooting
|
|
290
|
-
{common_issues}
|
|
291
|
-
|
|
292
|
-
## Resources
|
|
293
|
-
{links}
|
|
294
|
-
```
|
|
295
|
-
|
|
296
|
-
### Template: Build Roadmap
|
|
297
|
-
|
|
298
|
-
```markdown
|
|
299
|
-
# {FEATURE_NAME} Build Roadmap
|
|
300
|
-
|
|
301
|
-
## Phase 1: {name} ({time})
|
|
302
|
-
- [ ] {task}
|
|
303
|
-
- [ ] {task}
|
|
304
|
-
|
|
305
|
-
## Phase 2: {name} ({time})
|
|
306
|
-
- [ ] {task}
|
|
307
|
-
|
|
308
|
-
## Time Budget
|
|
309
|
-
{phase}: {time}
|
|
310
|
-
Total: {total_time}
|
|
311
|
-
|
|
312
|
-
## Key Files to Reference
|
|
313
|
-
{existing_files}
|
|
314
|
-
|
|
315
|
-
## Success =
|
|
316
|
-
{one_sentence_success}
|
|
317
|
-
```
|
|
318
|
-
|
|
319
|
-
### Template: Agent Prompt
|
|
320
|
-
|
|
321
|
-
```markdown
|
|
322
|
-
# Quick Start Prompt for Fresh Agent
|
|
323
|
-
|
|
324
|
-
**Copy-paste this to a new Gemini agent:**
|
|
325
|
-
|
|
326
|
-
---
|
|
327
|
-
|
|
328
|
-
Hi! I need you to build {feature_name}.
|
|
329
|
-
|
|
330
|
-
**Context:**
|
|
331
|
-
- Project: {absolute_project_path}
|
|
332
|
-
- Read this first: `{handoff_doc_path}`
|
|
333
|
-
- Follow roadmap: `{roadmap_doc_path}`
|
|
334
|
-
|
|
335
|
-
**Your mission:**
|
|
336
|
-
{one_paragraph}
|
|
337
|
-
|
|
338
|
-
**Key requirements:**
|
|
339
|
-
{5_6_bullets}
|
|
340
|
-
|
|
341
|
-
**Time estimate:** {hours}
|
|
342
|
-
|
|
343
|
-
**Acceptance criteria:** {success_description}
|
|
344
|
-
|
|
345
|
-
Start with Phase 1 in the roadmap!
|
|
346
|
-
|
|
347
|
-
---
|
|
348
|
-
```
|
|
349
|
-
|
|
350
|
-
---
|
|
351
|
-
|
|
352
|
-
## Prompts Used (for Startersan)
|
|
353
|
-
|
|
354
|
-
### Initial Request Pattern
|
|
355
|
-
|
|
356
|
-
**User says:**
|
|
357
|
-
> "can you create a roadmap and everything necessary for a fresh new Gemini agent to build this?"
|
|
358
|
-
|
|
359
|
-
**Agent interprets as:**
|
|
360
|
-
1. Create self-contained documentation
|
|
361
|
-
2. Include complete code templates
|
|
362
|
-
3. Add step-by-step instructions
|
|
363
|
-
4. Provide testing/verification steps
|
|
364
|
-
5. Make it copy-paste ready for delegation
|
|
365
|
-
|
|
366
|
-
### Workflow Execution Prompts
|
|
367
|
-
|
|
368
|
-
**Internal agent prompts to self:**
|
|
369
|
-
|
|
370
|
-
1. **"Create task checklist"**
|
|
371
|
-
- Output: task.md artifact
|
|
372
|
-
- Organizes handoff creation process
|
|
373
|
-
|
|
374
|
-
2. **"Analyze complexity and create implementation plan"**
|
|
375
|
-
- Output: implementation_plan.md artifact
|
|
376
|
-
- Time estimates, phases, tech stack
|
|
377
|
-
|
|
378
|
-
3. **"Transform implementation plan into agent handoff brief"**
|
|
379
|
-
- Output: docs/FEATURE_AGENT_HANDOFF.md
|
|
380
|
-
- Add complete code templates
|
|
381
|
-
- Add absolute paths
|
|
382
|
-
- Add test commands
|
|
383
|
-
|
|
384
|
-
4. **"Create condensed roadmap checklist"**
|
|
385
|
-
- Output: docs/FEATURE_BUILD_ROADMAP.md
|
|
386
|
-
- Just phases, tasks, time budget
|
|
387
|
-
|
|
388
|
-
5. **"Create copy-paste delegation prompt"**
|
|
389
|
-
- Output: docs/FEATURE_AGENT_PROMPT.md
|
|
390
|
-
- Minimal, ready to send to new agent
|
|
391
|
-
|
|
392
|
-
---
|
|
393
|
-
|
|
394
|
-
## Quality Checklist
|
|
395
|
-
|
|
396
|
-
Before handing off to new agent, verify:
|
|
397
|
-
|
|
398
|
-
- [ ] All file paths are absolute
|
|
399
|
-
- [ ] Code templates are copy-paste ready
|
|
400
|
-
- [ ] Every step has a test command
|
|
401
|
-
- [ ] Time estimates are realistic
|
|
402
|
-
- [ ] Acceptance criteria are clear
|
|
403
|
-
- [ ] No references to "this conversation"
|
|
404
|
-
- [ ] No undefined acronyms or jargon
|
|
405
|
-
- [ ] Links to existing code are correct
|
|
406
|
-
- [ ] New agent can start immediately
|
|
407
|
-
|
|
408
|
-
---
|
|
409
|
-
|
|
410
|
-
## Example Usage in Startersan
|
|
411
|
-
|
|
412
|
-
```bash
|
|
413
|
-
# Generate agent handoff package
|
|
414
|
-
startersan delegate "build web dashboard" \
|
|
415
|
-
--feature dashboard \
|
|
416
|
-
--complexity medium \
|
|
417
|
-
--estimate "4-6 hours"
|
|
418
|
-
|
|
419
|
-
# Outputs:
|
|
420
|
-
# - DASHBOARD_AGENT_HANDOFF.md
|
|
421
|
-
# - DASHBOARD_BUILD_ROADMAP.md
|
|
422
|
-
# - DASHBOARD_AGENT_PROMPT.md
|
|
423
|
-
```
|
|
424
|
-
|
|
425
|
-
**Startersan would:**
|
|
426
|
-
1. Analyze the project structure
|
|
427
|
-
2. Identify existing modules
|
|
428
|
-
3. Generate templates with correct paths
|
|
429
|
-
4. Create phase-by-phase instructions
|
|
430
|
-
5. Add testing scenarios
|
|
431
|
-
6. Output ready-to-use delegation docs
|
|
432
|
-
|
|
433
|
-
---
|
|
434
|
-
|
|
435
|
-
## Key Insight from ssan's Messages
|
|
436
|
-
|
|
437
|
-
**From "CRITICAL: Myceliumail Migration Plan":**
|
|
438
|
-
|
|
439
|
-
The delegation workflow should support **iterative development**:
|
|
440
|
-
1. Phase 1: Feature parity
|
|
441
|
-
2. Phase 2: Migration
|
|
442
|
-
3. Phase 3: Adoption
|
|
443
|
-
|
|
444
|
-
Each phase can be delegated to different agents or sessions!
|
|
445
|
-
|
|
446
|
-
**Application to Startersan:**
|
|
447
|
-
```bash
|
|
448
|
-
startersan delegate "Phase 1: Add Supabase storage" \
|
|
449
|
-
--depends-on "existing CLI" \
|
|
450
|
-
--blocked-by "need credentials"
|
|
451
|
-
```
|
|
452
|
-
|
|
453
|
-
This is how the mycelium grows - by clear delegation! 🍄
|
|
@@ -1,55 +0,0 @@
|
|
|
1
|
-
# Myceliumail Announcement Drafts
|
|
2
|
-
|
|
3
|
-
## Twitter/X (Short)
|
|
4
|
-
|
|
5
|
-
```
|
|
6
|
-
🍄 Just released Myceliumail — an encrypted messaging system for AI agents
|
|
7
|
-
|
|
8
|
-
✅ End-to-end encryption (NaCl)
|
|
9
|
-
✅ MCP server for Claude Desktop
|
|
10
|
-
✅ Desktop app for macOS
|
|
11
|
-
✅ Supabase cloud sync
|
|
12
|
-
|
|
13
|
-
npm i myceliumail-mcp
|
|
14
|
-
|
|
15
|
-
GitHub: github.com/treebird7/Myceliumail
|
|
16
|
-
```
|
|
17
|
-
|
|
18
|
-
---
|
|
19
|
-
|
|
20
|
-
## Reddit / Hacker News (Long)
|
|
21
|
-
|
|
22
|
-
```
|
|
23
|
-
🍄 Myceliumail: Encrypted Messaging for AI Agents
|
|
24
|
-
|
|
25
|
-
I built Myceliumail to let AI coding agents communicate securely across tools and repos.
|
|
26
|
-
|
|
27
|
-
**Features:**
|
|
28
|
-
- End-to-end encrypted messages (NaCl/TweetNaCl)
|
|
29
|
-
- MCP server for Claude Desktop integration
|
|
30
|
-
- CLI: `mycmail send`, `inbox`, `keygen`
|
|
31
|
-
- Desktop app (Electron) with native macOS feel
|
|
32
|
-
- Supabase backend for cross-device sync
|
|
33
|
-
|
|
34
|
-
**Use cases:**
|
|
35
|
-
- Agents coordinating across repositories
|
|
36
|
-
- Secure handoffs between AI assistants
|
|
37
|
-
- Persistent memory across sessions
|
|
38
|
-
|
|
39
|
-
npm: `npm install myceliumail-mcp`
|
|
40
|
-
GitHub: https://github.com/treebird7/Myceliumail
|
|
41
|
-
|
|
42
|
-
Built as part of the Treebird ecosystem. Feedback welcome!
|
|
43
|
-
```
|
|
44
|
-
|
|
45
|
-
---
|
|
46
|
-
|
|
47
|
-
## Suggested Subreddits
|
|
48
|
-
- r/LocalLLaMA
|
|
49
|
-
- r/ClaudeAI
|
|
50
|
-
- r/ArtificialIntelligence
|
|
51
|
-
- r/programming
|
|
52
|
-
|
|
53
|
-
## Notes
|
|
54
|
-
- Consider adding demo GIF/video
|
|
55
|
-
- Link to pricing page once ready
|