Scheduler - LLMs

#Overview

PrimeUI publishes the Vue Scheduler docs as markdown-friendly endpoints. Use them when an assistant needs the current Scheduler API, compound structure, setup steps, demos, and reference pages without scraping the rendered site.

Good Scheduler prompts give the assistant three things: the setup page, the architecture page, and the exact feature or view page for the task. Add API or reference pages only when the task needs a type, emitted event, slot payload, or data attribute.

#Usage

https://vue.primeuipro.dev/llms.txt
https://vue.primeuipro.dev/llms-full.txt
https://vue.primeuipro.dev/raw/docs/scheduler.md

/llms.txt is the compact documentation map. /llms-full.txt contains the full documentation bundle. /raw/docs/<path>.md returns one page as clean markdown, which is useful when a tool should focus on a single Scheduler topic.

Use /llms.txt for discovery, /raw/docs/... for focused work, and /llms-full.txt when the assistant needs broad context across views, features, demos, and references.

#Scheduler Pages

Point the assistant at the Scheduler index first, then add the exact page that matches the task.

https://vue.primeuipro.dev/raw/docs/scheduler.md
https://vue.primeuipro.dev/raw/docs/scheduler/getting-started/architecture.md
https://vue.primeuipro.dev/raw/docs/scheduler/getting-started/setup.md
https://vue.primeuipro.dev/raw/docs/scheduler/views/week.md
https://vue.primeuipro.dev/raw/docs/scheduler/features/scheduling/add-edit-events.md
https://vue.primeuipro.dev/raw/docs/scheduler/reference/api.md

Use focused pages for implementation work. Setup covers installation, style imports, and the CLI for copying PrimeOne or Tailwind Scheduler UI parts. Architecture covers the compound structure, Scheduler data model, view selection, grouping, overlays, and customization boundaries.

#Context Packs

Use a small pack instead of the full docs when the task is narrow.

#Demo Source

Scheduler demo source is included through the generated documentation data. When an assistant needs the code behind a rendered example, reference the page that owns the demo instead of asking it to infer behavior from screenshots.

https://vue.primeuipro.dev/raw/docs/scheduler/features/availability/appointment-slots.md
https://vue.primeuipro.dev/raw/docs/scheduler/grouping/resources.md
https://vue.primeuipro.dev/raw/docs/scheduler/features/customization/toolbar.md

The raw markdown keeps demo names in place, and /llms-full.txt expands Scheduler demo content during the documentation build.

Demo source can include helper-component tabs and shared data excerpts. Treat those as example app code, not required Scheduler runtime code. The reusable contract is the Scheduler compound structure, props, emitted events, context hooks, and style or data-attribute APIs documented on the page.

#Guardrails

Give the assistant explicit constraints when it writes Scheduler code.

Use @primeui/vue-scheduler as the source of Scheduler runtime parts.
Use the compound Scheduler API shown in the docs.
Keep Usage snippets headless unless the task is specifically about installed UI parts.
Use only documented Scheduler parts, props, emitted events, context hooks, and UI-part imports.
Use metadata for app-only event data.
Keep Scheduler responsible for placement, drag, resize, selection, focus, keyboard behavior, overlays, and scrolling.

If the assistant needs UI parts, point it to Setup first. Setup explains PrimeOne and Tailwind CLI installs, style imports, and when to write manual parts.

#Prompting Pattern

Give the assistant the Vue Scheduler scope, the page links, and the expected output.

Use the Vue Scheduler docs below as the source of truth.
Focus on the compound Scheduler API and installed UI parts only when the task asks for them.
Use only the APIs shown on the linked Scheduler pages.

Context:
- https://vue.primeuipro.dev/raw/docs/scheduler/getting-started/architecture.md
- https://vue.primeuipro.dev/raw/docs/scheduler/getting-started/setup.md
- https://vue.primeuipro.dev/raw/docs/scheduler/features/scheduling/add-edit-events.md

Task:
Write a Vue Scheduler event editor that opens from date selection and event click.

For customization tasks, add the relevant how-to guide and ask for the smallest working override first.

Use the Vue Scheduler customization docs below.
Start with a minimal override, then show the production version.
Keep Scheduler-owned behavior intact.

Context:
- https://vue.primeuipro.dev/raw/docs/scheduler/features/customization/event-ui.md
- https://vue.primeuipro.dev/raw/docs/scheduler/reference/slots-contexts.md
- https://vue.primeuipro.dev/raw/docs/scheduler/reference/data-attributes.md

Task:
Create a custom month event card that shows title, time, owner metadata, selected state, and drag/resize state.

#Output Checklist

Ask the assistant to return:

• imports from @primeui/vue-scheduler;
• the Scheduler.Root structure with only the required props;
• the child parts or scoped outlets it uses;
• event, resource, or category types when data is shown;
• style imports or UI-part imports when setup is part of the task;
• a note about which Scheduler behavior remains runtime-owned.

#Related Docs

• Architecture
• Setup
• Slots and Contexts
• Data Attributes
• API