brand-pack-reader

Validates store outputs against verified values from a single brand-pack.md file.

1|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/williamsforeal/Cyclone-SS --skill brand-pack-reader
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brand-pack-reader
Source: https://github.com/williamsforeal/Cyclone-SS/tree/main/global-skills/brand-pack-reader
Command: npx skills add https://github.com/williamsforeal/Cyclone-SS --skill brand-pack-reader

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents your AI outputs from guessing brand-specific facts by enforcing that every brand detail comes directly from a verified brand-pack.md source, avoiding incorrect colors, pricing, CTAs, and structured copy elements.

Core Features & Use Cases

  • Zero-hallucination brand ingestion: Reads context/brand-pack.md at the START of each session and uses only explicitly provided values.
  • Strict validation and blockers: Refuses to proceed when placeholders like [PLACEHOLDER] or [INSERT DATE] are present, and flags missing required fields instead of filling gaps silently.
  • Mapped application across store build outputs: Applies brand name, palette (hex codes), typography, pricing, announcement bar, emoji benefit bullets, sticky/buy button labels, shipping line, icon bar, ticker items, testimonials, how-it-works steps, guarantee, FAQ, and navigation/footer labels consistently.

Quick Start

Use brand-pack-reader to ingest context/brand-pack.md and generate store copy, sections, and UI styling using only the extracted brand facts from that file.

Frequently Asked Questions about brand-pack-reader

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stop AI from hallucinating brand colors and pricing when generating store content?

To stop AI from hallucinating brand colors and pricing, you must enforce strict ingestion of a verified brand-pack.md file at the start of your session. This ensures the AI uses only explicitly provided values and blocks placeholders.

How do I generate consistent PDP sections and ad copy using only verified brand guidelines?

Generate consistent PDP sections and ad copy by applying mapped brand details like typography, hex codes, and CTAs directly from a brand pack file. The system requires missing fields to be reported rather than inferred.

What happens if my brand pack file contains placeholders like [INSERT DATE] during content generation?

If your brand pack file contains placeholders like [INSERT DATE] during content generation, the process halts. Strict validation blocks placeholders and flags the missing required fields instead of filling gaps silently.

Can I use a single brand pack file to apply UI styling and navigation labels across a store build?

Yes, you can use a single brand pack file for a store build. It consistently maps brand names, palettes, announcement bars, icon bars, navigation labels, and footer details across all structured content outputs.

Why does my structured brand content output include incorrect testimonials and shipping lines?

Structured brand content outputs include incorrect testimonials and shipping lines because the AI inferred missing data instead of reading verified values. Enforcing start-of-session ingestion of a brand pack prevents this.

Do I need to manually input emoji benefit bullets and guarantee text for every store section?

No, you do not need to manually input emoji benefit bullets and guarantee text for every store section. A brand pack reader ingests these details from your source file once and applies them consistently across all outputs.