Vibecode Yaps
track this build5 steps, step by step0%KINDA · weekend project
price $15/moyou'd save $180/yrbuild time weekend for one platform and a narrow subset; the full suite is a major product buildcategory ✨ ai assistantsreplaced by 0 people
Kinda. A coding agent can one-shot an isolated Yaps feature, such as hotkey dictation, a Markdown notes shell, or local read-aloud, but not the integrated product. Yaps spans native work across macOS, Windows, Linux, Android, and iOS, with platform-level text insertion and mobile keyboards, local AI model orchestration, notes and cross-device sync, browser capture, transcription and diarization, speech and media tools, permissions, installers, updates, and long-tail reliability. The honest DIY outcome is a useful single-platform subset, not a replacement for the suite.
the project pack4 files · fastest path to a working personal build
You are building a lean indie version of Yaps. 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 ===== # Yaps indie build ## Goal Build the smallest trustworthy replacement for the core Yaps workflow for one developer or a tiny team. ## Scope Build one honest single-platform subset: local hotkey dictation into the active app plus a Markdown notes vault and read-aloud. ## 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 parity across macOS, Windows, Linux, Android, and iOS - reliable Fn and global-shortcut capture plus cursor insertion across native, browser, terminal, and Electron text surfaces - mobile keyboards, browser capture, a Markdown vault, and desktop-to-mobile note sync working as one system - bundled and warmed local runtimes for dictation, cleanup, TTS, transcription, diarization, translation, voice, and media tools - installers, model downloads, updates, permissions UX, performance tuning, recovery, and cross-platform regression testing If those capabilities are essential, use whisper.cpp 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 the closest honest single-platform subset of Yaps in an empty repository; do not claim it replaces the full product. Use Swift 6, SwiftUI with AppKit, AVFoundation, and a locally installed whisper.cpp CLI; do not offer alternative stacks. Target macOS 14 or later and make it a menu-bar accessory app with no Dock icon. State in the app and README that this subset covers dictation, Markdown notes, and read-aloud only. Provide one documented command that builds and launches a debug build from a clean clone. The core loop is: hold a global shortcut, record the microphone, transcribe locally, and insert clean text at the active cursor. Default to Control-Space, allow remapping, and do not claim to replace or reliably intercept the Fn key. Capture 16 kHz mono WAV with AVAudioEngine and show a compact recording and transcribing status pill. On release, invoke whisper.cpp with a configurable model path and no network request. Insert with the pasteboard plus Cmd-V, restore the previous clipboard, and leave the text copied when direct insertion cannot be verified. Keep the last 20 transcripts locally with timestamps, copy, retry, delete, and save-as-note actions. Save notes as plain Markdown under ~/Documents/YapsDIY and never hide content in an opaque database. Add a small notes window with create, edit, full-text filename/body search, and a recent-notes list. Add read-aloud for the current note using NSSpeechSynthesizer with voice, rate, pause, resume, and stop controls. Add a custom vocabulary text file whose terms are passed to whisper.cpp as an initial prompt. Keep raw audio only when the user enables it; otherwise delete it after a successful transcript. Store settings in Application Support and make the Markdown vault easy to relocate and back up. Handle denied microphone or Accessibility permission with clear instructions and a retry button. Include visible idle, recording, transcribing, success, and recoverable error states. Add focused tests for settings, history limits, vault file safety, clipboard restoration, and transcription command construction. Add one smoke test that injects a fixture WAV and proves a transcript becomes a Markdown note. Create a README covering setup, model download, permissions, data locations, privacy, backup, and limitations. Do not add accounts, billing, telemetry, analytics, cloud sync, or hidden network calls. Deliberately leave out Windows, Linux, Android, iOS, mobile keyboards, meetings, diarization, captions, voice cloning, media tools, browser capture, and sync. Finish by running the tests and build, fixing failures, and listing the exact commands used. ## Required capabilities - macOS 14 or later - Swift 6 and Xcode - whisper.cpp and a local speech model - microphone, Accessibility, and global-shortcut permissions - a local Markdown vault with explicit backup and export ## 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 Yaps. 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 ===== # Yaps indie build ## Goal Build the smallest trustworthy replacement for the core Yaps workflow for one developer or a tiny team. ## Scope Build one honest single-platform subset: local hotkey dictation into the active app plus a Markdown notes vault and read-aloud. ## 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 parity across macOS, Windows, Linux, Android, and iOS - reliable Fn and global-shortcut capture plus cursor insertion across native, browser, terminal, and Electron text surfaces - mobile keyboards, browser capture, a Markdown vault, and desktop-to-mobile note sync working as one system - bundled and warmed local runtimes for dictation, cleanup, TTS, transcription, diarization, translation, voice, and media tools - installers, model downloads, updates, permissions UX, performance tuning, recovery, and cross-platform regression testing If those capabilities are essential, use whisper.cpp 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 the closest honest single-platform subset of Yaps in an empty repository; do not claim it replaces the full product. Use Swift 6, SwiftUI with AppKit, AVFoundation, and a locally installed whisper.cpp CLI; do not offer alternative stacks. Target macOS 14 or later and make it a menu-bar accessory app with no Dock icon. State in the app and README that this subset covers dictation, Markdown notes, and read-aloud only. Provide one documented command that builds and launches a debug build from a clean clone. The core loop is: hold a global shortcut, record the microphone, transcribe locally, and insert clean text at the active cursor. Default to Control-Space, allow remapping, and do not claim to replace or reliably intercept the Fn key. Capture 16 kHz mono WAV with AVAudioEngine and show a compact recording and transcribing status pill. On release, invoke whisper.cpp with a configurable model path and no network request. Insert with the pasteboard plus Cmd-V, restore the previous clipboard, and leave the text copied when direct insertion cannot be verified. Keep the last 20 transcripts locally with timestamps, copy, retry, delete, and save-as-note actions. Save notes as plain Markdown under ~/Documents/YapsDIY and never hide content in an opaque database. Add a small notes window with create, edit, full-text filename/body search, and a recent-notes list. Add read-aloud for the current note using NSSpeechSynthesizer with voice, rate, pause, resume, and stop controls. Add a custom vocabulary text file whose terms are passed to whisper.cpp as an initial prompt. Keep raw audio only when the user enables it; otherwise delete it after a successful transcript. Store settings in Application Support and make the Markdown vault easy to relocate and back up. Handle denied microphone or Accessibility permission with clear instructions and a retry button. Include visible idle, recording, transcribing, success, and recoverable error states. Add focused tests for settings, history limits, vault file safety, clipboard restoration, and transcription command construction. Add one smoke test that injects a fixture WAV and proves a transcript becomes a Markdown note. Create a README covering setup, model download, permissions, data locations, privacy, backup, and limitations. Do not add accounts, billing, telemetry, analytics, cloud sync, or hidden network calls. Deliberately leave out Windows, Linux, Android, iOS, mobile keyboards, meetings, diarization, captions, voice cloning, media tools, browser capture, and sync. Finish by running the tests and build, fixing failures, and listing the exact commands used. ## Required capabilities - macOS 14 or later - Swift 6 and Xcode - whisper.cpp and a local speech model - microphone, Accessibility, and global-shortcut permissions - a local Markdown vault with explicit backup and export ## 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 Yaps. 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 ===== # Yaps product brief ## Problem Kinda. A coding agent can one-shot an isolated Yaps feature, such as hotkey dictation, a Markdown notes shell, or local read-aloud, but not the integrated product. Yaps spans native work across macOS, Windows, Linux, Android, and iOS, with platform-level text insertion and mobile keyboards, local AI model orchestration, notes and cross-device sync, browser capture, transcription and diarization, speech and media tools, permissions, installers, updates, and long-tail reliability. The honest DIY outcome is a useful single-platform subset, not a replacement for the suite. ## Product outcome Build one honest single-platform subset: local hotkey dictation into the active app plus a Markdown notes vault and read-aloud. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - macOS 14 or later - Swift 6 and Xcode - whisper.cpp and a local speech model - microphone, Accessibility, and global-shortcut permissions - a local Markdown vault with explicit backup and export ## Explicit non-goals for v1 - native parity across macOS, Windows, Linux, Android, and iOS - reliable Fn and global-shortcut capture plus cursor insertion across native, browser, terminal, and Electron text surfaces - mobile keyboards, browser capture, a Markdown vault, and desktop-to-mobile note sync working as one system - bundled and warmed local runtimes for dictation, cleanup, TTS, transcription, diarization, translation, voice, and media tools - installers, model downloads, updates, permissions UX, performance tuning, recovery, and cross-platform regression testing ## 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 the closest honest single-platform subset of Yaps in an empty repository; do not claim it replaces the full product. Use Swift 6, SwiftUI with AppKit, AVFoundation, and a locally installed whisper.cpp CLI; do not offer alternative stacks. Target macOS 14 or later and make it a menu-bar accessory app with no Dock icon. State in the app and README that this subset covers dictation, Markdown notes, and read-aloud only. Provide one documented command that builds and launches a debug build from a clean clone. The core loop is: hold a global shortcut, record the microphone, transcribe locally, and insert clean text at the active cursor. Default to Control-Space, allow remapping, and do not claim to replace or reliably intercept the Fn key. Capture 16 kHz mono WAV with AVAudioEngine and show a compact recording and transcribing status pill. On release, invoke whisper.cpp with a configurable model path and no network request. Insert with the pasteboard plus Cmd-V, restore the previous clipboard, and leave the text copied when direct insertion cannot be verified. Keep the last 20 transcripts locally with timestamps, copy, retry, delete, and save-as-note actions. Save notes as plain Markdown under ~/Documents/YapsDIY and never hide content in an opaque database. Add a small notes window with create, edit, full-text filename/body search, and a recent-notes list. Add read-aloud for the current note using NSSpeechSynthesizer with voice, rate, pause, resume, and stop controls. Add a custom vocabulary text file whose terms are passed to whisper.cpp as an initial prompt. Keep raw audio only when the user enables it; otherwise delete it after a successful transcript. Store settings in Application Support and make the Markdown vault easy to relocate and back up. Handle denied microphone or Accessibility permission with clear instructions and a retry button. Include visible idle, recording, transcribing, success, and recoverable error states. Add focused tests for settings, history limits, vault file safety, clipboard restoration, and transcription command construction. Add one smoke test that injects a fixture WAV and proves a transcript becomes a Markdown note. Create a README covering setup, model download, permissions, data locations, privacy, backup, and limitations. Do not add accounts, billing, telemetry, analytics, cloud sync, or hidden network calls. Deliberately leave out Windows, Linux, Android, iOS, mobile keyboards, meetings, diarization, captions, voice cloning, media tools, browser capture, and sync. Finish by running the tests and build, fixing failures, 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 Yaps capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
README.md
# Yaps indie build ## Goal Build the smallest trustworthy replacement for the core Yaps workflow for one developer or a tiny team. ## Scope Build one honest single-platform subset: local hotkey dictation into the active app plus a Markdown notes vault and read-aloud. ## 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 parity across macOS, Windows, Linux, Android, and iOS - reliable Fn and global-shortcut capture plus cursor insertion across native, browser, terminal, and Electron text surfaces - mobile keyboards, browser capture, a Markdown vault, and desktop-to-mobile note sync working as one system - bundled and warmed local runtimes for dictation, cleanup, TTS, transcription, diarization, translation, voice, and media tools - installers, model downloads, updates, permissions UX, performance tuning, recovery, and cross-platform regression testing If those capabilities are essential, use whisper.cpp 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 the closest honest single-platform subset of Yaps in an empty repository; do not claim it replaces the full product. Use Swift 6, SwiftUI with AppKit, AVFoundation, and a locally installed whisper.cpp CLI; do not offer alternative stacks. Target macOS 14 or later and make it a menu-bar accessory app with no Dock icon. State in the app and README that this subset covers dictation, Markdown notes, and read-aloud only. Provide one documented command that builds and launches a debug build from a clean clone. The core loop is: hold a global shortcut, record the microphone, transcribe locally, and insert clean text at the active cursor. Default to Control-Space, allow remapping, and do not claim to replace or reliably intercept the Fn key. Capture 16 kHz mono WAV with AVAudioEngine and show a compact recording and transcribing status pill. On release, invoke whisper.cpp with a configurable model path and no network request. Insert with the pasteboard plus Cmd-V, restore the previous clipboard, and leave the text copied when direct insertion cannot be verified. Keep the last 20 transcripts locally with timestamps, copy, retry, delete, and save-as-note actions. Save notes as plain Markdown under ~/Documents/YapsDIY and never hide content in an opaque database. Add a small notes window with create, edit, full-text filename/body search, and a recent-notes list. Add read-aloud for the current note using NSSpeechSynthesizer with voice, rate, pause, resume, and stop controls. Add a custom vocabulary text file whose terms are passed to whisper.cpp as an initial prompt. Keep raw audio only when the user enables it; otherwise delete it after a successful transcript. Store settings in Application Support and make the Markdown vault easy to relocate and back up. Handle denied microphone or Accessibility permission with clear instructions and a retry button. Include visible idle, recording, transcribing, success, and recoverable error states. Add focused tests for settings, history limits, vault file safety, clipboard restoration, and transcription command construction. Add one smoke test that injects a fixture WAV and proves a transcript becomes a Markdown note. Create a README covering setup, model download, permissions, data locations, privacy, backup, and limitations. Do not add accounts, billing, telemetry, analytics, cloud sync, or hidden network calls. Deliberately leave out Windows, Linux, Android, iOS, mobile keyboards, meetings, diarization, captions, voice cloning, media tools, browser capture, and sync. Finish by running the tests and build, fixing failures, and listing the exact commands used. ## Required capabilities - macOS 14 or later - Swift 6 and Xcode - whisper.cpp and a local speech model - microphone, Accessibility, and global-shortcut permissions - a local Markdown vault with explicit backup and export ## 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
# Yaps product brief ## Problem Kinda. A coding agent can one-shot an isolated Yaps feature, such as hotkey dictation, a Markdown notes shell, or local read-aloud, but not the integrated product. Yaps spans native work across macOS, Windows, Linux, Android, and iOS, with platform-level text insertion and mobile keyboards, local AI model orchestration, notes and cross-device sync, browser capture, transcription and diarization, speech and media tools, permissions, installers, updates, and long-tail reliability. The honest DIY outcome is a useful single-platform subset, not a replacement for the suite. ## Product outcome Build one honest single-platform subset: local hotkey dictation into the active app plus a Markdown notes vault and read-aloud. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - macOS 14 or later - Swift 6 and Xcode - whisper.cpp and a local speech model - microphone, Accessibility, and global-shortcut permissions - a local Markdown vault with explicit backup and export ## Explicit non-goals for v1 - native parity across macOS, Windows, Linux, Android, and iOS - reliable Fn and global-shortcut capture plus cursor insertion across native, browser, terminal, and Electron text surfaces - mobile keyboards, browser capture, a Markdown vault, and desktop-to-mobile note sync working as one system - bundled and warmed local runtimes for dictation, cleanup, TTS, transcription, diarization, translation, voice, and media tools - installers, model downloads, updates, permissions UX, performance tuning, recovery, and cross-platform regression testing ## 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 the closest honest single-platform subset of Yaps in an empty repository; do not claim it replaces the full product. Use Swift 6, SwiftUI with AppKit, AVFoundation, and a locally installed whisper.cpp CLI; do not offer alternative stacks. Target macOS 14 or later and make it a menu-bar accessory app with no Dock icon. State in the app and README that this subset covers dictation, Markdown notes, and read-aloud only. Provide one documented command that builds and launches a debug build from a clean clone. The core loop is: hold a global shortcut, record the microphone, transcribe locally, and insert clean text at the active cursor. Default to Control-Space, allow remapping, and do not claim to replace or reliably intercept the Fn key. Capture 16 kHz mono WAV with AVAudioEngine and show a compact recording and transcribing status pill. On release, invoke whisper.cpp with a configurable model path and no network request. Insert with the pasteboard plus Cmd-V, restore the previous clipboard, and leave the text copied when direct insertion cannot be verified. Keep the last 20 transcripts locally with timestamps, copy, retry, delete, and save-as-note actions. Save notes as plain Markdown under ~/Documents/YapsDIY and never hide content in an opaque database. Add a small notes window with create, edit, full-text filename/body search, and a recent-notes list. Add read-aloud for the current note using NSSpeechSynthesizer with voice, rate, pause, resume, and stop controls. Add a custom vocabulary text file whose terms are passed to whisper.cpp as an initial prompt. Keep raw audio only when the user enables it; otherwise delete it after a successful transcript. Store settings in Application Support and make the Markdown vault easy to relocate and back up. Handle denied microphone or Accessibility permission with clear instructions and a retry button. Include visible idle, recording, transcribing, success, and recoverable error states. Add focused tests for settings, history limits, vault file safety, clipboard restoration, and transcription command construction. Add one smoke test that injects a fixture WAV and proves a transcript becomes a Markdown note. Create a README covering setup, model download, permissions, data locations, privacy, backup, and limitations. Do not add accounts, billing, telemetry, analytics, cloud sync, or hidden network calls. Deliberately leave out Windows, Linux, Android, iOS, mobile keyboards, meetings, diarization, captions, voice cloning, media tools, browser capture, and sync. Finish by running the tests and build, fixing failures, 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 Yaps 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
People do not pay for a single prompt wrapped in a hotkey. They pay for one maintained product that joins five native platforms, mobile keyboards, reliable system-wide insertion, packaged local AI models, synced Markdown notes, browser capture, read-aloud, transcription, voice, and media workflows without making them assemble and operate each piece.
xnative parity across macOS, Windows, Linux, Android, and iOS
xreliable Fn and global-shortcut capture plus cursor insertion across native, browser, terminal, and Electron text surfaces
xmobile keyboards, browser capture, a Markdown vault, and desktop-to-mobile note sync working as one system
xbundled and warmed local runtimes for dictation, cleanup, TTS, transcription, diarization, translation, voice, and media tools
xinstallers, model downloads, updates, permissions UX, performance tuning, recovery, and cross-platform regression testing
share on X ↗"I just replaced Yaps ($15/mo) with one prompt"
Yaps pricing
pro$15/mo · monthly · $180/yr
free tierThe free plan is Android-only and includes on-device voice typing, voice notes, and two read-aloud voices with no account.
verified 2026-08-10 · source ↗
Is Yaps free?
The free plan is Android-only and includes on-device voice typing, voice notes, and two read-aloud voices with no account. Paid is Pro at $15/mo (checked 2026-08-10).
Vibecode Yaps
Kinda. The core of Yaps is buildable in a weekend with the prompt on this page, but there are real gaps: native parity across macOS, Windows, Linux, Android, and iOS, reliable Fn and global-shortcut capture plus cursor insertion across native, browser, terminal, and Electron text surfaces. Read the honest list above before committing.
How much does Yaps cost?
Yaps costs about $15/month (Pro, checked 2026-08-10), which is $180 per year.
What do I lose by replacing Yaps?
Honestly: native parity across macOS, Windows, Linux, Android, and iOS; reliable Fn and global-shortcut capture plus cursor insertion across native, browser, terminal, and Electron text surfaces; mobile keyboards, browser capture, a Markdown vault, and desktop-to-mobile note sync working as one system; bundled and warmed local runtimes for dictation, cleanup, TTS, transcription, diarization, translation, voice, and media tools; installers, model downloads, updates, permissions UX, performance tuning, recovery, and cross-platform regression testing. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Yaps?
Yes: whisper.cpp (The local speech-to-text engine that makes the personal dictation core realistic.). Using prior art is also vibecoding; the prompt is for when you want it exactly your way.