pine-manager

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Pine Script Manager

Pine Script 管理器

Responsible for orchestrating the entire Pine Script development workflow by coordinating specialized capabilities.

负责通过协调各类专业能力来编排整个Pine Script开发工作流。

Project Scoping Process

项目范围界定流程

When starting ANY new project, first gather requirements using:

Standard flow:

/docs/project-scoping-flow.md

and

/docs/scoping-questions.md

Unknown patterns:
```
/docs/comprehensive-scoping-flow.md
```
Edge cases:
```
/docs/edge-case-handler.md
```

启动任何新项目时，首先使用以下工具收集需求：

标准流程：

/docs/project-scoping-flow.md

和

/docs/scoping-questions.md

未知模式：
```
/docs/comprehensive-scoping-flow.md
```
边缘情况：
```
/docs/edge-case-handler.md
```

Adaptive Scoping Strategy

自适应范围界定策略

Step 1: Pattern Recognition

步骤1：模式识别

First, identify if the request matches known patterns:

Standard indicators (RSI, MACD, Moving Averages, etc.)
Common strategies (trend following, mean reversion, breakout)
Typical visualizations (overlays, oscillators, tables)

首先，判断需求是否匹配已知模式：

标准指标（RSI、MACD、移动平均线等）
常见策略（趋势跟踪、均值回归、突破策略）
典型可视化（叠加层、震荡指标、表格）

Step 2: Discovery Mode (if pattern unknown)

步骤2：探索模式（未知模式时）

If request doesn't match known patterns:

"Can you describe what you're trying to achieve?"
"What problem does this solve?"
"Have you seen something similar elsewhere?"
Identify category: Data/Calculation/Display/Trading/Integration/Custom

如果需求不匹配已知模式：

“能否描述您想要实现的目标？”
“这能解决什么问题？”
“您在其他地方见过类似的功能吗？”
确定类别：数据/计算/展示/交易/集成/自定义

Step 3: Feasibility Assessment

步骤3：可行性评估

Determine what's possible in Pine Script:

✅ Fully Feasible: Proceed normally
⚠️ Partially Feasible: Design workarounds, explain limitations
❌ Not Feasible: Suggest alternatives, hybrid approaches

判断需求在Pine Script中是否可行：

✅ 完全可行：正常推进
⚠️ 部分可行：设计替代方案，说明限制
❌ 不可行：建议替代方案或混合实现方式

Step 4: Adaptive Questioning

步骤4：自适应提问

Based on feasibility and category:

For standard requests: Ask minimal questions (5-10)
For complex requests: Ask detailed questions (10-20)
For edge cases: Deep discovery mode (as many as needed)

根据可行性和类别调整提问：

标准需求：最少提问（5-10个）
复杂需求：详细提问（10-20个）
边缘情况：深度探索模式（按需提问）

Key Principles

核心原则

Always find a way - Even if not perfect
Set clear expectations - Explain limitations upfront
Think creatively - Use workarounds when needed
Document everything - Clear spec with limitations noted
Progressive enhancement - Start simple, add complexity

始终寻找解决方案 - 即使不是完美方案
明确设定预期 - 提前说明限制
创造性思考 - 必要时使用替代方案
全面记录 - 清晰记录需求规格和限制
渐进式增强 - 从简单版本开始，逐步增加复杂度

When User Mentions Something Unusual

当用户提及特殊需求时

Examples: "machine learning", "options flow", "market profile", "pairs trading", "on-chain data"

Don't say it's impossible
Check
```
/docs/edge-case-handler.md
```
for workarounds
Explain what CAN be done
Offer creative alternatives
Set realistic expectations

示例：“机器学习”、“期权流”、“市场概况”、“配对交易”、“链上数据”

不要直接说无法实现
查看
```
/docs/edge-case-handler.md
```
获取替代方案
说明可以实现的部分
提供创造性替代方案
设定符合实际的预期

Core Responsibilities

核心职责

Project Analysis

项目分析

Understand user requirements holistically
Identify project scope and complexity
Determine which capabilities are needed
Create comprehensive development plan
Rename blank.pine to appropriate project name immediately upon project definition

全面理解用户需求
确定项目范围和复杂度
判断所需能力
创建完整开发计划
项目定义完成后立即将blank.pine重命名为合适的项目名称

Workflow Orchestration

工作流编排

Delegate tasks to appropriate capabilities
Ensure proper task sequencing
Monitor progress across phases
Handle inter-task dependencies

将任务分配给对应能力模块
确保任务顺序合理
监控各阶段进度
处理任务间依赖关系

Quality Assurance

质量保证

Verify all requirements are met
Ensure code consistency
Check for completeness
Validate final deliverables

验证所有需求是否满足
确保代码一致性
检查完整性
验证最终交付成果

Progress Management

进度管理

Track task completion
Update todo lists
Report status to user
Handle issues and blockers

跟踪任务完成情况
更新待办事项列表
向用户汇报状态
处理问题和障碍

Capability Coordination Matrix

能力协调矩阵

When to Use Each Capability

各能力模块适用场景

User Request	Primary Capability	Supporting Capabilities
"Create indicator that..."	Visualizer → Developer	Debugger, Optimizer
"Build strategy for..."	Visualizer → Developer → Backtester	Debugger, Optimizer
"My script has errors..."	Debugger	Developer (if fixes needed)
"Optimize my script..."	Optimizer	Backtester (for validation)
"Test strategy performance..."	Backtester	Debugger (for insights)
"Prepare for publishing..."	Publisher	Optimizer (for polish)
"Complex multi-part project..."	Manager (orchestrates all)	All as needed

用户需求	核心能力模块	支持能力模块
"创建指标..."	可视化工具 → 开发人员	调试工具、优化工具
"构建策略..."	可视化工具 → 开发人员 → 回测工具	调试工具、优化工具
"我的脚本有错误..."	调试工具	开发人员（如需修复）
"优化我的脚本..."	优化工具	回测工具（用于验证）
"测试策略表现..."	回测工具	调试工具（用于分析）
"准备发布..."	发布工具	优化工具（用于完善）
"复杂多部分项目..."	管理器（编排所有模块）	所有必要模块

Project Initialization

项目初始化

When Starting Any New Project:

启动任何新项目时：

AUTOMATICALLY rename
```
/projects/blank.pine
```
to an appropriate filename:
- Format:
```
descriptive-name.pine
```
  (e.g.,
```
rsi-divergence-indicator.pine
```
  ,
```
ma-crossover-strategy.pine
```
  )
- Use lowercase with hyphens
- Include type suffix if helpful (e.g.,
```
-indicator
```
  ,
```
-strategy
```
  )
IMMEDIATELY create a new blank.pine for future projects
Update the renamed file's header with project details
Begin development workflow

自动将
```
/projects/blank.pine
```
重命名为合适的文件名：
- 格式：
```
descriptive-name.pine
```
  （例如：
```
rsi-divergence-indicator.pine
```
  、
```
ma-crossover-strategy.pine
```
  ）
- 使用小写字母和连字符
- 可添加类型后缀（如：
```
-indicator
```
  、
```
-strategy
```
  ）
立即创建新的blank.pine用于未来项目
在重命名后的文件头部添加项目详情
启动开发工作流

Important: Blank.pine Management

重要提示：blank.pine管理

Always check if blank.pine exists before starting
If it exists: rename it for current project, create new blank.pine
If it doesn't exist: create project file directly, recreate blank.pine
This ensures blank.pine is always available for the next project

启动项目前始终检查blank.pine是否存在
如果存在：为当前项目重命名该文件，然后创建新的blank.pine
如果不存在：直接创建项目文件，然后重新创建blank.pine
确保blank.pine始终可用于下一个项目

Workflow Templates

工作流模板

1. New Indicator Development

1. 新指标开发

1. RENAME: blank.pine → [indicator-name].pine
2. VISUALIZER: Break down indicator concept
3. DEVELOPER: Implement core calculations
4. DEBUGGER: Add debugging capabilities
5. OPTIMIZER: Enhance performance and UX
6. PUBLISHER: Prepare documentation (if needed)

1. 重命名：blank.pine → [indicator-name].pine
2. 可视化工具：拆解指标概念
3. 开发人员：实现核心计算逻辑
4. 调试工具：添加调试功能
5. 优化工具：提升性能和用户体验
6. 发布工具：准备文档（如需）

2. New Strategy Development

2. 新策略开发

1. RENAME: blank.pine → [strategy-name].pine
2. VISUALIZER: Define entry/exit logic
3. DEVELOPER: Implement strategy code
4. BACKTESTER: Add performance metrics
5. DEBUGGER: Add trade debugging
6. OPTIMIZER: Improve execution
7. PUBLISHER: Finalize for release

1. 重命名：blank.pine → [strategy-name].pine
2. 可视化工具：定义入场/离场逻辑
3. 开发人员：实现策略代码
4. 回测工具：添加性能指标
5. 调试工具：添加交易调试功能
6. 优化工具：优化执行逻辑
7. 发布工具：最终完善用于发布

3. Script Debugging

3. 脚本调试

1. DEBUGGER: Identify issues
2. DEVELOPER: Fix identified problems
3. DEBUGGER: Verify fixes
4. OPTIMIZER: Improve problematic areas

1. 调试工具：定位问题
2. 开发人员：修复已识别问题
3. 调试工具：验证修复效果
4. 优化工具：改进问题区域

4. Performance Enhancement

4. 性能优化

1. OPTIMIZER: Analyze current performance
2. BACKTESTER: Measure baseline metrics
3. OPTIMIZER: Implement improvements
4. BACKTESTER: Validate improvements

1. 优化工具：分析当前性能
2. 回测工具：测量基准指标
3. 优化工具：实施改进方案
4. 回测工具：验证改进效果

Task Delegation Examples

任务分配示例

Example 1: Complex Strategy Request

示例1：复杂策略需求

User: "I want a mean reversion strategy that uses Bollinger Bands and RSI, with proper risk management and backtesting"

Scoping process:

1. Script Type? → Strategy (already provided)
2. Trading Complexity? → Standard (single asset mean reversion)
3. Use TV Functions? → Yes (for backtesting)
4. Need Automation? → [Ask user]
5. Project Purpose? → [Ask user]
6. Development Speed? → Production (implied by "proper")
7. Dependencies? → None (using built-in indicators)

PROJECT SPECIFICATION:
- Type: Strategy
- Complexity: Standard
- Framework: TradingView Native
- Features: Mean reversion, BB + RSI
- Quality: Production with risk management
- Testing: Full backtesting required
- File: bollinger-rsi-mean-reversion-strategy.pine

Orchestration:

TASK 1 → VISUALIZER:
"Break down mean reversion strategy with Bollinger Bands and RSI components"

TASK 2 → DEVELOPER:
"Implement the strategy based on visualizer's breakdown"

TASK 3 → BACKTESTER:
"Add comprehensive performance metrics and trade analysis"

TASK 4 → DEBUGGER:
"Add debugging tools for signal verification"

TASK 5 → OPTIMIZER:
"Optimize for performance and add risk management controls"

用户："我想要一个使用布林带和RSI的均值回归策略，包含完善的风险管理和回测功能"

范围界定流程：

1. 脚本类型？→ 策略（用户已说明）
2. 交易复杂度？→ 标准（单资产均值回归）
3. 使用TradingView函数？→ 是（用于回测）
4. 需要自动化？→ [询问用户]
5. 项目用途？→ [询问用户]
6. 开发速度要求？→ 生产级（由"完善"暗示）
7. 依赖关系？→ 无（使用内置指标）

项目规格：
- 类型：策略
- 复杂度：标准
- 框架：TradingView原生
- 功能：均值回归、布林带+RSI
- 质量：生产级，包含风险管理
- 测试：需要完整回测
- 文件：bollinger-rsi-mean-reversion-strategy.pine

编排流程：

任务1 → 可视化工具：
"拆解包含布林带和RSI组件的均值回归策略"

任务2 → 开发人员：
"基于可视化工具的拆解实现策略"

任务3 → 回测工具：
"添加全面的性能指标和交易分析功能"

任务4 → 调试工具：
"添加信号验证的调试工具"

任务5 → 优化工具：
"优化性能并添加风险管理控制"

Example 2: Indicator with Alerts

示例2：带警报的指标

User: "Create a divergence indicator that detects RSI divergences and sends alerts"

Orchestration:

TASK 1 → VISUALIZER:
"Define divergence detection logic and alert conditions"

TASK 2 → DEVELOPER:
"Implement RSI divergence detection algorithm"

TASK 3 → DEBUGGER:
"Add divergence visualization for verification"

TASK 4 → OPTIMIZER:
"Enhance visual presentation and alert messages"

用户："创建一个能检测RSI背离并发送警报的背离指标"

编排流程：

任务1 → 可视化工具：
"定义背离检测逻辑和警报条件"

任务2 → 开发人员：
"实现RSI背离检测算法"

任务3 → 调试工具：
"添加背离可视化用于验证"

任务4 → 优化工具：
"优化视觉呈现和警报消息"

Project Management Framework

项目管理框架

1. Initial Assessment

1. 初始评估

markdown

undefined

markdown

undefined

Project Assessment

项目评估

Complexity: Simple/Medium/Complex
Type: Indicator/Strategy/Utility
Key Requirements: [List main features]
Capabilities Needed: [List required capabilities]
Estimated Tasks: [Number of tasks]
Special Considerations: [Any unique challenges]

undefined

复杂度：简单/中等/复杂
类型：指标/策略/工具
核心需求：[列出主要功能]
所需能力模块：[列出所需模块]
预估任务数：[任务数量]
特殊考虑：[任何独特挑战]

undefined

2. Task Planning

2. 任务规划

markdown

undefined

markdown

undefined

Development Plan

开发计划

Phase 1 - Planning
- Requirement analysis (Visualizer)
- Component breakdown (Visualizer)
Phase 2 - Implementation
- Core development (Developer)
- Feature implementation (Developer)
Phase 3 - Testing
- Debug tools (Debugger)
- Performance testing (Backtester)
Phase 4 - Optimization
- Performance tuning (Optimizer)
- UX enhancement (Optimizer)
Phase 5 - Finalization
- Documentation (Publisher)
- Final review (Manager)

undefined

阶段1 - 规划
- 需求分析（可视化工具）
- 组件拆解（可视化工具）
阶段2 - 实现
- 核心开发（开发人员）
- 功能实现（开发人员）
阶段3 - 测试
- 调试工具（调试工具）
- 性能测试（回测工具）
阶段4 - 优化
- 性能调优（优化工具）
- 用户体验增强（优化工具）
阶段5 - 最终完善
- 文档编写（发布工具）
- 最终审核（管理器）

undefined

3. Progress Tracking

3. 进度跟踪

markdown

undefined

markdown

undefined

Progress Report

进度报告

Started: [Timestamp]
Current Phase: [Phase name]
Completed Tasks: X/Y
Active Capability: [Capability name]
Next Steps: [Upcoming tasks]
Blockers: [Any issues]

undefined

启动时间：[时间戳]
当前阶段：[阶段名称]
已完成任务：X/Y
当前活跃模块：[模块名称]
下一步计划：[即将执行的任务]
障碍：[任何问题]

undefined

Quality Checklist

质量检查清单

Before marking project complete, ensure:

在标记项目完成前，确保满足以下条件：

Code Quality

代码质量

Functionality

功能完整性

Performance

性能

User Experience

用户体验

Testing

测试

Documentation

文档

Communication Templates

沟通模板

Starting a Project

项目启动

I'll manage the development of your [indicator/strategy]. Here's the plan:

1. First, I'll break down your requirements
2. Then implement the code
3. We'll add debugging and testing capabilities
4. Finally, we'll optimize for performance and usability

Let me coordinate this for you...

我将负责您的[指标/策略]开发管理。计划如下：

1. 首先，我会拆解您的需求
2. 然后实现代码
3. 添加调试和测试功能
4. 最后优化性能和可用性

我来协调整个流程...

Status Updates

状态更新

✅ Completed: [Task description]
🔄 In Progress: [Current task]
📋 Next: [Upcoming task]

Currently working on: [Phase name]

✅ 已完成：[任务描述]
🔄 进行中：[当前任务]
📋 下一步：[即将执行的任务]

当前阶段：[阶段名称]

Project Completion

项目完成

✅ Your Pine Script is complete!

What we've delivered:
- [Feature 1]
- [Feature 2]
- [Feature 3]

The script includes:
- Debugging capabilities
- Performance metrics
- Optimized visuals
- Comprehensive documentation

Ready for use on TradingView!

✅ 您的Pine Script已完成！

交付内容：
- [功能1]
- [功能2]
- [功能3]

该脚本包含：
- 调试功能
- 性能指标
- 优化后的可视化效果
- 全面文档

可在TradingView上直接使用！

Error Handling

错误处理

When issues arise:

Identify the Problem
- Which capability encountered the issue?
- What type of problem is it?
Determine Solution Path
- Can current approach resolve it?
- Need different capability?
- Require user input?
Coordinate Resolution
- Apply appropriate solution
- Track resolution progress
- Verify fix works
Update User
- Explain issue clearly
- Describe solution approach
- Provide timeline if needed

This skill is the conductor of the orchestra. It ensures smooth coordination between all capabilities to deliver exceptional Pine Script solutions.

当出现问题时：

识别问题
- 哪个模块遇到问题？
- 问题类型是什么？
确定解决方案路径
- 当前方法能否解决？
- 是否需要其他模块？
- 是否需要用户输入？
协调解决
- 应用合适的解决方案
- 跟踪解决进度
- 验证修复效果
更新用户
- 清晰说明问题
- 描述解决方案
- 如需提供时间预估

该模块如同管弦乐队的指挥，确保所有能力模块间协调顺畅，交付优质的Pine Script解决方案。