Claude Prompt Library

30 Claude Prompts That Draft NDAs & Legal Agreements

30 copy-paste prompts

Describe your situation and Claude returns a clean, ready-to-edit legal document with bracketed placeholders for parties and terms. Prompts for mutual and one-way NDAs, employee and contractor confidentiality, non-competes, and drop-in clauses. Not "give me some legal text."

In short: This page contains 30 copy-paste ready prompts, organized into 6 categories with a description and pro tip for each. The first 15 prompts are free instantly โ€” no signup needed. Hand-curated and tested by the AI Academy team.

By Louis Corneloup ยท Founder, Techpresso
Last updated ยทHand-curated & tested by the AI Academy team

Mutual NDAs

5 prompts

Standard Mutual NDA

1/30

You are a commercial contracts attorney who drafts clear, balanced agreements. <context> Two businesses want to share confidential information both ways to explore working together. I need a complete, self-contained mutual non-disclosure agreement I can fill in and send today. </context> <inputs> - Party A (name, entity type, address): [PARTY A] - Party B (name, entity type, address): [PARTY B] - Purpose of disclosure: [WHY THEY ARE SHARING INFO] - Confidentiality term (years): [E.G. 3 YEARS] - Governing law / jurisdiction: [STATE OR COUNTRY] - Effective date: [DATE] </inputs> <task> Draft a full mutual NDA with numbered sections: parties and recitals, definition of Confidential Information, mutual obligations, standard exclusions (public knowledge, independently developed, lawfully received, required by law), permitted disclosures to representatives, term and survival, return or destruction of materials, no license or transfer of IP, no warranty, remedies including injunctive relief, governing law, entire agreement and amendments, and a signature block for both parties. </task> <constraints> - Plain English, professional tone; keep all party details and terms as [BRACKETED PLACEHOLDERS]. - Balanced obligations that apply equally to both sides. - This is a customizable template, not legal advice โ€” add a clear note that a qualified lawyer should review it before signing, and never invent statutes or case citations. </constraints> <format> Return the complete NDA as a clean document artifact, then a short list of the placeholders I must fill and the two clauses most worth negotiating. </format>

Produces a complete, balanced mutual NDA with all standard sections and a signature block, ready to use.

๐Ÿ’ก

Pro tip: Tell Claude the real reason the two sides are talking; a specific purpose clause narrows what counts as confidential and prevents overreach.

Partnership / Joint-Venture NDA

2/30

You are a corporate lawyer who structures early-stage partnership discussions. <context> Two companies are exploring a joint venture or strategic partnership and will exchange sensitive financials, roadmaps, and customer data. I need a mutual NDA tailored to a deep partnership evaluation. </context> <inputs> - Party A and Party B (names, entities): [PARTIES] - Nature of the potential partnership: [WHAT THEY MIGHT BUILD OR DO TOGETHER] - Sensitive categories being shared: [FINANCIALS, ROADMAP, CUSTOMERS, PRICING] - Confidentiality term and survival: [E.G. 5 YEARS] - Governing law: [JURISDICTION] </inputs> <task> Draft a mutual NDA with heightened protections for a partnership evaluation: parties and recitals framing the JV exploration, a broad but precise definition of Confidential Information listing the sensitive categories, mutual non-use except for evaluating the partnership, restrictions on sharing with affiliates and advisors without a matching duty of care, a non-circumvention clause preventing either side from going around the other to shared contacts, standard exclusions, term and survival, and dual signature blocks. </task> <constraints> - Keep parties and terms as [BRACKETED PLACEHOLDERS]; balanced and mutual throughout. - Include a non-circumvention section but keep it reasonable in scope and time. - Template only, not legal advice โ€” note that a qualified lawyer should review before signing; do not fabricate legal authorities. </constraints> <format> Return the full agreement as a document artifact, then explain how the non-circumvention clause works and what to adjust if only one side is disclosing the sensitive data. </format>

Generates a partnership-grade mutual NDA with non-circumvention protection for joint-venture talks, ready to edit.

๐Ÿ’ก

Pro tip: List the exact data categories being exchanged so the definition of Confidential Information is concrete instead of a catch-all.

One-Page Short-Form Mutual NDA

3/30

You are a pragmatic startup lawyer who writes tight, readable agreements. <context> I want a short, friendly mutual NDA that fits on roughly one page for a quick early conversation between two small companies โ€” enough protection without scaring the other side. </context> <inputs> - Party A and Party B: [NAMES] - Purpose (one line): [WHY THEY ARE MEETING] - Term: [E.G. 2 YEARS] - Governing law: [JURISDICTION] </inputs> <task> Draft a concise one-page mutual NDA covering only the essentials: parties, a plain definition of confidential information, mutual promise not to use or disclose it except for the stated purpose, the core exclusions, term, and a simple signature block. Favor short sentences and a single defined term over dense legalese, while still being enforceable in structure. </task> <constraints> - Must read as approachable and fit roughly one page; parties and terms as [BRACKETED PLACEHOLDERS]. - Do not drop the exclusions or the survival period even in short form. - This is a template, not legal advice โ€” add a one-line reviewer note; never invent statutes or citations. </constraints> <format> Return the short NDA as a document artifact, then note in two lines what protection you traded away to keep it short. </format>

Creates a friendly one-page mutual NDA that keeps the essentials while staying short and readable, ready to send.

๐Ÿ’ก

Pro tip: Ask for both a one-page and a full version so you can offer the short one first and fall back to the detailed one if pushed.

M&A Due-Diligence Mutual NDA

4/30

You are an M&A attorney who papers confidentiality for acquisition discussions. <context> A buyer and a target are entering due diligence for a possible acquisition. I need a mutual NDA with the extra protections deals require, since highly sensitive information will change hands. </context> <inputs> - Buyer and target (names, entities): [PARTIES] - Transaction being explored: [ACQUISITION / MERGER / INVESTMENT] - Data being disclosed: [FINANCIALS, CONTRACTS, EMPLOYEE, IP, CUSTOMERS] - Term and standstill period: [E.G. 2 YEARS CONFIDENTIALITY] - Governing law: [JURISDICTION] </inputs> <task> Draft a deal-grade mutual NDA: recitals framing the potential transaction, broad definition of Confidential Information including the existence of the discussions themselves, non-use except to evaluate the transaction, permitted disclosure to named representative categories under a duty of confidentiality, a non-solicitation of key employees clause for the evaluation period, an optional standstill clause the buyer will not acquire shares without consent, return or destruction with a retention carve-out for legal or archival copies, term and survival, and signature blocks. </task> <constraints> - Keep parties and terms as [BRACKETED PLACEHOLDERS]; clearly mark the standstill as optional. - Protect the confidentiality of the fact that a deal is being discussed. - Template only, not legal advice โ€” flag that deal counsel must review; do not invent case law or statutory references. </constraints> <format> Return the agreement as a document artifact, then briefly explain the standstill and non-solicit clauses and when each is appropriate to keep or cut. </format>

Drafts an acquisition-grade mutual NDA with standstill and employee non-solicit options for due diligence, ready to edit.

๐Ÿ’ก

Pro tip: Say whether you are the buyer or the seller; it changes whether you want the standstill clause in or out.

Vendor / Supplier Evaluation NDA

5/30

You are a procurement and commercial contracts lawyer. <context> We are evaluating a new vendor and both sides will exchange technical specs, pricing, and internal process details during the assessment. I need a mutual NDA scoped to a vendor evaluation. </context> <inputs> - Company and vendor (names, entities): [PARTIES] - What is being evaluated: [PRODUCT / SERVICE / INTEGRATION] - Information shared each way: [SPECS, PRICING, ROADMAP, SECURITY] - Term: [E.G. 3 YEARS] - Governing law: [JURISDICTION] </inputs> <task> Draft a mutual NDA for vendor evaluation: parties and purpose limited to assessing a possible commercial relationship, definition of Confidential Information covering technical and pricing data, mutual non-use and non-disclosure, permitted disclosure to employees and contractors on a need-to-know basis, a clause clarifying that the NDA creates no obligation to buy or sell and no exclusivity, data-security expectations for handling the other party's information, return or destruction, term and survival, and signature blocks. </task> <constraints> - Parties and terms as [BRACKETED PLACEHOLDERS]; keep it balanced and vendor-neutral. - Explicitly state the NDA does not commit either side to a purchase or partnership. - Template, not legal advice โ€” add a reviewer note; never fabricate legal authorities. </constraints> <format> Return the full NDA as a document artifact, then note which clauses to tighten if the vendor will touch your customer data. </format>

Builds a vendor-evaluation mutual NDA with need-to-know sharing and a no-obligation clause, ready to use.

๐Ÿ’ก

Pro tip: If the vendor will process personal data, ask Claude to add a pointer that a separate data-processing agreement is still needed.

XML tags are just the start. Learn the full Claude workflow.

A growing library of 300+ hands-on AI tutorials covering Claude, ChatGPT, and 50+ tools. New tutorials added every week.

Start 7-Day Free Trial

One-Way NDAs

5 prompts

Standard One-Way (Unilateral) NDA

6/30

You are a business attorney who drafts protective, one-directional agreements. <context> I am the only one disclosing confidential information and the other party is only receiving it. I need a complete unilateral NDA that protects the disclosing side. </context> <inputs> - Disclosing Party (name, entity, address): [DISCLOSER] - Receiving Party (name, entity, address): [RECIPIENT] - Purpose of disclosure: [WHY THEY NEED THE INFO] - Confidentiality term: [E.G. 3 YEARS] - Governing law: [JURISDICTION] - Effective date: [DATE] </inputs> <task> Draft a one-way NDA with numbered sections: parties and recitals, definition of Confidential Information, the Receiving Party's obligations to protect and not use the information except for the stated purpose, standard exclusions, permitted disclosure to representatives bound by confidentiality, no license granted, return or destruction on request, remedies including injunctive relief, term and survival, governing law, and a signature block for both parties. </task> <constraints> - Obligations fall only on the Receiving Party; keep all details as [BRACKETED PLACEHOLDERS]. - Include the standard exclusions so the clause is enforceable, not overbroad. - This is a template, not legal advice โ€” add a note that a qualified lawyer should review before signing; do not invent statutes or citations. </constraints> <format> Return the complete NDA as a document artifact, then list the placeholders to fill and explain why one-way protection suits this situation. </format>

Generates a complete unilateral NDA that binds only the receiving party, ready to fill and send.

๐Ÿ’ก

Pro tip: Define the purpose narrowly; a tight purpose clause is what stops the recipient from using your info for anything else.

Investor-Pitch NDA

7/30

You are a startup counsel who advises founders on protecting confidential pitch material. <context> I am about to share my business plan, financials, and product roadmap with a potential investor. I need a one-way NDA the investor signs before I disclose, written to be reasonable enough that a serious investor will actually sign it. </context> <inputs> - Company (name, entity): [DISCLOSING COMPANY] - Investor / recipient: [RECIPIENT NAME] - What I am sharing: [DECK, FINANCIALS, ROADMAP, METRICS] - Term: [E.G. 2 YEARS] - Governing law: [JURISDICTION] </inputs> <task> Draft a founder-friendly one-way NDA for an investor conversation: recitals framing the fundraising discussion, definition of Confidential Information covering the deck, financials, and metrics, the investor's non-use and non-disclosure obligations, sensible exclusions including information the investor already holds or receives from other deals, permitted sharing with the investor's advisors under confidentiality, an acknowledgment that signing creates no obligation to invest, term and survival, and a signature block. </task> <constraints> - Keep it reasonable and not hostile so an investor will sign; details as [BRACKETED PLACEHOLDERS]. - Include a carve-out recognizing investors see many similar companies. - Template, not legal advice โ€” add a reviewer note; never fabricate legal authorities. </constraints> <format> Return the NDA as a document artifact, then explain the investor-friendly carve-outs and note that many top VCs decline to sign NDAs at the pitch stage. </format>

Drafts a reasonable, founder-friendly one-way NDA for sharing pitch materials with an investor, ready to use.

๐Ÿ’ก

Pro tip: Keep the term short and the carve-outs generous; an aggressive NDA is the fastest way to get a pass from a busy investor.

Beta Tester / Product Demo NDA

8/30

You are a product counsel who protects unreleased features and demos. <context> We are giving external testers or prospects early access to an unreleased product or private demo. I need a one-way NDA that keeps the product, features, and any bugs confidential until launch. </context> <inputs> - Company (name, entity): [DISCLOSER] - Tester / recipient type: [INDIVIDUAL OR COMPANY] - What they can access: [BETA APP, FEATURES, ROADMAP, SCREENSHOTS] - Confidentiality term: [E.G. UNTIL PUBLIC LAUNCH PLUS 1 YEAR] - Governing law: [JURISDICTION] </inputs> <task> Draft a one-way beta NDA: recitals about early access, definition of Confidential Information that explicitly covers the existence of the beta, features, performance, and any defects, a no-screenshots or public-posting clause, obligations to keep access credentials private, feedback ownership so the company can freely use tester feedback, standard exclusions, term tied to public launch, return or deletion of materials, and a signature block that also works for an individual tester. </task> <constraints> - Cover both a company and an individual signer; details as [BRACKETED PLACEHOLDERS]. - Explicitly ban public screenshots, benchmarks, and social posts about the beta. - Template, not legal advice โ€” flag that a lawyer should review; do not invent statutes or citations. </constraints> <format> Return the NDA as a document artifact, then explain the feedback-ownership clause and how to adapt it into a click-through version for many testers. </format>

Creates a one-way beta NDA banning leaks and screenshots while assigning feedback rights to you, ready to use.

๐Ÿ’ก

Pro tip: Ask Claude to add a click-through acceptance version so you can gate a beta signup form without chasing signatures.

Idea-Protection NDA for a Contractor

9/30

You are an IP-focused attorney who protects business ideas shared with hired help. <context> I need to explain my business idea and confidential plans to a contractor or agency I am considering hiring, before we have a full contract. I want a one-way NDA that protects my idea while we talk. </context> <inputs> - Me / my company (name, entity): [DISCLOSER] - Contractor / agency: [RECIPIENT] - What I am revealing: [BUSINESS IDEA, PLANS, DESIGNS, DATA] - Term: [E.G. 3 YEARS] - Governing law: [JURISDICTION] </inputs> <task> Draft a one-way NDA protecting a disclosed idea: recitals about exploring a working relationship, a definition of Confidential Information that clearly includes concepts, ideas, and know-how even if not marked confidential, the recipient's non-use and non-disclosure duties, a clause stating no rights or license to the idea are granted, standard exclusions, permitted disclosure only to the recipient's team on a need-to-know basis, return or destruction, remedies including injunctive relief, term and survival, and a signature block. </task> <constraints> - Make clear that unmarked ideas and concepts are still protected; details as [BRACKETED PLACEHOLDERS]. - State plainly that no ownership of the idea passes to the recipient. - Template, not legal advice โ€” add a reviewer note; never fabricate legal authorities. </constraints> <format> Return the NDA as a document artifact, then note that a full contractor agreement with IP assignment is still needed once you actually hire them. </format>

Generates a one-way NDA that protects an unmarked business idea before hiring a contractor, ready to use.

๐Ÿ’ก

Pro tip: An NDA protects the conversation, not the work product; ask Claude to remind you to add IP assignment in the eventual contract.

Interview / Candidate NDA

10/30

You are an employment lawyer who handles confidentiality during hiring. <context> During interviews or a work trial, candidates will see confidential product, code, or strategy information. I need a one-way NDA a candidate signs before that exposure. </context> <inputs> - Company (name, entity): [DISCLOSER] - Candidate: [RECIPIENT NAME] - What they may see: [CODE, ROADMAP, FINANCIALS, CUSTOMER DATA] - Context: [INTERVIEW / TAKE-HOME / PAID TRIAL DAY] - Term: [E.G. 3 YEARS] - Governing law: [JURISDICTION] </inputs> <task> Draft a one-way candidate NDA: recitals about the interview or trial, a definition of Confidential Information covering anything seen or heard during the process, the candidate's non-use and non-disclosure obligations, a clause clarifying the NDA does not create an employment relationship or offer, ownership of any work product the candidate creates during a paid trial, standard exclusions, return or deletion of any materials or take-home data, term and survival, and a simple individual signature block. </task> <constraints> - Written for an individual signer; details as [BRACKETED PLACEHOLDERS]. - Include the no-employment-promise clause and, for paid trials, a work-product ownership clause. - Template, not legal advice โ€” flag lawyer review; do not invent statutes or citations. </constraints> <format> Return the NDA as a document artifact, then explain when to use this versus folding confidentiality into the offer letter. </format>

Drafts a one-way candidate NDA covering interviews and paid trials, with a no-offer clause, ready to use.

๐Ÿ’ก

Pro tip: For take-home projects, keep the work-product ownership clause so a candidate cannot reuse or resell what they build for you.

Employee Confidentiality

5 prompts

Standalone Employee Confidentiality Agreement

11/30

You are an employment attorney who drafts staff confidentiality agreements. <context> I need a standalone confidentiality agreement for a new or existing employee to sign, covering everything they learn on the job. </context> <inputs> - Employer (name, entity): [EMPLOYER] - Employee (name, role): [EMPLOYEE] - Categories of confidential info: [CUSTOMER DATA, PRICING, CODE, TRADE SECRETS] - Duration after employment ends: [E.G. INDEFINITELY FOR TRADE SECRETS] - Governing law: [JURISDICTION] </inputs> <task> Draft an employee confidentiality agreement: parties and purpose, a broad definition of Confidential Information including trade secrets and third-party information entrusted to the employer, the employee's duties during and after employment, a clause on proper handling and return of company property and data on separation, an acknowledgment that confidentiality survives termination, standard exclusions such as publicly known information, a non-disparagement-free reminder that this does not restrict legally protected whistleblowing or reporting, and a signature block. </task> <constraints> - Details as [BRACKETED PLACEHOLDERS]; obligations survive the end of employment. - Preserve the employee's right to report unlawful conduct to authorities. - This is a template, not legal advice โ€” note that an employment lawyer should review for local law; never fabricate statutes or citations. </constraints> <format> Return the agreement as a document artifact, then explain the whistleblower carve-out and which obligations survive termination. </format>

Produces a standalone employee confidentiality agreement with post-employment survival and a whistleblower carve-out, ready to use.

๐Ÿ’ก

Pro tip: Keep the lawful-reporting carve-out in; without it, confidentiality clauses can be challenged as trying to silence legal disclosures.

Confidentiality + IP Assignment Clause

12/30

You are an IP and employment lawyer who drafts invention-assignment language. <context> I need a combined confidentiality and IP-assignment clause to drop into an employment contract so anything an employee creates on the job belongs to the company. </context> <inputs> - Employer and employee: [PARTIES] - Type of work created: [SOFTWARE, DESIGNS, CONTENT, INVENTIONS] - Prior inventions the employee wants excluded: [LIST OR NONE] - Governing law: [JURISDICTION] </inputs> <task> Draft a clean, numbered clause combining confidentiality and IP assignment: the employee's confidentiality duty, present assignment of all work-related intellectual property created during employment, a duty to disclose and assist with registrations, a carve-out for pre-existing inventions the employee lists, a moral-rights waiver where permitted, and a clarification excluding work created entirely on the employee's own time without company resources unrelated to the business. Number the sub-clauses so it slots into an existing contract. </task> <constraints> - Write as an insertable clause, not a full agreement; keep details as [BRACKETED PLACEHOLDERS]. - Include the prior-inventions schedule and the own-time carve-out. - Template, not legal advice โ€” flag that assignment rules vary by jurisdiction and a lawyer should review; do not invent statutes. </constraints> <format> Return the clause as a document artifact with a blank prior-inventions schedule, then note where in a standard employment contract it belongs. </format>

Generates an insertable confidentiality-plus-IP-assignment clause with a prior-inventions schedule, ready to drop into a contract.

๐Ÿ’ก

Pro tip: Have the employee actually fill the prior-inventions schedule before signing; a blank one can be read as assigning everything they ever made.

Onboarding Confidentiality Acknowledgment

13/30

You are an HR-focused legal specialist who writes clear onboarding documents. <context> I want a short confidentiality acknowledgment new hires sign on day one, confirming they understand and accept the company's confidentiality expectations. </context> <inputs> - Company (name): [EMPLOYER] - Employee (name, role): [EMPLOYEE] - Key policies referenced: [HANDBOOK, SECURITY POLICY, DATA POLICY] - Governing law: [JURISDICTION] </inputs> <task> Draft a one-page onboarding confidentiality acknowledgment in plain language: a short statement of the employee's duty to protect confidential and proprietary information, examples of what counts (customer data, credentials, financials, unreleased products), a reminder about not sharing information externally or on personal devices without approval, a reference incorporating the handbook and security policy by name, a confirmation that the duty continues after employment, and a dated signature line. Keep the tone welcoming, not intimidating. </task> <constraints> - One page, plain English; keep names and policy titles as [BRACKETED PLACEHOLDERS]. - Incorporate the referenced policies rather than restating them in full. - Template, not legal advice โ€” add a brief reviewer note; never invent legal citations. </constraints> <format> Return the acknowledgment as a document artifact, then note how it complements a fuller confidentiality agreement rather than replacing it. </format>

Creates a friendly one-page onboarding confidentiality acknowledgment for day-one signing, ready to use.

๐Ÿ’ก

Pro tip: Reference your handbook by exact name and version so the acknowledgment stays valid as policies get updated over time.

Offboarding Confidentiality Reminder Letter

14/30

You are an employment lawyer who handles clean separations. <context> An employee is leaving and I want a professional exit letter reminding them of their continuing confidentiality obligations and asking them to confirm return of company information. </context> <inputs> - Company (name): [EMPLOYER] - Departing employee (name, role): [EMPLOYEE] - Last day: [DATE] - Obligations to remind them of: [CONFIDENTIALITY, IP, NON-SOLICIT IF ANY] - Governing law: [JURISDICTION] </inputs> <task> Draft a courteous offboarding confidentiality reminder letter: a thank-you opening, a clear restatement that confidentiality and any signed IP or non-solicit obligations continue after the last day, a specific checklist of company property and data to return or delete (laptop, credentials, documents, cloud access), a request to confirm they have not retained copies, a line preserving their right to make legally protected disclosures, contact details for questions, and a signature and acknowledgment section for the employee to sign. </task> <constraints> - Professional and respectful tone; details as [BRACKETED PLACEHOLDERS]. - Reference the actual signed agreements rather than creating new obligations. - Template, not legal advice โ€” flag lawyer review; do not fabricate statutes or citations. </constraints> <format> Return the letter as a document artifact with a return-of-property checklist, then note what to attach (a copy of the original agreement) for it to be effective. </format>

Drafts a courteous offboarding letter restating confidentiality duties with a return-of-property checklist, ready to send.

๐Ÿ’ก

Pro tip: Attach the employee's original signed agreement to the letter so the reminder points to real obligations, not new ones.

Intern / Temporary-Staff NDA

15/30

You are an employment attorney who advises on short-term and intern engagements. <context> I am bringing on an intern or temporary worker who will access confidential information but is not a full employee. I need a confidentiality agreement scoped to a short engagement. </context> <inputs> - Company (name, entity): [EMPLOYER] - Intern / temp (name): [WORKER] - Engagement dates: [START AND END] - Confidential info they will touch: [DATA, CODE, PROCESSES] - Governing law: [JURISDICTION] </inputs> <task> Draft an intern or temporary-staff confidentiality agreement: parties and the short engagement context, a clear definition of Confidential Information, the worker's duty not to use or disclose it, ownership of any work product created during the engagement, a duty to return or delete materials at the end of the term, an acknowledgment that confidentiality survives the engagement, standard exclusions, the lawful-reporting carve-out, and a signature block suitable for a minor's guardian co-signature if needed. </task> <constraints> - Scoped to a fixed-term engagement; details as [BRACKETED PLACEHOLDERS]. - Include a work-product ownership clause and an optional guardian signature line for minors. - Template, not legal advice โ€” note lawyer review, especially for interns who may be minors; do not invent statutes. </constraints> <format> Return the agreement as a document artifact, then note the extra care needed when the intern is under 18 or unpaid. </format>

Generates a short-engagement confidentiality agreement for interns and temps with work-product ownership, ready to use.

๐Ÿ’ก

Pro tip: For unpaid interns, ask Claude to keep the terms light; overreaching agreements on unpaid roles can raise legal red flags.

Contractor & Freelancer NDAs

5 prompts

Project-Based Freelancer NDA

16/30

You are a contracts lawyer who papers freelance engagements. <context> I am hiring a freelancer for a specific project and they will access confidential materials. I need a one-way NDA scoped to that project that a freelancer will find fair. </context> <inputs> - Client (name, entity): [CLIENT] - Freelancer (name): [FREELANCER] - Project: [WHAT THEY ARE DOING] - Confidential materials shared: [BRAND ASSETS, DATA, CREDENTIALS, DOCS] - Term: [E.G. 2 YEARS AFTER PROJECT ENDS] - Governing law: [JURISDICTION] </inputs> <task> Draft a project-scoped freelancer NDA: parties and project context, a definition of Confidential Information covering the client's materials and any access credentials, the freelancer's non-use and non-disclosure duties limited to the project, a clause that the freelancer will not showcase the work publicly without written consent, permitted use of subcontractors only under a matching NDA, return or deletion of materials at project end, standard exclusions, term and survival, and a signature block for an individual freelancer. </task> <constraints> - Fair and project-scoped; details as [BRACKETED PLACEHOLDERS]. - Include a portfolio-use consent clause and a subcontractor flow-down clause. - Template, not legal advice โ€” add a reviewer note; never fabricate legal authorities. </constraints> <format> Return the NDA as a document artifact, then explain the portfolio-consent clause and how to let the freelancer show the work later if you approve. </format>

Creates a fair, project-scoped freelancer NDA with portfolio-consent and subcontractor flow-down clauses, ready to use.

๐Ÿ’ก

Pro tip: Decide upfront if the freelancer can show the work in their portfolio; the consent clause avoids an awkward fight after launch.

Contractor NDA With IP Assignment

17/30

You are an IP attorney who drafts work-for-hire agreements for independent contractors. <context> A contractor will build something for me and I need both confidentiality and clear ownership of what they create, since default law often leaves IP with the contractor. </context> <inputs> - Client (name, entity): [CLIENT] - Contractor (name, entity): [CONTRACTOR] - Deliverables: [SOFTWARE, DESIGNS, CONTENT, ETC] - Pre-existing tools the contractor will reuse: [LIBRARIES, FRAMEWORKS OR NONE] - Governing law: [JURISDICTION] </inputs> <task> Draft a combined contractor confidentiality and IP-assignment agreement: parties and engagement, confidentiality obligations, a present assignment of all deliverables and related IP to the client upon creation or payment, a work-made-for-hire recital with an assignment backstop, a license-back for the contractor's pre-existing or general-purpose tools they reuse, a duty to assist with registrations, a warranty that the work is original and non-infringing, return of materials, standard exclusions, and a signature block. </task> <constraints> - Details as [BRACKETED PLACEHOLDERS]; include both a work-for-hire recital and an assignment backstop. - Add a license-back so the contractor keeps their general tools while the client owns the deliverable. - Template, not legal advice โ€” note IP rules vary by jurisdiction and a lawyer should review; do not invent statutes. </constraints> <format> Return the agreement as a document artifact, then explain why the assignment backstop matters if work-for-hire alone does not transfer ownership. </format>

Drafts a contractor NDA with full IP assignment, work-for-hire backstop, and tool license-back, ready to use.

๐Ÿ’ก

Pro tip: Ask Claude to keep both the work-for-hire recital and the assignment; work-for-hire alone often fails to transfer ownership for contractors.

Agency-Client Project Mutual NDA

18/30

You are a commercial lawyer who papers agency engagements. <context> My agency and a client will exchange confidential information both ways during a project. I need a mutual NDA that fits an agency-client relationship. </context> <inputs> - Agency and client (names, entities): [PARTIES] - Engagement: [WHAT THE AGENCY IS DELIVERING] - Info shared each way: [CLIENT DATA, STRATEGY, AGENCY METHODS, PRICING] - Term: [E.G. 3 YEARS] - Governing law: [JURISDICTION] </inputs> <task> Draft a mutual agency-client NDA: parties and engagement context, mutual definition of Confidential Information covering the client's business data and the agency's methods and pricing, mutual non-use and non-disclosure, permitted disclosure to staff and subcontractors under confidentiality, a clause protecting the agency's reusable know-how and templates as its own confidential property, a non-solicitation of each other's staff during the engagement, return or destruction, standard exclusions, term and survival, and dual signature blocks. </task> <constraints> - Balanced and mutual; details as [BRACKETED PLACEHOLDERS]. - Protect the agency's reusable methodologies while respecting the client's data. - Template, not legal advice โ€” flag lawyer review; do not fabricate legal authorities. </constraints> <format> Return the NDA as a document artifact, then explain the reusable-know-how clause so the agency keeps its general methods. </format>

Generates a balanced agency-client mutual NDA that also protects the agency's reusable methods, ready to use.

๐Ÿ’ก

Pro tip: Have Claude carve out your agency's general frameworks; otherwise a broad NDA can trap the methods you reuse on every client.

NDA Clause for a Service Agreement

19/30

You are a contracts attorney who writes modular clauses. <context> I already have a freelance or service agreement and just need a well-drafted confidentiality clause to insert into it, rather than a separate NDA. </context> <inputs> - Parties (roles): [CLIENT AND SERVICE PROVIDER] - Direction: [MUTUAL OR ONE-WAY] - Confidential categories: [DATA, DELIVERABLES, PRICING, KNOW-HOW] - Survival period: [E.G. 3 YEARS AFTER TERMINATION] - Governing law: [JURISDICTION] </inputs> <task> Draft a self-contained confidentiality clause suitable for insertion into a service agreement: a defined term for Confidential Information, the confidentiality and non-use obligation in the chosen direction, standard exclusions, permitted disclosures, a required-by-law carve-out, return or destruction on termination, survival, and a remedies sub-clause referencing injunctive relief. Number the sub-clauses so they slot cleanly under an existing section. </task> <constraints> - Deliver as an insertable clause, not a standalone agreement; details as [BRACKETED PLACEHOLDERS]. - Support either a mutual or one-way version based on the input. - Template, not legal advice โ€” add a short reviewer note; never fabricate statutes or citations. </constraints> <format> Return the clause as a document artifact, then note where in a typical service agreement it belongs and how to renumber it to fit. </format>

Produces a modular, insertable confidentiality clause for an existing service agreement, ready to drop in.

๐Ÿ’ก

Pro tip: Tell Claude the exact section number it will follow so the sub-clause numbering matches your contract without manual fixes.

Subcontractor Data-Handling NDA

20/30

You are a data-privacy and contracts lawyer. <context> A subcontractor will handle data that belongs to my client, so I need an NDA that flows down my confidentiality obligations and sets clear data-handling rules. </context> <inputs> - Prime contractor and subcontractor: [PARTIES] - End client whose data is involved: [CLIENT NAME] - Data being handled: [TYPES OF DATA] - Security expectations: [ENCRYPTION, ACCESS LIMITS, LOCATION] - Governing law: [JURISDICTION] </inputs> <task> Draft a subcontractor NDA with data-handling flow-down: parties and context, confidentiality obligations that flow down the prime contractor's duties to the end client, a definition of Confidential Information including the client's data, specific data-handling requirements (need-to-know access, encryption, no cross-border transfer without consent, no use for the subcontractor's own purposes), a breach-notification duty with a stated timeframe, return or secure deletion at termination, standard exclusions, term and survival, and a signature block. </task> <constraints> - Details as [BRACKETED PLACEHOLDERS]; obligations must flow down to protect the end client. - Include a breach-notification timeframe and a no-secondary-use clause. - Template, not legal advice โ€” note a separate data-processing agreement may be legally required and a lawyer should review; do not invent statutes. </constraints> <format> Return the NDA as a document artifact, then note when a formal data-processing agreement is required on top of this NDA. </format>

Creates a subcontractor NDA that flows down client duties with concrete data-handling and breach-notice terms, ready to use.

๐Ÿ’ก

Pro tip: If personal data is involved, treat this NDA as a floor and ask Claude whether a full data-processing agreement is also needed.

Non-Compete & Non-Solicit

5 prompts

Standalone Non-Compete Agreement

21/30

You are an employment lawyer experienced in restrictive covenants. <context> I need a standalone non-compete agreement restricting a departing employee or seller from competing for a reasonable period. Enforceability varies widely, so I want it drafted narrowly. </context> <inputs> - Company and restricted person: [PARTIES] - Context: [EMPLOYMENT / SALE OF BUSINESS] - Restricted activities: [SPECIFIC COMPETING ROLES OR PRODUCTS] - Geographic scope: [DEFINED AREA] - Duration: [E.G. 12 MONTHS] - Consideration offered: [PAY, SEVERANCE, PURCHASE PRICE] - Governing law: [JURISDICTION] </inputs> <task> Draft a narrowly tailored non-compete agreement: parties and recitals stating the legitimate business interest protected, a precise definition of the restricted activities, a reasonable geographic scope, a defined duration, the consideration given in exchange for the restriction, an acknowledgment of reasonableness, a severability and blue-pencil clause so a court can narrow rather than void it, standard carve-outs, and a signature block. </task> <constraints> - Keep scope, geography, and time as narrow as the inputs allow; details as [BRACKETED PLACEHOLDERS]. - Include a blue-pencil severability clause and clear consideration. - Template, not legal advice โ€” prominently warn that non-competes are banned or heavily limited in many jurisdictions and a local lawyer must review; do not invent statutes or citations. </constraints> <format> Return the agreement as a document artifact, then flag the three factors (scope, geography, duration) most likely to decide enforceability. </format>

Drafts a narrowly tailored non-compete with a blue-pencil clause and enforceability warnings, ready to review with counsel.

๐Ÿ’ก

Pro tip: Non-competes are void in some places and for some roles; before using this, confirm with a local lawyer that it is even allowed.

Non-Solicitation of Clients Agreement

22/30

You are a commercial lawyer focused on protecting client relationships. <context> I want an agreement stopping a departing employee or contractor from poaching the clients they worked with, without a full non-compete. </context> <inputs> - Company and restricted person: [PARTIES] - Clients protected: [CLIENTS THE PERSON WORKED WITH IN THE LAST 12 MONTHS] - Duration: [E.G. 12 MONTHS] - Consideration: [WHAT IS GIVEN IN EXCHANGE] - Governing law: [JURISDICTION] </inputs> <task> Draft a client non-solicitation agreement: parties and the legitimate interest in client goodwill, a precise definition of protected clients limited to those the person actually served or learned about, the restriction against soliciting or accepting business from those clients for the defined period, a clarification that it does not bar general advertising or unrelated clients, the consideration, a blue-pencil severability clause, standard carve-outs, and a signature block. </task> <constraints> - Limit protected clients to real relationships, not the whole market; details as [BRACKETED PLACEHOLDERS]. - Distinguish soliciting from merely being approached, and allow general advertising. - Template, not legal advice โ€” note enforceability varies and a lawyer should review; do not fabricate legal authorities. </constraints> <format> Return the agreement as a document artifact, then explain the difference between barring active solicitation and barring all business, and which is more enforceable. </format>

Generates a client non-solicitation agreement limited to real relationships with a blue-pencil clause, ready to review.

๐Ÿ’ก

Pro tip: Barring active solicitation is far more enforceable than banning a former hire from serving any of your clients at all.

No-Poach (Employee Non-Solicit) Clause

23/30

You are an employment attorney who drafts restrictive covenants. <context> I need a clause preventing a departing employee or a business partner from luring away my other staff for a period after they leave. </context> <inputs> - Company and restricted person: [PARTIES] - Staff protected: [ALL EMPLOYEES / THOSE THEY WORKED WITH] - Duration: [E.G. 12 MONTHS] - Governing law: [JURISDICTION] </inputs> <task> Draft an employee non-solicitation clause: the restriction against directly or indirectly soliciting, recruiting, or hiring the company's employees for the defined period, a scope limited to employees the person actually worked with or learned about, a carve-out for general job advertisements not targeted at the company's staff and for employees who independently apply, a reasonable duration, a blue-pencil severability clause, and numbered sub-clauses so it inserts into a larger agreement. </task> <constraints> - Deliver as an insertable clause; details as [BRACKETED PLACEHOLDERS]. - Include the general-advertising and independent-applicant carve-outs to stay reasonable. - Template, not legal advice โ€” warn that employee non-solicits and no-poach terms face antitrust scrutiny in some places and a lawyer should review; do not invent statutes. </constraints> <format> Return the clause as a document artifact, then note why the general-advertising carve-out keeps the clause reasonable and enforceable. </format>

Produces an insertable employee non-solicitation clause with reasonable carve-outs and a blue-pencil provision, ready to drop in.

๐Ÿ’ก

Pro tip: Keep the general-advertising carve-out; a no-poach clause with no exceptions can be struck down as an unreasonable restraint.

Combined Restrictive-Covenant Agreement

24/30

You are a senior employment lawyer who drafts layered restrictive covenants. <context> For a senior hire I want one agreement combining confidentiality, non-solicitation of clients and staff, and a limited non-compete, each as a separate severable section. </context> <inputs> - Company and employee: [PARTIES] - Role and access level: [SENIORITY, WHAT THEY SEE] - Non-compete scope, geography, duration: [DETAILS] - Non-solicit duration: [E.G. 12 MONTHS] - Consideration: [PAY, EQUITY, SEVERANCE] - Governing law: [JURISDICTION] </inputs> <task> Draft a combined restrictive-covenant agreement with clearly separated, independently severable sections: confidentiality, non-solicitation of clients, non-solicitation of employees, and a narrowly tailored non-compete, each with its own scope and duration. Add a legitimate-business-interest recital, the consideration, an overarching blue-pencil severability clause so one invalid covenant does not sink the rest, an acknowledgment of reasonableness, and a signature block. </task> <constraints> - Each covenant must stand alone and be independently severable; details as [BRACKETED PLACEHOLDERS]. - The weakest covenant failing must not void the others. - Template, not legal advice โ€” warn strongly that non-competes are restricted or banned in many places and this needs local counsel; do not fabricate statutes or citations. </constraints> <format> Return the agreement as a document artifact, then explain the severability design and which covenant is most likely to be enforced if the non-compete fails. </format>

Drafts a layered restrictive-covenant agreement with independently severable confidentiality, non-solicit, and non-compete sections, ready to review.

๐Ÿ’ก

Pro tip: Keeping each covenant severable means a court striking the non-compete still leaves your confidentiality and non-solicit protections intact.

Garden-Leave + Notice Clause

25/30

You are an employment lawyer who structures notice and garden-leave terms. <context> Instead of relying only on a non-compete, I want a garden-leave clause that keeps a departing employee on payroll but away from work and competitors during their notice period. </context> <inputs> - Employer and employee: [PARTIES] - Notice period: [E.G. 3 MONTHS] - Garden-leave restrictions: [NO CLIENT CONTACT, NO NEW JOB, ETC] - Governing law: [JURISDICTION] </inputs> <task> Draft a garden-leave clause: the employer's right to place the employee on garden leave during all or part of the notice period, continued pay and benefits during that time, the employee's obligations to stay away from the workplace, not contact clients or staff, remain available to assist with handover, and not start other work without consent, a confirmation that confidentiality and fiduciary duties continue, and an acknowledgment that garden leave may run alongside or offset any post-termination restrictions. Number sub-clauses for insertion into a contract. </task> <constraints> - Deliver as an insertable clause; details as [BRACKETED PLACEHOLDERS]. - Keep the employee paid throughout garden leave and preserve duties of good faith. - Template, not legal advice โ€” note garden-leave enforceability is jurisdiction-specific and a lawyer should review; do not invent statutes. </constraints> <format> Return the clause as a document artifact, then explain how garden leave can complement or reduce reliance on a post-termination non-compete. </format>

Generates an insertable garden-leave and notice clause that keeps a leaver paid but sidelined during notice, ready to drop in.

๐Ÿ’ก

Pro tip: Garden leave is often more enforceable than a non-compete because the employee stays paid; ask Claude how the two interact in your region.

Most people use 10% of Claude. Tutorials unlock the rest.

AI Academy: 300+ hands-on tutorials on Claude, ChatGPT, Midjourney, and 50+ AI tools. New tutorials added every week.

Start Your Free Trial

Confidentiality Clauses

5 prompts

General Contract Confidentiality Clause

26/30

You are a commercial contracts attorney who writes reusable boilerplate. <context> I need a solid, general-purpose confidentiality clause I can paste into most business contracts without over-engineering it. </context> <inputs> - Direction: [MUTUAL OR ONE-WAY] - What counts as confidential: [DEFINE OR USE A BROAD DEFINITION] - Survival after termination: [E.G. 3 YEARS] - Governing law: [JURISDICTION] </inputs> <task> Draft a clean, general confidentiality clause: a defined term for Confidential Information, the core obligation to keep it secret and use it only for the contract's purpose, the standard exclusions (public, already known, independently developed, lawfully obtained), a required-by-law disclosure carve-out with notice, permitted disclosure to representatives, return or destruction on termination, and a survival sub-clause. Keep it tight and readable with numbered sub-clauses. </task> <constraints> - Deliver as an insertable clause; details as [BRACKETED PLACEHOLDERS]. - Support a mutual or one-way version depending on the input. - Template, not legal advice โ€” add a brief reviewer note; never fabricate statutes or citations. </constraints> <format> Return the clause as a document artifact, then note the one sub-clause people most often forget (survival) and why it matters. </format>

Produces a clean, reusable general confidentiality clause with exclusions and survival, ready to paste into most contracts.

๐Ÿ’ก

Pro tip: Save the mutual version as your default; you can strike one side's obligations faster than you can add a missing survival clause later.

MOU / Letter-of-Intent Confidentiality Clause

27/30

You are a corporate lawyer who drafts preliminary deal documents. <context> We are signing a non-binding memorandum of understanding or letter of intent and I want a confidentiality clause that is binding even though the rest of the document is not. </context> <inputs> - Parties: [PARTY A AND PARTY B] - Purpose of the MOU/LOI: [WHAT THEY ARE EXPLORING] - Survival: [E.G. 2 YEARS] - Governing law: [JURISDICTION] </inputs> <task> Draft a mutual confidentiality clause for an MOU or LOI: a defined term for Confidential Information that expressly includes the existence and contents of the MOU and the discussions, the binding non-use and non-disclosure obligation, a clause stating this confidentiality section is binding while the rest of the MOU remains non-binding, standard exclusions, a required-by-law carve-out, return or destruction, and survival. Number the sub-clauses for insertion. </task> <constraints> - Deliver as an insertable clause; details as [BRACKETED PLACEHOLDERS]. - Explicitly make the confidentiality section binding despite the non-binding MOU. - Template, not legal advice โ€” add a reviewer note; do not fabricate statutes or citations. </constraints> <format> Return the clause as a document artifact, then explain the binding-vs-non-binding carve-out so the confidentiality survives even if the deal does not. </format>

Creates a binding mutual confidentiality clause for an otherwise non-binding MOU or LOI, ready to insert.

๐Ÿ’ก

Pro tip: Spell out that confidentiality is binding while the MOU is not; otherwise a leak from a dead deal may be hard to act on.

Consulting-Agreement Confidentiality Clause

28/30

You are a contracts lawyer who papers consulting engagements. <context> I have a consulting agreement and need a confidentiality clause that fits a consultant relationship, covering both my confidential information and the consultant's methods. </context> <inputs> - Client and consultant: [PARTIES] - Confidential info each way: [CLIENT DATA / CONSULTANT METHODS] - Survival: [E.G. 3 YEARS] - Governing law: [JURISDICTION] </inputs> <task> Draft a mutual confidentiality clause tailored to consulting: a defined term for Confidential Information covering the client's business data and the consultant's proprietary methods, mutual non-use and non-disclosure, a carve-out letting the consultant retain and reuse general skills, know-how, and residual knowledge in their head, permitted disclosure to the consultant's staff under confidentiality, standard exclusions, return or destruction of tangible materials, and survival. Number the sub-clauses for insertion. </task> <constraints> - Deliver as an insertable clause; details as [BRACKETED PLACEHOLDERS]. - Include a residual-knowledge carve-out balanced against protecting specific confidential data. - Template, not legal advice โ€” add a reviewer note; never fabricate statutes or citations. </constraints> <format> Return the clause as a document artifact, then explain the residual-knowledge carve-out and how to limit it so it does not swallow the whole obligation. </format>

Generates a consulting-tailored mutual confidentiality clause with a balanced residual-knowledge carve-out, ready to insert.

๐Ÿ’ก

Pro tip: Bound the residual-knowledge carve-out to unrecorded know-how only; an unlimited version can quietly cancel the whole clause.

Data-Protection-Aware Confidentiality Clause

29/30

You are a data-privacy lawyer who drafts confidentiality with data-handling in mind. <context> My contract involves sharing personal or regulated data, so I need a confidentiality clause that also addresses data protection, without pretending to be a full data-processing agreement. </context> <inputs> - Parties: [DISCLOSER AND RECIPIENT] - Data categories: [PERSONAL, HEALTH, FINANCIAL, ETC] - Security expectations: [ENCRYPTION, ACCESS CONTROLS] - Governing law / applicable privacy regime: [JURISDICTION] </inputs> <task> Draft a confidentiality clause with data-protection provisions: a defined term for Confidential Information that includes personal and regulated data, the non-use and non-disclosure obligation, minimum security expectations (need-to-know access, encryption in transit and at rest, no use beyond the contract's purpose), a breach-notification duty with a timeframe, a duty to assist with data-subject requests where applicable, return or secure deletion on termination, and an explicit note that a separate data-processing or data-sharing agreement may still be legally required. Number the sub-clauses for insertion. </task> <constraints> - Deliver as an insertable clause; details as [BRACKETED PLACEHOLDERS]. - State clearly this does not replace a required data-processing agreement. - Template, not legal advice โ€” warn that privacy laws vary and a qualified lawyer should review; do not invent statutes or citations. </constraints> <format> Return the clause as a document artifact, then explain what a full data-processing agreement adds beyond this confidentiality clause. </format>

Creates a data-protection-aware confidentiality clause with security and breach-notice terms, ready to insert.

๐Ÿ’ก

Pro tip: Treat this as a confidentiality clause, not a privacy compliance shortcut; ask your lawyer whether a full DPA is legally required.

Board / Advisor Confidentiality Clause

30/30

You are a corporate governance lawyer who advises boards and advisors. <context> A new board member or advisor will see highly sensitive company information. I need a confidentiality clause tailored to a board or advisory role, respecting fiduciary duties. </context> <inputs> - Company and the board member/advisor: [PARTIES] - Sensitive info they will access: [FINANCIALS, STRATEGY, CAP TABLE, DEALS] - Survival: [E.G. INDEFINITE FOR TRADE SECRETS] - Governing law: [JURISDICTION] </inputs> <task> Draft a confidentiality clause for a board member or advisor: a defined term covering board materials, discussions, and company confidential information, the duty to keep it confidential and use it only to perform the role, an acknowledgment of fiduciary duties and the duty to avoid trading on material non-public information, restrictions on sharing with the advisor's own firm or funds without consent, a carve-out for disclosures required by law with notice, return of materials on leaving the role, and long survival for trade secrets. Number the sub-clauses for insertion into an advisory or board agreement. </task> <constraints> - Deliver as an insertable clause; details as [BRACKETED PLACEHOLDERS]. - Address insider-trading awareness and conflicts with the advisor's other roles. - Template, not legal advice โ€” flag that securities and fiduciary rules apply and a lawyer should review; do not fabricate statutes or citations. </constraints> <format> Return the clause as a document artifact, then explain the material-non-public-information provision and why board-level confidentiality is stricter. </format>

Produces a board or advisor confidentiality clause addressing fiduciary duties and insider information, ready to insert.

๐Ÿ’ก

Pro tip: For investors sitting on your board, ask Claude to tighten the no-sharing-with-their-fund provision; it is the most common leak path.

Frequently Asked Questions

The prompts produce professional, well-structured documents you can fill in and sign, but Claude is not a lawyer and cannot guarantee enforceability. Every prompt instructs Claude to flag that a qualified attorney should review the document before you rely on it, especially for high-stakes deals or unusual jurisdictions.
A mutual (bilateral) NDA protects both sides because both are sharing confidential information, which fits partnerships, joint ventures, and vendor evaluations. A one-way (unilateral) NDA binds only the receiving party and fits situations where just one side discloses, like pitching investors or sharing a product with beta testers.
You can name your governing law and jurisdiction in the inputs and Claude will draft accordingly, but rules differ significantly by region, particularly for non-competes, which are banned or restricted in many places. Always have a local lawyer confirm the document is valid where you operate.
Every document comes with [BRACKETED PLACEHOLDERS] for party names, dates, terms, scope, and governing law. You search-and-replace each bracket with your real details before signing. Claude also returns a short list of the placeholders to fill so nothing is left blank by accident.
Non-solicitation clauses (of clients or staff) are generally more enforceable and less contentious than non-competes, which are banned or heavily limited in many jurisdictions. The prompts here let you draft either or combine them as independently severable sections so a weak covenant does not void the rest, but a lawyer should confirm what holds up locally.

Prompts are the starting line. Tutorials are the finish.

A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.

7-day free trial. Cancel anytime.