What problem does it solve? Adding data-driven styling (status colours, warning highlights, bold/italic emphasis) to a Thinkwise Software Factory model requires knowing which of several distinct conditional-layout entity families to use, their exact field shapes, and platform quirks like read-only flags and missing priority fields — mistakes here produce silently inactive or unpredictable formatting. ## Core Features & Use Cases - Verified entity and field references: Covers table-level conditional_layout, task-level task_conditional_layout, and cube-level cube_view_field_conditional_layout families, including the 18-value condition enum, light/dark theme colour pairs, and per-surface apply flags. - Design guidance for status visualization: Provides colour/severity mapping patterns for statuses, missing data, deadlines, and financial exceptions, plus accessibility rules so meaning is never conveyed by colour alone. - Known gaps and pitfalls documented: Flags unreachable report conditional layouts, the absent order_no priority field, the derived apply_to_edit flag, and the signed-Int32 colour encoding formula for connector-only sessions. - Use Case: When asked to make overdue orders appear red in a grid, the skill guides creating a conditional_layout row targeting the due_date column with a greater-than condition, setting both light and dark background colours, and confirming the design with the user before staging. ## Quick Start Ask the AI to add a conditional layout that colours the status column red for blocked orders in your Thinkwise Software Factory model via the MCP connector.
