Vibecode Ulysses
track this build5 steps, step by step0%YES · one-shottable
price $5.99/moyou'd save $71.88/yrbuild time one sittingcategory 🖋️ writing toolsreplaced by 0 people
The core loop is small enough for a capable coding agent to produce a useful local version in one sitting. For Ulysses, write in a focused Markdown library, organize sheets, set goals, and export polished documents. The hard boundary is native apple polish, icloud sync, mobile apps, and publishing integrations, plus polish, integrations, and proprietary language models.
the project pack4 files · fastest path to a working personal build
You are building a lean indie version of Ulysses. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # Ulysses indie build ## Goal Build the smallest trustworthy replacement for the core Ulysses workflow for one developer or a tiny team. ## Scope Write in a focused local Markdown library, organize sheets, set goals, apply editing passes with a visible diff, and export polished documents without uploading them. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - native Apple polish, iCloud sync, mobile apps, and publishing integrations - cross-device sync - large proprietary style models - browser and office-suite extensions - team style guides If those capabilities are essential, use LanguageTool instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build brief Build a personal replacement for Ulysses in an empty repository. Use Tauri 2, React, TypeScript, SQLite, and a small Rust filesystem layer; do not offer alternative stacks. The core loop is: write in a focused local Markdown library, organize sheets, set goals, apply editing passes with a visible diff, and export polished documents without uploading them. Make the first run work locally with one documented command. Store all user data locally by default and make export straightforward. Put secrets in .env, ship .env.example, and never commit credentials. Create a three-pane editor with source text, suggestion list, and accepted-result preview. Implement deterministic checks for repeated words, sentence length, passive constructions, and typography. Add an optional API-backed rewrite action that sends only the selected passage. Show every change as an accept-or-reject diff and support undo. Import and export .txt and .md while preserving headings and lists. Persist user rules, ignored terms, and recent documents in SQLite. Include clear empty, loading, success, and recoverable error states. Add input validation, safe filenames, and graceful handling of unavailable APIs. Write focused tests for the core transformation and one end-to-end happy path. Create a README with setup, architecture, permissions, data location, and backup steps. Do not add accounts, billing, telemetry, analytics, or a hosted control plane. Deliberately leave out a browser extension. Deliberately leave out Office or Google Docs plugins. Deliberately leave out collaborative editing and cloud sync. Finish by running the tests and listing the exact commands used. ## Required capabilities - macOS, Windows, or Linux - local files - optional OpenAI or Anthropic API key for semantic rewrites ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a lean indie version of Ulysses. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # Ulysses indie build ## Goal Build the smallest trustworthy replacement for the core Ulysses workflow for one developer or a tiny team. ## Scope Write in a focused local Markdown library, organize sheets, set goals, apply editing passes with a visible diff, and export polished documents without uploading them. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - native Apple polish, iCloud sync, mobile apps, and publishing integrations - cross-device sync - large proprietary style models - browser and office-suite extensions - team style guides If those capabilities are essential, use LanguageTool instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build brief Build a personal replacement for Ulysses in an empty repository. Use Tauri 2, React, TypeScript, SQLite, and a small Rust filesystem layer; do not offer alternative stacks. The core loop is: write in a focused local Markdown library, organize sheets, set goals, apply editing passes with a visible diff, and export polished documents without uploading them. Make the first run work locally with one documented command. Store all user data locally by default and make export straightforward. Put secrets in .env, ship .env.example, and never commit credentials. Create a three-pane editor with source text, suggestion list, and accepted-result preview. Implement deterministic checks for repeated words, sentence length, passive constructions, and typography. Add an optional API-backed rewrite action that sends only the selected passage. Show every change as an accept-or-reject diff and support undo. Import and export .txt and .md while preserving headings and lists. Persist user rules, ignored terms, and recent documents in SQLite. Include clear empty, loading, success, and recoverable error states. Add input validation, safe filenames, and graceful handling of unavailable APIs. Write focused tests for the core transformation and one end-to-end happy path. Create a README with setup, architecture, permissions, data location, and backup steps. Do not add accounts, billing, telemetry, analytics, or a hosted control plane. Deliberately leave out a browser extension. Deliberately leave out Office or Google Docs plugins. Deliberately leave out collaborative editing and cloud sync. Finish by running the tests and listing the exact commands used. ## Required capabilities - macOS, Windows, or Linux - local files - optional OpenAI or Anthropic API key for semantic rewrites ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a production product version of Ulysses. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== PRODUCT.md ===== # Ulysses product brief ## Problem The core loop is small enough for a capable coding agent to produce a useful local version in one sitting. For Ulysses, write in a focused Markdown library, organize sheets, set goals, and export polished documents. The hard boundary is native apple polish, icloud sync, mobile apps, and publishing integrations, plus polish, integrations, and proprietary language models. ## Product outcome Write in a focused local Markdown library, organize sheets, set goals, apply editing passes with a visible diff, and export polished documents without uploading them. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - macOS, Windows, or Linux - local files - optional OpenAI or Anthropic API key for semantic rewrites ## Explicit non-goals for v1 - native Apple polish, iCloud sync, mobile apps, and publishing integrations - cross-device sync - large proprietary style models - browser and office-suite extensions - team style guides ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees. ===== ARCHITECTURE.md ===== # Architecture ## Starting brief Build a personal replacement for Ulysses in an empty repository. Use Tauri 2, React, TypeScript, SQLite, and a small Rust filesystem layer; do not offer alternative stacks. The core loop is: write in a focused local Markdown library, organize sheets, set goals, apply editing passes with a visible diff, and export polished documents without uploading them. Make the first run work locally with one documented command. Store all user data locally by default and make export straightforward. Put secrets in .env, ship .env.example, and never commit credentials. Create a three-pane editor with source text, suggestion list, and accepted-result preview. Implement deterministic checks for repeated words, sentence length, passive constructions, and typography. Add an optional API-backed rewrite action that sends only the selected passage. Show every change as an accept-or-reject diff and support undo. Import and export .txt and .md while preserving headings and lists. Persist user rules, ignored terms, and recent documents in SQLite. Include clear empty, loading, success, and recoverable error states. Add input validation, safe filenames, and graceful handling of unavailable APIs. Write focused tests for the core transformation and one end-to-end happy path. Create a README with setup, architecture, permissions, data location, and backup steps. Do not add accounts, billing, telemetry, analytics, or a hosted control plane. Deliberately leave out a browser extension. Deliberately leave out Office or Google Docs plugins. Deliberately leave out collaborative editing and cloud sync. Finish by running the tests and listing the exact commands used. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it. ===== AGENTS.md ===== # Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone. ===== MILESTONES.md ===== # Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations. ===== OPERATIONS.md ===== # Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted Ulysses capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
README.md
# Ulysses indie build ## Goal Build the smallest trustworthy replacement for the core Ulysses workflow for one developer or a tiny team. ## Scope Write in a focused local Markdown library, organize sheets, set goals, apply editing passes with a visible diff, and export polished documents without uploading them. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - native Apple polish, iCloud sync, mobile apps, and publishing integrations - cross-device sync - large proprietary style models - browser and office-suite extensions - team style guides If those capabilities are essential, use LanguageTool instead of pretending the gap is solved.
AGENTS.md
# Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs".
BUILD_PLAN.md
# Build plan ## Original build brief Build a personal replacement for Ulysses in an empty repository. Use Tauri 2, React, TypeScript, SQLite, and a small Rust filesystem layer; do not offer alternative stacks. The core loop is: write in a focused local Markdown library, organize sheets, set goals, apply editing passes with a visible diff, and export polished documents without uploading them. Make the first run work locally with one documented command. Store all user data locally by default and make export straightforward. Put secrets in .env, ship .env.example, and never commit credentials. Create a three-pane editor with source text, suggestion list, and accepted-result preview. Implement deterministic checks for repeated words, sentence length, passive constructions, and typography. Add an optional API-backed rewrite action that sends only the selected passage. Show every change as an accept-or-reject diff and support undo. Import and export .txt and .md while preserving headings and lists. Persist user rules, ignored terms, and recent documents in SQLite. Include clear empty, loading, success, and recoverable error states. Add input validation, safe filenames, and graceful handling of unavailable APIs. Write focused tests for the core transformation and one end-to-end happy path. Create a README with setup, architecture, permissions, data location, and backup steps. Do not add accounts, billing, telemetry, analytics, or a hosted control plane. Deliberately leave out a browser extension. Deliberately leave out Office or Google Docs plugins. Deliberately leave out collaborative editing and cloud sync. Finish by running the tests and listing the exact commands used. ## Required capabilities - macOS, Windows, or Linux - local files - optional OpenAI or Anthropic API key for semantic rewrites ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden.
.env.example
# Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
PRODUCT.md
# Ulysses product brief ## Problem The core loop is small enough for a capable coding agent to produce a useful local version in one sitting. For Ulysses, write in a focused Markdown library, organize sheets, set goals, and export polished documents. The hard boundary is native apple polish, icloud sync, mobile apps, and publishing integrations, plus polish, integrations, and proprietary language models. ## Product outcome Write in a focused local Markdown library, organize sheets, set goals, apply editing passes with a visible diff, and export polished documents without uploading them. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - macOS, Windows, or Linux - local files - optional OpenAI or Anthropic API key for semantic rewrites ## Explicit non-goals for v1 - native Apple polish, iCloud sync, mobile apps, and publishing integrations - cross-device sync - large proprietary style models - browser and office-suite extensions - team style guides ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees.
ARCHITECTURE.md
# Architecture ## Starting brief Build a personal replacement for Ulysses in an empty repository. Use Tauri 2, React, TypeScript, SQLite, and a small Rust filesystem layer; do not offer alternative stacks. The core loop is: write in a focused local Markdown library, organize sheets, set goals, apply editing passes with a visible diff, and export polished documents without uploading them. Make the first run work locally with one documented command. Store all user data locally by default and make export straightforward. Put secrets in .env, ship .env.example, and never commit credentials. Create a three-pane editor with source text, suggestion list, and accepted-result preview. Implement deterministic checks for repeated words, sentence length, passive constructions, and typography. Add an optional API-backed rewrite action that sends only the selected passage. Show every change as an accept-or-reject diff and support undo. Import and export .txt and .md while preserving headings and lists. Persist user rules, ignored terms, and recent documents in SQLite. Include clear empty, loading, success, and recoverable error states. Add input validation, safe filenames, and graceful handling of unavailable APIs. Write focused tests for the core transformation and one end-to-end happy path. Create a README with setup, architecture, permissions, data location, and backup steps. Do not add accounts, billing, telemetry, analytics, or a hosted control plane. Deliberately leave out a browser extension. Deliberately leave out Office or Google Docs plugins. Deliberately leave out collaborative editing and cloud sync. Finish by running the tests and listing the exact commands used. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.
AGENTS.md
# Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone.
MILESTONES.md
# Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.
OPERATIONS.md
# Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted Ulysses capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
$ choose a build depth, inspect the files, then open the complete pack in your agent · this prompt is generated from the build plan · improve it via PR
People still pay for Ulysses because the paid tool is already present everywhere they write and its suggestions have been tuned across millions of documents. The recurring cost buys model quality, extension compatibility, dictionaries, releases, and sync, not just the visible interface.
xnative Apple polish, iCloud sync, mobile apps, and publishing integrations
xcross-device sync
xlarge proprietary style models
xbrowser and office-suite extensions
xteam style guides
share on X ↗"I just replaced Ulysses ($5.99/mo) with one prompt"
Don't feel like building it? These folks already made it free.
SiYuanA local-first writing library with blocks, links, huge documents, and real exports; less monastic than Ulysses, much harder to lose.open source↗
ZettlrA serious Markdown desk with folders, writing targets, citations, and export machinery that occasionally admits Pandoc is under the hood.open source↗no votes, no pay-to-list · just what's real
Ulysses pricing
| plan | monthly | annual (per mo) | what you get |
|---|---|---|---|
| monthly | $5.99/user | — | All Macs, iPads and iPhones on the subscriber's Apple Account |
| yearly | — | $3.33/user | All Macs, iPads and iPhones; Apple Family Sharing with up to 5 other family members |
| student | — | $1.83/user | All Macs, iPads and iPhones for 6 months; no Family Sharing |
| business / volume licensing | custom | — | Custom seat count for organizations |
free tierno free tier
billing$5.99 monthly or $39.99 yearly, both auto-renew; student option is $10.99 per 6 months and does not auto-renew
hidden costsUS prices can differ by App Store region; student pricing excludes Family Sharing, and business volume pricing is quote-only.
verified 2026-08-12 · source ↗
Vibecode Ulysses
Yes. A competent AI coding agent (Claude Code, Codex, Cursor) can build a usable personal Ulysses replacement in one session with the prompt on this page. It runs on your own machine or server with no subscription.
How much does Ulysses cost?
Ulysses costs about $5.99/month (Personal, checked 2026-07-31), which is $71.88 per year. That's what you save by replacing it with one prompt.
What do I lose by replacing Ulysses?
Honestly: native Apple polish, iCloud sync, mobile apps, and publishing integrations; cross-device sync; large proprietary style models; browser and office-suite extensions; team style guides. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Ulysses?
Yes: SiYuan (A local-first writing library with blocks, links, huge documents, and real exports; less monastic than Ulysses, much harder to lose.) Zettlr (A serious Markdown desk with folders, writing targets, citations, and export machinery that occasionally admits Pandoc is under the hood.) The prompt is for when you want it exactly your way.