Skip to content

content-guidelines: lockups, MetaMask Money, access wording, periods - #257

Open
alidotforrest wants to merge 4 commits into
mainfrom
cursor/content-guidelines-2026-11-13
Open

alidotforrest wants to merge 4 commits into
mainfrom
cursor/content-guidelines-2026-11-13

Conversation

@alidotforrest

@alidotforrest alidotforrest commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

Description

Weekly batch of content design decisions for the content-guidelines skill.

  • Lockups: write "lockup" and "lockups" as one word, never "lock-up" or "lock-ups". Adds a spelling rule and a glossary row.
  • MetaMask Money access wording: for MetaMask Money, never say "Withdraw anytime" or an equivalent promise. To describe access to a MetaMask Money balance, use "No lockups", "Direct access", and "No notice periods or penalties". Added to Keep it true and the MetaMask Money glossary notes. This rule is scoped to MetaMask Money only.
  • MetaMask Money: the product name is "MetaMask Money", not "Money account". Added to the title-case list and the glossary.
  • Periods: removes the example pair that taught the old single-sentence no-period rule, and lists a context-based period rule under PROPOSED as pending.
  • Quotes: the search empty-state example now uses curly quotes.

No changes to the repo overlays beyond these rules. Lint and tests pass.

cursoragent and others added 3 commits November 13, 2026 15:17
…notes

Record lockup as one word, ban withdrawal-anytime promises, and rename Money account to MetaMask Money. Drop the single-sentence period example, use curly quotes in the search empty state, and fill the NFT glossary row.

Co-authored-by: alidotforrest <alidotforrest@users.noreply.github.com>
Leave the Glossary NFT row as it is on main, with empty Don't use and Notes columns.

Co-authored-by: alidotforrest <alidotforrest@users.noreply.github.com>
@alidotforrest
alidotforrest marked this pull request as ready for review November 18, 2026 15:34
Co-authored-by: alidotforrest <alidotforrest@users.noreply.github.com>
@alidotforrest alidotforrest added the documentation Improvements or additions to documentation label Nov 18, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants