What problem does it solve? Building a Scheduler component in a Thinkwise Software Factory model requires coordinating many interdependent entities — the subject's data model, scheduler rows, scheduler views, resource columns, conditional layouts, screens, tasks, and process flows — and mistakes in any of them cause silent failures like drag-and-drop 400 errors or empty components. This Skill provides a verified, field-by-field reference so every entity is configured correctly the first time. ## Core Features & Use Cases - Full lifecycle reference: Covers the subject data model (single non-nullable primary key, UNION-based resource/activity rows), the scheduler and scheduler_view entities, resource panel columns, and time-cell conditional layouts with exact field names and enum values. - Verified real-world patterns: Includes the prefixed-synthetic-key technique for multi-table resource hierarchies, HTML activity formatting with a dispatcher domain, and the union-per-period pattern for coloring absence, downtime, or work-time windows. - API write quirks: Documents verified routing behaviors, such as adding a scheduler row as a detail of its owning table and editing pre-existing scheduler_view_resource_col overview rows instead of adding new ones. - Use Case: When asked to add a week view with business hours and drag-and-drop to a project planning scheduler, Claude uses this Skill to create the scheduler_view row with correct timescales, hidden days, and update handlers without guessing entity or property names. ## Quick Start Ask Claude to create a Scheduler component for a table in your Thinkwise Software Factory model, including resource grouping, views, and drag-and-drop behavior.
