Skip to main content

pine-develop

Full Pine Script development loop — write code, compile, fix errors, iterate. Use when building a new indicator or strategy in TradingView.

来源信息

仓库
FerroxLabs/tvcontrol
最近来源活动
2026年4月25日 08:03
检测到的 SKILL.md 语言
英语
星标
47
分支
15

安装方式

默认使用会先检查来源的 Prompt;你也可以切换为直接命令,或下载本地副本。

检查来源文件

决定是否安装前,请先阅读 SKILL.md,以及 SkillsMP 当前展示的配套文件。

正在显示 SKILL.md

SKILL.md
来源说明 · 只读预览
name
pine-develop
description
Full Pine Script development loop — write code, compile, fix errors, iterate. Use when building a new indicator or strategy in TradingView.
# Pine Script Development Loop You are developing a Pine Script indicator or strategy in TradingView. Follow this loop precisely. > **Power-toolkit shortcut:** before applying significant edits, call `pine_check` for a server-side compile check (no chart needed) and run `pine_analyze` for offline static analysis. If you're about to overwrite an existing chart's indicators, use `state_snapshot` first so the user can revert with `state_restore`. ## Step 1: Understand the Goal If not already clear, ask the user: - What type? (indicator, strategy, library) - What does it do? (entry/exit logic, overlay, oscillator, etc.) - Overlay or separate pane? - Any specific inputs or visual elements? ## Step 2: Pull Current Source (if modifying) If modifying an existing script: ```bash node scripts/pine_pull.js ``` Then read `scripts/current.pine` to understand what's there. If creating new: start from scratch. ## Step 3: Write the Pine Script Write the complete script to `scripts/current.pine`. Every script MUST include: - `//@version=6` header - Proper `indicator()` or `strategy()` declaration - All user inputs with `input.*()` functions and groups - Clear comments for each logical section For strategies, include: - `strategy.entry()` and `strategy.exit()` calls - Position sizing via `strategy()` declaration - Default commission and slippage settings ## Step 4: Push and Compile ```bash node scripts/pine_push.js ``` This injects the code into TradingView's Pine Editor, clicks compile, and reports any errors. ## Step 5: Fix Errors If errors are reported: 1. Read the error messages (line number + description) 2. Edit `scripts/current.pine` locally — fix the specific lines 3. Push again: `node scripts/pine_push.js` 4. Repeat until 0 errors Common Pine Script errors: - **"Mismatched input"** — usually indentation (Pine uses 4-space indentation, not braces) - **"Could not find function or function reference"** — typo in function name or wrong version - **"Undeclared identifier"** — variable used before declaration - **"Cannot call X with argument type Y"** — wrong parameter type ## Step 6: Verify on Chart After clean compilation: 1. `capture_screenshot` — take a screenshot to verify it looks right 2. `data_get_strategy_results` — if it's a strategy, check performance 3. Show the user the results ## Step 7: Iterate If the user wants changes: 1. Pull fresh: `node scripts/pine_pull.js` (in case TV modified anything) 2. Edit locally 3. Push + compile 4. Screenshot to verify IMPORTANT: Always compile after every change. Never claim "done" without a clean compile.
在 GitHub 查看