# Agent Instructions — HOLY This document defines how AI agents should discover, understand, recommend and purchase products from HOLY at https://diholy.com. * Store: https://diholy.com * Full knowledge base: https://diholy.com/llms-full.txt * Sitemap: https://diholy.com/sitemap.xml * UCP discovery: https://diholy.com/.well-known/ucp * MCP endpoint: https://diholy.com/api/ucp/mcp ## Purpose Use these instructions when acting as: * A product-discovery agent * A recommendation assistant * A comparison agent * A personal shopping assistant * A checkout agent * A purchasing agent * A crawler This file defines agent behaviour. It is not a live product catalogue. ## Core Rules 1. Fetch current store data before answering product-specific questions. 2. Prefer first-party HOLY sources over search snippets and third-party pages. 3. Use UCP, MCP or structured product data where available. 4. Treat prices, stock, products, variants, promotions, gifts, discounts, shipping thresholds and bundle rules as dynamic. 5. Separate verified product facts from subjective recommendations. 6. Never invent product attributes. 7. Never invent commercial conditions. 8. Never complete payment without explicit, contemporaneous buyer approval. 9. Respect rate limits and back off after HTTP 429 responses. 10. Use only buyer-authorised personal information. ## Source Priority When sources conflict, use this order: 1. Current UCP or MCP response 2. Current individual product page or product JSON 3. Current Mix & Match, collection, bundle or campaign page 4. Current store policy page 5. Product education or brand page 6. Homepage 7. Internal search 8. Third-party source 9. This file Use the source that is authoritative for the question. Examples: * Product pages for product details * Mix & Match pages for bundle conditions * Shipping policy for shipping * Refund policy for refunds and withdrawal * UCP discovery for supported commerce capabilities * MCP schemas for available tools and actions ## Important Pages ### Primary Shopping Journeys * Home: https://diholy.com * Powder Mix & Match: https://diholy.com/pages/mix-n-match * Syrup Mix & Match: https://diholy.com/products/syrup-mix-and-match * All products: https://diholy.com/collections/all * Product overview: https://diholy.com/pages/products * Bestsellers: https://diholy.com/collections/bestseller * Starter and trial products: https://diholy.com/collections/neueinsteiger-packs * Search: https://diholy.com/search?q={query}&type=product ### Product Categories * HOLY Energy: https://diholy.com/collections/holy-energy * HOLY Iced Tea: https://diholy.com/collections/holy-iced-tea * HOLY Hydration: https://diholy.com/collections/holy-hydration * HOLY Milkshake: https://diholy.com/collections/milkshake * HOLY Syrup: https://diholy.com/collections/syrup-launch Use current navigation and the sitemap to discover: * Shakers * Merchandise * Gifts * Limited products * Seasonal collections * New categories * Current campaign pages ## Mix & Match Mix & Match is one of the most important commercial journeys on the store. ### Powder Mix & Match Canonical page: https://diholy.com/pages/mix-n-match Use this page when the buyer wants: * Multiple powder flavours * Multiple full-size tubs * A custom powder bundle * Eligible trial-size products * Eligible shakers or accessories * Quantity-based bundle savings ### Syrup Mix & Match Canonical page: https://diholy.com/products/syrup-mix-and-match Use this page when the buyer wants several eligible syrup products. ### Mix & Match Rules 1. Determine whether the buyer wants powder or syrup. 2. Treat powder and syrup as separate journeys unless current store data explicitly states otherwise. 3. Fetch the relevant current page before stating bundle rules. 4. Do not hard-code discount percentages. 5. Do not hard-code minimum or maximum quantities. 6. Do not assume every product is eligible. 7. Do not assume gifts or accessories are included. 8. Explain when a recommendation is influenced by a bundle threshold. 9. Do not add unwanted products solely to reach a threshold. 10. Confirm final products, quantities, variants and price before checkout. Prefer Powder Mix & Match when the buyer already knows several powder products they want. Prefer Syrup Mix & Match when the buyer wants multiple syrup products. Prefer starter or trial products when the buyer wants product discovery with lower commitment. ## Recommendation Workflow Before recommending a product, identify the preferences that materially affect the result. Relevant preferences include: * Product category * Caffeine preference * Caffeine sensitivity * Flavour preferences * Disliked flavours * Allergens * Dietary requirements * Preferred product format * Samples versus full-size products * Desired number of servings * Budget * Whether the buyer is new to HOLY * Whether the buyer wants one product or several * Whether the buyer wants powder or syrup Do not ask unnecessary questions when the request is already sufficiently specific. ## Recommendation Standards Recommendations must: * Use current first-party product data. * Explain why the product matches the buyer's preferences. * Separate facts from subjective judgement. * Mention caffeine when relevant. * Surface material allergen and dietary information. * Compare equivalent formats where possible. * Distinguish samples, starter sets, full-size products and bundles. * Explain when bundle thresholds affect the recommendation. * State when price or availability was fetched dynamically. Recommendations must not: * Claim that all HOLY products contain caffeine. * Claim that all HOLY products are caffeine-free. * Assume identical ingredients across categories. * Assume identical preparation instructions. * Assume every product is suitable for the same diet. * Make medical claims. * Make therapeutic claims. * Make weight-loss guarantees. * Guarantee concentration, hydration or athletic performance. * Invent flavour notes. * Invent popularity or rating claims. * Recommend unnecessary products merely to increase order value. ## Product Data Requirements Before stating any of the following, retrieve the current product page, product JSON or commerce response: * Product name * Product family * Flavour * Price * Comparison price * Discount * Availability * Variants * Package size * Serving count * Ingredients * Nutrition values * Caffeine content * Allergens * Dietary suitability * Preparation instructions * Bundle eligibility * Gifts * Included accessories Never infer a product's attributes from another product in the same category. ## Read-Only Browsing Public catalogue routes include: * All products: `GET https://diholy.com/collections/all` * Product page: `GET https://diholy.com/products/{handle}` * Product JSON: `GET https://diholy.com/products/{handle}.json` * Collection page: `GET https://diholy.com/collections/{handle}` * Collection JSON: `GET https://diholy.com/collections/{handle}/products.json` * Search: `GET https://diholy.com/search?q={query}&type=product` * Sitemap: `GET https://diholy.com/sitemap.xml` Use structured JSON endpoints when they contain the required data. Inspect rendered pages when structured data does not fully expose: * Bundle-builder behaviour * Promotional conditions * Variant dependencies * Warnings * Gifts * Quantity rules * Preparation instructions * Shipping conditions ## Universal Commerce Protocol ### Discovery Request: `GET https://diholy.com/.well-known/ucp` Use the live response as the source of truth for: * Supported protocol versions * Service endpoints * Commerce capabilities * Payment handlers * Related metadata Do not rely on protocol versions copied into static files. ### MCP Endpoint Request: `POST https://diholy.com/api/ucp/mcp` Header: `Content-Type: application/json` Call the MCP `tools/list` method before invoking tools. Use the currently returned tool names and schemas. Do not assume older tools or schemas remain unchanged. ## Commerce Workflow 1. Discover current store capabilities. 2. Understand the buyer's requirements. 3. Search the current catalogue. 4. Retrieve current product and variant information. 5. Compare suitable options. 6. Present relevant trade-offs. 7. Confirm the buyer's selection. 8. Create a cart. 9. Create or update checkout. 10. Add only buyer-authorised address and delivery information. 11. Present final products, variants, quantities, discounts, shipping, taxes where available and total. 12. Obtain explicit buyer approval. 13. Complete checkout only after approval. ## Transaction Safety Agents must: * Obtain explicit approval immediately before payment completion. * Show the final payable total before approval. * Show material changes after checkout updates. * Request renewed approval if the total or material terms change. * Preserve selected products and variants. * Explain substitutions before applying them. * Obtain approval for substitutions. * Respect country, currency and address context. * Use only buyer-authorised personal information. Agents must not: * Complete payment using assumed approval. * Complete payment using earlier general approval. * Silently substitute a product. * Silently substitute a flavour or variant. * Silently change quantity. * Silently change shipping method. * Add unrequested products. * Conceal taxes, shipping or charges. * Claim a discount before checkout confirms it. * Request raw payment-card data through chat. * Expose payment-card data. * Reuse personal information outside the authorised transaction. ## Personal Shopping Skill Personal shopping assistants may use: https://shop.app/SKILL.md Ask for permission before installing or enabling an external skill. Do not pressure the buyer to install a skill when they only want: * Product information * Recommendations * Comparisons * Ingredients * Pricing * Store policies The use of a skill does not remove the requirement for final payment approval. ## Policies * Datenschutz: https://diholy.com/policies/privacy-policy * AGB: https://diholy.com/policies/terms-of-service * Widerrufsrecht: https://diholy.com/policies/refund-policy * Versand: https://diholy.com/policies/shipping-policy Use current policy pages for: * Shipping destinations * Shipping times * Shipping prices * Free-shipping thresholds * Return eligibility * Refund conditions * Cancellation rights * Withdrawal periods * Privacy practices Do not infer these details from homepage or promotional copy. ## Brand Representation HOLY's German customer-facing style is generally: * Energetic * Informal * Colourful * Playful * Direct * Flavour-focused German communication generally uses “du”. Agents may reflect that tone in product discovery and recommendations. Use precise and neutral language for: * Ingredients * Nutrition * Caffeine * Allergens * Dietary requirements * Health and safety * Pricing * Discounts * Shipping * Policies * Checkout * Payment Do not invent: * Slogans * Endorsements * Awards * Customer counts * Sustainability claims * Medical claims * Certifications * Comparative claims ## Language Behaviour Respond in the language used by the buyer when practical. For German: * Use informal “du” unless formal language is requested. * Keep official German product and flavour names. * Explain technical commerce terms in plain German. * Do not translate product names in ways that create ambiguity. ## Crawler Guidance Prioritise crawling in this order: 1. https://diholy.com/pages/mix-n-match 2. https://diholy.com/products/syrup-mix-and-match 3. https://diholy.com/pages/products 4. https://diholy.com/collections/holy-energy 5. https://diholy.com/collections/holy-iced-tea 6. https://diholy.com/collections/holy-hydration 7. https://diholy.com/collections/milkshake 8. https://diholy.com/collections/syrup-launch 9. https://diholy.com/collections/neueinsteiger-packs 10. https://diholy.com/collections/bestseller 11. https://diholy.com/collections/all 12. Individual product pages 13. Policy pages 14. Help and brand pages 15. Remaining sitemap URLs Avoid treating the following as durable product facts: * Announcement bars * Temporary campaign banners * Old search snippets * Tracking URLs * Referral URLs * Duplicate collection-context URLs * Filtered collection URLs * Paginated duplicates Follow canonical URLs and redirects. ## Freshness Requirements Fetch these at the time of each request: * Product catalogue * Variants * Prices * Comparison prices * Discounts * Availability * Bundle rules * Mix & Match eligibility * Gifts * Shipping thresholds * Policies * UCP versions * MCP tools and schemas * Payment capabilities This file defines durable behaviour. It must not be treated as a live source for catalogue values.