trade-execution
Guide the design, evaluation, and monitoring of trade execution quality and best execution practices. Use when assessing best execution obligations under FINRA Rule 5310 or RIA fiduciary duty, designing smart order routing across exchanges and dark pools, selecting execution algorithms (VWAP, TWAP, implementation shortfall, POV), building transaction cost analysis (TCA) for pre-trade estimation or post-trade measurement, analyzing bid-ask spread decomposition or market impact or information leakage, conducting best execution committee reviews, evaluating payment for order flow (PFOF) arrangements, interpreting Rule 605/606 reports, or handling fixed income or ETF execution via RFQ protocols. Also covers Reg NMS Order Protection Rule and venue fee structures.
What this skill does
# Trade Execution ## Purpose Guide the design, evaluation, and monitoring of trade execution quality in securities trading. Covers best execution obligations, venue selection and market structure, smart order routing, execution algorithms, transaction cost analysis, and market microstructure concepts. Enables building or evaluating execution infrastructure that achieves optimal outcomes for clients while satisfying regulatory obligations. ## Layer 11 — Trading Operations (Order Lifecycle & Execution) ## Direction both ## When to Use - Evaluating whether a firm's execution practices satisfy best execution obligations under SEC, FINRA, or fiduciary standards - Designing or configuring smart order routing logic across multiple execution venues - Selecting and parameterizing execution algorithms (VWAP, TWAP, implementation shortfall, POV) for specific order characteristics - Building or reviewing a transaction cost analysis framework for pre-trade estimation or post-trade measurement - Analyzing market microstructure factors such as bid-ask spread decomposition, market impact, or information leakage - Conducting periodic best execution committee reviews with quantitative evidence - Evaluating venue selection decisions including exchange routing, dark pool usage, and wholesaler arrangements - Interpreting Rule 605 and Rule 606 reports to assess execution quality and order routing practices - Designing execution quality dashboards and monitoring systems - Handling fixed income or ETF execution through RFQ protocols, dealer networks, or creation/redemption mechanisms ## Core Concepts ### Best Execution Obligation Best execution is the duty to seek the most favorable terms reasonably available for client transactions under the circumstances. The obligation applies differently depending on the entity type and regulatory framework. **Broker-dealer obligations (FINRA Rule 5310):** FINRA Rule 5310 (Best Execution and Interpositioning) requires broker-dealers to use reasonable diligence to ascertain the best market for a security and to buy or sell in that market so that the resultant price to the customer is as favorable as possible under prevailing market conditions. "Reasonable diligence" involves consideration of: - The character of the market for the security (e.g., price, volatility, and relative liquidity) - The size and type of transaction - The number of markets checked - The accessibility of the quotation - The terms and conditions of the order as communicated to the broker-dealer FINRA distinguishes between a "regular and rigorous" review of execution quality (conducted on a systematic basis, typically quarterly) and order-by-order best execution. The regular and rigorous review evaluates whether the firm's order routing arrangements deliver consistently favorable results. If the review reveals deficiencies, the firm must take corrective action — which may include changing routing destinations, modifying order handling procedures, or renegotiating execution quality commitments with venues. **RIA fiduciary obligation:** For registered investment advisers, best execution flows from the fiduciary duty of care established under Section 206 of the Investment Advisers Act. The SEC's 2019 fiduciary interpretation (Release IA-5248) explicitly identifies the duty to seek best execution when the adviser has the authority to select broker-dealers for client transactions. Unlike the broker-dealer standard, which focuses on individual orders, the RIA best execution obligation is evaluated in the context of the overall advisory relationship and considers qualitative factors such as the value of research, custodial services, and operational support provided by the executing broker — commonly referred to as "soft dollar" considerations under Section 28(e) of the Securities Exchange Act. **Factors in best execution analysis:** Best execution is not simply achieving the lowest possible price on every transaction. The SEC and FINRA have consistently held that best execution considers the totality of circumstances: - **Price:** The execution price relative to the national best bid and offer (NBBO) at the time of order entry - **Speed:** Time from order submission to execution, particularly important for market orders and time-sensitive strategies - **Likelihood of execution:** The probability that the order will be filled, especially for limit orders or orders in less liquid securities - **Settlement:** The certainty and timeliness of trade settlement - **Market impact:** The degree to which the order itself moves the market price, particularly relevant for large orders - **Total cost:** The all-in cost including explicit costs (commissions, exchange fees, regulatory fees) and implicit costs (spread, market impact, opportunity cost) **Best execution committees:** Firms typically establish a best execution committee (or equivalent governance body) that meets quarterly to review execution quality data, evaluate routing arrangements, assess venue performance, and document findings. The committee should include representatives from trading, compliance, and senior management. Committee minutes should record the data reviewed, the analysis performed, the conclusions reached, and any corrective actions ordered. Regulatory examiners routinely request best execution committee documentation. **Periodic review requirements:** Both FINRA and the SEC expect firms to conduct regular, documented reviews of execution quality — not merely react when problems are identified. FINRA's guidance on Rule 5310 specifies that the "regular and rigorous" review should examine execution quality for different order types and sizes, compare execution quality across available venues, evaluate whether routing arrangements are delivering competitive results, and assess whether changes in market structure warrant changes in routing practices. For RIAs, the SEC has indicated that the frequency of best execution reviews should correspond to the scope and nature of the advisory relationship. An RIA that exercises trading discretion should review execution quality at least annually (quarterly is best practice). The review should be documented in writing and presented to senior management or a governance committee. The documentation serves as evidence that the firm is fulfilling its ongoing best execution obligation and is the primary artifact that SEC and FINRA examiners request during examinations. ### Market Structure and Venues U.S. equity markets operate under a decentralized, multi-venue structure governed by Regulation NMS. Understanding venue types and their characteristics is essential for effective execution. **Exchanges:** National securities exchanges are registered with the SEC under Section 6 of the Securities Exchange Act. Major equity exchanges include the New York Stock Exchange (NYSE), Nasdaq, CBOE (Cboe BZX, BYX, EDGX, EDGA), and IEX. Each exchange operates a displayed limit order book with price-time priority. Exchanges differ in fee structures (maker-taker versus taker-maker), order type offerings, speed characteristics, and market data products. The listing exchange for a security often receives a disproportionate share of order flow in that security. **Electronic Communication Networks (ECNs):** ECNs are automated systems that match buy and sell orders electronically. Under Regulation ATS (Alternative Trading System), ECNs register as broker-dealers and file Form ATS with the SEC. ECNs display their best-priced orders in the consolidated quotation system. Historically, ECNs were distinct from exchanges, but many former ECNs have converted to exchange status (e.g., BATS became Cboe BZX). **Alternative Trading Systems / Dark Pools:** Dark pools are ATSs that do not publicly display quotations. They match orders internally without pre-trade transparency, which can reduce information leakage and market impact for large orders. Dark pools include broker-dealer-operated cr
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.