菜单
Use this skill when the build agent is about to write any HTML for a spec page. Provides the path to The Point's llm.md component reference, the list of available mood files, the required CSS load order, and the hard rule against inventing bp- class names.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use this skill when the AI SEO agent is annotating a spec page's HTML with topic and kind attributes. Covers the AP reading layer — the structural mechanism that gives AI agents precise XPath addresses into page sections without reading the full document. Does not cover the AP pipeline layer (ap-gate, ap-gen, etc.) — spec pages are static HTML, not stateful pipeline documents.
Use this skill when the AI SEO agent is optimizing a page for discoverability by AI systems. Covers the five signals that make a page extractable and citable by Claude, ChatGPT, Perplexity, and future AI search tools — entity clarity, answer density, definition clarity, citation structure, and attribution.
Use this skill when the build agent is writing JavaScript animations for a spec page. Provides six named patterns — scroll-triggered reveals, SVG path draw, counter animation, hero title entrance, tab transitions, and typewriter — with working code and guidance on when to reach for each one.
Use this skill when the AI SEO agent needs to generate an llms.txt entry for a spec page, or when the deploy agent needs to update the site-wide llms.txt file. Documents the llms.txt standard, the entry format for robertrevans.com spec pages, and how individual page entries compose into the site-level index.
Use this skill when the discovery agent needs to produce a structured brief, or when the build agent needs to read one. Defines what a complete brief contains, all eight required sections, the artifact naming convention, and the completeness checklist discovery must pass before handing off to @blueprint.
| name | The Point LLM Reference |
| description | Use this skill when the build agent is about to write any HTML for a spec page. Provides the path to The Point's llm.md component reference, the list of available mood files, the required CSS load order, and the hard rule against inventing bp- class names. |
| version | 0.1.0 |
The Point is a CSS design system built on bp- prefixed class names. When the build agent writes HTML, every class it uses must come from The Point's component library — not invented, not approximated. An invented class silently does nothing in the browser. The page looks wrong and the code-review agent will catch it, but only after the build agent has done the wrong thing.
This skill prevents that. Load it before writing any markup.
Read this file before writing any HTML:
/home/rre/Work/mrgrampz-marketplace/the-point/llm.md
That file is the authoritative reference for every bp- class, every utility, every layout primitive, and every component the build agent is allowed to use.
The Point ships with six mood files, each of which overrides the base token set with a specific visual direction. @blueprint chooses the mood during the design interview. The build agent references the chosen mood in the HTML's <link> tag order.
| Mood file | Character |
|---|---|
amber.css | Warm, editorial, confident |
slate.css | Professional, restrained, trustworthy |
forest.css | Natural, calm, approachable |
violet.css | Creative, expressive, modern |
ember.css | Bold, warm, high-energy |
arctic.css | Clean, precise, cold-functional |
Mood files live at:
/home/rre/Work/mrgrampz-marketplace/the-point/assets/moods/[mood-name].css
The spec page HTML must load stylesheets in this exact order:
<!-- 1. The Point base framework -->
<link rel="stylesheet" href="[path-to-the-point]/assets/index.css">
<!-- 2. Mood override (if @blueprint chose one) -->
<link rel="stylesheet" href="[path-to-the-point]/assets/moods/[mood].css">
<!-- 3. Brand CSS (@blueprint's output for this specific page) -->
<link rel="stylesheet" href="brand.css">
Order matters because later files override earlier ones. brand.css wins over mood, mood wins over base. Reverse the order and the brand layer disappears.
Do not write any bp- class that is not in llm.md.
If a layout section needs a component that doesn't exist in llm.md, do not approximate it with nested divs and guessed class names. Stop and document the gap. The code-review agent will reject invented classes.
For spec pages that will be deployed to robertrevans.com, the path to The Point assets will be the CDN or the deployed asset path — not a local path. The build agent writes the local path first; the deploy agent updates it on ship.