basaltbytes-skills

Produces human-sounding text that avoids detectable AI writing patterns. Activates on any writing task — tweets, emails, articles, bios, captions, reports, copy, messages, LinkedIn posts, cover letters, README files, or any content where the output must not read as AI-generated. Enforces banned vocabulary, structural variety, punctuation discipline, accuracy rules, and voice calibration. Use when the user says "write," "draft," "rewrite," "make this sound human," "anti-slop," "not AI," or any variation of wanting authentic-sounding output.

Generate an interactive, GitHub-styled single-file HTML walkthrough of a pull request or code change — UML-ish model diagram, fields & methods, views, wizards, security, and a Files-changed list. Use when the user asks to visualize, explain, or document a PR/diff/change, asks for a "code walkthrough" or "PR walkthrough", says "visualize this change", or wants a shareable HTML explainer. Odoo-focused but works for any codebase.

Basaltbytes coding-guidelines charter — always-valid domain modeling, functional-core architecture, typed-error discipline, idempotent workflows, observability, testing through real seams, and hygiene. Use when designing or reviewing domain models, value objects, or state machines, when parsing at API/DB/env boundaries (pydantic strict, Zod, branded/newtype ids), when structuring error handling or choosing test seams and mocks, or when code shows primitive obsession, validation inside function bodies, scattered rechecks, assert/non-null narrowing, or raw payloads flowing into domain functions.

Use when working on Odoo 19 server-side code or backend tests: Python models, ORM recordsets, fields/decorators, domains, SQL/cache, `__manifest__.py`, XML/CSV data, ACLs/rules, `sudo`, controllers, `@route`, `ir.cron`, JSON-2/XML-RPC, QWeb reports, `TransactionCase`, `HttpCase`, `Form`, tours, `start_tour`, or `--test-tags`. Not for web-client JS, Owl internals, Hoot, frontend assets, views, or widgets.

Use when working on Odoo 19 web-client customizations in JavaScript or arch XML: assets, `@odoo-module`, registries, services, systray/client actions, browser state, `patch(...)`, view descriptors, `js_class`, `searchModel`, modifiers, `options=`, XPath inheritance, built-in/custom views, field/view widgets, `standardFieldProps`, or `extractProps`. Not for backend ORM, Hoot tests, Owl internals, or generic JS/Owl.