OpenParable
Skip to content
← Back to skills

Experience System Blueprint

Design
experience-system-blueprint

Experience System Blueprint is an Agent Skill for design published in the gtmagents/gtm-agents repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Documentation pattern for translating brand platforms into modular experience systems.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/gtmagents/gtm-agents/blob/HEAD/plugins/brand-strategy/skills/experience-system-blueprint/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/experience-system-blueprint, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Experience System Blueprint Skill

When to Use

  • Creating scalable design systems anchored in brand strategy.
  • Handing off brand concepts to product, web, or event teams.
  • Auditing touchpoints for coherence and accessibility.

Framework

  1. System Principles – design tenets, accessibility standards, inclusivity commitments.
  2. Component Library – modules for hero sections, CTAs, motion behaviors, environmental elements.
  3. Sensory Spec – visual, motion, audio, haptics guidelines with do/don't examples.
  4. Channel Adaptations – matrices showing how components flex by channel/device.
  5. QA & Measurement – checklist + instrumentation hooks to track fidelity and impact.

Templates

  • Blueprint deck with principle → component → channel mapping.
  • Figma/Notion doc outlining specs, tokens, and usage rules.
  • QA worksheet for reviewing executions before launch.

Tips

  • Version-control blueprints so teams know which system is authoritative.
  • Embed accessibility best practices early to avoid retrofits.
  • Pair with design-multi-channel-brand-experience command for turnkey toolkits.