Hermes skill atlas · software-development

fromdonna-project

Operating manual for the FromDonna product repo — scope, tools-only environment rule, hard rules, and how Chitti should work with Ojas.

What this skill is

Hermes procedural memory for one product codebase. Not a dump of chat turns, not the philosophy skill, not the retired legacy donna-project / Pi stack.

Holds

Durable how-tos

Repo identity, Drive folder, FromDonna group boundary
Environment = tools only (ICM)
Ojas operating conventions (plan / ship / debug)
Hard rules that prevent rework and anger triggers

Does not hold

Ephemera & retired stack

PR numbers, commit SHAs, temporary TODOs
Retired sandbox image ladders and legacy Worker inventory
Reference-library sprawl from the old skill
Unrelated personal/company resources inside the FromDonna group

Standing instruction: when a stable FromDonna workflow is discovered, patch this skill immediately.

Scope & boundaries

Default interpretation when someone is talking about FromDonna in the FromDonna Telegram group.

Surface	Meaning
Local	`/home/ubuntu/FromDonna`
GitHub	`https://github.com/ojassurana/FromDonna` · branch `main`
Drive	Folder still named `Donna` · id `1dj7DjcmUy-kDNCukwdwaSWKC6Uug73LM`
Telegram group	FromDonna → this project by default
Repo docs	`documentation/gateway/gateway.md`, `telegram.md`

Legacy donna-project and the old local /home/ubuntu/Donna stack are retired. Do not open old Donna Worker/sandbox runbooks for this work.

Architecture the skill encodes

Only the current non-negotiable product rule is kept here.

ICM

Environment = tools only

Agent access to environment/context is via tools + Worker/store routes
Never auto-inject AGENTS.md, CONTEXT.md, or other ICM text into user turns
Ojas owns prompting and bootstrap himself
“SDK” means tools only — not harness prompt hooks, not prompt-injection packages

Hard rules the skill enforces

Field minimalism. If Ojas lists N payload/identity fields, ship exactly those — no extras.
Describe then deploy by default. “Just tell me” / “don’t do anything yet” = explain only. Ship only on explicit go.
One step at a time for greenfield design. Only the single next action until he advances you.
Deletes need double confirmation. Exact delete list vs keep list, then wait for yes.
Short replies. 1–2 lines / bullets unless he asks for depth.

How Chitti is supposed to operate

Planning mode

Think → explain → wait. No code until greenlit. Extreme incrementalism = first step only.

Ship mode

Only on explicit ship / fix-prod / “just add it.” Commit/push main and deploy when that is the ask; don’t claim prod without real verification.

Debug mode

“Figure it out yourself” = iterate with real tools/logs; don’t bounce testing back to him first if you can unblock yourself.

Drive fast paths

Composio into Drive folder id 1dj7DjcmUy-kDNCukwdwaSWKC6Uug73LM. Reply as terse name → link.

Companion: donna-company-management — Donna decides workflows, ~60% proactive, ordinary-user usable, no-nudge, bias for connection. That skill is product “why”; this one is FromDonna “how.”