Idea
--field <name> applies domain-aware reviewer weighting (feeds framings §3.C/§3.D/§3.I/§3.J). Today the set of shipped profiles is small. Adding more makes attack / code-audit / design noticeably sharper out of the box.
Proposed new profiles (one field-profiles/<name>.md each, from field-profiles/_template.md):
security — threat-model lens (STRIDE, trust boundaries, authz)ml — data leakage, eval validity, distribution shift, reproducibilityfrontend — a11y, perf budgets, state-management foot-gunsdistributed-systems — partial failure, idempotency, consistency, backpressure
What's involved
Each profile is one markdown file following the template; non-blocking if absent, so they're independent and low-risk. Great for anyone with domain expertise who wants to contribute without touching the engine.
Good first issue?
Yes — pick one domain you know well and write a single profile.
Idea
--field <name>applies domain-aware reviewer weighting (feeds framings §3.C/§3.D/§3.I/§3.J). Today the set of shipped profiles is small. Adding more makesattack/code-audit/designnoticeably sharper out of the box.Proposed new profiles (one
field-profiles/<name>.mdeach, fromfield-profiles/_template.md):security— threat-model lens (STRIDE, trust boundaries, authz)ml— data leakage, eval validity, distribution shift, reproducibilityfrontend— a11y, perf budgets, state-management foot-gunsdistributed-systems— partial failure, idempotency, consistency, backpressureWhat's involved
Each profile is one markdown file following the template; non-blocking if absent, so they're independent and low-risk. Great for anyone with domain expertise who wants to contribute without touching the engine.
Good first issue?
Yes — pick one domain you know well and write a single profile.