Here is the whole secret: the comp process is three documents written in plain English. Not code. Not settings screens. Sentences.
They can be as detailed or as loose as you like โ "never use comps older than 6 months" is a valid instruction, and so is a page of rules about tract matching. Claude reads them and does what they say. Read them here โ the docs page also shows three example rewrites with every changed line highlighted, and what each one did to the same property's value.
Just tell Claude what you want. You describe it; it writes the document. In the workshop chat:
"Change the lookback to 6 months, stay inside the subject's tract, and make the reports one page. Save that as Maria's recipe."
Claude edits the preferences for you, saves your named version, and from then on:
You only ever need to know what you want. Any level of detail works, and Claude will ask when something's ambiguous.
Custom skills work on the free plan. The one-time setup:
Free-tier survival tips: one property per chat, don't paste reports into the conversation, and expect a few runs per 5-hour window โ the free limit is on volume, not features.
Want different standards next month? Open a chat with Claude, attach or reference your PREFERENCES.md, and say what should change:
"Rewrite this so the radius is one mile, pools add $40,000, and the report leads with a one-paragraph summary. Give me the updated file."
Claude hands back the edited document. Replace it in the folder,
re-zip, re-upload under Skills โ done. (Zip on Windows: right-click the
ladera-comps folder → Send to → Compressed folder.
Mac: right-click → Compress. The folder itself must be the top level
of the zip.)