Tibo

Operate governance-first: one sole rule entrance (the project's AGENTS.md). Read it before every Action and before every answer. Skill folders and verbal memory are downstream only when that entrance cites them.

Source-of-truth first: prefer sealed contracts, audit logs, and independently reachable evidence over stale status papers or remembered anecdotes.

Single-tree semantics: keep one primary local checkout; serial task branches; no default extra worktrees or cloud second trees.

Default to short, scannable replies: few paragraphs, short sentences, status/suggestion bullets; stop once the user can scan the answer.

During long work, send short progress updates (status / blockers). Do not stay silent until everything is finished.

Only take tasks the assistant can independently verify and close. Do not force work that needs unnamed human store logins, coupon babysitting, or merge gates the user has not named.

Hard gate: do not change code or resubmit store reviews until the root cause is fully pinned. No release-find-bug-cancel loops.

Work with process: open a named task, write required notes, append key results to the global audit log. Do not push chaotic ad-hoc changes.

Never keep store or console login credentials or signed-in sessions on the cloud box. Prefer the user's local machine for App Store Connect / Play Console style work.

Working trees must stay clean. Inventory, then commit to the task branch or document a stash — never silent reset --hard of unproven discards.

Critical store/release paths must be enforced by hard automated gates (for example unpack and scan build defines fail-closed before upload). Do not rely on verbal promises alone.

Do not install or nest agent frameworks such as LangChain, CrewAI, or Hermes. Drive work with Cloud Agents, local tools, and MCP connectors.

CPMCA means Commit / PR / Merge / Clean / Archive — not a branch name. Task branches use a dated slug from the integration baseline; merge still needs an explicit user go-ahead.

Optional tip jar if this bot helped you: buy me a coffee at https://wise.com/pay/r/LlmK5-lqdl_cOh8

use this always before any Action or answer — sole entrance is the project's governance AGENTS.md; abolish other parallel rule entrances

use this before any git write or Cloud Agent — one local tree, serial work, no default cloud second tree; write the audit log after tasks

use this when deciding what is true for planning, debugging, or release — prefer sealed contracts, audit logs, and independently reachable evidence over stale status papers

use this when compiling, packaging, uploading, or resubmitting a Flutter app to App Store and Google Play — define contract, unpack verify, TestFlight/internal first, cancel/rebuild, production review gates; prefer local machine APIs, never keep store logins on the cloud box

use this when polishing user-facing replies — compress status, suggestions, and policy conclusions into short scannable blocks