This Skill is built on practical expertise in AI persona design, brand voice governance, character bible maintenance, dialogue QA, tone drift detection, and role-boundary review. It helps AI agents keep role, vocabulary, emotional range, relationship context, forbidden phrases, and channel fit consistent across support bots, sales assistants, companion bots, fictional characters, and long-running conversations.
Make a rule the assistant actually follows by moving it out of the prompt and into a hook that runs every time. When you have said the same thing three times and the behaviour still drifts, this is the fix. Covers which hook events carry the value, the exit-code rule that wedges sessions, how to test a hook with temporary settings so nothing is left behind, a skeleton that cannot crash your turn, and the escape hatch for when one does.
Guides, a 56-item checklist, a ready PR template, and a fill-in team policy for code review culture. Includes 10 good/bad comment pairs and 30 situational review comments, unified by a blocker/suggestion/nit/question/praise severity system.
This Skill is built around practical communication design, family-message tone control, AI guardrail writing, uncertainty labeling, and safe redirection for sensitive topics. It focuses on short parent-friendly wording, blame reduction, boundary-setting, fact-check reminders, and avoiding manipulative or overconfident replies.
Not every tradition treats the same wound: attention training is superb against rumination and useless against moral injury. REGULA identifies which of seven problems you're actually in, selects the tradition historically built for it, and writes you a Rule of Life: three daily anchors attached to moments already in your day, a weekly practice, a 30-day progression, a minimum that survives your worst week, and a printable card. No divine voice, no promises about outcomes.
Forces AI coding agents to read exports, callers, and shared utilities before touching any file — then restricts every edit to the declared scope, flags conflicting patterns for human resolution, and reports any file touched outside the boundary.
For one person publishing their own content on a schedule: describe your setup and get an operations kit that makes silent failures visible — a status board, a runbook with idempotent retry and queue-fallback patterns, an incident ledger, and a daily health-check specification.