ask-legal-terms-privacy-policy

Maintains the shared Terms of Service and Privacy Policy React package used across five sites.

74|11|Updated Jul 4, 2024
One-click install
npx skills add https://github.com/OpenSourceAGI/qwksearch-research-agent --skill ask-legal-terms-privacy-policy-opensourceagi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ask-legal-terms-privacy-policy
Source: https://github.com/OpenSourceAGI/qwksearch-research-agent/tree/main/skills/ask-legal-terms-privacy-policy
Command: npx skills add https://github.com/OpenSourceAGI/qwksearch-research-agent --skill ask-legal-terms-privacy-policy-opensourceagi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Five sites each carried their own 200-line copy of the same legal JSX, letting the Terms of Service and Privacy Policy drift apart silently. This Skill guides work on the single shared package (packages/legal-terms-privacy-policy) so every site renders one consistent legal document. ## Core Features & Use Cases - Single source of truth: Edit clauses once in src/react/full-terms.tsx and src/react/summary.tsx; all consuming sites update immediately since the package ships raw TypeScript with no build step. - Two entry points: Import LegalTermsPrivacyPolicy from legal-terms-privacy-policy/react for the full page with the full/summary switch, or use the React-free root entry for types and LEGAL_SUMMARY_URL in server code. - Troubleshooting guidance: Diagnose raw-TSX transpile errors, missing back links, client-component boundaries, and stylesheet @import ordering issues. - Use Case: You need to update the CCPA clause across QwkSearch, Debate AI, and three other properties — edit the clause once in the package, keep the summary in sync, and every site reflects the change without rebuilding. ## Quick Start Ask the AI to update a clause in the shared legal-terms-privacy-policy package and verify the change renders in the reference consumer page.

Frequently Asked Questions about ask-legal-terms-privacy-policy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a shared privacy policy page to a Next.js app?

Import LegalTermsPrivacyPolicy from legal-terms-privacy-policy/react and render it with appName, contactEmail, lastRevisedDate, and homeUrl props. Add the package to transpilePackages in next.config.mjs because it exports raw TypeScript with no build step.

How do I update a Terms of Service clause across multiple sites?

Edit the clause in src/react/full-terms.tsx and mirror the change in src/react/summary.tsx inside the shared package. Never edit a consumer's page copy; the package exists to prevent sites from drifting apart.

Why does importing legal-terms-privacy-policy cause a syntax error?

The package exports raw .ts/.tsx files with no dist build, so bundlers that do not transpile node_modules throw Unexpected token errors. Add the package to transpilePackages in Next.js or the equivalent allowlist in your bundler.

Can I use the legal package in server components without React?

Yes, the root entry legal-terms-privacy-policy exports LegalTermsPrivacyPolicyProps, LegalVariant, and LEGAL_SUMMARY_URL with no React dependency. Only the /react entry carries 'use client' and requires a client boundary.

Why is the back link missing from the legal page?

The back link only renders when the homeUrl prop is passed. Omitting it intentionally removes the link and leaves an empty span to preserve layout, so pass homeUrl to restore it.