codewarden
CLAUDE.md1 starsChanged 10 months agoMITView on GitHub
CodeWarden is a Claude Code plugin for enforcing modern development practices, code quality standards, and security best practices in TypeScript/React/Next.js applications. Commands are markdown files in commands/ that become slash commands prefixed with codewarden:. Agents are markdown files in agents/ that define specialized subagents. For skills with scripts (like vercel-deploy): When making changes:
In this repository7 other files it gives its agents.
- skills/ui-ux-guidelines/AGENTS.mdAGENTS.md
- react-best-practicesSkill
- react-next-modernSkill
- ui-ux-guidelinesSkill
- ultraciteSkill
- vercel-deploySkill
- vercel-design-guidelinesSkill
The file
We split this CLAUDE.md into the rules it gives an agent
8 rules. About 0 are common, 2 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 44
Keep SKILL.md under 500 lines: - put detailed reference material in separate files
- Very specific: line 52
SKILL.md: Always uppercase, always this exact filename
- Very specific: line 86
Use set -e for fail-fast behavior
- Very specific: line 87
Write status messages to stderr: echo "Message" >&2
- Distinctive: line 88
Write machine-readable output (JSON) to stdout
- Very specific: line 95
Update version in .claude-plugin/plugin.json (semver)
- Very specific: line 96
Add entry to CHANGELOG.md
- Distinctive: line 97
Update README.md if adding new features
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
CLAUDE.md
This file provides guidance to AI coding agents (Claude Code, Cursor, Copilot, etc.) when working with code in this repository.
Repository Overview
CodeWarden is a Claude Code plugin for enforcing modern development practices, code quality standards, and security best practices in TypeScript/React/Next.js applications.
Plugin Structure
codewarden/
├── .claude-plugin/
│ └── plugin.json # Plugin metadata (name, version, description)
├── skills/ # Agent Skills (model-invoked)
│ ├── {skill-name}/
│ │ ├── SKILL.md # Required: skill definition with frontmatter
│ │ └── references/ # Optional: supporting documentation
├── commands/ # Slash commands (user-invoked via /{name})
│ └── {command-name}.md
├── agents/ # Specialized subagents
│ └── {agent-name}.md
└── hooks/
└── hooks.json # Automation hooksCreating/Modifying Skills
SKILL.md Format
---
name: skill-name
description: One sentence describing when to use this skill. Include trigger phrases.
---
# Skill Title
Brief description and instructions for Claude to follow.Best Practices
- Keep SKILL.md under 500 lines - put detailed reference material in separate files
- Write specific descriptions - helps Claude know exactly when to activate the skill
- Use progressive disclosure - reference supporting files that get read only when needed
- Prefer scripts over inline code - script execution doesn't consume context (only output does)
Naming Conventions
- Skill directories:
kebab-case(e.g.,react-best-practices,vercel-deploy) - SKILL.md: Always uppercase, always this exact filename
- Scripts:
kebab-case.sh(e.g.,deploy.sh)
Creating/Modifying Commands
Commands are markdown files in commands/ that become slash commands prefixed with codewarden:.
---
description: Short description shown in command menu
---
Instructions for Claude when this command is invoked.Creating/Modifying Agents
Agents are markdown files in agents/ that define specialized subagents.
---
name: agent-name
description: When to use this agent
skills: skill1, skill2 # Optional: skills to inject into agent context
---
Agent instructions and capabilities.Script Requirements
For skills with scripts (like vercel-deploy):
- Use
#!/bin/bashshebang - Use
set -efor fail-fast behavior - Write status messages to stderr:
echo "Message" >&2 - Write machine-readable output (JSON) to stdout
- Include a cleanup trap for temp files
Version Management
When making changes:
- Update version in
.claude-plugin/plugin.json(semver) - Add entry to
CHANGELOG.md - Update
README.mdif adding new features
Testing Changes
# Test plugin locally
claude --plugin-dir /path/to/codewarden
# Verify skills load
"What skills are available?"Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

