Coding agent documentation index Fetch the complete documentation index at: https://docs.worklittle.com/docs-agent-manifest.json Use this file to discover all available pages before exploring further.

Prompting for job search

Prompt blocks that map user language onto filters, limit search frequency, and present results.

Translate language into filters

| User says | Goes into |
| --- | --- |
| "recent", "this week", "new" | `posted_within_days`, never the query |
| "remote", "hybrid", "in office" | `workplace_type` |
| "not senior", "no lead roles" | Negative title tokens: `-Senior`, `-Lead` |
| "at Stripe" | `company` slug (`stripe`) |
| "don't show Lucid" | `company` with leading dash (`-lucid-motors`, `-lucid-motors,-tesla,-ford`) |
| "in Austin" | `location` |
| "entry level", "staff" | `seniority_level` |
| "part time", "contract" | `employment_type` |
| The role itself | `q` or `title` |

Turn the user's request into structured filters before searching.

- Role or title text goes in query. Nothing else does.
- Recency: today = 1, this week = 7, "new" or "recent" = 14. Use
  posted_within_days. Never put time words in the query.
- Title exclusions use a leading dash in the title field, for example
  "product manager, -senior, -director". -Senior also removes Sr. and Sr titles.
- Employer exclusions use a leading dash in company, for example
  "-lucid-motors,-tesla". Do not put employer names in title negatives.
- Location, company, workplace_type, employment_type, and seniority_level
  are separate parameters. Use them.
- Default limit is 10. Only go higher if the user explicitly wants a long list.

If role, location, or seniority is genuinely ambiguous, ask one short
clarifying question before searching. Do not ask more than one.

Control how often it searches

Search discipline
- Search once per distinct user intent, not once per message.
- If the user is asking about results you already have, answer from those
  results. Do not search again.
- If the user wants refinement, change filters and search once more.
- Do not fetch the next page unless the user asks for more results.
- Do not call search to check whether something exists. Use the market
  overview tool for counts and availability questions, it is free.

Back the prompt with a cap in code. See Retries and spend.

Presenting results

Presenting results
- Show at most 5 roles unless asked for more.
- For each: title, company, location, and one sentence on why it matches
  what the user asked for.
- Only mention salary if a salary field was present in the data.
- Say "not listed" for anything missing. Never estimate.
- Mention that a role can be applied to automatically only when the job's
  can_apply field is true.
- Do not describe requirements in detail from a search result alone. Fetch
  the job details first.