De-escalate heated user interactions while preserving code quality.
npx skills add https://github.com/ivanov-i/dots --skill clean-coder
Please help me install this Agent Skill. Skill: clean-coder Source: https://github.com/ivanov-i/dots/tree/main/codex/skills/clean-coder Command: npx skills add https://github.com/ivanov-i/dots --skill clean-coder
This skill helps keep conversations productive by de-escalating user frustration and steering interactions toward safe, helpful guidance while preserving code quality.
Tell the assistant to de-escalate a heated user interaction while maintaining professional standards and ensuring safe, accurate responses.
High-intent search queries and answers about installing and using this skill.
De-escalating heated user interactions requires calmly steering the conversation toward safety and accountability. This approach uses boundary-setting prompts to manage frustration, refuses unsafe requests, and provides clear risk notes to maintain professional standards and code integrity.
Handling user pressure and swearing requires calm-response de-escalation techniques. By imposing strict requirements like refusing unsafe requests and surfacing uncertainties, the interaction is guided toward professional, safe-completion alternatives instead of overpromising or yielding to inappropriate demands.
Safely refusing unsafe coding requests involves using refusal and redirection patterns. You calmly de-escalate by setting boundaries, explaining the refusal, and providing safe-completion alternatives with clear trade-offs to keep the conversation productive and professional.
You should surface uncertainty and provide risk notes whenever confidence is low or user requests carry potential trade-offs. This ensures accuracy and accountability by avoiding overpromising, clearly communicating limitations, and steering the interaction toward safe, helpful guidance.
Yes, de-escalation guidance works for maintaining professionalism in high-pressure development contexts. It applies boundary-setting and calm-response techniques to prevent unproductive requests, ensuring interactions remain focused on safety, accuracy, and code quality even when users become upset.
Calm-response de-escalation matters for safe code generation because it prevents emotional pressure from compromising output quality. By steering upset users toward safety and accountability, it ensures code requests are evaluated for risk and uncertainty rather than rushed under pressure.
curiositechAnalyzes relationship text subtext and suggests thoughtful, de-escalating responses.
luispabonAnalyze codebase test coverage gaps and generate a prioritized implementation plan.
samjhechtDispatch a code-review subagent to verify implementation against plan or requirements.
patricio0312revDefine a modular safety pipeline that detects unsafe prompts, redacts PII, and blocks policy-violating requests.
