fulcrum-ai-toolkit

Design least-privilege Fulcrum access. Use for system and custom roles, role-versus-resource permissions, memberships, groups, App MCP role/member inspection, SSO, SCIM, provisioning, and current plan checks.

Guided, novice-friendly workflow for creating or updating a Fulcrum app. Use when a user wants to build an app, add or change fields, or asks whether a Fulcrum app can support a workflow. Explain capabilities and limits, ask focused discovery questions, propose a plain-English schema for approval, then use Fulcrum App MCP as the default control plane when it is available. If App MCP is unavailable, produce a ready-to-implement schema and handoff instead.

Use when building or modifying a Fulcrum app — guides app structure, field type selection, linked apps vs single app, repeatables, and choice list design. Also use when reviewing an existing app for structural improvements.

Use when building, modifying, or reviewing Fulcrum App Extensions. Defers pattern knowledge and artifact generation to App MCP, then covers the generated bridge contract, Reference File workflow, offline decisions, data exchange, and picker anti-pattern.

Use when creating a new Fulcrum app or reviewing an existing one — ensures every app has a clear goal, a defined deliverable, and a known audience before building begins. Flag when a goal is missing or unclear.

Use when writing, reviewing, persisting, or debugging Fulcrum Data Event JavaScript. Defers current hooks and signatures to App MCP knowledge, stores the single script through form get/update operations, and covers patterns, constraints, lifecycle, offline behavior, and security.

Assess and design supported Fulcrum data migrations. Use for inventory, identity and key mapping, history/timestamp/media/URL risk, dry runs, reconciliation, cutover, rollback, and public API boundaries.

Process discovery interview for Fulcrum app building. Use before building to understand the field workflow, deliverable, and constraints. User-invoked — run manually when starting a new project.

Select Fulcrum GIS and mapping capabilities. Use for layers, basemaps, ArcGIS, online/offline maps, geometry capture, spatial import/export, and current web/mobile support checks.

Select and design Fulcrum Workflows and integrations. Use for webhooks, global webhooks, URL Actions, REST integrations, middleware, authentication, retries, timeouts, payload safety, and delivery boundaries.

Route cross-cutting Fulcrum platform questions to the owning portable skill or current public source. Use for capability boundaries, plan checks, public AI capabilities, offline constraints, and App MCP scope.

Model safe read-only Fulcrum Query API work. Use for system, app, repeatable, link, and media tables; metadata discovery; parameterization; documented PostgreSQL/PostGIS analysis; and Query execution boundaries.

Use when building, modifying, generating, or debugging Fulcrum reports and Report Templates. Covers the documented Report Builder runtime, App MCP template CRUD and report generation, EJS patterns, context objects, QUERY() for multi-record reports, and common mistakes.

Use when building or reviewing a Fulcrum app for field work — flags missing safety steps, ensures safety documentation is included in workflows that involve physical hazards, and recommends safety-related fields when appropriate.

Guide a Fulcrum builder through documenting a completed app, extension, workflow, report, or integration. Produce a reusable one-pager, review it for privacy and audience suitability, and prepare optional share formats for a destination chosen by the user. Use when someone wants to explain, review, hand off, or share what they built.

Use when a Fulcrum app has grown too complex — too many fields, too many data events, too many status paths. Guides breaking monolithic apps into composable, maintainable pieces. Also use when reviewing an app that shows signs of monolith creep.