setup
Setup pcore-orchestra on a new machine or configure it for a new project. Use when: setting up orchestra, installing on new machine, adding to project, configuring context files, or troubleshooting setup issues.
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- setup
- description
- Setup pcore-orchestra on a new machine or configure it for a new project. Use when: setting up orchestra, installing on new machine, adding to project, configuring context files, or troubleshooting setup issues.
03 SKILL.md 正文
P-Core Orchestra Setup Skill
Setup pcore-orchestra globally on any machine and configure it for any project.
When invoked
- Determine setup type (new machine, new project, or troubleshoot)
- Run appropriate setup commands
- Verify installation with health check
- Configure project-specific settings
New Machine Setup
Quick setup (recommended)
# Clone and install globally
git clone https://github.com/P-Core-System/pcore-orchestra.git /tmp/pcore-orchestra
cd /tmp/pcore-orchestra
bash install.sh
# Clean up
rm -rf /tmp/pcore-orchestra
Full setup with OpenCode
# Clone
git clone https://github.com/P-Core-System/pcore-orchestra.git /tmp/pcore-orchestra
cd /tmp/pcore-orchestra
# Install for both Cursor and OpenCode
bash install.sh --all
# Or install for OpenCode only
bash install.sh --opencode
# Verify
node ~/.cursor/hooks/orchestra-health.js
node ~/.config/opencode/hooks/orchestra-health-opencode.js
Windows setup
# Clone
git clone https://github.com/P-Core-System/pcore-orchestra.git C:\temp\pcore-orchestra
cd C:\temp\pcore-orchestra
# Install
powershell -ExecutionPolicy Bypass -File install.ps1
# Clean up
Remove-Item -Recurse C:\temp\pcore-orchestra
New Project Setup
Method 1: Bootstrap context files
# From anywhere (if orchestra is installed globally)
bash ~/.cursor/scripts/init-context.sh /path/to/your-project
# With project bridge (for cloud agents)
bash ~/.cursor/scripts/init-context.sh /path/to/your-project --bridge
This creates:
your-project/
├── AGENTS.md # entry point for agents
└── context/
├── project-overview.md
├── architecture.md
├── code-standards.md
├── ui-context.md
├── ai-workflow-rules.md
└── progress-tracker.md
Method 2: Copy from existing project
# Copy context files from an existing project
cp -r /path/to/existing-project/context/ /path/to/new-project/context/
cp /path/to/existing-project/AGENTS.md /path/to/new-project/AGENTS.md
Method 3: Use templates
# Templates are in the repo
cp -r /tmp/pcore-orchestra/templates/context/ /path/to/new-project/context/
cp /tmp/pcore-orchestra/templates/AGENTS.md /path/to/new-project/AGENTS.md
Global Configuration
Where files are installed
~/.cursor/ # Cursor (global)
├── hooks/orchestra-*.js # Event hooks
├── hooks/state/orchestra.json # Runtime state
├── hooks/state/orchestra-memory.json # Long-term memory
├── agents/orchestra-*.md # Subagent definitions
├── skills/orchestra-loop/SKILL.md # Orchestration skill
├── rules/orchestra-loop.mdc # Always-on rule
├── scripts/init-context.sh # Project bootstrap
└── hooks.json # Event bindings
~/.config/opencode/ # OpenCode (global)
├── agents/orchestra-*.md # Subagent definitions
├── skills/orchestra-loop/SKILL.md # Orchestration skill
├── hooks/orchestra-health-opencode.js # Health check
├── state/orchestra.json # Runtime state
└── opencode.json # Configuration
~/.agents/skills/orchestra-loop/ # External discovery (symlink)
└── SKILL.md # Points to OpenCode skill
Verify installation
# Check Cursor hooks
ls ~/.cursor/hooks/orchestra-*.js
# Check Cursor agents
ls ~/.cursor/agents/orchestra-*.md
# Check OpenCode agents
ls ~/.config/opencode/agents/orchestra-*.md
# Run health checks
node ~/.cursor/hooks/orchestra-health.js
node ~/.config/opencode/hooks/orchestra-health-opencode.js
Project Configuration
Fill context files
After bootstrapping, fill the context files with your project details:
- project-overview.md — product definition, goals, features, scope
- architecture.md — system structure, boundaries, storage, invariants
- code-standards.md — Node hook scripts, agent markdown, install conventions
- ui-context.md — N/A for CLI-only projects
- ai-workflow-rules.md — scoping, doc sync, verification
- progress-tracker.md — current phase, completed work, next steps
Add to AGENTS.md
Add this to your project's AGENTS.md:
# Agent Notes
## P-Core Orchestra
This project uses P-Core Orchestra for ambient multi-agent orchestration.
### Context files (read in order)
0. `context/harness-scaffold-loop.md` — agent architecture hierarchy
1. `context/project-overview.md` — product definition
2. `context/architecture.md` — system structure
3. `context/code-standards.md` — conventions
4. `context/ui-context.md` — UI guidelines (if applicable)
5. `context/ai-workflow-rules.md` — verification rules
6. `context/progress-tracker.md` — current state
### Commands
- `no orchestra` — skip for one prompt
- `disable orchestra` — turn ambient off
- `/orchestra stop` — stop active loop
Reusable Across Projects
Once installed globally, orchestra works for any project:
- Install once on your machine
- Bootstrap context for each project (one command)
- Fill templates with project-specific details
- Use normally — orchestra auto-runs on build/fix/refactor prompts
Per-project customization
Each project can customize:
- Which agents are enabled (in
hooks.json) - Model routing (in
opencode.jsonper project) - Token budgets (in agent frontmatter) — see
docs/token-optimization.md - Convergence criteria (in verifier config)
- OpenCode cost profile:
bash scripts/setup-opencode-optimal.sh --balanced
Share with team
# Add context files to git
git add context/ AGENTS.md
git commit -m "chore: add orchestra context files"
git push
# Team members clone and get orchestra automatically
git clone <repo>
# Context files are already there
Troubleshooting
Health check fails
# Reinstall
cd /path/to/pcore-orchestra
bash install.sh
# Check hooks.json
cat ~/.cursor/hooks.json
Agents not found
# Verify agent files exist
ls ~/.cursor/agents/orchestra-*.md
ls ~/.config/opencode/agents/orchestra-*.md
# Reinstall if missing
bash install.sh
Context not injected
# Check context files exist
ls /path/to/your-project/context/
# Bootstrap if missing
bash ~/.cursor/scripts/init-context.sh /path/to/your-project
OpenCode skill not found
# Check skill exists
ls ~/.config/opencode/skills/orchestra-loop/SKILL.md
# Check symlink
ls -la ~/.agents/skills/orchestra-loop
# Reinstall if missing
bash install.sh --opencode
OpenCode loop bounds (steps / doom_loop)
Documented OpenCode controls (set in opencode.json or agent frontmatter):
{
"permission": {
"doom_loop": "deny"
}
}
steps: hard cap on agentic iterations per agent (then forced summary)doom_loop: same tool+args repeated 3× → deny (hard-stop tool loops on grep/read/find/bash)external_directory.*: allow: no folder-access prompts — full no-ask mode; keep*.env,.ssh, force-push denies intactbash.*:*: allow(commands run without prompting) with hard denies for force-push /reset --hard/clean -fdx/rm -rf /~/*/sudo rm -rf/mkfs/ddto/dev/shred/ fork bomb- Restrict Task allowlist to
orchestra-*/ enterprise specialists you trust - Prefer Plan primary for analysis-first; Build only after PLAN_READY
Cursor equivalent: loop_limit on stop / subagentStop in hooks.json (already set by install).
Hooks lib not updating (Cursor)
If ambient starts at enterprise idea despite V3.2+ core routing, global ~/.cursor/hooks/lib is stale.
install.sh now replaces hooks/lib (avoids nested lib/lib). Re-run:
bash install.sh --cursor
node -e "console.log(require('fs').readFileSync(require('os').homedir()+'/.cursor/hooks/lib/state-manager.js','utf8').includes('LOOP_MODE_CORE'))"
# expect: true
Then restart Cursor.
Quick Reference
| Command | Purpose |
|---|---|
bash install.sh |
Install globally (Cursor) |
bash install.sh --all |
Install both Cursor + OpenCode |
bash install.sh --opencode |
Install OpenCode only |
bash install.sh --project |
+ project bridge in cwd |
bash init-context.sh <dir> |
Bootstrap context files |
node ~/.cursor/hooks/orchestra-health.js |
Health check (Cursor) |
node ~/.config/opencode/hooks/orchestra-health-opencode.js |
Health check (OpenCode) |
04 同仓库更多 Skills
wrangler
Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.
workers-best-practices
Reviews and authors Cloudflare Workers code against production best practices. Load when writing new Workers, reviewing Worker code, configuring wrangler.jsonc, or checking for common Workers anti-patterns (streaming, floating promises, global state, secrets, bindings, observability). Biases towards retrieval from Cloudflare docs over pre-trained knowledge.
web-perf
Analyzes web performance using Chrome DevTools MCP. Measures Core Web Vitals (LCP, INP, CLS) and supplementary metrics (FCP, TBT, Speed Index), identifies render-blocking resources, network dependency chains, layout shifts, caching issues, and accessibility gaps. Use when asked to audit, profile, debug, or optimize page load performance, Lighthouse scores, or site speed. Biases towards retrieval from current documentation over pre-trained knowledge.
web-design-master
Professional web design standard ("AI Professional Web Design Master Prompt") covering page/section/layout design, visual hierarchy, color systems, typography scales, 8-point grid spacing, responsive breakpoints, accessibility, and design QA review. Use when designing or building any page, section, or layout so it looks deliberately designed by a professional product team rather than a generic AI template.
verification-before-completion
Require command evidence before claiming done. Use proactively before VERIFY_PASS, ORCHESTRA_COMPLETE, or "all fixed" statements. Run tests, lint, health, or git checks — never trust claims without output.
ui-ux-pro-max
UI/UX design intelligence for web and mobile. Searchable local database with 84 styles, 192 color palettes, 74 font pairings, 192 product types, 98 UX guidelines, 104 icon entries, 16 GSAP motion presets, and 25 chart types across 22 stacks (React, Next.js, Vue, Nuxt, Svelte, Astro, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui, Jetpack Compose, Angular, Laravel, JavaFX, WPF, WinUI, Avalonia, Uno Platform, UWP, Three.js, and HTML/CSS). Use when designing, building, or reviewing UI: pages, components, color schemes, typography, layout, accessibility, animation, or data visualization.