ZCO Claude - Claude Code Configuration Manager
ZCO Claude is a Claude Code configuration management tool that helps you quickly initialize .claude configuration directories for your projects, sharing custom skills, coding standards, and automation scripts.
✨ Features
- 🔗 Project Linking - Share ClaudeSettings configurations across multiple projects via symlinks
- 🧩 Custom Skills - Provides extended skills like
zco-plan,zco-plan-new,zco-help - 📋 Development Plan Management - Structured task planning and execution system
- 📝 Coding Standards - Built-in coding standards and best practices for Go/Python
- 🔧 Auto Repair - Detect and fix broken symlink configurations
📦 Installation
Option 1: Install via pip (Recommended)
pip install zco-claude
Option 2: Local Development Install/Uninstall
git clone <repository-url>
cd <project-directory>
##; method A: Copy install to ~/.local/bin
make install
##; method B: Symlink install (recommended for development)
make link
##; Uninstall
make uninstall
🚀 Quick Start
1. Initialize a Project
# Initialize current directory
zco-claude init
# Initialize a specific project
zco-claude init /path/to/project
# Use custom template
zco-claude init /path/to/project --tpl /custom/template
After initialization, the project will have a .claude/ directory with the following symlinks:
.claude/rules/→ Coding standards.claude/hooks/→ Git hooks.claude/commands/→ Custom commands.claude/skills/→ Extended skills
2. Start Claude Code
cd /path/to/project
claude .
3. Use Extended Skills
# View all available tools
/zco-help
# Execute a development plan
/zco-plan 001
# Create a new plan
/zco-plan-new {describe your requirement in any language}
📚 Core Skills
| Skill | Command | Description |
|---|---|---|
| zco-plan | zco-plan {seq} |
Execute structured development plans |
| zco-plan-new | zco-plan-new <description> |
Create a new development plan |
| zco-docs-update | zco-docs-update |
Update CLAUDE.md Git metadata |
| zco-help | zco-help [filter] |
Display available Claude tools |
🛠️ CLI Commands
| Command | Description | Example |
|---|---|---|
init [path] [--tpl] |
Initialize project configuration | zco-claude init . |
list-linked-repos |
List all linked projects | zco-claude list-linked-repos |
fix-linked-repos [--remove-not-found] |
Fix symlinks for all projects | zco-claude fix-linked-repos |
fix [path] [--tpl] |
Fix specific project configuration | zco-claude fix /path/to/project |
📁 Project Structure
zco-claude-init/
├── ClaudeSettings/ # Master configuration templates
│ ├── skills/ # Custom skills (zco-* prefix)
│ │ ├── zco-plan/ # Execute development plans
│ │ ├── zco-plan-new/ # Create new plans
│ │ ├── zco-docs-update/ # Update document metadata
│ │ └── zco-help/ # Display help information
│ ├── rules/ # Coding standards
│ ├── hooks/ # Git hooks
│ ├── commands/ # Custom commands
│ ├── settings.json # Team-shared settings
│ └── README.md # Configuration guide
│
├── docs/plans/ # Structured development plans
│ ├── plan.template.md # Plan template
│ └── plan.{seq}.{date}.md # Specific plan documents
│
├── zco_claude_init.py # Project linking script
├── pyproject.toml # Package configuration
├── setup.py # Installation script
└── Makefile # Shortcut commands
🔧 Development Plan Management
Create a Plan
# using skill in claude code
/zco-plan-new {describe your requirement in any language}
# Or manually copy template
cp docs/plans/plan.template.md docs/plans/plan.002.$(date +%y%m%d).md
Execute a Plan
# using skill in claude code
/zco-plan 002
Plan documents use YAML front matter to define metadata, including status tracking, priority, verification criteria, etc.
🏗️ Development
Build Package
# Local build and check
make twine-pypi-local
# Upload to PyPI
make twine-pypi-upload
Create a New Skill
-
Create skill directory:
mkdir -p ClaudeSettings/skills/zco-{your-skill}
-
Create SKILL.md:
--- name: zco-your-skill description: Skill description allowed-tools: Bash, Read, Glob --- # Skill documentation...
-
Test the skill:
zco-help zco-your-skill
📄 License
🤝 Contributing
Issues and Pull Requests are welcome!
Maintainer: NicoNing (vmico@outlook.com)
Homepage: https://github.com/zco-team/zco-claude
Metadata
Release files for zco-claude 0.1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| zco_claude-0.1.4.tar.gz | 169.5 kB | Without provenance | Details for zco_claude-0.1.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| zco_claude-0.1.4-py3-none-any.whl | Python 3 | none | any | Details for zco_claude-0.1.4-py3-none-any.whl |
Total release size: 377.6 kB
Release files / zco_claude-0.1.4.tar.gz
| Download URL | zco_claude-0.1.4.tar.gz |
|---|---|
| Size | 169.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
307c58b09a750fe8127666aa5e96072859daeff22ff2256c524b54272f2de2a3
|
|
BLAKE2b-256 checksum How to use checksums |
daa57cce8b5140e33d4bce6fc2a5b222e6712a17a0372ff5f5e38b09e4a8b179
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.16
|
Release files / zco_claude-0.1.4-py3-none-any.whl
| Download URL | zco_claude-0.1.4-py3-none-any.whl |
|---|---|
| Size | 208.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0dc2ebca0518b36a8fcd000ba0d560295ac45e77eb9cbc7cfed03cfeecc831cc
|
|
BLAKE2b-256 checksum How to use checksums |
9a3361f8c916e12cb1df49b67d9c11803505f62d04046e317b04d6f19784a736
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.16
|
Security for zco-claude 0.1.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.