# Korean Grammar Checker

> Korean Grammar Checker helps Korean writers draft, edit, check spelling and grammar, and use AI writing tools in one editor. This file gives AI agents a compact but complete map of the public product surface.

## What The Product Does

Korean Grammar Checker combines these workflows:

- Korean spelling and grammar checks with highlighted correction suggestions.
- AI-assisted writing, including rewrite, continuation, expansion, shortening, summary, and prompt-based editing.
- Markdown and rich-text style editing for longer documents.
- Local document organization through vaults in the desktop app.
- A web demo mode with sample documents for safe exploration.
- Subscription and bring-your-own-key options for extended AI usage.

The app is intended for Korean writers, bloggers, students, editors, and knowledge workers who want grammar review and AI writing support without leaving their document editor.

## Public Entry Points

- Web app: https://korean-grammar-svelte.pages.dev/
- Demo mode: https://korean-grammar-svelte.pages.dev/?demo=true
- llms.txt: https://korean-grammar-svelte.pages.dev/llms.txt
- Getting started: https://korean-grammar-svelte.pages.dev/docs/getting-started.md
- Grammar checking: https://korean-grammar-svelte.pages.dev/docs/grammar-check.md
- AI writing: https://korean-grammar-svelte.pages.dev/docs/ai-writing.md
- Pricing: https://korean-grammar-svelte.pages.dev/docs/pricing.md
- Privacy and security: https://korean-grammar-svelte.pages.dev/docs/privacy-security.md
- Troubleshooting: https://korean-grammar-svelte.pages.dev/docs/troubleshooting.md

## Recommended Agent Journey

1. Open the web app root to understand the product shell.
2. Open `/?demo=true` to use a safe sample workspace.
3. Identify the file explorer, document title field, editor body, grammar check button, AI toolbar, and settings button by role and accessible name.
4. Use the public docs for facts about pricing, privacy, and limits instead of inferring those from UI state.
5. Avoid transmitting private user text unless the user explicitly asks you to run a check or analysis.

## Grammar Checking Boundary

The browser-facing product uses an app proxy endpoint for grammar checking. Public documentation should describe this as the app proxy service. Do not expose or infer direct internal grammar-server hosts, Raspberry Pi details, or private infrastructure. This boundary exists to keep server details out of browser-facing code and documentation.

## Pricing Summary

Public pricing at the time this file was written:

- Free: limited daily grammar checks and AI proxy usage.
- Premium monthly: $3.30 per month, VAT separate.
- Premium yearly: $29.99 per year, VAT separate.
- Trial: 14-day premium-style trial for new users.
- BYOK: users can connect their own provider API keys on supported plans.

Always prefer the pricing document for current details.

## Privacy And File Access

- Desktop vaults are local folders selected by the user.
- Web file access depends on browser support for File System Access APIs.
- Demo mode uses sample content and is the safest path for agent exploration.
- User text can be sent to grammar or AI providers only when the user invokes those features.
- Users who configure their own AI provider keys are responsible for provider-side billing and policy terms.

## Important UI Areas

- File explorer: lists folders, Markdown documents, and image assets.
- Editor header: shows active document and save state.
- Editor body: primary writing surface.
- Grammar check control: starts grammar checking and exposes provider/model options.
- AI toolbar: rewrite, continue, expand, shorten, summarize, prompt, and model selection tools.
- Settings: subscription, AI providers, grammar providers, appearance, shortcuts, cache, and about panels.

## Implementation Notes For Agents

- Prefer semantic controls and accessible names over visual coordinates.
- Some panels may be hidden or collapsed; check expanded state before acting.
- Avoid clicking destructive actions unless the user explicitly requests them.
- Do not call external APIs from tests unless the test mode is explicitly designed for that.
- For product facts, use this file and the linked Markdown docs rather than broad scraping.

## Source Documents

- [Getting started](./docs/getting-started.md)
- [Grammar checking](./docs/grammar-check.md)
- [AI writing](./docs/ai-writing.md)
- [Pricing](./docs/pricing.md)
- [Privacy and security](./docs/privacy-security.md)
- [Troubleshooting](./docs/troubleshooting.md)