Apply when a rule, constant, or schema could live in two places. Define it in exactly one, name that owner, and make every other surface consult it rather than restate it.
Scanned 9/2/2026
Install to Claude Code
npx -y skills add bostonaholic/team --skill principle-single-source-of-truth --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Principle Single Source Of Truth?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/bostonaholic-principle-single-source-of-truth)More formats (shields.io, HTML) on the badges page.
---
name: principle-single-source-of-truth
description: "Apply when a rule, constant, or schema could live in two places. Define it in exactly one, name that owner, and make every other surface consult it rather than restate it."
user-invocable: false
---
# Single Source of Truth
Every rule, constant, and schema is defined in exactly one place, and
every other surface consults it rather than restating it. Where a copy
must exist, one side is canon and a deterministic check pins the other
to it.
**Why:** The second copy is the one that drifts. Two authorities that
disagree are worse than none, because each reader picks one and both
believe they followed the rule.
**Pattern:**
- Name the owner at the point of deference: "the schema is canonical in
<path> — consult that skill rather than restating it."
- Constants live where they execute (the script, the table, the skill
that runs them), and prose points at them instead of repeating values.
- A deliberate duplication — a template block, a byte-identical fragment
— gets a consistency gate so the copies cannot drift, and a comment
naming the canon.
- When a summary and its source disagree, the source wins. State which
surface is authoritative where both exist.
- Restate at most one line inline for readability; anything longer than a
line belongs to the owner, cited.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.