mainsequence-sdk

Use this skill when the task is about operational execution in a Main Sequence project. This skill owns jobs, schedules, batch scheduling files, project images, run inspection, project resources, releases, Streamlit dashboard deployment, and Artifacts as operational inputs. It does not own DataNode producer design, MetaTable schema design, API route contracts, Streamlit dashboard design, or RBAC policy.

Reviews a Main Sequence project for status, blockers, failures, and completion.

Use this skill to bootstrap work in a Main Sequence repository. This skill owns project context verification, docs-first behavior, success-definition discipline, routing between specialized domain skills, and project-state file discipline. It does not own domain implementation semantics.

Use this skill when the task is about selecting, creating, validating, or documenting Command Center connections before workspace widgets consume data. This skill owns connection type discovery, connection instance readiness, query model/output-contract checks, connection-first workspace dataflow, and routing backend adapter gaps. Use this before creating data-consuming widgets. It does not own workspace layout, widget JSON mutation, AppComponent form contracts, or generic FastAPI implementation.

Use this skill when the task is about translating user intent into a Main Sequence Command Center workspace concept. This skill owns workspace design, widget selection, visualization strategy, information architecture, connection-first dataflow planning, and deciding which widgets best express a business idea. It does not mutate workspace JSON, patch mounted widgets, create connections, create FastAPI endpoints, or create project resources/releases.

Use this skill when the task is to discover what `DataNode` or `MetaTable` data already exists on the Main Sequence platform before implementation starts.

Use this skill when the task is about RBAC, resource sharing, or access verification in a Main Sequence project. This skill owns organization and team access concepts, view and edit semantics, choosing the correct shareable resource boundary, and access checks across projects, DataNodeStorage, constants, secrets, buckets, artifacts, and releases. It does not own job scheduling, DataNode producer logic, or API route design.

Canonical guidance for discovering agents and sending session-scoped A2A requests through Main Sequence.

Use this skill when creating, updating, reviewing, or planning evaluation cases in the SdkAgentTraining repository, including writing case.yaml, prompt.md, expected responses, rubrics, skill case-bank READMEs, and cases derived from SDK skill snapshots or training-source documents.

Use this skill when updating SdkAgentTraining for a new public mainsequence SDK version, deciding whether a new authored case-set version is required, refreshing sdk/<version>/ snapshots, creating cases/vN, and mapping the SDK to the correct case set.

Use this skill when the task is about defining, changing, querying, or reviewing Main Sequence SimpleTables and SimpleTableUpdaters. This skill owns row schemas, backend-managed ids, insert versus overwrite behavior, filtering, foreign keys, and validation rules. It does not own DataNode producers, API route contracts, scheduling, or sharing policy.

Use this skill when the task is about producing, changing, validating, or reviewing Main Sequence DataNode update processes. This skill owns DataNode update configuration, dependencies, update logic, hashing, namespaces, and validation against a PlatformTimeIndexMetaTable storage contract. It does not own generic MetaTable governance, Alembic migration execution, API route contracts, scheduling, sharing policy, or storage registration internals.

Use this skill when the task is about defining, querying, or reviewing Main Sequence MetaTables. This skill owns SQLAlchemy table contracts, backend-managed table authoring, external table registration, governed compiled SQL operations, foreign keys, indexes, naming, cadence, and validation rules. For Alembic migration lifecycle work, use the mainsequence-metatable-migrations skill. It does not own DataNode producers, API route contracts, scheduling, releases, or sharing policy.

Use this skill when the task is about producing, changing, validating, or reviewing Main Sequence DataNodes. This skill owns DataNode contracts, hashing, namespaces, update logic, metadata, asset-indexed nodes, and DataNode validation. It does not own SimpleTable row modeling, API route contracts, scheduling, or sharing policy.

Use this skill when the task is about building or changing APIs in a Main Sequence repository. In a Main Sequence project, project APIs should be implemented as FastAPI project resources. This skill owns FastAPI structure, request and response contracts, request user binding, APIDataNode and SimpleTable consumption inside APIs, and exact widget-facing API response contracts. It does not own producer-side DataNode or SimpleTable design, workspace payloads, or scheduling and release workflows.

Use this skill when the task is about AppComponent widgets in a Main Sequence project. This skill owns AppComponent input contracts, custom forms, form sections and field definitions, and the boundary between AppComponent input contracts and widget-facing output contracts. It does not own workspace layout, generic FastAPI design, or Streamlit dashboards.

Use when building, modifying, refactoring, reviewing, or documenting Command Center connections, connection type definitions, connection config editors, Explore UIs, backend adapter contracts, connection registry sync, or connection usage guidance. Ensures every connection has clear agent-readable guidance, field-level examples, local README documentation, and backend contract impact assessment.

Use after building, modifying, refactoring, reviewing, or documenting Command Center widgets, widget definitions, widget settings, widget IO ports, registry contracts, runtime execution behavior, or USAGE_GUIDANCE.md files. Ensures widget maintenance tasks are completed, especially keeping the backend-synced widget usage guidance accurate. Do not use consantly on every modificaiton as this shoudl be only maintence cycle