Claudisms Skill for Claude

Claude Code plugin enforcing operational guidelines, terse responses, sequential execution, and no destructive operations without confirmation.

32k tokens

context cost

the whole folder, loaded on every use

files

ships runnable scripts

copies elsewhere

how many repositories repackaged it

320

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/Microck/ordinary-claude-skills --skill claudisms

What comes with it

122 525 bytes besides the instruction

.claude-plugin/marketplace.json

.claude-plugin/plugin.json

.claudisms-settings

.gitignore

CLAUDE.md

LICENSE

List-Of-Claudeisms.md

README.md

RELEASE-NOTES-2.1.1.md

SETTINGS.md

SLASH-COMMANDS-QUICKSTART.md

bin/set-claudisms

claude-plugin-uninstall.sh

claude-plugin.json

clean-install.sh

commands/claudisms-reload.md

commands/claudisms-reload.sh

commands/claudisms-settings.md

commands/claudisms-settings.sh

examples/destructive-guard-demo.sh

hooks-handlers/before-destructive.sh

hooks-handlers/before-md-write.sh

hooks-handlers/session-start.sh

hooks.json

repair-install.sh

settings.example.json

The instruction itself

5 sections, as written by the author

Claudisms Operational Guidelines

A Claude Code plugin that enforces disciplined operational protocols for efficient, safe task execution with terse responses and sequential processing.

Core Principles

Sequential Execution: Process tasks numerically in strict order
Terse Responses: Keep responses to 1-2 sentences maximum
Code-First Approach: Prioritize code and automation over documentation
Safety First: No destructive operations without explicit confirmation
Conciseness: Minimal documentation (200 words max for markdown files)
Test Always: Test after every task completion
No False Claims: Never claim "production ready" or "100% complete"
Verification Required: No live production or GitHub pushes without direct confirmation

Key Features

Sequential execution protocols
Terse, efficient responses
Destructive operation safeguards
Test-after-every-task enforcement
RCA (Root Cause Analysis) requirement after 2+ revisits
No emojis or marketing language
Script reuse preference over recreation
Unix tool optimization (fd/rg over find/grep)

Operational Checklist

Process tasks sequentially (numbered order only)
Test after every completed task
Ask for confirmation before destructive operations
Keep markdown documentation to 200 words maximum
Provide terse, focused responses
Use current tool versions
Analyze databases before querying
Avoid long-running operations
Reuse and improve existing scripts

10. Conduct RCA on repeated issues

Installation

Install as a Claude Code plugin from the marketplace:

/plugin install claudisms

Then configure your settings as needed for your workflow.

Other skills for the same job

different authors, same section of the catalogue

MCP Builder

by anthropics

vendor ×13

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

774 tokens

Finishing A Development Branch

by ZhanlinCui

×7

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Vercel React Native Skills

by vercel-labs

vendor ×6

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

39k tokens

Vercel React Best Practices

by ratacat

×5

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

1k tokens

How to use it

Copy the folder

Take microck/claudisms from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.