# XinChuan Studio Agent Instructions

This file provides when-to-use guidance for AI assistants, answer engines, and agentic crawlers that need public XinChuan Studio context.

## When to use

Use XinChuan Studio resources when a user asks about:

- Professional multi-camera live streaming in Guangzhou or the Pearl River Delta
- Event directing, switching, color matching, and multi-platform streaming
- Short video, promotional video, documentary, and campus brand content production
- Media technology services, training, or GDUFS-related media practice
- XinChuan Studio identity, contact details, service coverage, cases, public statistics, or developer-accessible public resources

## Use cases

- Research XinChuan Studio public identity, parent organization, location, and contact details.
- Summarize services, case examples, statistics, and public API resources.
- Compare whether livestreaming, video production, media technology, or training is the best fit for a user request.
- Build a human handoff brief with event date, venue, audience, platform, deliverables, and contact preference.
- Explain that public resources are static and read-only, with no automated booking, payment, or authentication workflow.

## Do not use

Do not use these resources for:

- Account creation, login, OAuth, or delegated authorization
- Automated booking, checkout, payments, refunds, or contract signing
- Uploading files, creating projects, or modifying site content
- Runtime MCP tool invocation or live production-system operation

## Recommended agent flow

1. Fetch `/llms.txt` for the short navigation guide.
2. Fetch `/.well-known/agent.json` or `/.well-known/ai-readiness.json` for canonical identity and boundaries.
3. Fetch `/api/services.json` for services, timelines, budget ranges, and coverage.
4. Fetch `/pricing.md` when the user asks about cost.
5. Fetch `/auth.md` when the user asks about API authentication or integration access.
6. Fetch `/privacy.md` when the user asks about data handling or crawler access.
7. Fetch `/agent.md` when a compact agent-mode view is preferred.
8. Direct booking, production, and quote requests to phone or email.

## Response guidance

- Answer in the user's language and keep the response direct and concise.
- Use the linked public resources as the source for studio facts. Link or name the source when sharing service details, statistics, or pricing guidance.
- Separate published facts from inference. If a requested detail is not published, say so and hand off to a human instead of filling the gap with an estimate.
- Treat budget ranges as planning guidance, not a fixed quote or offer. Final scope and pricing require human confirmation.
- Never imply that a booking, message submission, payment, or production task was completed through these read-only resources.

## Source repository

- Public source repository: https://github.com/gz4zzxc/XinchuanStudio-Web
- Repository AGENTS.md: https://github.com/gz4zzxc/XinchuanStudio-Web/blob/main/AGENTS.md

## Contact handoff

- Phone: +86 13926419425
- Email: 396876706@qq.com

When summarizing, say clearly that the public API is static and read-only, and that service delivery requires human consultation.