docs(skill): add taos-development-skill (coding standards for contributing agents)

[jaylfc]

Your idea from the email thread: a taOS development skill plus soul.md so any contributing agent (Hermes, OpenClaw, your Skald agents, and others) writes code that lands right the first time. Push the two files here and we evolve them in-repo, and any of our agents can optimise them over time.

Where: .claude/skills/taos-development-skill/ (a SKILL.md plus your soul.md), alongside the existing impeccable / taste skills.

Purpose: carry taOS coding standards and conventions so a contributing agent gets it right first time, especially if its training data is outdated or it is a weaker model.

Please cover (acceptance criteria):

1. Cardinal rule: assume your training is stale. Verify version, branch, symbols, and which repos exist before acting; never invent version numbers, file paths, API routes, or flags. Weaker or older models may not know these exist, so give the exact commands to check each.
2. Orientation: the repos that exist (taOS, the rkllama fork, taos-website) and where code lives.
3. Gates and how to pass them locally first: compileall, pytest (3.12 and 3.13), doc-gate (invariants / diff-gate / managed-lint), and the SPA build.
4. Branch and PR flow: cut from origin/dev, small fixes to dev, larger via PR, never force-push a shared branch, fork-CI approval expectation.
5. Bot review discipline: wait for Kilo (authoritative) and CodeRabbit, then resolve every finding by either fixing it or replying with a one-line reason it is a non-issue; never defer or silently drop a finding, and do not blindly apply a suggestion you believe is wrong.
6. Release-train lockstep files and real pitfalls: the Regression: install-rknpu.sh generates incompatible rkllama.service after rkllama fix (#1529 resurfaced) #1730 --preload regression (never pin an unverified upstream ref), the uv.lock normalized-version gotcha, no em dashes in public text, no AI attribution.
7. A right-the-first-time pre-submit checklist.

Reference the canonical docs (CONTRIBUTING.md, docs/agent-coordination.md, CLAUDE.md, docs/doc-gate.toml) rather than duplicating them.

Loop: you push the first version from the profile you built, I add the house rules and fill gaps, then your agents pick it up. I already have a house-rules draft staged to fold in, so I can extend yours quickly once it lands. No rush, and shout if any of the scope is unclear. Over to @hognek.