← Plugin catalog
Other
Fotoluce
FOTOLUCE Di Spartà Lucia v1.0.0
Publisher description
From the marketplace listing
Fotoluce helps users search and compare the current photography catalogue, assemble evidence-based camera kits, review store policies, manage their linked Fotoluce cart, continue to Fotoluce checkout, and view their own orders.
Language: English · Automatically detected from descriptions.
Files & skills
File archives
Plugin package10 files · 4.04 KBBrowse files →
Skill instructions
fotoluce-kit-builder2.33 KB
--- name: fotoluce-kit-builder description: Build a Fotoluce camera, lens, and accessories kit when a shopper wants compatible components, a complete setup, or additions for a specific camera or model. --- # Fotoluce Kit Builder Build an evidence-based kit from current Fotoluce products. Keep compatibility evidence distinct from merchandising recommendations. ## Establish the base 1. Identify the camera or other base item, intended use, total budget, and required components. If the base item is unclear, use `search_products` and let the shopper disambiguate materially different models. 2. Call `get_product` for the selected base and inspect its attributes and relationships. 3. Treat `included_in_box` relationships as already included, not as extra purchases. ## Select components Use the following evidence order: 1. An explicit model compatibility attribute on the candidate is strong evidence for that exact model. 2. An exact shared lens-mount attribute, such as the same `attacco-mirrorless` or `attacco-reflex` value, supports a mount match. Also check sensor-format attributes when present and disclose missing coverage information. 3. An `often_bought_together` relationship is a curated Fotoluce recommendation, not proof of technical compatibility. Call `get_product` on the candidate and look for stronger attribute evidence before calling it compatible. 4. Brand-level compatibility alone is insufficient for model-level compatibility. Present it only as requiring confirmation. Search for lenses using the exact returned mount value plus the shopper's use case, then inspect each candidate with `get_product`. Prefer in-stock options unless the shopper accepts unavailable items. Never infer compatibility from similar names, descriptions, brand, price, or category alone. ## Present the kit Separate the result into: - base item; - included-in-box items; - compatibility-confirmed components and the evidence for each; - curated or generic recommendations that still need confirmation; - current total for items that must be purchased, excluding included items; - availability, promotion, and compatibility caveats. If reliable evidence is missing, say that compatibility cannot be confirmed and link the candidate for human verification. Do not add items to the cart unless the shopper explicitly asks; hand off cart actions to the purchase workflow.
Referenced files: 1
fotoluce-order-assistant1.22 KB
--- name: fotoluce-order-assistant description: Review and explain a linked customer's Fotoluce orders when they ask about order history, payment state, fulfillment, pickup, shipment, or tracking. --- # Fotoluce Order Assistant Use only orders belonging to the explicitly linked Fotoluce account. 1. If the shopper asks generally about recent orders, call `list_orders` and identify the requested order without guessing a code. 2. Call `get_order` for the selected order before explaining its current state. 3. Distinguish order status, payment status, and fulfillment status. Report shipment tracking or pickup information only when returned by the tool. 4. Summarize the items, totals, current status, and the clearest next action. Link the Fotoluce order page when available. 5. If the shopper needs policy or support information, call `get_store_info` and provide the official contact or policy link. Do not reveal whether an order belongs to another customer, expose internal identifiers, infer delivery dates, or claim that a missing tracking code means the order has not shipped. This workflow cannot cancel, edit, return, refund, or pay an order; explain that limitation and direct the shopper to Fotoluce support or the hosted order page.
Referenced files: 1
fotoluce-product-advisor1.4 KB
--- name: fotoluce-product-advisor description: Find and compare current Fotoluce photography products when a shopper asks for recommendations, prices, availability, promotions, or alternatives within stated needs or budget. --- # Fotoluce Product Advisor Help the shopper choose from Fotoluce's current catalogue using the Fotoluce MCP tools as the source of truth. 1. Identify the product class, intended use, budget, and any hard constraints already stated. Ask a short follow-up only when a missing constraint would materially change the shortlist. 2. Call `search_products` with a concise product name, model, or category rather than the shopper's whole sentence. Apply price, brand, and availability filters when the request provides them. 3. Shortlist no more than four relevant results. Call `get_product` for the strongest candidates when detailed attributes are needed to compare them. 4. Compare `current_price`, availability, meaningful attributes, and active promotions. Treat the returned observation time as the freshness boundary. 5. Explain the tradeoffs in plain language and link to each canonical Fotoluce product page. Do not invent specifications, compatibility, stock, delivery dates, promotion eligibility, or product relationships. If a fact is absent, label it as unconfirmed. Do not modify the cart unless the shopper explicitly asks to do so; use the purchase workflow for cart or checkout actions.
Referenced files: 1
fotoluce-purchase-assistant1.33 KB
--- name: fotoluce-purchase-assistant description: Manage a linked Fotoluce cart and continue to hosted checkout when a shopper asks to add, change, remove, clear, review, or check out selected products. --- # Fotoluce Purchase Assistant Use Fotoluce's authenticated cart as the single source of truth. 1. Call `get_cart` before any mutation and use its current generation. 2. Resolve every requested product to a stable `item_id`. Ask before acting when the item, variant, or quantity is ambiguous; do not substitute a similar product silently. 3. For each logical mutation, use a unique idempotency key and the freshest cart generation. Read the complete cart returned by the mutation before deciding the next action. 4. Never clear the whole cart unless the shopper explicitly requests that exact action. 5. Before checkout, verify the latest cart is non-empty and `can_checkout` is true. Call `create_checkout_link` only for that current generation. 6. Explain current items, warnings, totals, and the next step. The checkout link hands control to Fotoluce, where address, delivery, final totals, terms, and payment are confirmed. Do not claim that generating a checkout link reserves stock, creates an order, or completes payment. Never handle card credentials or promise that a price or availability will remain unchanged after the observation time.
Referenced files: 1
Package details
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
- Package author
- FOTOLUCE Di Spartà Lucia
Package observed Oct 2, 2026.
Technical details
- First seen
- Sep 30, 2026 · 22:02 UTC
- Last seen
- Oct 2, 2026 · 18:00 UTC
- Collection status
- Collected
plugin_asdk_app_6a95a9b0a92c8191aaf3c8cf0a1f3090
Download plugin data (JSON)