feat: add workflows/job-search/ with linkedin.md and indeed.md; update all READMEs, llm.txt, manifest

README.md

@@ -47,7 +47,10 @@ llm-tools/
 │   └── codex.md
 │
 ├── workflows/          Reusable workflows and automation
-│   └── README.md
+│   ├── README.md
+│   └── job-search/
+│       ├── linkedin.md
+│       └── indeed.md
 │
 ├── documents/          Project specs, architecture docs, written context
 │   ├── README.md

llm.txt

@@ -44,6 +44,9 @@ New agent? Read documents/onboarding.md first — it sequences the full orientat
 
   workflows/             Reusable workflows, automation scripts, and prompt chains
     README.md
+    job-search/
+      linkedin.md          LinkedIn job search, AMS candidate sourcing, outreach templates
+      indeed.md            Indeed job search, alerts, applying, tracking
 
   documents/             Project specs, architecture docs, written context
     README.md

manifest.json

@@ -207,7 +207,9 @@
     "workflows": {
       "description": "Reusable workflows, automation scripts, and prompt chains",
       "files": {
-        "README.md": "Index and intended contents for workflows"
+        "README.md": "Index of workflows and intended contents",
+        "job-search/linkedin.md": "LinkedIn \u2014 personal job search, AMS candidate sourcing, outreach templates",
+        "job-search/indeed.md": "Indeed \u2014 job search queries, alerts, applying, tracking"
       }
     },
     "documents": {

workflows/README.md

@@ -1,12 +1,23 @@
 # Workflows
 
-Reusable workflows and automation scripts for LLM agents working in this environment.
+Reusable workflows and automation guides for AI agents working in this environment.
 
-> This folder is a placeholder — add workflow definitions, prompt chains, and automation scripts here as they are developed.
+## Contents
 
-## Intended Contents
+### job-search/
+Job search and candidate sourcing workflows for personal contracting and AMS Enterprises pipeline.
 
-- CI/CD workflow templates
+| File | Purpose |
-- Deployment automation scripts
+|------|---------|
-- Prompt chains for common tasks
+| [`job-search/linkedin.md`](./job-search/linkedin.md) | LinkedIn — personal job search, AMS candidate sourcing, outreach templates, pipeline logging |
-- Multi-agent orchestration definitions
+| [`job-search/indeed.md`](./job-search/indeed.md) | Indeed — job search, alerts, applying, tracking |
+
+## Adding a New Workflow
+
+Create a subfolder or `.md` file here, then update `workflows/README.md` and `manifest.json`.
+
+Intended future contents:
+- Deploy workflows (Amplify, S3, Lambda)
+- New project setup checklist
+- New client onboarding steps
+- Prompt chains for common dev tasks

workflows/job-search/indeed.md

@@ -0,0 +1,113 @@
+# Indeed Job Search Workflow
+
+Workflow guide for using Indeed in job search — primarily for Jacob Mathison's personal contracting and full-time opportunities.
+
+---
+
+## Account
+
+| Field | Value |
+|-------|-------|
+| Email | jacob@mathisonprojects.com |
+| Resume | Upload latest from workspace_Father or LinkedIn export |
+
+---
+
+## Job Search (Personal Contracting)
+
+### Target roles
+- Senior / Principal / Staff Software Engineer
+- Frontend Architect, Full-Stack Lead, React/Vue/TypeScript Engineer
+- AWS / cloud-focused roles
+- Remote preferred, Omaha NE base
+
+### Recommended search queries
+```
+"React developer" remote contract
+"Vue.js" senior engineer remote
+"TypeScript" architect remote
+"AWS" full stack engineer remote contract
+"Next.js" developer remote
+"PHP" Laravel senior developer remote
+```
+
+### Search filters
+```
+Location:    Remote
+Job type:    Contract, Full-time
+Salary:      Set minimum based on current rate target
+Date posted: Last 14 days (keeps results fresh)
+```
+
+---
+
+## Indeed Resume
+
+Keep the resume updated and set to **Public** so recruiters can find it.
+
+Best practices:
+- Match keywords to job postings you're targeting (ATS optimization)
+- Lead with current role: Principal / Senior Engineer, Independent Contractor
+- Feature: React, Vue, TypeScript, PHP, AWS, CI/CD, Agile
+- Include client names where permissible (Capital One, Comcast, Amazon, etc.)
+
+---
+
+## Applying
+
+### Quick Apply (Indeed's version of Easy Apply)
+- Pre-fills from Indeed profile
+- Good for volume applications
+- Attach resume each time — don't rely on stored version being current
+
+### Employer site redirect
+- Indeed redirects to company ATS for many roles
+- Have resume file ready to upload
+- Tailor cover letter if applying to a top-target role
+
+---
+
+## Job Alerts
+
+Set up email alerts for key searches:
+1. Go to **Jobs** → run a search → **Get job alerts for this search**
+2. Set frequency to **Daily**
+3. Recommended alert searches:
+   - `React developer remote`
+   - `TypeScript senior engineer remote`
+   - `Full stack developer remote contract`
+
+---
+
+## Tracking Applications
+
+Log applications to the AMS pipeline Discord channels when relevant to AMS placements:
+- `#opportunities` (channel ID: `1446581171847696514`) — new opportunity found
+- `#contacted` (channel ID: `1446581227992780972`) — applied / reached out
+
+For personal job search tracking, maintain a local spreadsheet or note in `workspace_Father`.
+
+---
+
+## Indeed vs. LinkedIn
+
+| | Indeed | LinkedIn |
+|--|--------|---------|
+| **Best for** | Job postings, volume applications | Networking, recruiter outreach, candidate sourcing |
+| **Contract roles** | Good supply | Better for senior/niche |
+| **Recruiter contact** | Limited | Strong |
+| **Automation risk** | Low (standard apply) | High (scraping banned) |
+| **Resume visibility** | Public resume searchable | Profile always visible |
+
+Use both in parallel — Indeed for applying to posted roles, LinkedIn for networking and inbound recruiter leads.
+
+---
+
+## Useful Indeed URLs
+
+```
+Job search:    https://www.indeed.com/jobs
+My applications: https://my.indeed.com/resumebuilder/history
+Resume:        https://my.indeed.com/resume
+Alerts:        https://www.indeed.com/prefs/email-settings
+```

workflows/job-search/linkedin.md

@@ -0,0 +1,97 @@
+# LinkedIn Job Search Workflow
+
+Workflow guide for using LinkedIn in job search and candidate/opportunity sourcing — for both AMS Enterprises pipeline work and Jacob Mathison's personal contracting search.
+
+---
+
+## Accounts
+
+| Account | Purpose |
+|---------|---------|
+| Jacob Mathison | Personal profile — contractor/engineer presence. 2K followers. Currently showing Capital One. |
+| AMS Enterprises | Company page — staffing and consulting brand |
+
+**Profile URL:** https://www.linkedin.com/in/jacobmathison (verify current)
+
+---
+
+## Job Search (Personal Contracting)
+
+### Target roles
+- Principal / Senior / Staff Engineer
+- Frontend Architect, Full-Stack Lead
+- React, Vue, TypeScript, AWS, PHP stacks
+- Remote or hybrid preferred — Omaha NE base
+
+### Search filters
+```
+Keywords:   "React" OR "Vue" OR "TypeScript" OR "AWS" OR "Next.js"
+Location:   Remote (United States)
+Job type:   Contract, Full-time
+Experience: Director, Executive (maps to senior IC / lead levels)
+```
+
+### Easy Apply vs. Direct Apply
+- **Easy Apply** — fast, good for volume. Pre-fills from profile.
+- **Direct Apply** — sends to company ATS. Use for top targets.
+
+### Saved searches
+Set up saved searches with email alerts for:
+- `React architect remote contract`
+- `Vue.js senior engineer remote`
+- `AWS full stack remote contract`
+
+---
+
+## Candidate Sourcing (AMS Pipeline)
+
+AMS Enterprises sources developers for client placement. LinkedIn is the primary sourcing channel.
+
+### Search operators (LinkedIn Recruiter / Basic)
+```
+"software engineer" "React" "remote" #opentowork
+"senior developer" "TypeScript" "AWS" location:"United States"
+"full stack" "Vue" "Laravel" -"looking for"
+```
+
+### Outreach message template
+```
+Hi [Name],
+
+Came across your profile — your background in [stack] looks like a strong fit
+for a [role] opportunity we're working on. It's [remote/hybrid], [contract/FTE],
+with [company type / industry].
+
+Worth a quick chat? Happy to share details.
+
+— Jacob @ AMS Enterprises
+```
+
+### Tagging prospects in AMS pipeline
+After identifying a candidate, log to the appropriate Discord channel:
+- Initial find → `#prospected` (channel ID: `1446581198179799120`)
+- Contacted → `#contacted` (channel ID: `1446581227992780972`)
+- Meeting set → `#meetings-scheduled` (channel ID: `1446581306166087730`)
+
+> ⚠️ AMS pipeline channels are monitored by the sales-helper bot. Stick to pipeline data — no casual conversation.
+
+---
+
+## LinkedIn API / Automation Notes
+
+LinkedIn heavily restricts automation. For any programmatic work:
+- Use **official LinkedIn APIs** only (requires app approval)
+- Do not scrape or use unofficial clients — account ban risk
+- For bulk outreach, use LinkedIn's native **InMail** or **Sales Navigator** features
+- Browser automation (Whisker/Playwright) should be used sparingly and human-like
+
+---
+
+## Useful LinkedIn URLs
+
+```
+Job search:     https://www.linkedin.com/jobs/search/
+My applications: https://www.linkedin.com/my-items/saved-jobs/
+Network:        https://www.linkedin.com/mynetwork/
+AMS page:       https://www.linkedin.com/company/ams-enterprises (verify)
+```