Install Chinese-localized Superpowers workflows for coding agents
Use superpowers-zh to install Chinese-localized coding-agent methods, China-specific development skills, and cross-tool setup for Claude Code, Codex, Cursor, Gemini CLI, OpenClaw, and related assistants.
npx skills add agentskillexchange/skills --skill install-chinese-localized-superpowers-workflows-for-coding-agents
Use superpowers-zh when a Chinese-speaking operator wants coding agents to follow repeatable software-development methods instead of ad hoc prompting. The workflow installs the skill pack globally or into a project, targets the active coding assistant, and gives the agent structured habits for discovery, planning, TDD, code review, debugging, Chinese documentation, China-local Git and CI conventions, MCP building, and workflow execution.
What this skill actually does
Invoke it instead of using the upstream English Superpowers package when the team needs localized Chinese guidance, China-specific platform conventions, or one-command setup across multiple AI coding tools. The agent/operator actually installs and applies a documented skill pack during repository work; this is not a generic Claude Code plugin list, training course, or broad prompt collection. Its scope boundary is the installed superpowers-zh skill set and documented agent behavior, especially the Chinese localization and added China-focused skills.
Inputs and prerequisites: Node.js and npx; target coding-agent host such as Claude Code, Codex, Cursor, Gemini CLI, OpenClaw, OpenCode, Windsurf, Copilot CLI, or another supported Superpowers-compatible tool.
Setup notes: Install globally with npx superpowers-zh –global, or run npx superpowers-zh inside a project so it can detect the active coding-agent tool. Use –tool when automatic detection is not enough, then restart or reload the target assistant so the installed skills are available.
Source and verification boundary: use https://sp.aiolaola.com as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.
Framework fit: publish this as a Multi-Framework workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.