视觉画布设计
canvas-design
基于设计原则创作静态视觉作品,用于海报与品牌图形。
flexport-core-workflow-b【文档与办公】Create and reconcile Flexport purchase orders, commercial invoices, and shipment documents without inventing update semantics. Use when moving approved trade data into Flexport or attaching documents. Trigger with: "create Flexport purchase order", "upload Flexport document", "submit commercial invoice".
独立 GitHub 快照 · 自动分类 · 以原作者文档为准
name: flexport-core-workflow-b description: >- Create and reconcile Flexport purchase orders, commercial invoices, and shipment documents without inventing update semantics. Use when moving approved trade data into Flexport or attaching documents. Trigger with: "create Flexport purchase order", "upload Flexport document", "submit commercial invoice". allowed-tools: Read, Grep, Write, Edit version: 2.0.0 argument-hint: '[document-type-and-approved-record]' model: inherit effort: high license: MIT author: Jeremy Longshore jeremy@intentsolutions.io tags:
Treat structured trade records and uploaded files as separate governed operations. Validate referenced network entities first, apply only documented create/update behavior, and never assume an uploaded document can be updated in place.
Choose purchase order, commercial invoice, or document from the business outcome; do not overload one endpoint with another resource's fields.
Verify network entity, location, shipment, and product identifiers with read-only lookups before mutation.
Confirm the OAuth credential includes the required endpoint resource. Commercial invoice create/update also requires Flexport-side enablement and permission.
Persist an operation digest, then use the documented endpoint: /purchase_orders, /commercial_invoices, or /documents. Base64 document content must remain within the documented 10 MB pre-encoding limit.
Store opaque returned IDs and retrieve the resource. For documents, replace through an approved new upload rather than inventing an update call.
Link the Flexport resource to the approved source revision, actor, version header, and redacted outcome.
REST calls authenticate with a cached OAuth 2.0 client-credentials Bearer token using audience https://api.flexport.com, or an explicitly accepted broad API key. Use distinct credentials per workload and never log credentials or tokens. MCP calls use the authenticated connection to https://mcp.flexport.com/mcp and remain subject to each tool's documented account permissions.
Use Read and Grep for discovery and evidence. Use Write or Edit only for the approved artifact, code, configuration, test, or receipt described by this workflow; do not make an unapproved Flexport-side change.
Return a machine-reviewable receipt in this shape; adapt the operation values, but never place credentials or provider payloads in it:
surface: rest-v3
operation: shipment-read
decision: approved
outcome: verified
evidence:
release_sha: recorded-out-of-band
provider_reference: redacted
rollback_owner: logistics-platform
A validated commercial invoice is enabled for the client, submitted once, read back by its opaque ID, and linked to the source revision. A corrected file becomes a separately approved document rather than an undocumented in-place edit.
| Failure | Response |
|---|---|
| 422 response | Correct the source payload; do not retry unchanged validation failures. |
| Commercial invoice disabled | Stop and request Flexport enablement/permission. |
| Document too large | Reject before base64 encoding and route to an approved alternative. |
| Ambiguous create | Retrieve or reconcile by known business references before resubmission. |