'Reference architecture for Apple Notes automation systems.
Scanned 5/29/2026
Install to Claude Code
npx -y skills add jeremylongshore/claude-code-plugins-plus-skills --skill apple-notes-reference-architecture --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Apple Notes Reference Architecture?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/jeremylongshore-apple-notes-reference-architecture)More formats (shields.io, HTML) on the badges page.
---
name: apple-notes-reference-architecture
description: 'Reference architecture for Apple Notes automation systems.
Trigger: "apple notes architecture".
'
allowed-tools: Read, Write, Edit, Bash(osascript:*), Grep
version: 1.0.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
tags:
- saas
- macos
- apple-notes
- automation
compatibility: Designed for Claude Code
---
# Apple Notes Reference Architecture
## Overview
Apple Notes automation systems are fundamentally different from cloud SaaS integrations. There is no REST API, no server-side SDK, and no webhook infrastructure. Everything runs locally on macOS through the Apple Events IPC bridge. This reference architecture defines the standard layered approach: a Node.js application layer that calls JXA scripts via `osascript`, a local SQLite cache for fast queries, a change detection poller for event-driven workflows, and optional Shortcuts integration for cross-app automation.
## System Architecture
```
┌─────────────────────────────────────────────────────┐
│ macOS Machine │
│ │
│ ┌──────────┐ ┌───────────┐ ┌────────────────┐ │
│ │ Your App │──▶│ osascript │──▶│ Notes.app │ │
│ │ (Node.js)│ │ (JXA) │ │ (local DB) │ │
│ └────┬─────┘ └───────────┘ └───────┬────────┘ │
│ │ │ │
│ ┌────▼─────┐ ┌───────────┐ ┌───────▼────────┐ │
│ │ SQLite │ │ Shortcuts │ │ iCloud Sync │ │
│ │ Cache │ │ Automations│ │ (bird/cloudd) │ │
│ └──────────┘ └───────────┘ └────────────────┘ │
│ │ │ │
│ ┌────▼─────┐ ┌────────▼───────┐ │
│ │ Poller / │ │ Other Apple │ │
│ │ FSEvents │ │ Devices │ │
│ └──────────┘ └────────────────┘ │
└─────────────────────────────────────────────────────┘
```
## Project Structure
```
apple-notes-automation/
├── src/
│ ├── notes-client.ts # JXA wrapper class (osascript calls)
│ ├── cache.ts # SQLite cache layer
│ ├── templates/ # Note templates (HTML fragments)
│ ├── export/ # Export to MD/JSON/SQLite/CSV
│ ├── events/ # Change detection via polling
│ └── server.ts # Optional: local HTTP API for remote access
├── scripts/
│ ├── notes-cli.sh # CLI wrapper for common operations
│ ├── health-check.sh # Monitoring and alerting
│ ├── export-all.sh # Full backup export
│ └── install.sh # launchd deployment installer
├── tests/
│ ├── mocks/ # Mock JXA client for CI (non-macOS)
│ └── unit/ # Unit tests (vitest)
├── config/
│ ├── environments.json # Account/folder per environment
│ └── launchd.plist # Service definition template
└── package.json
```
## Component Design
```typescript
// src/notes-client.ts — Core abstraction over osascript
import { execSync } from "child_process";
export class NotesClient {
private account: string;
constructor(account = "iCloud") { this.account = account; }
private exec(jxa: string): string {
return execSync(`osascript -l JavaScript -e '${jxa.replace(/'/g, "'\\''")}'`,
{ encoding: "utf8", timeout: 30000 }).trim();
}
count(): number {
return parseInt(this.exec(`Application("Notes").accounts().find(a => a.name() === "${this.account}").notes.length`));
}
list(): Array<{ id: string; title: string; modified: string }> {
return JSON.parse(this.exec(`
JSON.stringify(Application("Notes").accounts().find(a => a.name() === "${this.account}")
.notes().map(n => ({id: n.id(), title: n.name(), modified: n.modificationDate().toISOString()})))
`));
}
create(title: string, body: string, folder = "Notes"): string {
return this.exec(`
const Notes = Application("Notes");
const acct = Notes.accounts().find(a => a.name() === "${this.account}");
const f = acct.folders().find(f => f.name() === "${folder}") || acct.folders[0];
const n = Notes.Note({name: "${title}", body: "${body}"});
f.notes.push(n); n.id();
`);
}
}
```
## Key Constraints
| Constraint | Impact | Workaround |
|-----------|--------|------------|
| macOS only | No Linux/Windows servers | Run on Mac; export data for cross-platform consumption |
| No REST API | Cannot access remotely | Optional: expose local HTTP server; lock down to localhost |
| iCloud sync lag | Writes may take 5-30s to appear on other devices | Poll with delay; verify on target device |
| No webhooks | Cannot receive push notifications | Poll for changes every 60s; watch FSEvents on Notes DB |
| HTML-only body | No native Markdown support | Convert HTML to/from Markdown in export/import layer |
| No attachment export via JXA | Binary data inaccessible from scripting | Use Shortcuts for attachment extraction |
## Error Handling
| Issue | Cause | Solution |
|-------|-------|----------|
| Architecture requires macOS server | No cloud-native option | Dedicate a Mac mini as automation server; use Tailscale for remote access |
| Local HTTP API exposed to network | Security risk if not locked down | Bind to 127.0.0.1 only; use SSH tunnel for remote access |
| Cache out of sync with Notes | Polling interval too long | Reduce poll interval; use FSEvents on NoteStore.sqlite for faster detection |
| Template HTML rejected by Notes | Invalid HTML tags | Test templates with a canary note before bulk creation |
## Resources
- [Mac Automation Scripting Guide](https://developer.apple.com/library/archive/documentation/LanguagesUtilities/Conceptual/MacAutomationScriptingGuide/)
- [JXA Cookbook](https://github.com/JXA-Cookbook/JXA-Cookbook)
- [macOS Security Architecture](https://support.apple.com/guide/security/welcome/web)
## Next Steps
For deploying this architecture as a service, see `apple-notes-deploy-integration`. For monitoring the running system, see `apple-notes-observability`.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!