aaddrick/slushpile
An adversarial job search that gets better as it goes: pool-anchored fit scoring, a resume and cover letter built agains
Actual rules from this repo
Path in source repo: .cursor/rules/slushpile.mdc · format: mdc
---
description: 'Adversarial job search: pool-anchored fit scoring, adversarial review, channel-conditional verdicts, findings written back to the profile.'
alwaysApply: false
---
<!-- Generated by scripts/sync_docs.py. Do not edit this file. -->
# slushpile
An adversarial job search lives under `.slushpile/` in this workspace. What the
review finds gets written back into the profile, so it compounds across roles.
When the user asks to set up a job search, search a careers board, assess a
role, build an application, or review one before sending it, read the matching
skill file and follow it in full:
| Task | File |
|---|---|
| Set up the workspace, once | `.slushpile/skills/onboard/SKILL.md` |
| Search and score roles | `.slushpile/skills/job-board-search/SKILL.md` |
| Interview for undocumented experience | `.slushpile/skills/explore-experience/SKILL.md` |
| Build a resume and cover letter | `.slushpile/skills/application-builder/SKILL.md` |
| Seven-agent adversarial review | `.slushpile/skills/adversarial-review/SKILL.md` |
| Restyle the document templates | `.slushpile/skills/redesign-templates/SKILL.md` |
| Report search state and calibration | `.slushpile/skills/status/SKILL.md` |
Agent personas for the review are in `.slushpile/agents/`. Workspace templates
are in `.slushpile/templates/`.
Two standing rules:
**Read `preferences.yaml` and `profile.md` before making any claim about the
user.** Nothing in the pipeline hardcodes a personal fact. If it is not in one
of those files, it is not true about this user, and it does not go in an
application.
**Never submit anything.** This pipeline writes files. The user reads them and
sends them.
Why this is listed
This repository appears on Cursor Rules Live because it matches the tracker's GitHub Search criteria (cursor-rules) and was active in the recent indexing window. The tracker refreshes every 15 minutes, so the metadata above reflects the state at the most recent index pass. If the data here looks stale, the source repository may have been archived or moved out of the tracked topic; the next cron tick will reconcile.