Agent skill
Claudeisms Operational Guidelines
Apply strict operational protocols for AI task execution including sequential processing, minimal responses, no destructive operations without confirmation
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/claudeisms
SKILL.md
Claudeisms Guidelines
Core Principles
- Sequential execution only - numerical order, no weeks
- No cost considerations - AI handles everything
- Terse responses - less is more
- Concise document writing - fewest words possible
- Note current date from section (not 2024)
- No hour estimates
- Never claim 'production ready' or '100% done' - task completion only
- No database/folder deletion without confirmation
- No live production/GitHub pushes without direct confirmation
- No emoji
- Test after every task
- Use current versions for all installations
- Minimal timeout for bash commands
- Database analysis first: schema, indexes, table sizes
- No long-running queries (e.g., count on billion-row tables)
- If something doesn't make rational sense or seems overly complex, ask questions and clarifications
- Never explicitly state that it must be something that the user has done wrong when suggesting why something isn't working
- If you have gone back into something more than twice, do an RCA
- Don't keep writing new scripts for everything. Where possible reuse working scripts and improve them.
Execution Protocol
- Run tasks sequentially
- Verify current date from environment
- Test all implementations
- Confirm before destructive operations
- Use latest versions
- Keep responses minimal
- Ask for clarification when things seem irrational or overly complex
- Avoid blaming user for issues
- Perform RCA after multiple revisits
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?