Vidyard

Build me a focused screen recording, walkthroughs and product demos workflow for the personal core of Vidyard. Requirements:

- Use Tauri 2, React, TypeScript, ffmpeg, and SQLite. Model recordings, transcript segments, notes, speakers, and export files; store source IDs and timestamps for each.
- Paid product context: Record personalized sales videos and organize them locally for manual sending. Build only this DIY scope: Record personalized sales videos by capturing a screen or window with microphone audio, trim and annotate key moments, organize the files locally, and export shareable videos for manual sending.
- Show an always-visible recording timer and make stop available from the tray.
- Create a non-destructive trim view with crop, zoom, cursor highlight, and text callouts.
- Render locally through ffmpeg with sensible H.264 and WebM presets. Generate a poster frame, transcript, and Markdown summary beside each video.
- Use a desktop window with source import, a work list, and result export. Required input or access: macOS or Windows screen-recording permission; microphone permission.
- Recovery: If macOS or Windows screen-recording permission is unavailable, keep the source record and show a recoverable error instead of a fabricated result.
- Acceptance: with one labelled sample, show the input, saved intermediate state, and exported result; verify this invariant: Denying screen or microphone permission must not create an empty success artifact; audio and video durations must remain aligned.
- Out of scope: video hosting, viewer identity, CRM integrations, team analytics, and sales workflows; instant hosted sharing. Keep this a personal, inspectable workflow.
- Include a README with setup, a sample input, required keys or permissions, data location, and the supported scope.

# AGENTS.md — Build guide for Vidyard

## Project scope
Record personalized sales videos by capturing a screen or window with microphone audio, trim and annotate key moments, organize the files locally, and export shareable videos for manual sending.

Catalogue verdict: no. A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Vidyard, record personalized sales videos and organize them locally for manual sending. The hard boundary is video hosting, viewer identity, crm integrations, team analytics, and sales workflows, plus capture polish, hosting, and collaboration.
Use the implementation prompt below to define the deliverable. Complete each phase's acceptance checks before extending the scope.

## Working agreement
- Inspect the repository and its existing instructions before choosing paths, dependencies or commands. Keep one coherent stack and explain changes to the proposed architecture.
- Plan a vertical slice that accepts a real input and produces the useful output described below. Persist only the state the prompt calls for; respect memory-only and upstream-managed workflows. Use fixtures only when they are clearly labelled.
- After scaffolding, document the actual install, development, check and build commands in README and keep them synchronized with the package or project manifest. Do not report commands as successful unless they ran.
- Work in small steps. At handoff, list implemented flows, checks actually performed, remaining blockers, and any credentials or provider setup the owner must supply.
- Do not publish, spend money, contact customers, delete source data or run irreversible migrations without the project owner's authorization.

## Prerequisites
- macOS or Windows screen-recording permission
- microphone permission
- ffmpeg
- local disk space

## Stack and architecture
- Use Tauri 2, React, TypeScript, ffmpeg, and SQLite.
- Model recordings, transcript segments, notes, speakers, and export files; store source IDs and timestamps for each.
- Interface for this screen recording, walkthroughs and product demos workflow: a desktop window with source import, a work list, and result export.

## Security and data integrity
- If macOS or Windows screen-recording permission is unavailable, keep the source record and show a recoverable error instead of a fabricated result.
- Validate imported records and file paths; keep user data within the storage location named in the prompt.
- State the practical limit: video hosting, viewer identity, CRM integrations, team analytics, and sales workflows.

## Agent implementation rules
- Project rule, data: Model recordings, transcript segments, notes, speakers, and export files; store source IDs and timestamps for each.
- Project rule, behavior: Show an always-visible recording timer and make stop available from the tray.
- Project rule, recovery: If macOS or Windows screen-recording permission is unavailable, keep the source record and show a recoverable error instead of a fabricated result.

## Optional agent skills and references
No installable skill is listed for this guide; use the project rules and the stack documentation.

Read the linked SKILL.md and its dependencies before adding a skill. Select only the skills matching this project's runtime and task; their documentation does not supply API access, credentials or approval to perform external actions. Pin the reviewed revision where the tool supports it. Follow the chosen agent's documented project-level installation mechanism.

## Distribution ideas
These are optional planning notes. Obtain the owner's approval before publishing or contacting anyone.
- Demonstrate this screen recording, walkthroughs and product demos operation with sample or user-owned data: Show an always-visible recording timer and make stop available from the tray.
- Show a concrete result or export: Generate a poster frame, transcript, and Markdown summary beside each video.
- State the practical limit: video hosting, viewer identity, CRM integrations, team analytics, and sales workflows.

## Engineering roadmap
1. Phase 1, architecture and data: Use Tauri 2, React, TypeScript, ffmpeg, and SQLite. Model recordings, transcript segments, notes, speakers, and export files; store source IDs and timestamps for each.
2. Phase 2, implement: Show an always-visible recording timer and make stop available from the tray.
3. Phase 3, implement: Create a non-destructive trim view with crop, zoom, cursor highlight, and text callouts.
4. Phase 4, review and output: Render locally through ffmpeg with sensible H.264 and WebM presets. Generate a poster frame, transcript, and Markdown summary beside each video.
5. Phase 5, recovery and acceptance: If macOS or Windows screen-recording permission is unavailable, keep the source record and show a recoverable error instead of a fabricated result. Verify this invariant with a saved fixture: Denying screen or microphone permission must not create an empty success artifact; audio and video durations must remain aligned. State the practical limit: video hosting, viewer identity, CRM integrations, team analytics, and sales workflows.

## Paid-product capabilities outside this build
- video hosting, viewer identity, CRM integrations, team analytics, and sales workflows
- instant hosted sharing
- viewer analytics
- team libraries
- cross-device capture

## Implementation prompt
Build me a focused screen recording, walkthroughs and product demos workflow for the personal core of Vidyard. Requirements:

- Use Tauri 2, React, TypeScript, ffmpeg, and SQLite. Model recordings, transcript segments, notes, speakers, and export files; store source IDs and timestamps for each.
- Paid product context: Record personalized sales videos and organize them locally for manual sending. Build only this DIY scope: Record personalized sales videos by capturing a screen or window with microphone audio, trim and annotate key moments, organize the files locally, and export shareable videos for manual sending.
- Show an always-visible recording timer and make stop available from the tray.
- Create a non-destructive trim view with crop, zoom, cursor highlight, and text callouts.
- Render locally through ffmpeg with sensible H.264 and WebM presets. Generate a poster frame, transcript, and Markdown summary beside each video.
- Use a desktop window with source import, a work list, and result export. Required input or access: macOS or Windows screen-recording permission; microphone permission.
- Recovery: If macOS or Windows screen-recording permission is unavailable, keep the source record and show a recoverable error instead of a fabricated result.
- Acceptance: with one labelled sample, show the input, saved intermediate state, and exported result; verify this invariant: Denying screen or microphone permission must not create an empty success artifact; audio and video durations must remain aligned.
- Out of scope: video hosting, viewer identity, CRM integrations, team analytics, and sales workflows; instant hosted sharing. Keep this a personal, inspectable workflow.
- Include a README with setup, a sample input, required keys or permissions, data location, and the supported scope.

## Completion evidence
Demonstrate the prompt's acceptance scenarios against the scoped workflow. Include setup from a clean checkout and failure recovery. Check persistence across restart and export/restore only for the state the prompt says to store; for memory-only tools, confirm that temporary content is discarded as specified. Record actual results and remaining limitations. A detailed plan alone does not establish a working replacement.