thedaviddias/front-end-checklist

terms-of-service

Use when reviewing whether a website or web application has a visible Terms of Service link accessible from every page.

First seen Jun 19, 2026

Installation

$ npx skills add thedaviddias/front-end-checklist --skill terms-of-service

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from thedaviddias/front-end-checklist · top by installs.

npx skills add thedaviddias/front-end-checklist

Browse all from thedaviddias/front-end-checklist

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 74.1K
License MIT
Default branch main
Open issues 5
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

More metadata
category
security
priority
medium
difficulty
beginner
estimatedTime
10
source
frontendchecklist.io
url
https://frontendchecklist.io/en/rules/security/terms-of-service

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,350 B
  • docs SUMMARY.md 143 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 8 installs

SKILL.md

Link to your terms of service in the footer

Terms of Service protect your business by limiting liability, establishing jurisdiction, setting rules for user conduct, and specifying your rights to user-generated content — but only if users could reasonably discover and read them.

Quick Reference

  • Link to Terms of Service from the site footer on every page
  • Terms of Service (ToS) are not legally required in most jurisdictions, but they are best practice for any service with user accounts
  • Courts have found ToS unenforceable when they were not clearly presented or linked before the user took action
  • For enforceable acceptance, require users to check a checkbox 'I agree to the Terms of Service' during signup
  • Keep terms up to date — outdated terms that contradict current practices can create legal liability

Check

Check whether the website footer contains a link to a Terms of Service page. Verify the link is present on all pages including interior pages. Check that during user registration there is a checkbox or explicit acceptance step for the terms.

Fix

Add a 'Terms of Service' link to the site footer on every page. For services with user accounts, add an explicit acceptance checkbox during registration that links to the terms. Ensure the terms page has a stable URL.

Explain

Explain what Terms of Service are for, why they need to be discoverable before a user takes action, and the difference between browsewrap (just a link) and clickwrap (explicit acceptance) agreements.

Code Review

Review server config, headers, forms, and integration points related to Link to your terms of service in the footer. Flag exact responses, cookies, or browser behaviors that violate the rule, and verify them against the effective production-like response.


For full implementation details, code examples, and framework-specific guidance, see references/rule.md.

Rule page: https://frontendchecklist.io/en/rules/security/terms-of-service