RaySpec is a Claude Code plugin that takes any idea, brief, or URL and runs it through a seven-agent Ray Pattern pipeline — one command as the entry point, specialized agents as the rays — to produce a complete, deployed HTML spec page built on The Point CSS framework and optimized for both traditional SEO and AI discoverability.
One command, seven agents, a live spec page. The entry point is a single slash command. The pipeline handles everything else.
Most AI page generators are a single large prompt with no quality gate and no design system. RaySpec is a pipeline: seven specialized agents, each with one job, each producing a reviewed artifact the next agent reads. The last agent is the one nobody else is building — an AI SEO pass that optimizes for answer density and entity clarity, not keyword density, so the page gets found by Claude, ChatGPT, and Perplexity, not just Google.
/spec-page [your idea, brief, or URL]
Not a single large prompt. A sequence of specialized agents, each with one job, each producing a reviewed artifact the next agent reads.
Takes a brief, URL, or blank slate. Interviews, extracts, confirms. Produces the structured discovery brief.
Design interview. Chooses mood, resolves typography, documents every visual decision. Produces brand.css + design rationale.
Reads llm.md and the brief. Every bp- class it uses must exist in llm.md. Produces the complete single-file HTML.
Quality gate. Eight specific checks. Returns PASS or NEEDS WORK. Same failure twice escalates to user.
Traditional search optimization. Title tag, meta description, Open Graph, canonical URL, structured data, heading hierarchy.
Optimizes for AI discoverability. Answer density, entity clarity, citation structure, AP reading layer, llms.txt entry.
Ships to target host. Updates site index and llms.txt. Writes deploy log entry. Reports live URL.
Seven jobs, seven agents, each with a defined input, a defined output, and a list of what it must not do. Engineers should understand the full system from this section alone.
Every RaySpec page is built on The Point CSS framework — a design system built for AI agents to read and use. One import, one optional brand file, every component documented in llm.md.
Every layout primitive, component, and utility is a bp- prefixed class. An invented class silently does nothing in the browser — the system enforces that every class the build agent uses must exist in llm.md.
Six pre-built color directions. Blueprint chooses one during the design interview. The mood file loads between index.css and brand.css — the CSS @layer system ensures brand.css always wins.
The authoritative reference for every bp- class. The build agent reads it before writing any markup. If a component isn't in llm.md, it doesn't go on the page — the code-review agent will catch invented class names.
CSS load order is enforced: index.css → mood → brand.css. The @layer system makes brand.css the final word on every property it touches.
AI systems don't rank pages. They extract answers from them. Optimizing for extraction requires a different discipline than optimizing for crawl rank.
Ranking signals — what Google crawls
Extraction signals — what AI systems read
How RaySpec differs from other page generation approaches.
| Feature | RaySpec | MindStudio / Ajelix | Mintlify | Manual prompting |
|---|---|---|---|---|
| Pipeline structure | 7 specialized agents, each with one job | Single large prompt | Single pass from code comments | One-off, no structure |
| Quality gate | Dedicated code review agent — 8 specific checks | None | None | None |
| Design system | The Point CSS — agent-enforced | None | Custom, limited to docs | None |
| Traditional SEO pass | Dedicated SEO agent | None | None | Manual |
| AI SEO pass | Dedicated AI SEO agent | None | None | None |
| Claude Code integration | Native plugin | None | None | Prompt only |
| Output type | Spec pages for concepts, tools, architectures | Generic landing pages | API reference docs only | Any (no quality guarantee) |
Agents are the execution layer. Skills are the knowledge layer. Each skill file is loaded by the relevant agent before it does any work.
spec-page-brief-format
Defines the eight required sections of a complete brief. The contractor must be able to build from the permit alone. If the brief is vague, the building will be wrong. This skill prevents the discovery agent from handing off an incomplete brief.
the-point-llm
Loads the path to llm.md and enforces the hard rule: do not write any bp- class that is not in llm.md. An invented class silently does nothing in the browser. Reading llm.md is the build agent's most critical action.
anime-js-animations
Six named animation patterns for Anime.js v4. Scroll-triggered reveals (Pattern 1), SVG path drawing (Pattern 2), counter animation (Pattern 3), hero word-by-word entrance (Pattern 4), tab transitions (Pattern 5), terminal typewriter (Pattern 6). Pattern selection is deterministic — section type maps directly to pattern.
ai-seo-principles
The five AI SEO signals. AP reading layer annotation patterns. Differentiation question structure. Citation audit criteria. llms.txt format and site index conventions. The knowledge layer the AI SEO agent reads before touching any HTML.
The plugin is working when it can generate this page from the README. The README points to the page. The page points to the README. The circularity is the demonstration.
RaySpec ships as a Claude Code plugin. Every agent is an agent file. Every skill is a skill file. The pipeline is the plugin.json manifest listing each agent in sequence. Nothing is hidden in a prompt — the architecture is the implementation.
The source is public. The Ray Pattern is a pipeline architecture where one command serves as the single entry point and specialized agents fan out from it as rays — each with one job, reviewed artifacts at each handoff, and a clean separation between discovery and execution. Every pipeline you build from this pattern shares the same skeleton: one entry command, N specialized agents, reviewed artifacts at each handoff.
One command. The pipeline handles the rest.
Install instructions: see README at github.com/revans/rayspec