# worksby.design

> HubSpot apps, themes and documentation by Works by Design. The docs below are
> served as clean Markdown — fetch the .md URL, not the HTML. The entire set in
> one request: https://worksby.design/llms-full.txt

## Guides

- [Build custom HubSpot CPQ quote modules — zero to hero](https://worksby.design/docs/cpq-quote-modules.md): The complete path from CMS-module knowledge to a production CPQ quote — data bridge, Islands, PDF, line items, SDK actions, serverless, lifecycle.

## App references

- [Events app — reference](https://worksby.design/docs/events.md): What the worksby.design Events app does, and the full integration contract — CRM schema, endpoints, and call patterns for listing events, registering attendees, and checking people in via QR code.
- [Commerce — reference](https://worksby.design/docs/commerce.md): What the worksby.design Commerce app does — B2B quoting (CPQ), a B2C storefront, and the payment platform every other app on the portal buys through — plus the six-step contract for consuming it.
- [File Manager — reference](https://worksby.design/docs/filemanager.md): A file library for portal members that keeps documents against the CRM records they belong to — what it does, which storage backends it spans, how identity is bound, and the endpoints behind it.
- [ATS — reference](https://worksby.design/docs/ats.md): A careers site and applicant-tracking system that runs inside a HubSpot portal — job listings, application intake, a recruiter workspace on the CRM records, and a transparent scoring engine that ranks candidates against a posting.
- [ATS — candidate matching](https://worksby.design/docs/ats-matching.md): How the ATS scores a candidate against a job posting — the ten dimensions and their arithmetic, the must-have gate, all 57 tuning settings, and the three places a weight can be changed.
- [ATS — integration guide](https://worksby.design/docs/ats-integration.md): Calling the ATS over HTTP — the three authentication surfaces, the generated endpoint index, the careers-embed and candidate-status contracts, the match API and its persisted score shape, and the gaps that are not built yet.
- [ATS — install & operate](https://worksby.design/docs/ats-setup.md): Installing and running the ATS on a HubSpot portal — the tier decision, what install provisions, the candidate and posting fields matching depends on, the schema migration an existing portal needs, verification, and what an uninstall destroys.
- [Keyring — reference](https://worksby.design/docs/keyring.md): A loyalty, gift-card and identity platform built inside HubSpot — what it does, what customers and staff see, the CRM objects it stores value in, and how it connects to a point-of-sale system, to Events and to Commerce.
- [Keyring — integration guide](https://worksby.design/docs/keyring-integration.md): The full HTTP contract for integrating a point-of-sale system, kiosk or third party into Keyring — authenticating a till, parsing scanned codes, redeeming and topping up value, idempotency, error handling, and what does not exist yet.
- [Keyring — install and operate](https://worksby.design/docs/keyring-setup.md): What it takes to run Keyring on a HubSpot portal — prerequisites, what the install provisions, the venue and staff decisions only the customer can make, verification that proves it actually works, and what a reinstall does and does not destroy.

## AI access

- [Docs MCP — setup & access](https://worksby.design/docs/mcp.md): Connect the Claude app, Claude Code or Codex to the Works by Design HubSpot documentation over MCP — access, client setup, available tools, and security.