Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

notes-sync-strategy

Sterne0

Forks0

Aktualisiert7. Februar 2026 um 10:02

Specialized workflow for implementing Notes workspace file synchronization with offline-first support, conflict resolution, and AI synthesis integration. Use this workflow when implementing sync for Notes workspace, creating note-specific conflict resolution, or integrating AI with note files.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

shynlee04

shynlee04/idumb-v2

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

name	Notes Sync Strategy
description	Specialized workflow for implementing Notes workspace file synchronization with offline-first support, conflict resolution, and AI synthesis integration. Use this workflow when implementing sync for Notes workspace, creating note-specific conflict resolution, or integrating AI with note files.

Notes Sync Strategy Workflow

This Workflow provides Claude Code with step-by-step guidance for implementing Notes workspace sync.

When to use this workflow

When implementing Notes workspace file system sync
When creating offline-first note editing
When implementing note-specific conflict resolution (text merge, versioning)
When integrating AI synthesis with notes (per-note, batch)
When creating sync status indicators for Notes workspace

Workflow Steps

Step 1: Notes File System Strategy (2-3 hours)

Agent: file-sync-specialist Input: Notes workspace requirements Output: File system strategy document

Acceptance Criteria:

Desktop: FSA API with per-note file storage
Mobile: IndexedDB with sync-to-FSA on desktop
Note file format defined (Markdown, metadata, attachments)
Folder structure defined (notebooks, tags, search index)
Permission handling (read/write per notebook)

Step 2: Sync Concurrency Handling (3-4 hours)

Agent: file-sync-specialist Input: File system strategy Output: Concurrent sync implementation

Acceptance Criteria:

File locking per note (granular locking)
Conflict resolution for text notes (git-style merge)
Version history (undo/redo support)
Conflict UI (side-by-side diff, user choice)
Automatic save (debounce to avoid conflicts)

Step 3: AI Synthesis Integration (4-6 hours)

Agent: workspace-architect Input: Sync implementation Output: AI integration with notes

Acceptance Criteria:

Per-note AI synthesis (summarize, expand, rewrite)
Batch AI synthesis (process entire notebook)
AI-powered search (semantic search across notes)
AI tool permissions (read, write with user consent)
Progress indicators for AI operations

Step 4: Sync Status UX/UI (2-3 hours)

Agent: component-splitter Input: AI integration Output: Sync status UI components

Acceptance Criteria:

Sync status indicator (syncing, synced, conflict, offline)
Conflict resolution UI (side-by-side diff, accept button)
AI operation progress (progress bar, cancel button)
Offline mode indicator (editing while offline)
Error states (sync failed, retry button)

Step 5: Validation & Testing (2-3 hours)

Agent: test-writer Input: Complete Notes sync implementation Output: Test suite + validation report

Acceptance Criteria:

Unit tests for sync logic (CRUD, conflict resolution)
Integration tests (sync + AI integration)
E2E tests (critical user journeys)
Test coverage ≥80%
Zero data loss scenarios validated

Example Usage

"Implement Notes sync strategy using the notes-sync-strategy workflow"

Validation Commands

# TypeScript check
pnpm tsc --noEmit --incremental

# Test suite
pnpm test

# Notes-specific tests
pnpm test notes-*

# Sync validation
pnpm test sync-notes-*

Success Criteria

✅ Notes file system sync working (read, write, sync)
✅ Conflict resolution implemented (text merge, user choice)
✅ AI integration working (per-note, batch, search)
✅ Sync status indicators visible
✅ Offline-first support (IndexedDB queue)
✅ Zero data loss scenarios
✅ Test coverage ≥80%
✅ E2E tests passing

Artifacts

For detailed workflow documentation, refer to: Notes Sync Strategy Workflow

Mehr aus diesem Repository

gleiches Repository

agent-browser

shynlee04/idumb-v2

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

2026-02-070

gap-analysis

shynlee04/idumb-v2

Systematically identify what's missing, unknown, or needs investigation before making changes or decisions. Use proactively when proposing features, implementing changes, or making technical decisions to ensure all critical areas are covered. This skill catches overlooked dependencies, edge cases, and integration points before they become problems. Examples: - "Implement user authentication" → trigger gap analysis (what's the current auth system?) - "Add caching to API" → trigger gap analysis (what caching infrastructure exists?) - "Migrate to TypeScript" → trigger gap analysis (what's the build pipeline?) - "Refactor this module" → trigger gap analysis (what depends on this module?) - "Add new API endpoint" → trigger gap analysis (what endpoints exist, what patterns?)

2026-02-070

intent-clarification

shynlee04/idumb-v2

Detect ambiguous or underspecified research requests and guide through structured clarification questions before executing any research. Use proactively when user requests are vague, lack specificity, missing context, or have unclear goals. This skill prevents wasted research by ensuring intent is crystal clear before any web searches, file reads, or data gathering. Examples: - "Research the codebase" → ❌ Too vague, trigger clarification - "Why is this slow?" → ❌ Missing context (what is "this"?), trigger clarification - "Add a feature" → ❌ Not research, this is implementation - "Investigate authentication flow" → ❌ What specifically about it? Trigger clarification - "Compare React and Vue" → ✅ Specific enough, but still validate dimensions

2026-02-070

multi-aspect-assessment

shynlee04/idumb-v2

Evaluate requests, proposals, or decisions from multiple dimensions (technical, business, UX, security, performance, maintainability, etc.) to ensure holistic understanding before proceeding. Use proactively when making technical decisions, choosing solutions, or proposing changes. This skill prevents single-minded thinking and uncovers trade-offs, risks, and opportunities across all relevant aspects. Examples: - "Use Redis for caching" → assess multiple aspects (performance, cost, complexity, ops) - "Add AI to our app" → assess aspects (technical feasibility, user experience, data privacy) - "Refactor to microservices" → assess aspects (benefits, costs, migration complexity, team readiness) - "Implement authentication" → assess aspects (security, UX, integration effort, maintenance) - "Switch to React 19" → assess aspects (benefits, migration cost, breaking changes, learning curve)

2026-02-070

opencode-primitive-selector

shynlee04/idumb-v2

Choose the right OpenCode primitive (Command, Skill, Tool, Prompt, CustomTool, Plugin hook) for a given task or workflow. Use proactively when deciding which OpenCode capability to use, or when trying to understand what's available. This skill maps research and development needs to appropriate OpenCode mechanisms, ensuring optimal use of the platform's capabilities. Examples: - "How do I search the codebase?" → select tool (read/grep) - "I need a reusable workflow for feature development" → select command - "How do I intercept file writes?" → select plugin hook - "What primitive should I use for systematic debugging?" → select skill - "I need a custom tool for X" → select CustomTool (if innate tools insufficient)

2026-02-070

research-workflow-planner

shynlee04/idumb-v2

Create structured, executable research plans with clear phases, checkpoints, and validation criteria. Use proactively when research intent is clear but execution plan is missing. This skill transforms research goals into actionable workflows with defined deliverables, time estimates, and success metrics, ensuring research is systematic and produces useful outputs. Examples: - "Research how to add OAuth" (intent clear, need plan) → trigger workflow planner - "Investigate performance bottlenecks" (intent clear, need plan) → trigger workflow planner - "Analyze codebase architecture" (intent clear, need plan) → trigger workflow planner - "Find best practices for X" (intent clear, need plan) → trigger workflow planner - "Compare technology options" (intent clear, need plan) → trigger workflow planner

2026-02-070

Jeden Skill mit einem Klick ausführen