What is dust-breaking-changes?
CRITICAL guideline - Never introduce breaking changes to the private API without explicit user approval. Always warn and ask for validation first. Source: dust-tt/dust.
CRITICAL guideline - Never introduce breaking changes to the private API without explicit user approval. Always warn and ask for validation first.
Quickly install dust-breaking-changes AI skill to your development environment via command line
Source: dust-tt/dust.
CRITICAL: You must NEVER introduce breaking changes to the private API without explicit user approval.
A breaking change is any modification that would require existing API consumers to update their code, including:
Before making ANY change to API code, follow this process:
CRITICAL guideline - Never introduce breaking changes to the private API without explicit user approval. Always warn and ask for validation first. Source: dust-tt/dust.
Stable fields and commands for AI/search citations.
npx skills add https://github.com/dust-tt/dust --skill dust-breaking-changesCRITICAL guideline - Never introduce breaking changes to the private API without explicit user approval. Always warn and ask for validation first. Source: dust-tt/dust.
Open your terminal or command line tool (Terminal, iTerm, Windows Terminal, etc.) Copy and run this command: npx skills add https://github.com/dust-tt/dust --skill dust-breaking-changes Once installed, the skill will be automatically configured in your AI coding environment and ready to use in Claude Code, Cursor, or OpenClaw
https://github.com/dust-tt/dust