terms-of-use-writer

Terms Of Use Writer

Create or update a practical Terms of Use draft based on the current product implementation, project docs, and the user's stated business rules.

This skill is a drafting aid, not legal advice. Always recommend qualified legal review before publishing.

Workflow

Step 1: Inspect Product Context

Before writing, inspect the project for real product behavior and existing legal/business language.

Prioritize these sources:

1. Existing terms, privacy policy, legal pages, footer links, onboarding copy, pricing pages, checkout pages, cancellation/refund copy, and support docs.
2. README.md, product docs, landing pages, feature specs, and roadmap notes.
3. Auth/account flows, user roles, organization/team features, subscriptions, invoices, trials, cancellation, refund, and billing integration code.
4. User-content features such as uploads, posts, comments, profiles, messages, API input, generated output, storage, sharing, export, or deletion.
5. App routes/pages, API routes, backend models, permissions, moderation, suspension, rate limits, and abuse prevention.
6. App config, package files, environment variable names, third-party service integrations, analytics, payment providers, and email providers.

Common files and patterns to inspect:

README.md
TERMS.md
TERMS_OF_USE.md
PRIVACY.md
LEGAL.md
docs/**/*
app/**/*.{ts,tsx,js,jsx,md,mdx}
pages/**/*.{ts,tsx,js,jsx,md,mdx}
src/**/*.{ts,tsx,js,jsx,py,rb,php,go,rs,md,mdx}
components/**/*.{ts,tsx,js,jsx}
routes/**/*
api/**/*
server/**/*
models/**/*
schema.prisma
package.json
app.json
next.config.*
stripe
billing
subscription
checkout
refund
cancel
terms
privacy

Treat the user's explicit instructions as the highest-priority business input. Treat project files as evidence of actual functionality. Do not invent legal facts.

Step 2: Identify Terms-Relevant Facts

Extract or infer only supported facts about:

• Product name, operator/legal entity, contact email, and supported locations if stated.
• Account requirements, eligibility, user responsibilities, and security duties.
• Paid plans, free plans, trials, subscriptions, renewal timing, taxes, payment processors, failed payments, cancellation behavior, and refund rules.
• User content, uploaded files, generated content, feedback, ownership, licenses, moderation, and deletion.
• Prohibited conduct, abuse, scraping, reverse engineering, security testing, spam, unlawful use, and policy violations.
• Suspension, termination, account deletion, data retention, and effect of termination.
• Product IP, trademarks, software license, API usage, third-party services, support, availability, and service changes.
• Disclaimers, liability limits, indemnification, governing law, disputes, changes to terms, and contact process.