chore: apply BRAND.md copy and remove duplicated brand guidelines

BRAND.md in usememos/.github is now the single source of truth for brand
copy. Delete docs/brand-guidelines.md, point references to BRAND.md, and
update the tagline, descriptions, docs introduction, llms.txt summary and
the homepage social image to the approved copy.

Author: boojack

AGENTS.md

@@ -8,7 +8,7 @@ Treat it as a **Next.js 16 marketing/docs site plus an account app**. Current ac
 
 ## Branding Authority
 
-Read `docs/brand-guidelines.md` before changing product messaging, taglines, default metadata, or social-preview copy. It is the authoritative messaging contract. Reuse `src/shared/lib/branding.ts` for approved brand strings.
+Brand positioning and approved copy live in [`BRAND.md`](https://github.com/usememos/.github/blob/main/BRAND.md) in the `usememos/.github` repository; it is the single source of truth. Do not keep brand guidelines in this repository. Read it before changing product messaging, taglines, default metadata, or social-preview copy, and reuse `src/shared/lib/branding.ts`, which copies its strings verbatim.
 
 ## Public Website Design Authority
 
@@ -170,3 +170,13 @@ Use `pnpm run preview` or `pnpm run deploy:dry-run` to validate Cloudflare produ
 - Set `NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY` before building the static account routes; deploy and upload check that it is present. There are no current `CLERK_SECRET_KEY` consumers or server-side Clerk handlers. Introduce server credentials and narrowly matched auth middleware together when a feature needs them.
 - Ordinary builds use committed API schemas. `pnpm docs:refresh` can fall back to a local snapshot after a failed download; inspect its log before claiming a snapshot is current.
 - Before adding persistence or a binding, document the feature's requirements and follow `docs/architecture.md` ("Future data layer"). D1, Drizzle, KV, and Clerk user-sync webhooks are not existing infrastructure or mandatory next steps.
+
+<!-- BEGIN:nextjs-agent-rules -->
+
+# This is NOT the Next.js you know
+
+This version has breaking changes — APIs, conventions, and file structure may all differ from your training data. Read the relevant guide in `node_modules/next/dist/docs/` (resolved from this file's directory; in monorepos the `next` package may not be visible from the repo root) before writing any code. Heed deprecation notices.
+
+This block is written and re-added by `next dev` — verify at `node_modules/next/dist/server/lib/generate-agent-files.js`. Removing it from a diff only re-creates the uncommitted change; committing it with your work keeps the tree clean.
+
+<!-- END:nextjs-agent-rules -->

DESIGN_SYSTEM.md

@@ -453,8 +453,8 @@ hover or supporting signal. Brand-filled controls MAY be used when the
 surrounding composition requires it, but blue MUST NOT become a default fill
 for every action and icon.
 
-Use `HeroAccent` for display emphasis, including the Homepage's “Keep it yours.”
-line. Its `text-brand-600 dark:text-brand-300` treatment is the standard brand
+Use `HeroAccent` for display emphasis, including the second line of the
+Homepage tagline. Its `text-brand-600 dark:text-brand-300` treatment is the standard brand
 accent, not a page-specific exception.
 
 Color rules:
@@ -603,7 +603,7 @@ system.
 
 ## 16. Content and voice
 
-`docs/brand-guidelines.md` defines the approved product tagline, supporting description, and messaging constraints. Use the shared constants in `src/shared/lib/branding.ts` for brand-level copy; page-specific headings and descriptions should describe their own subject.
+[`BRAND.md`](https://github.com/usememos/.github/blob/main/BRAND.md) in `usememos/.github` defines the positioning and approved copy. Use the shared constants in `src/shared/lib/branding.ts` for brand-level copy; page-specific headings and descriptions should describe their own subject.
 
 Words are part of the composition.
 

README.md

@@ -1,3 +1,3 @@
 <samp>website: [usememos.com](https://www.usememos.com)</samp>
 
-Brand messaging: [brand guidelines](docs/brand-guidelines.md). Visual design: [DESIGN_SYSTEM.md](DESIGN_SYSTEM.md).
+Brand messaging: [BRAND.md](https://github.com/usememos/.github/blob/main/BRAND.md). Visual design: [DESIGN_SYSTEM.md](DESIGN_SYSTEM.md).

content/docs/faq.mdx

@@ -5,7 +5,7 @@ description: Common questions about running and using Memos.
 
 ## What is Memos?
 
-Memos is a personal timeline for quick notes: write short memos as they come, and find them later by search, tag, or date. You run it yourself, so your memos stay on the server you choose.
+Memos is an open-source timeline for your thoughts. Write a memo in seconds, tag it, attach files, and move on. Every memo is private by default; share one with the people you choose, or with anyone who has the link, when you want to. Your notes are yours: you keep them where you decide, nobody else reads them, and you can take them with you at any time.
 
 ## Is Memos open source?
 

content/docs/getting-started.mdx

@@ -3,7 +3,7 @@ title: Getting Started
 description: Run Memos locally with Docker, create the first admin user, and write your first memo.
 ---
 
-Memos is a personal timeline for quick notes: write short memos as they come, and find them later by search, tag, or date. The shortest path to a running instance is one Docker command with SQLite and a local data volume. Harden deployment and storage once the instance is up.
+The shortest path to a running instance is one Docker command with SQLite and a local data volume. Harden deployment and storage once the instance is up.
 
 ## Prerequisite
 

content/docs/index.mdx

@@ -3,7 +3,9 @@ title: Documentation
 description: Official Memos documentation — self-host with Docker, configure storage and authentication, write and find memos in Markdown, and use the API.
 ---
 
-Memos is a personal timeline for quick notes: write short memos as they come, and find them later by search, tag, or date. It is open source and self-hosted, so your memos stay on the server you choose. Start with Getting Started, then move into deployment, configuration, and daily use.
+Memos is an open-source timeline for your thoughts. Write a memo in seconds, tag it, attach files, and move on. Every memo is private by default; share one with the people you choose, or with anyone who has the link, when you want to. Your notes are yours: you keep them where you decide, nobody else reads them, and you can take them with you at any time.
+
+Start with Getting Started, then move into deployment, configuration, and daily use.
 
 The usage and configuration guides cover **0.31.0**, the latest stable release. Read the [release changelog](/changelog/0-31-0) and [0.31 upgrade notes](/docs/operations/upgrade#upgrading-to-031) before upgrading. The API reference provides separate version selections.
 

docs/brand-guidelines.md

@@ -1,7 +1,7 @@
 /// <reference types="next" />
 /// <reference types="next/image-types/global" />
-import "./.next/types/routes.d.ts";
-import "./.next/types/root-params.d.ts";
+import "./.next/dev/types/routes.d.ts";
+import "./.next/dev/types/root-params.d.ts";
 
 // NOTE: This file should not be edited
 // see https://nextjs.org/docs/app/api-reference/config/typescript for more information.

next-env.d.ts

@@ -1,7 +1,7 @@
 const baseUrl = process.env.SMOKE_BASE_URL ?? "http://localhost:8788";
 
 const checks = [
-  { path: "/", type: "html", contains: "Catch a thought.", cacheControlIncludes: "s-maxage=31536000" },
+  { path: "/", type: "html", contains: "Your thoughts, your data,", cacheControlIncludes: "s-maxage=31536000" },
   {
     path: "/docs/faq",
     type: "html",

scripts/smoke-test.mjs

@@ -7,7 +7,7 @@ import { buildBreadcrumbJsonLd, buildMarketingMetadata } from "@/shared/lib/seo"
 
 export const metadata: Metadata = buildMarketingMetadata({
   title: "Brand",
-  description: "Official brand assets, logos, and usage guidelines for Memos, a personal timeline for quick notes.",
+  description: "Official brand assets, logos, and usage guidelines for Memos.",
   path: "/brand",
 });