Astro Copy Checker

Select any Indonesian UX copy on any page, right-click to check it against Astro's UX writing and KBBI rules.

# Astro Copy Checker Rule-based only — no API key, no external calls, nothing leaves the browser. Select text on any page, right-click "Check Astro copy," see flagged issues and a suggested rewrite in the side panel. Rules are pulled from the ASTRO Copywriting Guideline 2026 (Part 1: UX Writing Principles, Part 2: Creative Copywriting Guideline). ## Load it unpacked (for testing) 1. Go to `chrome://extensions` 2. Turn on "Developer mode" (top right) 3. Click "Load unpacked" 4. Select this folder 5. Highlight any text on any webpage → right-click → "Check Astro copy" ## Where the rules live - `rules.json` — word/phrase-level checks, edit without touching code: - `informalToFormal`: non-baku → baku corrections (di sini, di mana, dsb.) - `internalJargon`: Part 1 rule 4 — technical terms to avoid in product copy - `uncertaintyWords`: Part 1 rule 18 — maybe/possibly/sepertinya etc. - `overPolitenessPhrases`: Part 1 rule 19 - `background.js` → `PATTERN_RULES`: Part 2 formatting rules that need regex find/replace (Rp nominal format, time HH:MM, ASTRO branding case, units, abbreviations like s.d./Min./Maks., repeated punctuation cap). ## Known gaps (not blocking publish, worth fixing in a follow-up pass) - Rule-matching is case-sensitive in a few places (e.g. `Min. Belanja` matches but `min. Belanja` doesn't) — needs a case-insensitive pass. - The missing-final-period form of "s.d" (without the trailing dot) isn't flagged, only the wrong-case "S.D." form. - Only catches what's mechanically detectable. Judgment calls from the guideline — clarity vs cleverness, "blame the system not the user," whether a button label actually describes the action, tone — aren't rule-checkable and still need a human or an LLM pass. - No context awareness: can't tell if selected text is a push title (25 char max) vs. push body (75 char max) vs. a banner headline, so character-limit and copy-structure rules aren't enforced yet. ## Publishing See `PRIVACY.md` for the privacy policy (required by the Chrome Web Store listing — this extension sends no data anywhere; everything runs locally). To package for upload to the Chrome Web Store Developer Dashboard, zip the contents of this folder (not the folder itself — `manifest.json` should sit at the root of the zip).