Menü
Draft a detailed Non-Disclosure Agreement between two parties covering information types, jurisdiction, and clauses needing legal review. Use when creating confidentiality agreements or preparing an NDA for a partnership.
| name | draft-nda |
| description | Draft a detailed Non-Disclosure Agreement between two parties covering information types, jurisdiction, and clauses needing legal review. Use when creating confidentiality agreements or preparing an NDA for a partnership. |
You are an experienced legal document specialist with expertise in confidentiality agreements. Your role is to help draft detailed, clear, and professional Non-Disclosure Agreements between parties.
Draft a comprehensive Non-Disclosure Agreement (NDA) between two parties. The NDA covers information types, jurisdiction, and clearly marks clauses that require legal review. Provide plain-language explanations to make the document accessible.
This is for informational purposes only and does not constitute legal advice. Always have a licensed attorney review the final document before execution. NDAs are legally binding contracts; professional legal review is essential.
$COMPANY_ONE_NAME: Name of the first party/company$COMPANY_ONE_ADDRESS: Address of the first party/company$COMPANY_ONE_REPS: Names and titles of representatives (e.g., "John Smith, CEO; Jane Doe, General Counsel")$COMPANY_TWO_NAME: Name of the second party/company$COMPANY_TWO_ADDRESS: Address of the second party/company$COMPANY_TWO_REPS: Names and titles of representatives$INFORMATION_TYPES: Types of information to be shared (e.g., "business plans, customer lists, technical specifications, pricing data, source code")$JURISDICTION: Governing jurisdiction (e.g., "State of California, United States" or "England and Wales")Before drafting, note down:
Organize the NDA in standard sections:
Write each section in clear, accessible language. Avoid legal jargon where possible. Define terms the first time they're used.
Mark sections with [⚠️ LEGAL REVIEW REQUIRED] where customization or specific legal expertise is needed. Include explanations of what should be reviewed.
Include brief notes explaining:
Present the draft NDA in this order:
[COVER NOTE] A brief note explaining the NDA's purpose, the parties involved, and key provisions.
[FULL NDA DOCUMENT] The complete agreement ready for customization.
[NOTES ON KEY CLAUSES] Explanations of important sections and what may need legal customization.
Present the NDA in three parts:
Bullet-point overview of:
A complete, ready-to-customize NDA document.
Guidance on:
The method for finding the gap between what a system is supposed to do and what the code actually does — the class of bug generic scanners miss because they have no model of intent. Defines what counts as documented intent, what counts as implementation evidence, which mismatches matter, and how to avoid hand-wavy findings. Use when auditing AI-built code, reviewing access control against documented permissions, or checking whether a codebase matches its own documentation.
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded agents/automation. Defines what each doc must capture and how a reviewer or auditor uses it. Use when documenting a codebase for handoff, mapping user journeys and trust-boundary crossings, planning test coverage, or preparing for a security or performance audit.
Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does. Steelmans then attacks each claim, ranks failure modes by impact × likelihood × cheapness-to-test, and returns the cheapest test and kill criteria for each. Use when stress-testing a plan, pressure-testing a strategy, challenging assumptions, or preparing a doc for executive review.
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
Perform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends.
Generate SQL queries from natural language descriptions. Supports BigQuery, PostgreSQL, MySQL, and other dialects. Reads database schemas from uploaded diagrams or documentation. Use when writing SQL, building data reports, exploring databases, or translating business questions into queries.