first-responder-program-finder
Use when an agent needs to navigate the FirstResponderHomePrograms website UI to find statewide verified programs, under-review signals, free deeper-opportunity teasers, or paid Research Vault and workspace information.
What this skill does
# FirstResponder Program Finder Use this skill when the task is about using the website UI of [https://firstresponderhomeprograms.com/](https://firstresponderhomeprograms.com/), not when the task is about editing the codebase or calling internal APIs directly. ## Core framing The site is: - a neutral information site - not a lender - free for statewide verified program discovery - layered so local, specialty, and deeper research can sit behind the paid workspace It mainly helps answer: - whether a state has verified statewide options - which official options fit a state and role - the support type, amount, and repayment structure - whether there are under-review official signals - whether the state has deeper opportunities beyond the free layer - how a paid user should use the private workspace ## Workflow 1. Decide whether the user needs: - free statewide verified information - under-review information - deeper/local/specialty information - private workspace features 2. For normal public discovery, start with the homepage finder. 3. For state-level overview, go to the state page. 4. For full rules, official documents, and official options, open the program detail page. 5. If the finder shows `0 verified matches`, do not stop there. Check: - whether `Support type` should be reset to `Any` - whether `Repayment` should be reset to `Any` - whether under-review signals exist - whether the state has deeper opportunities 6. If the task needs local, specialty, employer, pension, or full research records, move into the paid workspace flow. 7. Keep these layers distinct: - `Verified` - `Under review` - `Deeper opportunities teaser` - `Research Vault` ## Quick rules - On the homepage finder, `State` and `Role` are required. - `Support type` and `Repayment` are optional. - `State` accepts: - full state names - two-letter abbreviations - case-insensitive input - Verified results appear first. - Under-review signals are expanded separately. - Deeper opportunities are shown as a teaser in the free layer, not as free detailed records. - If there are no verified matches: - try clearing optional filters - check under-review signals - check the deeper-opportunities teaser - Do not present the site as: - an instant quote tool - an underwriting tool - a pre-approval tool - a lender recommender ## Free layer Read `references/free-finder-and-state-pages.md` before answering detailed navigation questions. Use the free layer for: - homepage search - state-level verified discovery - official option review - under-review summaries - official document links - free deeper-opportunities teaser counts and categories ### Homepage finder Path: - `/` Best for: - "Texas firefighter home loans" - "Connecticut first responder mortgage help" - "Ohio EMT down payment assistance" Recommended agent path: 1. enter state 2. enter role 3. optionally set support type and repayment 4. click `Search` 5. review verified results first 6. expand under-review signals if needed 7. inspect deeper teaser if present ### State pages Examples: - `/states/connecticut/` - `/states/texas/` State pages help the agent answer: - how many verified statewide programs the state has - whether under-review signals exist - whether deeper opportunities exist - what governance/review status the page carries ### Program pages Program pages are for: - amount or structure - who qualifies - support type - repayment / forgiveness / triggers - official documents - official option matrix If a finder row represents an official option, the program detail page may already open with the matching option highlighted. ## Paid layer Read `references/paid-decision-pack-workspace.md` before explaining paid access. The paid layer is centered on: - `Decision Pack` - `Account` - `Workspace` - `Research Vault` ### Sign-in entry Anonymous users: - should see `Sign in` - may encounter an auth modal first - can also use: - `/account/sign-in/` - `/account/register/` - `/account/forgot-password/` Supported account paths: - Google sign-in - email registration and email/password sign-in ### Workspace entry Signed in, not purchased: - header should usually show `Account` - primary page is `/account/` Active paid user: - header should usually show `Workspace` - primary page is `/account/workspace/` ### What the paid user can access The paid workspace can include: - `Research Vault` - `Saved scenarios` - `Saved programs` - `Saved opportunities` - `Comparisons` - `Conflict checks` - `Question kit` - `Action checklist` - `Reminder settings` The Research Vault is not just a list of verified programs. It may include: - `Current opportunities` - `Needs judgment` - `Historical / blocked` - `Research notes` Agents should say clearly: - these are research records - not every record is a verified, broadly available current program - conditional, historical, and blocked records require direct source review and user judgment ## When to use this site Good fit: - starting from statewide verified programs - reviewing official options - explaining under-review signals - showing whether a state has deeper opportunities - guiding paid users into the workspace Bad fit: - instant mortgage quotes - lender underwriting decisions - definitive eligibility promises - monthly payment calculations ## Recommended language Prefer: - `verified` - `under review` - `deeper opportunities teaser` - `Research Vault` - `official option` - `official documents` Avoid: - "the site has confirmed you qualify" - "this is the lender's approval result" - "all records are equivalent programs" ## Minimal answer template When a user asks how to use the site, the safest short answer is: 1. Start on the homepage and enter `State` and `Role`. 2. Review `Verified matches` first. 3. If there are `0 verified matches`, reset `Support type` and `Repayment` back to `Any`. 4. Then expand `under-review signals`. 5. Then check `Deeper opportunities in this state`. 6. Open the state page for statewide overview. 7. Open the program detail page for rules and official documents. 8. Use the paid workspace only when local, specialty, or deeper research detail is needed.
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".