Claudeisms Operational Guidelines
This is a workflow discipline layer for Claude that enforces pragmatic engineering practices when working on code projects. It pushes sequential task execution, terse communication, and safety rails like requiring confirmation before deleting databases or pushing to production. The guidelines discourage blame-oriented debugging and encourage root cause analysis when you're circling the same problem. Notable specifics include testing after every task, analyzing database schemas before queries, and reusing scripts instead of rewriting them. It's opinionated about response style (no emoji, no "production ready" claims) and treats AI assistance as a workhorse rather than a conversational partner. Useful if you want Claude to act more like a cautious senior engineer and less like an enthusiastic assistant.
- GitHub stars
- 237
- last updated
- Apr 30, 2026
Install
$ npx -y skills add microck/ordinary-claude-skills --skill 'Claudeisms Operational Guidelines' --agent claude-codeInstalls into .claude/skills of the current project.
Files
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.
Sponsors
Agent CaffeineSponsoredClose your lid, come back to finished work
SnugSponsoredThe clipboard manager for the AI eraPromote your product hereReach 125k+ visitors monthly
WaxSponsoredBlock anything with supervision, without erasing your iPhonePromote your product hereReach 125k+ visitors monthly
knobsSponsoredSee your site on any phone, any day, in any languageDetails
- Repository
- github.com/microck/ordinary-claude-skills
- First seen
- Jun 11, 2026
More from microck/ordinary-claude-skills
All 9Recommended
cavemanjuliusbrussee/cavemanUltra-compressed communication mode. Cuts output tokens 65% (measured) by speaking like caveman while keeping full technical accuracy. Supports intensity levels618.3Kskills.sh installs
improveshadcn/improveSurvey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute. Strictly read-only on s40Kskills.sh installs
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes326.7Kskills.sh installs
karpathy-guidelinesforrestchang/andrej-karpathy-skillsBehavioral guidelines to reduce common LLM coding mistakes through explicit assumptions, simplicity, and verifiable success criteria.17.9Kskills.sh installs
find-skillsvercel-labs/skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express int4.3Mskills.sh installs