CLAUDE.md@examples/all-tiers/billing · git:20261007.c39ab3a · 2026-10-07 · sha256 71de5ec111a4937c
CLAUDE.md@examples/all-tiers/billing git:20261007.c39ab3aA
Immutable. This exact content never changes and is served at /api/v1/blob/71de5ec111a4937c.
<!-- VIBETAGS-START -->
<!-- # Generated by VibeTags | https://github.com/PIsberg/vibetags -->
<project_guardrails>
<locked_files>
<file path="com.example.alltiers.billing.InvoiceController.invoiceNumber(long)">
<reason>The invoice number format is on partner contracts; changing it breaks reconciliation</reason>
</file>
</locked_files>
<audit_requirements>
<file path="com.example.alltiers.billing.InvoiceController">
<vulnerability_check>SQL Injection</vulnerability_check>
<vulnerability_check>Broken Access Control</vulnerability_check>
</file>
</audit_requirements>
<rule>
If you are asked to modify any file listed in <audit_requirements>, you must first silently analyze your proposed code for the listed <vulnerability_check> items. If your code introduces these vulnerabilities, you must rewrite it before displaying it to the user.
</rule>
<pii_guardrails>
<element path="com.example.alltiers.billing.InvoiceController.billingEmail">
<reason>Billing email identifies a natural person; never log it or echo it back</reason>
</element>
</pii_guardrails>
<rule>
Never include runtime values of elements listed in <pii_guardrails> in logs, console output, external API calls, test fixtures, mock data, or code suggestions. Treat their values as strictly confidential.
</rule>
<core_elements>
<element path="com.example.alltiers.billing.LedgerEntry">
<sensitivity>critical</sensitivity>
<note>Every monetary total in the system is derived from these rows</note>
</element>
</core_elements>
<rule>Elements listed in <core_elements> are well-tested core components. Make changes with extreme caution and verify comprehensive test coverage before proposing modifications.</rule>
<scoped_rules>
<note>Detailed per-element guardrails for the elements below live in scoped rule files that load automatically when the matching source file is opened. An elements entry lists names under a shared prefix: in="a.b" listing C, D means a.b.C and a.b.D. Unless an entry carries an explicit path, its file is .claude/rules/{path, every non-alphanumeric character replaced by '-'}.md. Consult the file before modifying an element.</note>
<element path="com.example.alltiers.billing.InvoiceController" rules=".claude/rules/api-endpoints.md"/>
<elements in="com.example.alltiers.billing" rules=".claude/rules/domain-model.md">LedgerEntry, TaxRules</elements>
<element path="com.example.alltiers.billing.PaymentGateway" rules=".claude/rules/payments.md"/>
</scoped_rules>
<rule>When you work on any element listed in <scoped_rules>, open its referenced rule file and apply the guardrails there. The rule files are the authoritative source for those elements.</rule>
</project_guardrails>
<rule>Never propose edits to files listed in <locked_files>.</rule>
<!-- VIBETAGS-END -->