claudeisms
Operational guidelines: terse responses, sequential execution, no destructive ops without confirmation
Summary
This skill enforces operational guidelines for Claude Code, ensuring responses are terse, actions are executed sequentially, and no destructive operations occur without user confirmation.
- It helps developers maintain safe and efficient workflows by preventing accidental data loss and keeping interactions concise.
Install & Usage
/plugin marketplace add <org/repo>Add the configuration to /plugin install claudeisms@<marketplace>
/pluginUse Cases
Usage Examples
/claudeisms delete the temp files in /tmp
/claudeisms refactor the function calculateTotal to use async/await
/claudeisms run the tests and then commit if all pass
Security Audits
Frequently Asked Questions
What is claudeisms?
This skill enforces operational guidelines for Claude Code, ensuring responses are terse, actions are executed sequentially, and no destructive operations occur without user confirmation. It helps developers maintain safe and efficient workflows by preventing accidental data loss and keeping interactions concise.
How to install claudeisms?
To install claudeisms: add a marketplace (/plugin marketplace add <org/repo>), then add the config to /plugin install claudeisms@<marketplace>. Finally, /plugin in Claude Code.
What is claudeisms best for?
claudeisms is a plugin categorized under General. Created by Jefferson Warrior.
What can I use claudeisms for?
claudeisms is useful for: Prevent accidental file deletion or overwrite by requiring confirmation before destructive operations.; Keep Claude Code responses short and to the point for faster development iterations.; Ensure commands are executed one at a time to avoid race conditions or unintended side effects.; Safely refactor code by confirming each file modification before applying changes.; Streamline debugging sessions with minimal output and step-by-step execution.; Automate repetitive tasks with confidence that each step is confirmed before proceeding..