moeen-mahmud

On-device AI processing pipeline for Remen — model lifecycle, LLM prompts, tag/title/classify generation, queue management, and react-native-executorch integration.

Remen codebase architecture — file structure conventions, module patterns, component organization, and coding standards. Must-read before making any structural changes.

Remen SQLite database — schema, migrations, CRUD operations, query patterns, and expo-sqlite usage.

react-native-executorch integration guide — model loading, API surface, lifecycle management, quantization, and device optimization for Remen.

Remen search and retrieval system — semantic search, keyword search, temporal parsing, query NLP, and result ranking.

Build, package, and publish TermHeat to npm — the full release checklist from preflight through bun build --target=node, bin shebang, npm pack inspection, Node smoke test, publish, and git tag. Use this for any release, publish, version-bump, npm-packaging, or "ship it" task in this repo, including the first v1.0.0 publish (Day 3 of PLAN.md) and every roadmap release after it.

Add or modify a TermHeat CLI flag the repo's way — the five files that must change together (commands.ts, schema.ts, args.ts, index.tsx, args.test.ts) and the conventions each one follows. Use this whenever adding a new flag or option (e.g. --export, --year, --status, --no-animation), renaming a flag, changing a flag's argument handling, or when a task mentions argv, parseArgs, CommandMaps, or CLI options in this repo.

Add a new color theme (palette) to TermHeat following the repo's theme registry conventions — THEMES const, THEME_MAP, hex format rules, and the live-verification pass. Use this whenever adding, tweaking, or reviewing a theme or palette, when a contributor PR adds one, or when a task mentions colors, palettes, THEME_MAP, FIRE_RAMP, or scaleHex in this repo. Themes are the project's

Run and visually verify the TermHeat TUI end-to-end — interactive PTY testing with simulated keypresses, non-TTY pipe checks, exit-code verification, and the error-state checklist. Use this whenever you need to confirm a change actually works in the running app (not just unit tests), before committing rendering/animation/CLI changes, when asked to "run it", "test it live", "verify", or "smoke test" TermHeat, and when the built-in verify or run skills look for a project-specific recipe.