✨ Full Documentation: ZCF Docs

Zero-config, one-click setup for Claude Code & Codex with bilingual support, intelligent agent system and personalized AI assistant

🚀 Quick Start

• Recommended: npx @benbenwu/zcf opens the interactive menu — pick what you need.
• Common commands:

npx @benbenwu/zcf i        # Full initialization: install + workflows + API/CCR + MCP
npx @benbenwu/zcf u        # Update workflows only
npx @benbenwu/zcf --lang zh-CN  # Switch interface language (example)
npx @benbenwu/zcf i -s -T codex # Non-interactive Codex setup

• Non-interactive example (provider preset):

npx @benbenwu/zcf i -s -p 302ai -k "sk-xxx"

Claude Code Superpowers Plugin

For Claude Code, Superpowers is installed as a plugin via Claude Code's plugin marketplace, not as local commands/ or agents/ files.

npx @benbenwu/zcf i -s -T claude-code --install-superpowers true

ZCF will execute the Claude Code plugin flow for you during init.

Optional Codex Skill Pack

zcf i -T codex always installs the built-in zcf-* workflow skills. You can optionally add a general-purpose Codex skill pack with:

npx @benbenwu/zcf i -s -T codex --install-codex-skill-pack true

This Codex skill pack is separate from Claude Code Superpowers.

The optional pack contains:

• brainstorming
• plan-work
• systematic-debugging
• verification-before-completion
• playwright
• deep-research

When enabled, these skills are installed into ~/.codex/skills/ to cover ideation, planning, debugging, verification, browser automation, and deep research workflows.

• For local development validation, use the repo entrypoints instead of bare npx @benbenwu/zcf:

pnpm dev -- i -s -T codex
pnpm start -- i -s -T codex
node bin/zcf.mjs i -s -T codex

Bare npx @benbenwu/zcf resolves the published npm package, so it will not automatically use your local repository changes.

📦 Release to npm

If you want npx @benbenwu/zcf to pick up your local changes, you must publish a new npm version. Republishing the same version is not allowed.

Recommended release flow for this repository:

# 1. Create a changeset and choose version bump type
pnpm changeset

# 2. Apply the version bump
pnpm changeset version

# 3. Run validation
pnpm lint
pnpm typecheck
pnpm test:run
pnpm build

# 4. Login to npm if needed
npm login

# 5. Publish using the repo release script
pnpm release

Notes:

• package.json already sets "publishConfig": { "access": "public" }, so pnpm release / changeset publish will publish as a public package.
• If your npm account uses passkeys / WebAuthn and changeset publish still asks for a one-time password, first verify the project is using @changesets/[email protected] or newer:

pnpm exec changeset --version
pnpm list @changesets/cli

• Older Changesets releases handled OTP in-process and could not use npm's newer web-based authentication flow. If you hit that issue, upgrade Changesets and log in again with web auth:

pnpm add -D @changesets/cli@latest
npm login --auth-type=web
pnpm release

• This repository already declares @changesets/cli@^2.30.0, which is the first series that delegates OTP / web auth handling back to the package manager.
• pnpm publish --access public can still be used as a manual fallback after you run pnpm changeset version and pnpm build, but it is not the primary workflow in this repo.

More usage, options, and workflows: see documentation.

📖 Full Documentation

• https://zcf.ufomiao.com/

💬 Community

Join our Telegram group for support, discussions, and updates:

🙏 Acknowledgments

This project is inspired by and incorporates work from:

• LINUX DO - New Ideal Community
• CCR
• CCometixLine
• ccusage
• BMad Method

Thanks to these community contributors for sharing!

📄 License

MIT License

🚀 Contributors

⭐️ Star History

If this project helps you, please give me a ⭐️ Star!