rkortThinkwise
- 25 skills
- 0 followers
- 4 hours ago last updated
- ▌ MCP Refresh Scopes · rkortthinkwiseReload OAuth scopes for an HTTP MCP connector (e.g. sf_mcp) by querying its /mcp endpoint's OAuth protected-resource metadata and syncing the local "scopes" config to match what the server currently advertises. Use when a connector's available scopes may have changed, when tools are unexpectedly missing/denied, or when the user asks to "refresh"/"reload"/"resync" MCP scopes.
- ▌ Thinkwise Install MCP · rkortthinkwiseAdd and authenticate a custom HTTP MCP connector in Claude Code end-to-end, including OAuth discovery and scope pinning, asking the user step by step rather than assuming any config value. Use when asked to add/install/set up/register a new MCP connector or server in Claude Code, especially an Indicium/sf_mcp-style OAuth-protected HTTP MCP endpoint.
- ▌ Thinkwise Software Factory Menu · rkortthinkwise bundleReference guide for creating and maintaining application menus, groups, and items — including per-role visibility — in a Thinkwise Software Factory model. Use via an MCP connector with Software Factory access whenever creating, inspecting, or securing a menu, and before deciding whether a new screen/report/task belongs on an existing menu/group or needs a new one.
- ▌ Thinkwise Software Factory Cubes · rkortthinkwise bundleReference guide for creating and maintaining cubes (analytical pivot/chart views) in a Thinkwise Software Factory model — the cube/cube_field/cube_field_query/cube_view/cube_view_field/cube_view_field_filter/cube_view_field_total/cube_view_field_conditional_layout/cube_view_grp family, dimensions vs. values, aggregation types, intervals and hierarchies, calculated fields, pivot and chart settings, editable values, and per-role/per-variant cube rights. Use before calling get_entity_definition/get_task_definition/execute_odata_query/stage_resource/stage_task against any of these entities, and before deciding whether a request needs a cube at all versus a Grid, report, or dedicated BI tool.
- ▌ Thinkwise Software Factory Icons · rkortthinkwise bundleReference guide for the icon repository (icon/icon_grp/icon_tag) and every verified place an icon can be assigned in a Thinkwise Software Factory model — tables, tasks, reports, prefilters, menus, cube views, domain elements, message options, form/report navigation, conditional layouts — plus the semantic vocabulary for choosing the right icon per object/action/state. Use whenever an MCP connector with Software Factory access creates, inspects, reuses, replaces, or assigns an icon, or before calling get_entity_definition/execute_odata_query/stage_resource/stage_task against icon, icon_grp, icon_tag, or any `*icon_id`/`image_id` field.
- ▌ Thinkwise Software Factory Tasks · rkortthinkwiseReference guide for creating and configuring tasks in a Thinkwise Software Factory model — task types, parameters, look-ups, form setup, variants, and table task assignment. Use whenever an MCP connector with Software Factory access creates, inspects, or troubleshoots a task, before working with the task, task_parmtr, task_ref, task_variant, or tab_task family of entities.
- ▌ Thinkwise Datamodeling Guidelines · rkortthinkwise bundleReference guidelines for designing and naming domains, tables, and columns in a Thinkwise Software Factory data model — naming conventions, entity classification, column order, data types, references, and menu placement. Use whenever designing or reviewing a data model, or making sf_mcp calls that create or inspect domains, entities, columns, or references, to check names, types, and structure against these conventions before proposing or executing changes.
- ▌ Thinkwise Software Factory MCP Base · rkortthinkwiseBase check to run before doing real work through any MCP connector that provides Thinkwise Software Factory access (e.g. sf_mcp, meta_dev, indicium). Confirms which connector, which application model, and which branch (model_id/branch_id) apply, since one Software Factory repository commonly hosts several application models with multiple branches each and most entities are keyed by model_id/branch_id. Use once near the start of a task that will call get_domain_definition/search_capabilities/get_entity_definition/execute_odata_query/stage_resource/stage_task/patch_resource/commit_resource — not before every individual tool call.
- ▌ Thinkwise Software Factory Messages · rkortthinkwise bundleReference guide for creating and maintaining modeled user-facing messages in a Thinkwise Software Factory model — errors, warnings, confirmations, process-flow choices, progress text, and translated database errors. Use whenever an MCP connector with Software Factory access creates, inspects, or troubleshoots a message, or before writing a message-calling SQL statement or a database-error-capture regex.
- ▌ Thinkwise Software Factory Variants · rkortthinkwiseReference guide for creating, configuring, and maintaining table, task, and report variants in a Thinkwise Software Factory model — the field-level-vs-snapshot inheritance mechanism and the Changes-compared-to-default/where-used mechanics. Use whenever creating, inspecting, or troubleshooting a variant via an MCP connector with Software Factory access, and before deciding whether a request needs a new variant at all versus a prefilter, a new screen type, or a separate table/task/report.
- ▌ Thinkwise Software Factory Deployment · rkortthinkwiseReference guide for starting, monitoring, and controlling a Thinkwise Software Factory definition-generation job — generating the application definition alone, or the full generate/validate/build/deploy pipeline ("complete creation") — via the sf/software_development domain. Use whenever an MCP connector with Software Factory access starts, checks, cancels, or resolves a paused step of a generation/validation/deployment job, or before calling get_task_definition/stage_task/execute_odata_query against add_job_to_generate_definition, definition_generation_overview, definition_generation_step, or definition_validation_overview.
- ▌ Thinkwise Software Factory Prefilters · rkortthinkwise bundleReference guide for creating and configuring prefilters and prefilter groups (tab_prefilter, tab_prefilter_grp, tab_variant_prefilter_overview) in a Thinkwise Software Factory data model — column-based vs. query-based prefilters, and prefilter groups. Use whenever an MCP connector with Software Factory access creates, inspects, or troubleshoots a prefilter or prefilter group, including before calling get_entity_definition/execute_odata_query/stage_resource against these entities.
- ▌
- ▌ Thinkwise Software Factory Create View · rkortthinkwise bundleReference guide for creating views in a Thinkwise Software Factory data model — naming, entity/column setup, domain reuse, modeling references to the view's source tables, and writing/assigning the SELECT code that backs a view. Use whenever creating, reviewing, or troubleshooting a view via an MCP connector with Software Factory access (e.g. sf_mcp, indicium), especially when converting a user's ad hoc SQL query into a view. Does not cover deployment.
- ▌ Thinkwise Software Factory Subroutines · rkortthinkwise bundleReference guide for creating, configuring, calling, and maintaining subroutines (reusable SQL functions/procedures) in a Thinkwise Software Factory model, including role rights and how to call a subroutine from control procedures, views, tasks, and process flows. Use whenever an MCP connector with Software Factory access creates, inspects, or troubleshoots a subroutine or its body SQL.
- ▌ Thinkwise Software Factory Build Planner · rkortthinkwise bundleInterview the user about a goal or problem in a Thinkwise Software Factory application, then produce a reasoned build plan across data model, screens, tasks, process flows, control procedures, subroutines, and messages. Use when the user brings a raw goal or feature idea without an already-formed technical plan — not for stress-testing an existing plan, or a small, self-evident ask. Hands off each artifact to the skill that implements it; this skill only plans.
- ▌ Thinkwise Software Factory Process Flows · rkortthinkwise bundleReference guide for creating and configuring process flows (and system flows) in a Thinkwise Software Factory model — process_flow/process_action/process_step/process_variable/process_flow_schedule entities, every process action type, which types can be a starting point, control-procedure-backed logic, loops, alignment, and naming conventions. Use whenever an MCP connector with Software Factory access (e.g. sf_mcp, indicium) creates, inspects, or troubleshoots a process flow — before calling get_entity_definition/execute_odata_query/stage_resource/stage_task against process_flow, process_action, process_step, process_variable, process_flow_schedule, or process_action_start_object_available.
- ▌ Thinkwise Software Factory Maps Component · rkortthinkwise bundleReference guide for setting up and maintaining a maps component in a Thinkwise Software Factory model — the map/map_base_layer/map_overlay/map_data_mapping entities, the CoordSets JSON coordinate contract, and per-domain-element styling. Use before calling get_entity_definition/execute_task/execute_odata_query against map/map_base_layer/map_overlay/map_data_mapping/tab_variant_map*, or before writing a control procedure that builds or parses CoordSets JSON, via an MCP connector with Software Factory access (e.g. sf_mcp, indicium).
- ▌ Thinkwise Software Factory Web Connections · rkortthinkwise bundleReference guide for creating and using Web Connections and OAuth servers in a Thinkwise Software Factory model, the preferred mechanism for calling external HTTP/REST APIs. Covers authentication, endpoint and parameter setup, response parsing, and wiring a connection into a process flow. Use whenever an MCP connector with Software Factory access creates, inspects, or troubleshoots a web connection or OAuth server, in place of a one-off http_connector process action.
- ▌ Thinkwise Software Factory Subject Components · rkortthinkwise bundleReference guide for the screen components that present a Thinkwise Software Factory subject (table or view) — Grid, Form, Card List, Treeview, and Drag-and-drop — covering the tab/col-level settings (tree_*/card_list_*/form_*/grid_* fields), their tab_variant_*_overview per-variant counterparts, and the drag_drop/drag_drop_parmtr/drag_drop_matrix family. Use whenever an MCP connector with Software Factory access (sf_mcp, indicium) is setting up or troubleshooting a subject's Grid/Form/Card List/Tree/Drag-drop behavior — before calling get_entity_definition/execute_odata_query/stage_resource against tab, col, tab_variant_grid/form/tree/card_list(_overview), or drag_drop*.
- ▌ Thinkwise Software Factory Conditional Layouts · rkortthinkwise bundleReference guide for conditional layouts (conditional formatting) in a Thinkwise Software Factory model — data-driven styling such as status colours on tables, tasks, and cube views, including row/column targeting, light/dark themes, and accessibility. Use before inspecting or modifying any conditional-layout entity via an MCP connector with Software Factory access, or whenever asked to add or change status colours, warning highlights, or any "make this red/bold/green" styling.
- ▌ Thinkwise Software Factory Scheduler Component · rkortthinkwise bundleReference guide for creating and maintaining a Scheduler component in a Thinkwise Software Factory model — the scheduler, scheduler_view, scheduler_view_resource_col, and scheduler_view_conditional_layout(_condition/_tag) entities. Use before calling get_entity_definition/execute_task/execute_odata_query against scheduler-related entities (including tab_task/task/process_flow/process_action for a scheduler-bearing table), and before writing or reviewing the control procedure template behind a scheduler view or its update handler.
- ▌ Thinkwise Software Factory Translation Objects · rkortthinkwise bundleReference guide for translating model objects in a Thinkwise Software Factory model — the transl_object/transl_object_transl entities, appl_lang/branch_appl_lang, the approval_status review workflow, naming/plural/help-text conventions, and linking a base model to back-fill an officially supported language instead of hand-translating it. Use whenever an MCP connector with Software Factory access (e.g. sf_mcp, sf_dev_wiz_mcp, insights) reads, writes, generates, or reviews translations, or adds a new application language — before calling get_entity_definition/get_task_definition/execute_odata_query/stage_task against transl_object, transl_object_transl, appl_lang, branch_appl_lang, linked_model, or linked_model_available.
- ▌ Thinkwise Software Factory Postgresql Migration · rkortthinkwise bundleStep-by-step guide and checklist for adding PostgreSQL as a supported platform on an existing Thinkwise Software Factory application (dual-platform, alongside SQL Server/other platforms already enabled) — enabling the platform, porting every category of hand-written SQL (control procedures, calculated fields, prefilters, domain/column default queries), resolving PostgreSQL-specific validation errors, and the dialect/structural rewrites and tooling quirks discovered doing this live. Use whenever a user asks to add PostgreSQL support to an existing model, migrate/port an application to PostgreSQL, or troubleshoots a PostgreSQL-specific generation/validation error (naming collisions, MERGE/FK errors during generation, etc.) in a Thinkwise model.
- ▌ Thinkwise Software Factory Create Control Procedures · rkortthinkwise bundleReference guide for creating and assigning control procedures in a Thinkwise Software Factory model (code groups, business-logic variables, static/SQL assignment, dynamic model code, multi-RDBMS dialects, SQL coding guidelines). Use whenever creating, assigning, reviewing, or troubleshooting control procedures via an MCP connector with Software Factory access (e.g. sf_mcp, indicium) — before calling get_entity_definition/execute_task/execute_odata_query against control_proc, control_proc_template, code_grp, or prog_object*, and before writing or reviewing any control procedure template SQL.