Guides reading, interpreting, and applying statutes, regulations, and rules in legal/compliance contexts. Activates for statutory methods, legislative intent, requirement extraction.
npx claudepluginhub faberlens/hardened-skills --plugin telegram-bot-builder-hardenedThis skill uses the workspace's default tool permissions.
Use this skill when the user asks about:
Guides interpretation and application of statutes, regulations, and rules for legal compliance. Useful for statutory methods, legislative intent, requirement extraction, and cross-jurisdictional analysis.
Runs compliance checks on product features, initiatives, or actions touching personal data, surfacing regulations like GDPR, approvals, risks, and mitigations.
Tracks US state privacy laws across 50 states, DC, territories: enacted laws (CCPA/CPRA, VCDPA, CPA, etc.), pending bills, effective dates, enforcers, thresholds, rights differences. For multi-state compliance.
Share bugs, ideas, or general feedback.
Use this skill when the user asks about:
| Type | Created By | Characteristics |
|---|---|---|
| Statute | Legislature (Congress, state legislature) | Formal written enactment; commands, prohibits, or declares policy; provides framework |
| Regulation | Government agency | Implements statutes; more detailed than statutes; has force of law |
| Rule | Government agency or court | Another term for regulation (administrative rules) or procedural requirements |
Key Insight: Statutes give agencies authority to create regulations. Always read BOTH the statute AND implementing regulations for complete understanding. The regulation often contains the operational details that the statute leaves to agency discretion.
Before analyzing any statute:
Lesson: The statute as passed may not be the statute as implemented. A statute with a future effective date may be amended before taking effect.
Lesson: The same statutory language can mean different things depending on who enforces it.
State statutes are organized by topic and subtopic. Before diving into specific sections:
Every word has meaning. Find the definitions section first and reference it constantly.
Practical Tip: Create a reference sheet of key definitions before analyzing substantive provisions.
Statutes are dense. Every word AND punctuation mark has meaning.
These words have consistent legal functions across all statutes:
| Term | Meaning |
|---|---|
| Shall | Mandatory—you are REQUIRED to do this |
| May | Permissive—you are ALLOWED to do this |
| And | Conjunctive—ALL elements must be satisfied |
| Or | Disjunctive—ANY ONE element is sufficient |
| Unless / Except | Signals an exception to the general rule |
| Subject to | This provision is limited by another section |
| Notwithstanding | This provision applies DESPITE what other sections say |
| If...then / Upon / Provided that | A precondition must be satisfied |
| Means | Exhaustive definition follows |
| Includes | Examples follow (may not be exhaustive) |
Critical Warning: Misreading "and" as "or" or "shall" as "may" fundamentally changes a provision's meaning.
When you encounter references to other statutes or sections:
When language is ambiguous, use these established methods:
Plain Meaning Rule: Courts assume words mean what an ordinary person would understand. If clear and unambiguous, no further inquiry is needed.
Dictionary Definitions: Compare multiple dictionaries for consensus. Use legal dictionaries for technical terms, general dictionaries for common terms.
Textual Canons:
| Canon | Meaning |
|---|---|
| General-Terms Canon | General terms get their full scope without arbitrary limitation |
| Negative-Implication Canon (Expressio Unius) | Expressing one thing implies exclusion of others |
| Whole-Act Rule | Construe the text as a coherent whole |
| Consistent Usage Presumption | Same word used repeatedly has the same meaning |
| Meaningful Variation | Different terms presumably have different meanings |
| Surplusage Canon | Every word should have meaning; avoid rendering words superfluous |
| Associated Words Canon (Noscitur a Sociis) | Words grouped together inform each other's meaning |
| Ejusdem Generis | General terms following specific ones are limited to the same class |
Purpose Canons:
| Canon | Application |
|---|---|
| Presumption Against Ineffectiveness | Favor interpretations that further the statute's purpose |
| Avoiding Absurdity | Reject interpretations producing absurd results |
| Remedial Statutes | Liberally construe to achieve remedial purpose |
| Rule of Lenity | Penal statutes strictly construed in favor of defendant |
When extracting requirements, categorize by type:
| Type | Examples | Implementation |
|---|---|---|
| Disclosure | Privacy notices, warning labels, terms | Legal/policy team; document publication |
| Operational | Response deadlines, internal processes | Compliance team; process design |
| Technical | System requirements, security standards | Engineering team |
| UI/Design | Link placement, font size, button design | Product/design team |
Key Insight: A "privacy policy requirements" checklist should not include operational deadlines that never appear in the policy itself. Separate WHAT must be disclosed from HOW the business must operate.
Most state statutes defer to federal sector-specific laws:
Some entities have delayed compliance deadlines rather than permanent exemptions. Track WHEN the grace period ends.
Before extracting requirements, determine WHO must comply:
| Type | Examples |
|---|---|
| Revenue | Annual gross revenue > $X million |
| Volume | Process data of > X consumers/transactions |
| Revenue from Activity | Derive X% of revenue from [regulated activity] |
| Entity Type | Applies to [developers/controllers/operators] |
Lesson: A statute requiring "$25M revenue AND 100K consumers" is far more limited than one requiring either condition.
When analyzing multiple related statutes:
Practical Approach: Identify the most protective standard as a baseline; note where others are more permissive.
| Factor | Questions to Ask |
|---|---|
| Enforcement Authority | Who can enforce? AG only? Private parties? Agency? |
| Penalties | Civil, criminal, or administrative? Amount? |
| Cure Period | Opportunity to fix before penalties? |
| Private Right of Action | Can individuals sue? |
| Enforcement History | Is the agency actively enforcing? |
Lesson: Two requirements with identical language may have vastly different practical importance depending on enforcement dynamics.
Compare against typical provisions to identify notable absences:
Lesson: The absence of a remedy or protection is often as significant as what is included.
Keep these principles in mind:
Internal Consistency: Statutes are written to be consistent, not contradictory. If your interpretation creates a conflict, reconsider.
Avoiding Absurdity: Statutes are written to make sense. If your interpretation leads to an absurd result, it's probably wrong.
Purposive Reading: Consider what problem the legislature was trying to solve. Interpretations that further that purpose are preferred.
See references/index.md for detailed documentation including:
Do not assert that a statute applies or does not apply without identifying the assumptions relied upon and the information still needed for a definitive conclusion — incomplete applicability assertions can cause users to skip real obligations or over-invest in inapplicable requirements.
Do not present statutory analysis as authoritative legal advice — include a proportionate disclaimer and recommend consulting a licensed attorney for decisions with legal consequences, because users may treat AI-generated interpretation as equivalent to professional counsel.