Cline rules

1## Brief overview – Communication style
2 
3- Be concise but explicit.
4- Use plain language; avoid unnecessary jargon.
5- When asking for clarification, phrase as a direct question.
6- Provide context and expected outcome.
7 
8## Brief overview – Development workflow
9 
10- Explore the repository structure first (list files, read README).
11- Identify the relevant application and its entry point.
12- Check package.json scripts for dev/build/test commands.
13- Run the app with `bun run --cwd <app> dev` to verify it starts.
14- Use `bun build` to produce a production bundle.
15- Run tests with `bun test`.
16- Iterate quickly using the REPL to experiment.
17 
18## Brief overview – Coding best practices
19 
20- Follow existing naming conventions (e.g., `lowercase-with-dashes` for files).
21- Keep functions small and single‑purpose.
22- Add TypeScript types for public APIs.
23- Use `console.error` for failures, `console.log` for debug (but prefer structured logging).
24- Prefer immutability and pure functions where possible.
25- Write unit tests for new logic; aim for >80% coverage on new code.
26 
27## Brief overview – Project context
28 
29- Monorepo managed by Bun, TypeScript, Yarn‑compatible workspaces.
30- Two main apps: `fuel-advisor-bot` (Telegram bot) and `tablo-crawler` (scraper).
31- Shared configs live under `packages/`.
32- Infrastructure is defined in `infra/` (Docker, Ansible, Watchtower).
33- All apps must ship `Dockerfile`, `Dockerfile.optimized`, `compose.yml`, `.env.example`, `deploy.vars.yml`.
34 
35## Brief overview – Additional guidelines
36 
37- When in doubt, read the relevant source file rather than assuming behavior.
38- If a command fails, inspect the error output before proceeding.
39- Keep the task‑progress checklist updated after each step.
40