LegalTek.ai – AI-Powered Legal Solutions

    Nothing else in the world is so powerful as an idea whose time has come.

    — Victor Hugo
    All Training
    Epic Guide · Volume I · April 2026

    Claude for Legal Practice

    The Practitioner's Guide to the Meta Prompt Method and Structured Block Workflows

    ByMatt Mishak, Esq.·LegalTek.ai Monograph
    Not legal advice
    This guide is for general informational and educational purposes only. It is not legal advice, does not create an attorney-client relationship, and does not substitute for jurisdiction-specific counsel. LegalTek.ai is a technology company, not a law firm. Always verify citations against independent authoritative sources.

    The tutorials already on YouTube teach you to click buttons. They show you the pricing page, how to upload a PDF, and how to get Claude to build a personal website. That is fine for content creators and solo entrepreneurs picking a stack. This guide is not that.

    When a lawyer opens Claude, the stakes are different. A bad prompt does not mean a weird blog post. It means a flawed settlement demand, a missed suppression issue, a financial affidavit that exposes your client, or an RPC 1.1 problem waiting to surface at grievance. The features that matter are the quiet ones — the data training toggle, project isolation, Skills as codified SOPs, the connector permissions matrix, Extended Thinking on a close pretrial motion.

    Four governance frameworks sit underneath everything. COUNSEL for individual task decisions. G3M for firm-wide policy. ADAPT for tool rollout. OVRST for output oversight. We map all four to ABA Formal Opinion 512 and the Ohio Rules of Professional Conduct.

    Chapter 1

    Why Claude, and Why Now

    You have options. ChatGPT is the most famous. Gemini is the fastest. Copilot is in the office suite you already own. For most lawyers most of the time, I recommend Claude — for three reasons that matter to a practitioner.

    • Long context. The 200-page transcript, the 400-page financial production, the full Ohio Revised Code chapter — it does not flinch.
    • Citation discipline. When prompted correctly, Claude refuses to fabricate. For a lawyer, that refusal is a feature.
    • Anthropic's ethics posture. The vendor's own governance becomes part of your governance.
    Recommended Model Mix · Mishak Law Practice
    25%50%25%
    • Opus (Court / Client)
    • Sonnet (Internal)
    • Haiku (Triage)
    Chapter 2

    Setup & the Lawyer's Privacy Stack

    Setup is not setup. For a lawyer, setup is the first ethics decision. The default onboarding will ask whether you allow Anthropic to train on your conversations. Turn this off. There is no scenario where a practicing attorney should leave it on.

    Pick the plan
    Pro min · Team for firms
    Disable training
    Privacy → Toggle OFF
    Enable MFA
    Authenticator, not SMS
    Name workspace
    Firm name, not 'Test'
    Conflicts protocol
    Project naming convention
    The toggle rule
    Verify the data-training toggle is OFF at account creation, after every Claude update, and on a monthly cadence. Client data sent while the toggle was on is, in principle, already in the training pipeline.
    Chapter 3

    Model Selection for Legal Work

    Claude ships in three active sizes — Opus, Sonnet, Haiku. Picking the wrong one is the most common mistake I see. Lawyers either burn Opus credits on tasks Haiku could handle, or they use Haiku on a dispositive motion and wonder why the output is thin.

    TaskModelWhy
    Dispositive motion draftingOpusDeep reasoning, nuanced argument
    Appellate brief synthesisOpusMulti-source integration, citation discipline
    Settlement memorandumOpusClient-facing, stakes high
    Discovery response (1st pass)SonnetVolume work, structured output
    Deposition outlineSonnetLong context, predictable structure
    Client intake summarySonnetClear inputs, clean format
    Email triageHaikuSpeed, brevity, cost
    Template letter fillsHaikuMechanical substitution
    Practical rule
    If the output goes to a client, opposing counsel, or a court without further human editing beyond proofreading, start with Opus. If it returns to you for substantial revision, Sonnet. If it is scaffolding you will rewrite anyway, Haiku.
    Chapter 4

    Why Structured Blocks Beat Prose

    Most lawyers prompt Claude the way they write emails to a paralegal — conversational, context-heavy at the front, buried instructions in the middle, the actual deliverable mentioned in a P.S. This works sometimes. It fails when the matter is complex.

    The Meta Prompt Method replaces that with named structured blocks. Think of it as the difference between a rambling voicemail and a written research memo assignment.

    ✗ Prose Prompt
    • · Conversational opener
    • · Context scattered
    • · Task buried in middle
    • · Rules in a P.S.
    • · Format implicit
    → Draft you must rewrite
    ✓ Structured Block
    • · ROLE: explicit
    • · CONTEXT: labeled
    • · TASK: one sentence
    • · CONSTRAINTS: hard rules
    • · FORMAT: exact shape
    • · REFERENCE: labeled inputs
    → Draft you can use
    Chapter 5

    The Meta Prompt Anatomy

    Six blocks, in this order. Order matters. Claude reads linearly: foundational framing must come before the task, and rules must come before the shape of the output.

    ROLE
    Who Claude is
    CONTEXT
    Matter, jurisdiction, facts
    TASK
    The single deliverable
    CONSTRAINTS
    Hard rules, house style
    FORMAT
    Exact output shape
    REFERENCE
    Statutes, prior drafts
    Six blocks · order matters · CONSTRAINTS before FORMAT

    The canonical example — modify spousal support

    <ROLE>
    You are a senior Ohio domestic relations attorney
    preparing a motion to modify spousal support.
    </ROLE>
    
    <CONTEXT>
    Client: Obligor husband. Paying spousal support under a 2019
    decree. Original monthly obligation $2,500. Client involuntarily
    terminated from employment in February 2026. New employment
    obtained at 40% reduced compensation. Jurisdiction: Lorain County
    Court of Common Pleas, Domestic Relations Division.
    </CONTEXT>
    
    <TASK>
    Draft a Motion to Modify Spousal Support with supporting
    memorandum.
    </TASK>
    
    <CONSTRAINTS>
    Ohio state law only. Cite R.C. 3105.18 as the controlling
    modification statute. Identify and apply the substantial change
    of circumstances standard. Case names in italics. Full Bluebook.
    No hyphens, no em dashes. Do not invent case citations. If a
    supporting case is needed and you are not certain of it, flag
    that with a bracketed [VERIFY: SECOND SOURCE] note.
    </CONSTRAINTS>
    
    <FORMAT>
    1. Caption block (party names bracketed for fill)
    2. Motion heading
    3. Memorandum in Support
       a. Introduction
       b. Factual Background
       c. Law and Argument
       d. Conclusion
    4. Certificate of Service placeholder
    </FORMAT>
    Chapter 6

    Using Claude to Build Your Own Prompts

    The best prompt engineer for your firm is Claude itself. The meta-prompting loop turns a fuzzy intent into a production-grade structured block in three to five iterations.

    Describe intent
    Plain English, one paragraph
    Claude drafts blocks
    ROLE → REFERENCE
    You critique
    What's missing? Tighten.
    Claude revises
    Output v2
    Lock as Skill
    Save to firm library

    The meta-prompt seed

    <ROLE>
    You are a prompt engineer specializing in legal practice
    workflows. You write prompts in the Mishak Law Meta Prompt
    Method: ROLE, CONTEXT, TASK, CONSTRAINTS, FORMAT, REFERENCE.
    </ROLE>
    
    <TASK>
    I need a reusable prompt for the following recurring task:
    [DESCRIBE TASK IN ONE PARAGRAPH]. Draft the structured block
    prompt. Where I would need to paste matter-specific facts, use
    [BRACKETED PLACEHOLDERS]. After the prompt, list three
    critique questions I should answer to tighten it further.
    </TASK>
    
    <CONSTRAINTS>
    Ohio practice. Full Bluebook. Case names italics. No invented
    citations. Output the prompt inside a code block.
    </CONSTRAINTS>
    Chapter 7

    Projects as Matter Workspaces

    Projects are the single most underused feature in Claude for lawyers. A Project is a matter file. Persistent instructions, uploaded files, a conversation history — all scoped to one container.

    Project naming
    Use a consistent format: [PracticeArea] [Client Last Name] [Matter Short Name]. A domestic relations matter for the Marcum family becomes DR Marcum Divorce. Trivial intake, conflict checks, and archiving.

    Project Instructions template

    <ROLE>
    You are co-counsel on this matter. Junior but sharp. Your job is
    to help me draft, research, and think through issues in this case.
    </ROLE>
    
    <CONTEXT>
    Matter: [Case caption]
    Jurisdiction: [Court and division]
    Client: [Name, role in case]
    Practice area: [DR / PI / Criminal]
    Key issues: [2-3 bullet points]
    Our theory: [1-2 sentences]
    </CONTEXT>
    
    <CONSTRAINTS>
    Treat all matter facts as confidential and privileged.
    All legal citations in full Bluebook, Ohio state level when
    available. Case names in italics. No hyphens or em dashes.
    URLs go in an appendix, not inline.
    </CONSTRAINTS>
    Chapter 8

    Artifacts for Drafting

    Artifacts are Claude's persistent draft pane. They live alongside the conversation, version automatically, and survive iteration without losing your prior work. If you will paste it into Word or file it, generate it as an Artifact.

    Decision
    Will I file or send this?
    Request Artifact
    "Produce as an Artifact"
    Iterate in pane
    Versions tracked
    Export
    Copy → Word, archive
    When NOT to use Artifacts
    Short answers, single-paragraph summaries, exploratory Q&A. Reach for an Artifact only when the deliverable is a document.
    Chapter 9

    Skills as Codified SOPs

    A Skill is a packaged set of instructions Claude activates when a prompt matches its trigger. For lawyers, a Skill is a codified standard operating procedure. Once written, every Affidavit One, every demand letter, every QDRO follows the same shape forever.

    SKILL.md frontmatter
    Trigger description — what activates it
    SKILL.md body
    The instructions Claude follows
    Reference files
    Forms, templates, checklists

    Example trigger frontmatter — Ohio Affidavit One

    ---
    name: Ohio Affidavit One
    description: Use whenever the user asks for an Ohio domestic
      relations Affidavit of Income and Expenses (Affidavit One)
      for a divorce, dissolution, or post-decree matter.
    ---
    
    You are drafting an Ohio Affidavit One. Pull income from W2s
    and paystubs in the Project. Pull expenses from the client's
    budget worksheet. Use the official Lorain County form layout
    in /reference/affidavit-one-form.md. Round all figures to the
    nearest dollar. Mark every unverified entry with [CONFIRM].
    Chapter 10

    Connectors and MCP

    Connectors (built on the Model Context Protocol) let Claude reach into Google Drive, GitHub, calendars, search, and other systems. For a firm, this is where governance gets real. Default to denying every connector. Allow only what a specific matter requires, document the permission, and audit quarterly.

    ✓ Generally allowed
    • · Read-only access to a single matter folder
    • · Public web search (with verification)
    • · Calendar read for scheduling
    ✗ Default deny
    • · Write access to client files
    • · Email send on lawyer's behalf
    • · Banking, payment, or trust account systems
    • · Any cross-matter data access
    Quarterly audit
    Under G3M Governance, every active connector is reviewed on the first business day of each quarter. Permissions that no living matter requires are revoked.
    Chapter 11

    Memory, PII, and When to Turn It Off

    Claude's Memory feature lets the model remember facts about you across conversations. For a lawyer, this is a category-five ethical hazard. Memory is a backdoor into the cross-matter data leakage that RPC 1.6 is designed to prevent.

    Single account (personal + firm)
    Memory OFF everywhere. Period. Rules and preferences live in Project instructions and structured prompt blocks.
    Separate accounts
    Personal Claude: Memory ON is acceptable. Firm Claude: Memory OFF anyway.
    Chapter 12

    Extended Thinking

    Extended Thinking gives Claude additional inference time to reason through a problem before answering. It is slower and costs more. For most prompts, leave it off. For three categories, turn it on.

    • Suppression motions and other close pretrial work where the legal theory must be airtight.
    • Settlement memorandum drafting when the matter has competing valuations and counterarguments.
    • Final decree assembly where every clause must reconcile with every other clause.
    The default rule
    Extended Thinking ON whenever the deliverable will be filed, served, or sent to a client without intermediate redrafting.
    Chapter 13

    Personal Injury Workflow

    The four-step PI matter arc, intake to demand. Total time on a clean matter: under two hours from raw intake notes to a demand letter ready for attorney review.

    Intake Summary
    Sonnet · Matter Summary
    Records Review
    Sonnet · Treatment + Causation
    Damages Analysis
    Opus · R.C. 2315.18 cap
    Demand Letter
    Opus · Pre-suit Artifact
    Send
    To adjuster

    Step 4 — Demand Letter prompt

    <ROLE>
    You are a senior Ohio personal injury attorney drafting a
    pre-suit demand letter to the adverse insurer.
    </ROLE>
    
    <TASK>
    Draft a complete demand letter to [ADJUSTER NAME AND CARRIER]
    using the Matter Summary, Treatment Chronology, and Damages
    Analysis already in this Project. Produce the letter as an
    Artifact.
    </TASK>
    
    <CONSTRAINTS>
    Ohio state law. Reference R.C. 2305.10 (statute of limitations)
    only if timing warrants. Professional tone. Firm but not
    aggressive. No threats beyond "we are prepared to file suit if
    a reasonable resolution is not reached." Present the demand as
    the recommended midpoint from the Damages Analysis.
    </CONSTRAINTS>
    
    <FORMAT>
    1. Letterhead block (placeholder)
    2. Date
    3. Adjuster and carrier address block
    4. Subject: Re: Our Client, [CLIENT]; DOL [DATE];
       Your Insured, [DEFENDANT]; Claim No. [NUMBER]
    5. Opening paragraph (liability in two sentences)
    6. Facts of the Collision
    7. Injuries and Treatment
    8. Economic Damages (itemized)
    9. Non-Economic Damages
    10. Settlement Demand ($ figure)
    11. Response deadline (30 days)
    12. Closing
    13. Enclosures list
    </FORMAT>
    Chapter 14

    Criminal Defense Workflow

    From discovery receipt to motion to suppress. Hypothetical: client charged with OVI under R.C. 4511.19, Lorain Municipal Court. Theory: marked-lanes stop unsupported by reasonable suspicion; extension into OVI investigation unsupported by independent reasonable suspicion.

    Discovery
    Upload to Project
    Issues Memo
    Sonnet + Extended Thinking
    Motion to Suppress
    Opus · [VERIFY] flags
    Two-Source Verify
    OVRST step R
    Hearing Prep
    5-part packet

    Step 1 — Discovery Issues Memo

    <ROLE>
    You are a senior Ohio criminal defense attorney with particular
    experience in OVI suppression litigation.
    </ROLE>
    
    <TASK>
    Review all discovery in this Project and produce a Discovery
    Issues Memo.
    </TASK>
    
    <CONSTRAINTS>
    Ohio law. Fourth Amendment analysis. Cite rules of criminal
    procedure by number (Crim. R.). Cite R.C. provisions in full.
    Case names in italics. Full Bluebook. If you identify a potential
    suppression issue but cannot recall a specific controlling Ohio
    case, flag with [VERIFY: CONTROLLING OHIO AUTHORITY] and describe
    the legal principle. Do not invent citations.
    </CONSTRAINTS>
    
    <FORMAT>
    1. Stop Analysis (RS for initial stop · supporting/undermining
       evidence · suppression issue yes/no/maybe)
    2. Duration Analysis (Rodriguez-line issues · independent RS)
    3. Field Sobriety Tests (NHTSA compliance · HGN, WAT, OLS)
    4. Chemical Test (BMV 2255, calibration, observation period)
    5. Statements by Client (Miranda analysis if any)
    6. Recommended Motions
    7. Additional Discovery to Request
    </FORMAT>
    Chapter 15

    Domestic Relations Workflow

    The deepest practice area for Mishak Law and the area LegalTek.ai was built to serve. The full matter arc, not just a single deliverable, structured around the Five Pillars: grounds, property division, spousal support, parental rights, child support.

    Strategy Memo
    Five Pillars
    Affidavit 1
    via Skill
    Discovery Set
    Civ. R. 33 / 34
    Settlement Memo
    Opus
    Decree
    Opus + Extended Thinking
    The Five Pillars
    Every DR matter analyzed across the same five issues: Grounds, Property (R.C. 3105.171), Spousal Support (R.C. 3105.18), Parental Rights (R.C. 3109.04), and Child Support (R.C. 3119). Use this scaffolding in every prompt and every memo.

    Step 1 — Matter Strategy Memo

    <ROLE>
    You are a senior Ohio domestic relations attorney with twenty
    years of experience.
    </ROLE>
    
    <TASK>
    Review the intake notes and produce a Matter Strategy Memo.
    </TASK>
    
    <CONSTRAINTS>
    Ohio R.C. Chapter 3105 framework. Identify the five pillar
    issues: grounds, property division, spousal support, parental
    rights and responsibilities, and child support. For each pillar,
    give a preliminary analysis, note the evidence we will need,
    and flag any issue that justifies urgent action (ex parte TROs,
    emergency custody orders, asset preservation).
    </CONSTRAINTS>
    
    <FORMAT>
    1. Executive Summary (5 bullets)
    2. Grounds Analysis
    3. Property Division
    4. Spousal Support (R.C. 3105.18 factors)
    5. Parental Rights (R.C. 3109.04 best interest)
    6. Child Support (R.C. 3119 framework)
    7. Urgent Actions
    8. Evidence and Discovery Plan
    9. Estimated Timeline
    10. Client Counseling Points
    </FORMAT>
    
    <REFERENCE MATERIAL>
    [PASTE INTAKE NOTES HERE]
    </REFERENCE MATERIAL>
    Hours per Deliverable · Before vs. With Claude (illustrative)
    Demand Letter (PI)Suppression MotionDecree DraftingDiscovery SetSettlement Memo0h3h6h9h12h
    • Before Claude
    • With Claude + Meta Prompt
    Chapter 16

    Claude Code for Lawyers

    Claude Code is the terminal interface that lets you turn a repetitive task into an automated tool. You do not need to be a developer. You need to be able to write a one-page plain-English specification.

    Pick the task
    15-30 min weekly
    Write spec
    Plain English, one page
    Run Claude Code
    Iterative build
    Test
    On real matter data
    Deploy
    Retire manual workflow
    Lawyer-friendly first builds
    Conflict-check spreadsheet diff. Affidavit-One field extractor. Pretrial deadline calculator. Discovery batch redactor. None require code knowledge — only a clear specification.
    Chapter 17

    Iteration: Prompt → Skill → Tool

    Every workflow in this guide follows the same maturation arc. Today's structured prompt becomes next quarter's Skill becomes next year's tool. The pattern is universal.

    1 · Prompt
    Used 1-3 times
    2 · Saved Prompt
    Used 4-10 times
    3 · Skill
    Used 10+ / known SOP
    4 · Connector
    Touches a system
    5 · Tool
    Claude Code automates

    The error most firms make: jumping straight to Step 5. Build to Step 3 first. Most firm value is unlocked there. Step 5 is for the workflows you have proven through Step 3 for at least a quarter.

    Chapter 18

    When Claude Gets It Wrong

    Four failure modes you must train yourself to spot:

    Fabricated citation
    A case that doesn't exist or doesn't say what's claimed.
    Wrong-jurisdiction authority
    Out-of-circuit case cited as controlling.
    Plausible factual drift
    Numbers or names invented to sound right.
    Confident oversimplification
    A nuanced doctrine flattened into a tidy rule.

    Six-step response

    1. STOP. Do not file or send anything containing the suspect content.
    2. Assess scope. Filed? Served? Sent to a client? Internal only?
    3. Correct the record where you can — motion to amend, corrective letter, candid call.
    4. Notify court, opposing, and client per RPC 3.3.
    5. Document the incident under G3M Measurement.
    6. Review the prompt. Tighten CONSTRAINTS. Add the reference material.
    Chapter 19

    ABA Formal Opinion 512 & Ohio RPC

    ABA Formal Opinion 512 (July 2024) is the first comprehensive guidance on lawyers' use of generative AI. Six duties, mapped cleanly to the Ohio Rules of Professional Conduct.

    ABA Op. 512 → Ohio RPC · Risk Weighting
    0255075100Competence(1.1)Confidentiality(1.6)Communication(1.4)Candor (3.3)Supervision(5.1/5.3)Fees (1.5)
    Competence (RPC 1.1)
    Understand the benefits and risks of the AI you use.
    Confidentiality (RPC 1.6)
    Every prompt is a disclosure. Training toggle OFF, ZDR plan.
    Communication (RPC 1.4)
    Proactive disclosure in the engagement letter.
    Candor (RPC 3.3)
    Two-source verification of every citation in every filing.
    Supervision (RPC 5.1 / 5.3)
    AI is a non-lawyer assistant; supervise its output.
    Fees (RPC 1.5)
    If AI cuts your time, you cannot bill the time you didn't work.
    Chapter 20

    The LegalTek.ai Framework Stack

    Four frameworks, stacked vertically. A lawyer runs COUNSEL at the task level. Output passes through OVRST before it leaves the firm. The firm runs G3M as an institution. New tools enter through ADAPT.

    G3M
    Firm-level governance · Quarterly
    ADAPT
    Tool & workflow rollout · Quarterly pilots
    COUNSEL
    Individual task · Every prompt
    OVRST
    Output oversight · Every deliverable
    COUNSEL
    Per task: Classify · Own confidentiality · Use the right tool · Name reference material · Structure the prompt · Evaluate · Log.
    G3M
    Firm-level: Governance · Guardrails · Growth · Measurement. Annual policy review.
    ADAPT
    Rollout: Assess · Design · Adopt (pilot) · Prove · Transition. No firm-wide rollout without a closed pilot.
    OVRST
    Per output: Originator · Verification · Reference confirmation · Signatures and Scope · Timestamp and Tool record.
    One thing to do this week
    Write your firm's COUNSEL checklist on a single page. Print it. Tape it to the wall next to your desk. Everything else follows.
    Appendix A

    Copy-Paste Prompt Library

    Three high-leverage prompts to get started. Paste, fill in your matter specifics, run.

    A1. Universal House Style CONSTRAINTS Block

    Ohio state law primary. Full Bluebook citations. Case names in
    italics, never bold. Ohio state-level citations preferred when
    available. URLs go in an Appendix, never inline. Do not invent
    citations. Flag single-source citations with [VERIFY: SECOND
    SOURCE]. No hyphens, no em dashes, use commas or periods. Do not
    use "leverage" as a verb. Professional, formal register. If a
    fact is not in the reference material, do not assume it.

    A2. New Client Intake Summary

    <ROLE>
    You are a senior paralegal at [FIRM NAME] with deep experience
    in [PRACTICE AREA] intakes.
    </ROLE>
    
    <TASK>
    Convert the intake notes below into our standard Matter Summary.
    </TASK>
    
    <CONSTRAINTS>
    [Paste A1]. Preserve every fact from the notes. Mark anything
    silent as "Not yet known."
    </CONSTRAINTS>
    
    <FORMAT>
    1. Parties and Contacts
    2. Matter Type and Posture
    3. Key Facts
    4. Theory of the Case (preliminary)
    5. Immediate Actions Required
    6. Open Items
    </FORMAT>
    
    <REFERENCE MATERIAL>
    [PASTE NOTES]
    </REFERENCE MATERIAL>

    A3. Settlement Offer Analysis

    <ROLE>
    You are advising me on whether to accept, reject, or counter an
    incoming settlement offer.
    </ROLE>
    
    <TASK>
    Produce a Settlement Offer Analysis Memo.
    </TASK>
    
    <CONSTRAINTS>
    [Paste A1]. Compare the offer against the best case, worst case,
    and expected value ranges from the Matter Strategy Memo. Factor
    in litigation costs, time value, client circumstances, and
    collection risk.
    </CONSTRAINTS>
    
    <FORMAT>
    1. Offer summary (one paragraph)
    2. Comparison to case valuation
    3. Cost to proceed analysis
    4. Non-financial factors
    5. Recommendation (accept, counter, reject) with specific
       counter if applicable
    6. Client counseling points
    </FORMAT>

    Ready to operationalize this in your firm?

    The COUNSEL Framework is the firm-wide companion to this guide. It gives you the policy templates, intake protocols, and AI vendor due-diligence checklists referenced throughout.

    About the Author

    Matthew A. Mishak is the Managing Attorney of Mishak Law LLC, where he has practiced for twenty years across domestic relations, criminal defense, and municipal law, including service as Chief Prosecutor. He is the Founder and CEO of LegalTek.ai LLC. His AI education includes the MIT Sloan executive program on AI Implications for Business Strategy, the MIT CSAIL applied AI program, and the Harvard Business School Online AI Essentials for Business program.

    This guide is for general informational and educational purposes. It is not legal advice. It does not create an attorney-client relationship. Legal authorities flagged in bracketed notes require verification against independent sources before citation in any pleading. LegalTek.ai is a technology company, not a law firm.