dust-swagger
Swagger Documentation Sync - Mandatory Rule
MANDATORY: Any change to an API endpoint schema must be reflected in the Swagger documentation. Do not consider an API change complete until Swagger is updated.
When This Rule Applies
Automatically applies whenever you are:
- Modifying files in
front/pages/api/**orfront/app/api/** - Adding, removing, or renaming fields in request/response bodies (at any nesting level)
- Changing field types or optionality in API schemas
- Adding or removing endpoints
What to Update
When modifying API schemas, check and update the following:
pages/api/swagger_private_schemas.ts— shared schemas for the private APIpages/api/v1/w/[wId]/swagger_schemas.ts— shared schemas for the public API
More from dust-tt/dust
react-hook-form-writer
Write and refactor React forms using react-hook-form with Zod validation. Use when creating new form components, converting existing forms to react-hook-form, or implementing form validation patterns.
74dust-mcp-server
Step-by-step guide for creating new internal MCP server integrations in Dust that connect to remote platforms (Jira, HubSpot, Salesforce, etc.). Use when adding a new MCP server, implementing a platform integration, or connecting Dust to a new external service.
60dust-temporal
Step-by-step guide for creating Temporal workflows in Dust. Use when adding background jobs, async processing, durable workflows, or task queues.
59dust-llm
Step-by-step guide for adding support for a new LLM in Dust. Use when adding a new model, or updating a previous one.
55dust-test
Step-by-step guide for writing focused, practical tests for Dust codebases following the 80/20 principle.
54writing-react-effects
Writes React components without unnecessary useEffect. Use when creating/reviewing React components, refactoring effects, or when code uses useEffect to transform data or handle events.
53