#Agent rules for sigit-si

Rules for agents working in this repo and across the siGit / smbCloud codebases. Read this before writing code or docs.

#Repositories and the public boundary

Cardinal rule: sigit is public. Everything committed there is world-readable: code, comments, doc strings, tests, commit messages. Never put any of the following in the public repo:

• secrets, API keys, tokens, or credentials;
• the identity of the upstream model providers behind siGit Code Cloud, or the fact that any specific provider sits behind it;
• business strategy, pricing, or positioning;
• internal smbCloud auth mechanics (app_secret, validation flows, trust boundaries);
• customer names or internal infrastructure detail.

That material belongs in sigit-si (server and strategy) or sigit-app (desktop), which are private. When in doubt, put the explanation in a private skill and keep the public comment purely about what the code does.

#Writing for the public repo

• Keep comments and docs technical and neutral. Say what the code does, not why it is a good business.
• Strip AI-writing tells: no em dashes, no forced groups of three, no promotional or significance-inflating language, no "not just X but Y". Plain is correct for reference text.
• User- and client-facing error messages must not name a provider or echo upstream error bodies. Log the detail server-side; return something neutral.

#Branding

Names are case-sensitive: siGit Code (product), siGit Code Cloud (hosted tier), sigit (CLI and crate), smbCloud (company), Onde Cloud / Onde Inference (infrastructure), onde (crate). The public sigit repo has a branding skill with the full rules.

#Skills in this repo

• sigit-code: engineering reference for siGit Code and how it connects to the ecosystem (accounts, the cloud tier, cross-repo work).
• sigit-code-cloud: the hosted inference product: auth, tiers, backend selection, and the onde-cloud API behind it.
• smbcloud-auth: the auth service integration.
• sigit-app: the desktop client.
• deployment, design-system, local-environment: as named.

The public sigit repo carries its own skills (ai-assisted-coding, agent-client-protocol, tool-calling, branding, sigit-code-release). Those stay public-safe.

#Validation

• Rust (sigit, onde-cloud): cargo build, cargo test, cargo clippy.
• Rails (sigit-si): bundle exec rails routes, ruby -c on touched files, rails db:migrate when the schema changes.

#Common mistakes

• Putting strategy, a provider name, or a secret into the public sigit repo.
• Leaving AI-writing tells in public prose.
• Mixing the product, CLI, and company names.