wave-theory
Skill95 starsChanged 3 days agoMITView on GitHub
Elliott 波浪分析:在用户明确要求数浪时识别推动浪、调整浪、否定位和备选路径。
In this repository21 other files it gives its agents.
- AGENTS.mdAGENTS.md
- bottom-volumeSkill
- box-oscillationSkill
- bull-trendSkill
- chan-theorySkill
- dragon-headSkill
- emotion-cycleSkill
- event-drivenSkill
- expectation-repricingSkill
- growth-qualitySkill
- hot-themeSkill
- ma-crossoverSkill
- market-reviewSkill
- one-yang-three-yinSkill
- sector-rotationSkill
- shrink-pullbackSkill
- stock-analysisSkill
- stock-screenerSkill
- strategy-backtestSkill
- volume-breakoutSkill
- wisburg-researchSkill
The file
Files
波浪理论分析
核心理念
市场走势遵循"5 浪推动 + 3 浪调整"的基本模式。通过识别当前所处的浪形位置,预判后续走势方向和幅度。
执行流程
1. 采集数据
运行数据采集脚本获取 120 根日K线及技术指标:
python3 scripts/gather.py <symbol>2. 推动浪识别(1-2-3-4-5)
基本规则:
- 浪2 不能跌破浪1 的起点
- 浪3 不能是推动浪中最短的
- 浪4 不能进入浪1 的价格区间
各浪特征:
| 浪 | 特征 | 量价 |
| 1浪 | 底部启动,市场半信半疑 | 温和放量 |
| 2浪 | 回调,市场认为是反弹结束 | 缩量 |
| 3浪 | 主升浪,最长最强 | 持续放量 |
| 4浪 | 调整,形态复杂 | 量能递减 |
| 5浪 | 末升浪,分歧加大 | 量价背离 |
3. 调整浪识别(A-B-C)
- A浪:初始下跌,多数人认为回调
- B浪:反弹,形成"牛市陷阱"
- C浪:破坏性下跌,恐慌出现
调整浪形态:锯齿形(5-3-5)、平坦形(3-3-5)、三角形(3-3-3-3-3)
4. 斐波那契关系
- 浪2 回调浪1 的 38.2%-61.8%
- 浪3 = 浪1 的 1.618 倍(最常见)
- 浪4 回调浪3 的 23.6%-38.2%
- 浪5 = 浪1(等长)或 浪3 的 0.618 倍
- C浪 = A浪 或 A浪的 1.618 倍
5. 浪形定位
结合以上分析确定当前所处浪形位置,推演后续可能走势。
输出要求
- 当前波浪结构标注(从最近明确的起点开始)
- 当前所处浪形位置
- 各浪的斐波那契测量
- 后续走势推演(最可能的路径)
- 关键价位(各浪的目标位和否定位)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

