By willdady

Response-body conventions for the Platypus backend API — the error key for failures, the message key for 2xx status messages, and when to throw a typed error instead of returning a response.

willdady/platypus

Platypus tools and tool sets — writing a tool, contributing a tool set from a plugin, scoping tools to a workspace, sharing a tool across sets, chat icons, and custom tool UI.

willdady/platypus

Guide for adding new API endpoints to the Platypus backend using Hono.js — routing, tenant scoping middleware, validation, and database access.

willdady/platypus

Guide for making database schema changes in Platypus using Drizzle ORM — editing the schema, pushing to a dev database, and generating the migration that ships.

willdady/platypus

Audit one section of the docs content against the code, and report what is wrong, stale, fragile, off-voice, or missing.

willdady/platypus

Post-save conventions for Platypus frontend forms — where a save lands the user, and what the submit button is called.

willdady/platypus

The final gate before a release is cut — go green, reconcile the release PR against what actually landed, sweep what CI can't see, check the roadmap and ADR statuses, optionally deep-review, then…

willdady/platypus