// Writing/updating project documentation for RakuRaku IME (README, TODOs, LICENSE notices, AI-assistant guide files). Use when the user asks to update docs or rewrite user-facing text.
| name | docs-engineering |
| description | Writing/updating project documentation for RakuRaku IME (README, TODOs, LICENSE notices, AI-assistant guide files). Use when the user asks to update docs or rewrite user-facing text. |
| argument-hint | task description |
You are performing documentation tasks for RakuRaku IME (輕鬆輸入法).
| File | Purpose |
|---|---|
README.md | Project overview, attribution, licensing, setup instructions. |
LICENSE | GPL-3.0-or-later full text for the application. |
TODOs.md | Active feature backlog and completion tracking. |
GEMINI.md | Guidance for the Gemini AI assistant (project primer). |
CLAUDE.md | (may be added) Guidance for Claude Code. Follow the same tone as GEMINI.md if added. |
app/src/main/assets/gpl.txt | GPLv2 text bundled for the dictionary data. |
app/src/main/assets/ezphrase.txt | 輕鬆資訊 public license text bundled for the dictionary data. |
There is currently no PRIVACY-POLICY.md, NOTICES.md, or fastlane/ metadata. If the user asks to add any of those, confirm scope first — they are new artifacts, not updates.
The dictionary data (ezbig.utf-8.cin) was produced by:
Any user-facing doc that describes the dictionary must preserve this attribution and the dual license note (GPLv2 + 《輕鬆資訊「輕鬆輸入法大詞庫」公眾授權書》). See README.md for the canonical wording.
If the user asks for a third-party notices document, derive the contents from gradle/libs.versions.toml and app/build.gradle.kts. Do not invent library licenses — check each dependency's declared license before listing it.
Capture the four RakuRaku showcase screenshots on a connected device and refresh the fastlane metadata. Use when the user asks to take, update, or regenerate screenshots.
Release engineering tasks for RakuRaku IME — version bumping, building release APKs, tagging, and creating GitHub releases. Use when the user asks to prepare a release, bump version, tag, or build for distribution.
Commit code changes and push via Git. Use when the user asks to commit, push, or save their work to the repository.
Review code for quality, correctness, and security vulnerabilities. Use when the user asks to review code, audit for security issues, or check for bugs and anti-patterns.