aus-integration
Design AUS (Automated Underwriting System) integration workflow specifications for DU, LP, and GUS. Use when integrating a mortgage LOS with Fannie Mae Desktop Underwriter, Freddie Mac Loan Product Advisor, or USDA GUS.
What this skill does
# AUS Integration Workflow Design Design the integration workflow between a mortgage LOS and Automated Underwriting Systems (AUS): Fannie Mae Desktop Underwriter (DU), Freddie Mac Loan Product Advisor (LP), and USDA Guaranteed Underwriting System (GUS). Covers submission setup, findings interpretation, documentation requirements, and resubmission workflows. ## AUS System Overview | AUS | Owner | Programs | Access Method | |-----|-------|---------|--------------| | Desktop Underwriter (DU) | Fannie Mae | Conventional Fannie, FHA, VA (via integration), USDA (via integration) | Fannie Mae Connect API + Selling & Servicing Guide | | Loan Product Advisor (LP) | Freddie Mac | Conventional Freddie, FHA (via integration) | Freddie Mac API + Selling & Servicing Guide | | GUS | USDA Rural Development | USDA Section 502 Guaranteed Rural Housing | GUS portal (direct entry or LOS integration) | --- ## Section 1: Connection Setup **DU connection configuration:** | Configuration Item | Required Value | |--------------------|---------------| | Fannie Mae Seller/Servicer ID | [Client's Seller/Servicer number] | | DU API credentials | Obtained through Fannie Mae Connect; stored securely in LOS credential vault | | Submission format | MISMO 3.4 XML (current standard) | | Response format | DU findings XML + PDF findings report | | Environment | Production (separate from test/sandbox) | | Network access | Fannie Mae whitelists IP addresses — provide production IPs to Fannie Mae | **LP connection configuration:** | Configuration Item | Required Value | |--------------------|---------------| | Freddie Mac Seller/Servicer ID | [Client's Seller/Servicer number] | | LP API credentials | Obtained through Freddie Mac Loan Advisor Suite portal | | Submission format | MISMO XML or ULDD format | | Response format | LP feedback certificate XML + PDF | | Environment | Production | **GUS connection configuration:** | Configuration Item | Description | |--------------------|-------------| | USDA GUS access | GUS web portal or LOS-GUS integration (not all LOS have native GUS API) | | USDA Business Partner ID | Client's USDA lender ID | | If LOS integration not available | Manual GUS submission with copy of findings stored in LOS document management | **Credential management:** - AUS credentials stored in LOS encrypted credential vault (never in plain text config files) - Credentials rotated per AUS provider policy (typically annually) - Separate sandbox/test credentials for pre-production testing - Service account credentials (not tied to individual employee) --- ## Section 2: Submission Workflow **When to submit to AUS:** | Event | Action | |-------|--------| | Borrower has expressed intent to proceed and application is complete | Initial AUS submission | | Any of the following data changes | Resubmission required (see Section 4) | | Final submission before underwriting | Submit current AUS run; findings in file | **Loan setup before AUS submission:** 1. Confirm loan program (Conventional Fannie / Conventional Freddie / FHA / VA / USDA / other) 2. Map program to AUS: Conventional → DU or LP (client's choice or program eligibility); FHA → DU or LP (FHA accepts both); USDA → GUS; VA → DU (VA-approved lender with DU access) 3. Confirm all 1003 data is complete in LOS — AUS submission pulls from 1003 data 4. If both DU and LP are being run: submit to both; use more favorable findings **LOS-to-AUS data mapping:** The LOS MISMO XML export must correctly map 1003 data to AUS fields. Critical mappings to validate: | 1003 Field | AUS Field | Common Mapping Error | |-----------|-----------|---------------------| | Borrower SSN | BorrowerSSN | Dashes stripped correctly | | Property address (all components) | PropertyStreetAddress, City, State, ZIP | ZIP+4 if required | | Loan amount | BaseLoanAmount | Must match LE; not purchase price | | Property value / sales price | PropertyEstimatedValue (lower of appraised or sales) | Using purchase price before appraisal | | Monthly income — all types | MonthlyIncome by income type | Bonus/overtime — 24-month average required | | Monthly obligations | MonthlyLiability — each installment/revolving debt | Missing liabilities from credit report | | Housing expense | HousingExpense (PI + taxes + insurance + HOA) | Escrow estimate must be included | | Loan purpose | LoanPurposetype | Cash-out vs. rate-term distinction | | Occupancy | PropertyUsageType | Investment property inputs differently | --- ## Section 3: Findings Interpretation ### 3a: DU Findings **DU recommendation types:** | DU Recommendation | Meaning | Workflow | |------------------|---------|---------| | Approve/Eligible | Loan meets Fannie Mae guidelines; DU has determined it is eligible for delivery | Proceed to processing using DU findings documentation requirements | | Approve/Ineligible | DU approves the risk but loan is ineligible for delivery to Fannie for some reason (e.g., loan limit exceeded, property type) | Cannot deliver to Fannie; explore other options (Freddie, portfolio) | | Refer | DU cannot approve; manual underwriting may be performed per Fannie guidelines | Manual UW required; more conservative documentation standards | | Refer with Caution | DU has identified elevated risk factors; manual UW very unlikely to approve | Explore alternative programs or restructure | | Out of Scope | Loan type not supported by DU (e.g., construction, reverse, HELOC) | Use appropriate AUS for loan type | **DU Approve/Eligible documentation requirements (Documentation Type matrix):** | Asset/Liability | DU Documentation Level | What to Collect | |----------------|------------------------|----------------| | Salaried income (stable employment 2 years) | Full documentation | 30-day pay stubs + W-2s (2 years) | | W-2 only | W-2 waiver (DU may waive returns for W-2 employees) | Verify DU findings message for waiver | | Self-employed | Full documentation — always | 2 years tax returns (personal + business) + YTD P&L | | Bank accounts | Standard (2 months statements) | Most loans: 2 months most recent statements | | Retirement accounts | If needed for reserves | 2 months or quarterly statement | | Gift funds | Gift letter + donor bank statement | DU findings will specify if gift is acceptable | **Reading DU findings for required verifications:** The DU findings report lists specific verifications required. These override general Selling Guide requirements. Process: 1. Print or save DU findings report to loan file immediately upon receipt 2. Processor creates conditions checklist based on DU-listed verifications (not generic checklist) 3. If DU says "No income documentation required" — document this finding; do not require documentation anyway 4. If DU requires a verification not expected — research Selling Guide for explanation; do not override DU ### 3b: LP Findings **LP feedback certificate types:** | LP Recommendation | Meaning | Workflow | |------------------|---------|---------| | Accept | LP recommends the loan for purchase; reduced documentation applies | Use LP-specified documentation requirements | | Caution | LP is unable to recommend; elevated risk; manual UW may be considered | LP Seller/Servicer Guide manual UW criteria apply | **LP Accept documentation requirements:** Similar to DU but with Freddie Mac-specific variations. Key differences from DU: - LP uses the term "feedback certificate" for findings - LP "ACE" (Automated Collateral Evaluation): if LP issues ACE, appraisal may be waived — verify in feedback certificate before ordering appraisal - LP "LPA" verification messages differ in wording from DU — use Freddie Seller/Servicer Guide as reference - For FHA loans run through LP: LP findings are for risk only; FHA program guidelines still apply for eligibility **LP Accept — property eligibility notes:** LP feedback certificate identifies property eligibility (e.g., condo project approval status, manufactured housing eligibility). If LP flags a proper
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.