closing-checklist
Design pre-closing and post-closing checklist automation for mortgage loan closings. Use when automating the closing preparation workflow, closing day coordination, and post-closing package review for a mortgage lender or broker.
What this skill does
# Closing Checklist Automation Design Design the automated pre-closing and post-closing checklist workflow for mortgage loan closings, including condition clearance, CD issuance compliance, closing day coordination, post-closing package review, and trailing document tracking. --- ## Section 1: Pre-Closing Checklist **Trigger:** CTC (Clear to Close) issued by underwriter **Timeline:** CTC typically issued 3–10 days before closing. All pre-closing items below should target completion 24–48 hours before the scheduled closing date. ### 1a: Condition Clearance Verification Before beginning any closing preparation, confirm all UW conditions are cleared: | Check | Verified By | Method | |-------|------------|--------| | All CTC conditions marked cleared in LOS | Processor / Underwriter | LOS condition log | | No outstanding stips remaining | Underwriter | Final approval document | | Any PTD (Prior to Docs) conditions cleared | Processor | LOS | | Any PTF (Prior to Funding) conditions noted | Closer | List carried to funding checklist | | Flood cert confirmed: flood zone, standard vs. SFHA | Processor | Flood determination in file | | Hazard insurance binder received and coverage adequate | Processor | Binder in file; coverage = replacement cost or min loan amount | | Condo: HO-6 insurance if required by program | Processor | Binder in file | ### 1b: CD Issuance and TRID Compliance - [ ] Final CD issued to borrower(s) with all parties correct - [ ] CD delivery method documented: in-person / e-sign (timestamp) / mail (calculate 3-day receipt) - [ ] 3-business-day waiting period calculated and closing date confirmed to be on or after waiting period expiry - [ ] CD fees reconciled against LE: tolerance analysis complete; no violations - [ ] If tolerance cure required: cure amount calculated, method determined, documented on CD or memo - [ ] Seller CD (purchase only): separate CD for seller generated with seller-side transactions - [ ] Borrower has received and confirmed receipt of CD (e-sign confirmation or acknowledgment) ### 1c: Title Review - [ ] Final title commitment received - [ ] Title company and agent confirmed for closing - [ ] Effective date of title search within lender's acceptable window (typically 30–60 days pre-close) - [ ] Exceptions reviewed and cleared (or accepted per lender guidelines): - Existing mortgage(s) to be paid off at closing — payoff figures received - Easements — recorded easements reviewed; none affecting marketability - Survey matters — if survey required, reviewed and acceptable - Liens — all liens addressed (paid off at closing or per lender exception) - HOA dues — current; no delinquency - [ ] Vesting/how title will be taken: matches 1003 and approved by lender - [ ] If leasehold: lease reviewed per program requirements ### 1d: Hazard and Flood Insurance Verification | Item | Requirement | |------|-------------| | Hazard insurance binder | Effective date = on or before closing date; term at least 1 year | | Coverage amount | Greater of: replacement cost or loan amount (cannot be less than loan amount) | | Mortgagee clause | Correct lender name and ISAOA language | | First year premium | Paid in advance (or at closing if escrowed — verify funds at closing) | | Flood insurance (if required) | Coverage = minimum required (lesser of: loan amount, building replacement cost, $250K for NFIP) | | Flood insurance mortgagee clause | Correct lender name | | Flood first-year premium | Paid in advance or at closing | ### 1e: Wire Instructions Verification - [ ] Wire instructions received from settlement agent / title company - [ ] Wire instructions verified by callback to title company at number on file (NOT the number in the email — fraud risk) - [ ] Confirm wire instructions have not changed since prior verification - [ ] Documentation: log of when instructions were verified, who verified, callback number used - [ ] Wire fraud warning provided to borrower in CD and separately: borrowers should never wire based on email alone; always call to verify using a number obtained independently ### 1f: Closing Agent Confirmation - [ ] Settlement agent / closing attorney confirmed for scheduled date, time, and location - [ ] Remote online notarization (RON) setup if applicable: notary confirmed, technology tested, state RON law confirmed - [ ] Closing documents to be delivered to closing agent: method (electronic delivery / overnight / courier) and timeline confirmed - [ ] POA (Power of Attorney) review: if any party is signing via POA, confirm POA is acceptable to lender (recorded or recordable, specific to the transaction, not expired) ### 1g: Loan Document Package Before releasing loan documents to settlement agent: - [ ] Final loan amount confirmed (no changes since last AUS and LOS) - [ ] Interest rate and all loan terms confirmed (match rate lock) - [ ] Loan documents generated in LOS or doc prep vendor - [ ] Note reviewed: loan amount, interest rate, payment amount, maturity date, prepayment penalty (Y/N) - [ ] Deed of Trust / Mortgage reviewed: property legal description, vesting, lender name, loan terms - [ ] MERS Registration: if MERS is used, MERS MIN assigned and in documents - [ ] Right to cancel (if refinance, non-purchase money): 3-business-day rescission period documents included --- ## Section 2: Closing Day Workflow ### 2a: Disbursement Authorization **Before authorizing wire disbursement:** - [ ] All PTF (Prior to Funding) conditions cleared - [ ] Signed closing package received from settlement agent (wet or e-sign) - [ ] Closing affidavit / compliance agreement executed - [ ] Note signed by all borrowers - [ ] Deed of Trust / Mortgage signed by all vested parties - [ ] Right to cancel executed (refi) — confirm 3-day rescission period has run (or waiver executed if applicable) - [ ] Funds confirmed received: borrower's closing funds wired in or cashier's check confirmed - [ ] Closing disclosure re-reviewed post-signing: no changes from issued CD (if changes, additional disclosure may be required) - [ ] HMDA data confirmed for LAR reporting ### 2b: Wire Release - [ ] Funding department approves wire release - [ ] Wire released to settlement agent escrow account - [ ] Wire confirmation number saved in LOS - [ ] Settlement agent confirms receipt of wire - [ ] Disbursement date = funding date (used for first payment due date calculation and HMDA) ### 2c: Closing Package Receipt Confirmation After closing is complete: - [ ] Settlement agent sends executed closing package to lender (overnight or electronic) - [ ] Package received and logged (date received) - [ ] Receipt acknowledgment sent to settlement agent --- ## Section 3: Post-Closing Package Review **Trigger:** Executed closing package received from settlement agent **Timeline:** Must be completed within lender's investor delivery commitment (typically 15–30 days post-close) ### 3a: Document Review Checklist **Note review:** - [ ] All borrowers have signed (wet or e-sign per investor requirements) - [ ] Loan amount matches final CD and LOS - [ ] Interest rate matches final CD and rate lock confirmation - [ ] Monthly payment matches final CD (PI only) - [ ] Maturity date correct - [ ] Prepayment penalty terms correct (or none, if applicable) - [ ] Endorsement required: blank endorsement or to specific investor / MERS **Deed of Trust / Mortgage review:** - [ ] All parties have signed (all vested owners) - [ ] Notary acknowledgment complete (notary seal legible, notary commission expiration date valid on date of signing) - [ ] Legal description of property matches title commitment and survey - [ ] Loan amount correct - [ ] Lender name correct (not prior lender if refinance) **Title insurance:** - [ ] ALTA Lender's Title Insurance Policy (or binder pending recording) received - [ ] Policy amount = loan amount - [ ] Policy insures lender in first lien position (for purchase or rate/term refi) - [ ] Named insured = lender (or MERS as
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.