laneweaver-tms-agents

Context-isolated agent for Svelte frontend work. Isolates the reactive programming mental model from Go imperative patterns. <example> Context: User wants to build a new Svelte component user: "create component for displaying load details" assistant: "I'll use the frontend-component-agent to create a Svelte 5 component for displaying load details." <commentary> User explicitly asked to create a component. This agent will build it using Svelte 5 runes and shadcn-svelte patterns. </commentary> </example> <example> Context: User is working on Svelte frontend user: "help me with the svelte page for carriers" assistant: "Let me use the frontend-component-agent to help with the Svelte carrier page." <commentary> User mentioned svelte explicitly. The agent will provide guidance using Svelte 5 patterns. </commentary> </example> <example> Context: User needs help with Svelte 5 reactivity user: "how do I use runes to manage the form state?" assistant: "I'll use the frontend-component-agent to help you implement form state with Svelte 5 runes." <commentary> User mentioned runes - Svelte 5's reactivity primitives. The agent will guide proper $state and $derived usage. </commentary> </example> <example> Context: User wants to add a frontend page user: "add a frontend page for shipment tracking" assistant: "Let me use the frontend-component-agent to create the shipment tracking page." <commentary> User asked for a frontend page. The agent will create a SvelteKit route with proper patterns. </commentary> </example> <example> Context: User is using Svelte 5 state runes user: "I need to use $state for the driver list" assistant: "I'll use the frontend-component-agent to help implement $state for your driver list." <commentary> User mentioned $state explicitly. The agent will ensure correct reactive state implementation. </commentary> </example> <example> Context: User needs computed values user: "how do I use $derived to filter these loads?" assistant: "Let me use the frontend-component-agent to help you implement $derived for filtering loads." <commentary> User mentioned $derived. The agent will guide proper derived state implementation. </commentary> </example>

You are a PostgreSQL 17 database schema expert for laneweaverTMS. Your role is to design, analyze, and generate database migrations following strict conventions.

Implement geofences, spatial queries, real-time tracking, and mapping features in laneweaverTMS using PostGIS and PGRouting. Use when building location-based features, distance calculations, ETA predictions, or fleet visualization.

Provide patterns for implementing Role-Based Access Control and multi-tenant authorization in laneweaverTMS. Use when implementing user roles, permissions, tenant isolation, Echo authorization middleware, RLS policies for multi-tenant access, or JWT claims structure for freight brokerage applications.

Unified patterns for external API integrations including OAuth2 token lifecycle, exponential backoff, webhooks vs polling, rate limiting, error handling, multi-tenant isolation, and webhook security. Use when integrating with QuickBooks, MyCarrierPackets, Slack, or any external OAuth2-based API in laneweaverTMS.

Step-by-step guide for implementing new features in laneweaverTMS, orchestrating use of specialized skills and agents for database, backend, and frontend work.

Freight brokerage industry terminology and domain concepts. Use when working with laneweaverTMS to understand loads, tenders, carriers, accounts, facilities, stops, financial terms, status workflows, equipment types, and common abbreviations.

Document the critical business logic for load lifecycle and billing workflows in laneweaverTMS. Use when implementing load status transitions, billing workflows, financial calculations, TONU handling, or quick pay features.