Focusmate

Build me a focused virtual coworking workflow for the personal core of Focusmate. Requirements:

- Use exactly this stack: Tauri 2 + React + TypeScript + SQLite. Model local triggers, rules, permissions, action history, and settings; keep stable source IDs and timestamps.
- Paid product context: Scheduled one-to-one virtual coworking sessions for accountability. Build only this DIY scope: Build a local desktop utility that captures the essential virtual coworking workflow with keyboard-first controls and local storage.
- For virtual coworking, define one explicit local trigger and its permitted action scope.
- Run the action with a visible preview and persist the user-controlled configuration.
- Show recent actions, allow undo where possible, and export settings.
- Use a desktop window with source import, a work list, and result export. Required input or access: macOS, Windows, or Linux development machine; Local filesystem access and OS permissions.
- Acceptance: with one labelled sample, show the input, saved intermediate state, and exported result; verify this invariant: A denied OS permission or unavailable target must leave user data unchanged and show what permission is missing.
- Out of scope: deep operating-system edge-case coverage; polished shortcuts and accessibility. 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 Focusmate

## Project scope
Build a local desktop utility that captures the essential virtual coworking workflow with keyboard-first controls and local storage.

Catalogue verdict: no. Do not mistake the interface for the product. Focusmate's durable value is polish, OS integration, which a solo one-shot build cannot reproduce responsibly. The prompt therefore builds only the closest honest personal consolation tool.
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, Windows, or Linux development machine
- Node.js 22 and Rust toolchain
- Local filesystem access and OS permissions
- Explicit README warning that this is a consolation build, not a production replacement

## Stack and architecture
- Use exactly this stack: Tauri 2 + React + TypeScript + SQLite.
- Model local triggers, rules, permissions, action history, and settings; keep stable source IDs and timestamps.
- Interface for this virtual coworking workflow: a desktop window with source import, a work list, and result export.

## Security and data integrity
- A denied OS permission or unavailable target must leave user data unchanged and show what permission is missing.
- Validate imported records and file paths; keep user data within the storage location named in the prompt.
- State the practical limit: deep operating-system edge-case coverage.

## Agent implementation rules
- Project rule, data: Model local triggers, rules, permissions, action history, and settings; keep stable source IDs and timestamps.
- Project rule, behavior: For virtual coworking, define one explicit local trigger and its permitted action scope.
- Project rule, recovery: A denied OS permission or unavailable target must leave user data unchanged and show what permission is missing.

## 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 virtual coworking operation with sample or user-owned data: For virtual coworking, define one explicit local trigger and its permitted action scope.
- Show a concrete result or export: Show recent actions, allow undo where possible, and export settings.
- State the practical limit: deep operating-system edge-case coverage.

## Engineering roadmap
1. Phase 1, architecture and data: Use exactly this stack: Tauri 2 + React + TypeScript + SQLite. Model local triggers, rules, permissions, action history, and settings; keep stable source IDs and timestamps.
2. Phase 2, implement: For virtual coworking, define one explicit local trigger and its permitted action scope.
3. Phase 3, implement: Run the action with a visible preview and persist the user-controlled configuration.
4. Phase 4, review and output: Show recent actions, allow undo where possible, and export settings.
5. Phase 5, recovery and acceptance: Verify this invariant with a saved fixture: A denied OS permission or unavailable target must leave user data unchanged and show what permission is missing. State the practical limit: deep operating-system edge-case coverage.

## Paid-product capabilities outside this build
- deep operating-system edge-case coverage
- polished shortcuts and accessibility
- vendor-maintained updates
- bank, payment, tax, and reconciliation integrations
- cross-device sync

## Implementation prompt
Build me a focused virtual coworking workflow for the personal core of Focusmate. Requirements:

- Use exactly this stack: Tauri 2 + React + TypeScript + SQLite. Model local triggers, rules, permissions, action history, and settings; keep stable source IDs and timestamps.
- Paid product context: Scheduled one-to-one virtual coworking sessions for accountability. Build only this DIY scope: Build a local desktop utility that captures the essential virtual coworking workflow with keyboard-first controls and local storage.
- For virtual coworking, define one explicit local trigger and its permitted action scope.
- Run the action with a visible preview and persist the user-controlled configuration.
- Show recent actions, allow undo where possible, and export settings.
- Use a desktop window with source import, a work list, and result export. Required input or access: macOS, Windows, or Linux development machine; Local filesystem access and OS permissions.
- Acceptance: with one labelled sample, show the input, saved intermediate state, and exported result; verify this invariant: A denied OS permission or unavailable target must leave user data unchanged and show what permission is missing.
- Out of scope: deep operating-system edge-case coverage; polished shortcuts and accessibility. 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.