Claude Skills by JiaWeiXie

Answer one focused repository question with a read-only Pi scout. Use for a grounded second analysis pass; route diff findings to review, change design to plan, multiple perspectives to orchestrate, and edits to implement.

Configure Pi providers, credentials, models, role routing, and shared project policy in the guided local setup. Use for first setup, recovery, provider or model changes, or full reconfiguration; use swarm-pi-project when provider connections must stay unchanged.

Investigate unknown requirements or unresolved technical claims through Pi's fixed research, experiment, and convergence sequence. Use when reproducible evidence and Human Decision gates are required; route one answer to ask and evidence-ready design to plan.

Implement an explicitly authorized change, fix, or refactor in an existing repository with Pi. Use for scoped file mutation; route new projects to scaffold, project tooling to setup, and design-only work to plan. Delivery, commit, and push remain separate decisions.

Compare bounded read-only Pi perspectives on repository architecture, migration, tradeoffs, or risk. Use when independent perspectives materially improve a decision; route one question to ask, one change plan to plan, and file mutation to implement.

Plan a decision-ready implementation, migration, or architecture change with a read-only Pi planner. Use when requirements and evidence are sufficient; route unresolved research to discover, diff findings to review, and code changes to implement.

Configure Pi project routing, execution safety, scope, Host Assistance, Decision Mode, Advisor, timing, and testing defaults while preserving provider connections. Use for project-policy changes; use swarm-pi-configure for provider or authentication changes.

Review a Git working tree or branch with read-only Pi workers. Use standard for bugs, security, regressions, and missing tests; use lean for diff-bound simplification, deletion, reuse, YAGNI, or native replacements. Route one question to ask and broader risk analysis to orchestrate.

Scaffold a new project through a reviewed Pi ScaffoldSpec, isolated staging, verification, and explicit materialization. Use for empty or explicitly adopted non-Git targets; route existing repositories to implement and tooling-only changes to setup.

Set up reproducible project-local dependencies, build, test, lint, and development tooling with Pi's supervised environment engineer. Use for repository tooling changes; route product code to implement and new projects to scaffold. Global provisioning and deployment stay out of scope.