Results for “shipping”

Generate a packing slip PDF with order details, item list, and shipping address.

Review local code changes for concrete correctness, regression, security, and test gaps before shipping.

Final quality pass before shipping. Fixes alignment, spacing, consistency, and detail issues that separate good from great.

Final quality pass before shipping. Fixes alignment, spacing, consistency, and detail issues that separate good from great.

Agent profile for final UI/UX QA before shipping visible design, web design, app screens, or 3D web UI.

Scans modified files for debug leftovers before shipping. Catches console.log, debugger, test URLs, and commented-out code.

Use this skill before merging, deploying, or shipping changes. It reviews code for bugs, security, auth, data loss, migrations, observability, performance, and rollback risks.

Provides a structured pre-launch checklist, staged rollout plan, monitoring setup, and rollback strategy for safe production deployments.

Uses two independent review agents to verify output quality, requiring both to pass before shipping.

Use when building or debugging interactive 3D scenes on the web with Three.js (scene/camera/renderer, lights/materials, GLTF loading, controls, performance). Helpful for designers shipping 3D UI moments.

Generates 3-5 editable SVG logo concepts with design rationale and usage notes, ready for refinement and shipping.

Audits local code for production readiness, identifying risks in security, data integrity, payments, operations, and UX before shipping.

Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.

Audits a page or component against the Digital Curator design spec and movemental conventions, checking visual quality, accessibility, token compliance, and consistency before shipping.

Ship already-finished work, optionally deploy it, and prepare the next step

Prepare safe production launches — pre-launch checklist, monitoring, staged rollout, and rollback. Load when deploying to production, releasing a major change, opening beta access, or the user asks for a launch checklist, go-live plan, rollout strategy, or rollback plan. Not for local-only prototypes. Pairs with ci-cd-and-automation and app-security-hardening.

Use this skill when the user asks about refrigerated (reefer) trucking — cold chain compliance, FDA temperature recording requirements, Sanitary Transportation Rule (STR / 21 CFR 1.900-1.934), commodity-specific temperature ranges, refrigeration unit operation, temperature recorder calibration, and how a load is challenged if temperature deviates. Cite 21 CFR Part 1 Subpart Q.

Orchestrates a strict four-stage shipping pipeline: session critique, validation, commit, and pull request, halting on failure. Supports a critique-only mode for mid-session quality checks.

Anti-pattern detector and design rules for AI coding agents. Catches the specific mistakes AI makes when generating UI: gray text on color, nested cards, broken buttons, missing states. Use before shipping any frontend.

Prepares production launches. Use when preparing to deploy to production. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.

Extracts structured product data from Amazon search results, including prices, ratings, sales estimates, and shipping info, using the BrowserAct API.

Use when a carrier (asset-based, brokerage, or 3PL) asks how to respond to a shipper RFP / RFQ — bid packaging, lane analysis, rate strategy, SOPs/SOWs, qualifications response, insurance compliance, EDI requirements, and how to win competitive bids without leaving margin on the table.

spec-ship

Deploy the app, create landing page, set up analytics, and log the shipment

Augment the standard ship lifecycle with monorepo package-scoped and transitive-dependent validation

Stages all changes, creates a commit with a provided or prompted message, and pushes to the current branch.

Publish to npm, create README, set up repo, and log the shipment

Send and receive transactional emails using Cloudflare Email Service, including Workers binding, REST API, Agents SDK integration, and email routing with deliverability setup.

Commit, push, and open a pull request with a conventional commit message

Takes an approved plan from docs/plans/ and drives it to an open PR. Implements it by milestones, commits per milestone in the repo's style, and opens the PR against the repo's base branch. Use whenever the user approves a plan, says "ship it", "go", "start", "implement it", "do it", or asks to open a PR for already-planned work — or in Spanish "dale", "arrancá", "implementalo", "hacelo".