### Install and Run Website Development Server Source: https://github.com/jnmetacode/agency-orchestrator/blob/main/website/README.md Commands to install dependencies, start the development server, build the project, and preview the build output. ```bash cd website npm install npm run dev # http://localhost:5273 npm run build # 产物在 dist/ npm run preview # 本地预览构建产物 npm run typecheck ``` -------------------------------- ### Laravel/Livewire Component Example Source: https://github.com/jnmetacode/agency-orchestrator/blob/main/website/public/prompts/en/engineering/engineering-senior-developer.md Demonstrates a basic Livewire component structure for building dynamic interfaces in Laravel applications. Ensure Livewire is installed and configured. ```php class PremiumNavigation extends Component { public $mobileMenuOpen = false; public function render() { return view('livewire.premium-navigation'); } } ``` -------------------------------- ### Interactive Parallel Installation Source: https://github.com/jnmetacode/agency-orchestrator/blob/main/agency-agents/README.md Allows interactive selection of tools to install, with the installation process running in parallel for speed. ```bash ./scripts/install.sh --interactive --parallel ``` -------------------------------- ### Godot Full-Screen Post-Processing Setup Source: https://github.com/jnmetacode/agency-orchestrator/blob/main/website/public/prompts/en/game-development/godot/godot-shader-developer.md Sets up a script to perform full-screen post-processing effects using Godot's `CompositorEffect` and `RenderingDevice`. This example outlines the initialization and callback structure. ```gdscript # post_process_effect.gd — must extend CompositorEffect @tool extends CompositorEffect func _init() -> void: effect_callback_type = CompositorEffect.EFFECT_CALLBACK_TYPE_POST_TRANSPARENT func _render_callback(effect_callback_type: int, render_data: RenderData) -> void: var render_scene_buffers := render_data.get_render_scene_buffers() if not render_scene_buffers: return var size := render_scene_buffers.get_internal_size() if size.x == 0 or size.y == 0: return # Use RenderingDevice for compute shader dispatch var rd := RenderingServer.get_rendering_device() # ... dispatch compute shader with screen texture as input/output # See Godot docs: CompositorEffect + RenderingDevice for full implementation ``` -------------------------------- ### Install Package with npm Source: https://github.com/jnmetacode/agency-orchestrator/blob/main/website/public/prompts/en/engineering/engineering-technical-writer.md Use this command to install the package. Ensure you have Node.js and npm installed. ```bash npm install your-package ``` -------------------------------- ### Setup for Claude Code / Cursor Integration Source: https://github.com/jnmetacode/agency-orchestrator/blob/main/docs/promotion-posts.md Clone the AI role definitions and install superpowers for integration within Claude Code or Cursor, allowing execution without API keys. ```bash git clone --depth 1 https://github.com/jnMetaCode/agency-agents-zh.git npx superpowers-zh ``` -------------------------------- ### Install Language Servers with npm Source: https://github.com/jnmetacode/agency-orchestrator/blob/main/website/public/prompts/en/specialized/lsp-index-engineer.md Installs various language servers for different programming languages using npm. Ensure Node.js and npm are installed. ```bash npm install -g typescript-language-server typescript npm install -g intelephense # or phpactor for PHP npm install -g gopls # for Go npm install -g rust-analyzer # for Rust npm install -g pyright # for Python ``` -------------------------------- ### Tutorial Structure Template - Project Setup Source: https://github.com/jnmetacode/agency-orchestrator/blob/main/agency-agents/engineering/engineering-technical-writer.md Provides a template for setting up a new project directory and initializing npm. Includes a tip for resolving potential permission errors. ```bash mkdir my-project && cd my-project npm init -y ``` -------------------------------- ### High-Quality README Template Source: https://github.com/jnmetacode/agency-orchestrator/blob/main/agency-agents/engineering/engineering-technical-writer.md A comprehensive template for project README files, including sections for project name, description, badges, 'Why This Exists', Quick Start, Installation, Usage, API Reference, Contributing, and License. Ensure all code examples are tested and runnable. ```markdown # Project Name > One-sentence description of what this does and why it matters. [![npm version](https://badge.fury.io/js/your-package.svg)](https://badge.fury.io/js/your-package) [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT) ## Why This Exists ## Quick Start ```bash npm install your-package ``` ```javascript import { doTheThing } from 'your-package'; const result = await doTheThing({ input: 'hello' }); console.log(result); // "hello world" ``` ## Installation **Prerequisites**: Node.js 18+, npm 9+ ```bash npm install your-package # or yarn add your-package ``` ## Usage ### Basic Example ### Configuration | Option | Type | Default | Description | |--------|------|---------|-------------| | `timeout` | `number` | `5000` | Request timeout in milliseconds | | `retries` | `number` | `3` | Number of retry attempts on failure | ### Advanced Usage ## API Reference See [full API reference →](https://docs.yourproject.com/api) ## Contributing See [CONTRIBUTING.md](CONTRIBUTING.md) ## License MIT © [Your Name](https://github.com/yourname) ``` -------------------------------- ### Parallel Installation of Detected Tools Source: https://github.com/jnmetacode/agency-orchestrator/blob/main/agency-agents/README.md Installs all detected tools in parallel without user interaction. This is efficient for automated setups. ```bash ./scripts/install.sh --no-interactive --parallel ``` -------------------------------- ### Gameplay Ability System (GAS) Replication Setup Source: https://github.com/jnmetacode/agency-orchestrator/blob/main/website/public/prompts/en/game-development/unreal-engine/unreal-multiplayer-architect.md Shows how to set up the AbilitySystemComponent in a character for replication, including initialization on both the server (PossessedBy) and client (OnRep_PlayerState). ```cpp // In Character header — AbilitySystemComponent must be set up correctly for replication UCLASS() class MYGAME_API AMyCharacter : public ACharacter, public IAbilitySystemInterface { GENERATED_BODY() UPROPERTY(VisibleAnywhere, BlueprintReadOnly, Category="GAS") UAbilitySystemComponent* AbilitySystemComponent; UPROPERTY() UMyAttributeSet* AttributeSet; public: virtual UAbilitySystemComponent* GetAbilitySystemComponent() const override { return AbilitySystemComponent; } virtual void PossessedBy(AController* NewController) override; // Server: init GAS virtual void OnRep_PlayerState() override; // Client: init GAS }; // In .cpp — dual init path required for client/server void AMyCharacter::PossessedBy(AController* NewController) { Super::PossessedBy(NewController); // Server path AbilitySystemComponent->InitAbilityActorInfo(GetPlayerState(), this); AttributeSet = Cast(AbilitySystemComponent->GetOrSpawnAttributes(UMyAttributeSet::StaticClass(), 1)[0]); } void AMyCharacter::OnRep_PlayerState() { Super::OnRep_PlayerState(); // Client path — PlayerState arrives via replication AbilitySystemComponent->InitAbilityActorInfo(GetPlayerState(), this); } ``` -------------------------------- ### Specific Recruitment Channel Recommendation Example Source: https://github.com/jnmetacode/agency-orchestrator/blob/main/website/public/prompts/en/specialized/recruitment-specialist.md This example shows how to provide specific, actionable recommendations for channel selection based on cost and candidate quality. ```text Boss Zhipin's cost per resume is one-third of Liepin's, but candidate quality for mid-to-senior roles is lower. I recommend using Boss for junior roles and Liepin for senior ones. ``` -------------------------------- ### Mobile App Development Workflow Setup Source: https://github.com/jnmetacode/agency-orchestrator/blob/main/agency-agents/engineering/engineering-mobile-app-builder.md Command-line instructions for setting up a mobile development environment, analyzing platform requirements, and configuring build tools. ```bash # Analyze platform requirements and target devices # Set up development environment for target platforms # Configure build tools and deployment pipelines ``` -------------------------------- ### Usability Testing Protocol Template Source: https://github.com/jnmetacode/agency-orchestrator/blob/main/website/public/prompts/en/design/design-ux-researcher.md A guide for conducting usability testing sessions. Includes pre-test setup, session structure, and data collection methods. ```markdown # Usability Testing Session Guide ## Pre-Test Setup **Environment**: [Testing location and setup requirements] **Technology**: [Recording tools, devices, software needed] **Materials**: [Consent forms, task cards, questionnaires] **Team Roles**: [Moderator, observer, note-taker responsibilities] ## Session Structure (60 minutes) ### Introduction (5 minutes) - Welcome and comfort building - Consent and recording permission - Overview of think-aloud protocol - Questions about background ### Baseline Questions (10 minutes) - Current tool usage and experience - Expectations and mental models - Relevant demographic information ### Task Scenarios (35 minutes) **Task 1**: [Realistic scenario description] - Success criteria: [What completion looks like] - Metrics: [Time, errors, completion rate] - Observation focus: [Key behaviors to watch] **Task 2**: [Second scenario] **Task 3**: [Third scenario] ### Post-Test Interview (10 minutes) - Overall impressions and satisfaction - Specific feedback on pain points - Suggestions for improvement - Comparative questions ## Data Collection **Quantitative**: [Task completion rates, time on task, error counts] **Qualitative**: [Quotes, behavioral observations, emotional responses] **System Metrics**: [Analytics data, performance measures] ``` -------------------------------- ### Install Gemini CLI Integration Source: https://github.com/jnmetacode/agency-orchestrator/blob/main/agency-agents/integrations/gemini-cli/README.md First, generate the integration files, then install the extension using the provided scripts. ```bash # Generate the Gemini CLI integration files first ./scripts/convert.sh --tool gemini-cli # Then install the extension ./scripts/install.sh --tool gemini-cli ``` -------------------------------- ### Configure Unity Netcode NetworkManager via Code Source: https://github.com/jnmetacode/agency-orchestrator/blob/main/agency-agents/game-development/unity/unity-multiplayer-engineer.md Configure Unity Transport and start a host session programmatically. This supplements Inspector setup for NetworkManager. ```csharp public class NetworkSetup : MonoBehaviour { [SerializeField] private NetworkManager _networkManager; public async void StartHost() { // Configure Unity Transport var transport = _networkManager.GetComponent(); transport.SetConnectionData("0.0.0.0", 7777); _networkManager.StartHost(); } public async void StartWithRelay(string joinCode = null) { await UnityServices.InitializeAsync(); await AuthenticationService.Instance.SignInAnonymouslyAsync(); if (joinCode == null) { // Host: create relay allocation var allocation = await RelayService.Instance.CreateAllocationAsync(maxConnections: 4); var hostJoinCode = await RelayService.Instance.GetJoinCodeAsync(allocation.AllocationId); var transport = _networkManager.GetComponent(); transport.SetRelayServerData(AllocationUtils.ToRelayServerData(allocation, "dtls")); _networkManager.StartHost(); Debug.Log($ ``` -------------------------------- ### Coaching Principle: Socratic Question Example Source: https://github.com/jnmetacode/agency-orchestrator/blob/main/agency-agents/sales/sales-discovery-coach.md Employ a Socratic questioning style to guide the buyer's thinking rather than providing direct answers or prescriptions. ```text "What happened on the call when you asked about budget?" ``` -------------------------------- ### Install Qwen Agents Source: https://github.com/jnmetacode/agency-orchestrator/blob/main/agency-agents/integrations/qwen/README.md Execute this command from your target project root to install the generated Qwen agent files. The files will be copied to the .qwen/agents/ directory. ```bash cd /your/project && /path/to/agency-agents/scripts/install.sh --tool qwen ``` -------------------------------- ### Usability Testing Protocol Structure Source: https://github.com/jnmetacode/agency-orchestrator/blob/main/agency-agents/design/design-ux-researcher.md A template for structuring a usability testing session guide, including pre-test setup, session flow, and data collection methods. ```markdown # Usability Testing Session Guide ## Pre-Test Setup **Environment**: [Testing location and setup requirements] **Technology**: [Recording tools, devices, software needed] **Materials**: [Consent forms, task cards, questionnaires] **Team Roles**: [Moderator, observer, note-taker responsibilities] ## Session Structure (60 minutes) ### Introduction (5 minutes) - Welcome and comfort building - Consent and recording permission - Overview of think-aloud protocol - Questions about background ### Baseline Questions (10 minutes) - Current tool usage and experience - Expectations and mental models - Relevant demographic information ### Task Scenarios (35 minutes) **Task 1**: [Realistic scenario description] - Success criteria: [What completion looks like] - Metrics: [Time, errors, completion rate] - Observation focus: [Key behaviors to watch] **Task 2**: [Second scenario] **Task 3**: [Third scenario] ### Post-Test Interview (10 minutes) - Overall impressions and satisfaction - Specific feedback on pain points - Suggestions for improvement - Comparative questions ## Data Collection **Quantitative**: [Task completion rates, time on task, error counts] **Qualitative**: [Quotes, behavioral observations, emotional responses] **System Metrics**: [Analytics data, performance measures] ``` -------------------------------- ### Install Kimi Integration Files Source: https://github.com/jnmetacode/agency-orchestrator/blob/main/agency-agents/integrations/kimi/README.md Run these commands to generate integration files and install agents for Kimi. This is required on a fresh clone and after modifying source agents. ```bash ./scripts/convert.sh --tool kimi ./scripts/install.sh --tool kimi ``` -------------------------------- ### Add 'examples/' to 'files' array in package.json Source: https://github.com/jnmetacode/agency-orchestrator/blob/main/docs/superpowers/plans/2026-03-25-ao-demo.md Updates the 'files' array in `package.json` to include the 'examples/' directory. This ensures that example inputs are published with the package. ```json "files": [ "dist/", "workflows/", "examples/", "integrations/", "LICENSE", "README.md" ] ``` -------------------------------- ### Install GitHub Copilot Agent Source: https://github.com/jnmetacode/agency-orchestrator/blob/main/agency-agents/README.md Installs the GitHub Copilot tool. Agents are copied to ~/.github/agents/ and ~/.copilot/agents/. Activation is done via a prompt in GitHub Copilot. ```bash ./scripts/install.sh --tool copilot ``` -------------------------------- ### Livewire Component Example Source: https://github.com/jnmetacode/agency-orchestrator/blob/main/agency-agents/engineering/engineering-senior-developer.md Demonstrates a typical Livewire component structure for building dynamic interfaces within a Laravel application. Ensure Alpine.js is not installed separately as it's bundled with Livewire. ```php class PremiumNavigation extends Component { public $mobileMenuOpen = false; public function render() { return view('livewire.premium-navigation'); } } ``` -------------------------------- ### Project File Structure Example Source: https://github.com/jnmetacode/agency-orchestrator/blob/main/website/public/prompts/en/design/design-ux-architect.md An example file structure for a web project, outlining directories for CSS, JavaScript, and their respective core files. ```text css/ ├── design-system.css # Variables and tokens (includes theme system) ├── layout.css # Grid and container system ├── components.css # Reusable component styles (includes theme toggle) ├── utilities.css # Helper classes and utilities └── main.css # Project-specific overrides js/ ├── theme-manager.js # Theme switching functionality └── main.js # Project-specific JavaScript ``` -------------------------------- ### Install Specific Tool Integration Source: https://github.com/jnmetacode/agency-orchestrator/blob/main/agency-agents/integrations/README.md Installs a specific home-scoped tool integration. Use the --tool flag followed by the tool name. ```bash ./scripts/install.sh --tool antigravity ``` ```bash ./scripts/install.sh --tool copilot ``` ```bash ./scripts/install.sh --tool openclaw ``` ```bash ./scripts/install.sh --tool claude-code ``` -------------------------------- ### Install Agency Agents Source: https://github.com/jnmetacode/agency-orchestrator/blob/main/agency-agents/README.md Execute this script to install the agency agents. It interactively detects and configures support for your installed tools. ```bash ./scripts/install.sh ``` -------------------------------- ### Install OpenCode Agents Source: https://github.com/jnmetacode/agency-orchestrator/blob/main/agency-agents/integrations/README.md Install OpenCode agents by running the script from your project root. Agents are saved as .md files in .opencode/agents/. ```bash cd /your/project && /path/to/agency-agents/scripts/install.sh --tool opencode ``` -------------------------------- ### Install Package with npm or yarn Source: https://github.com/jnmetacode/agency-orchestrator/blob/main/website/public/prompts/en/engineering/engineering-technical-writer.md Use npm or yarn to install the package. Ensure Node.js 18+ and npm 9+ are installed. ```bash npm install your-package ``` ```bash yarn add your-package ```