claude-skills-czl

Battle-tested Claude Code configurations — opinionated CLAUDE.md baselines, skills, slash commands, and enforcement hooks you drop into any project so the AI follows your engineering standards by default.

Stop re-explaining your standards every session. Drop a config into your project's .claude/ folder and the agent already knows your rules for code style, security, testing, commits, and docs — and the hooks enforce the non-negotiable ones mechanically.

What's in here

Two ready-to-use configurations:

Both are self-contained — each is a complete .claude/ folder.

Repository layout

claude-skills-czl/
├── configs/
│   ├── agnostic/            # generic, language-agnostic config
│   │   ├── CLAUDE.md            # the short, enforced baseline
│   │   ├── settings.json        # registers the hooks + permissions
│   │   ├── commands/            # slash commands (/check, /done, /pr, …)
│   │   ├── hooks/               # PostToolUse / Stop / PreToolUse checks
│   │   ├── rules/               # optional per-stack rules (auto-applied by globs)
│   │   └── skills/              # the detailed "how" playbooks
│   └── langflow/            # same shape, specialized for Langflow
└── README.md

What a config contains

Every config is a drop-in .claude/ folder made of five parts:

• CLAUDE.md — the single source of truth: a short, actionable baseline (code style, security, tests, commits, workflow). It's the what; it defers to the skills for the how.
• skills/ — detailed, self-contained playbooks the agent reads before a matching task. Each has a SKILL.md, references/, and a learnings/ folder for project-specific knowledge that accumulates over time.
• commands/ — slash commands for the recurring workflow (start a session, run checks, review a diff, open a PR…).
• hooks/ — Python/shell scripts wired via settings.json that run automatically and block on violations.
• rules/ — optional per-stack rule files that auto-attach by file globs (e.g. only on **/*.py). Copy TEMPLATE.md to add your own.

Skills

Commands

/init · /next · /check · /test · /review · /done · /commit · /push · /pr · /roadmap · /task · /sync · /security · /help · /learn · /verify · /dual-review · /evolve · /update-agnostic · /update-langflow

Hooks (what gets enforced)

Quick start

The whole setup is: copy one config folder into your project, rename it to .claude, and git-ignore it. That's it — Claude Code reads .claude/ automatically.

1. Copy a config into your project as .claude/ (this both copies and renames):

# from the root of YOUR project — pick agnostic (any language) or langflow
cp -R /path/to/claude-skills-czl/configs/agnostic .claude

Use configs/langflow instead when working inside the Langflow codebase.

2. Git-ignore it so your project repo doesn't track it:

echo ".claude/" >> .gitignore

3. Done. Open the project in Claude Code — the CLAUDE.md baseline, skills, commands, and hooks are active. (Want the whole team to share these rules instead of keeping them local? Skip step 2 and commit .claude/.)

Keep it in sync (optional)

Prefer a symlink instead of a copy if you want updates to this repo to flow through automatically:

# from the root of YOUR project
ln -sfn /path/to/claude-skills-czl/configs/agnostic .claude
echo ".claude" >> .gitignore

Updating a copied install

If you copied the config (not symlinked), pull the latest from inside the project with a slash command:

• /update-agnostic — refresh .claude/ from configs/agnostic.
• /update-langflow — refresh .claude/ from configs/langflow.

They download the latest version, back up the current .claude/, and preserve your local additions (each skill's learnings/, settings.local.json, and any project-only rules/skills). A variant guard stops you from cross-updating — e.g. running /update-agnostic on a project that has the langflow config installed — unless you explicitly confirm the switch.

If you symlinked instead, you don't need these — just git pull in this repo.

Requirements

• Claude Code
• python3 (the enforcement hooks)
• jq (used by a couple of hooks)
• git (the doc-sync and pre-push hooks)

Customize

• Add per-stack rules: copy rules/TEMPLATE.md to rules/<stack>.md, set its globs, keep it short, and point to the skills for depth.
• Teach the agent project specifics: drop a dated note in any skill's learnings/ folder. A learning overrides the skill's defaults — the agent reads it first.
• Tune the hooks: they're small, dependency-free scripts; the thresholds live at the top of each file.

Contributing

Contributions welcome — see CONTRIBUTING.md. All content (code, comments, docs, skills) is in English. By participating you agree to the Code of Conduct.

Security

These configs are scripts and instructions that run on your machine — read settings.json and hooks/ before installing. To report a vulnerability, see SECURITY.md; don't open a public issue.

License

MIT © Cristhian Zanforlin