القائمة
Chart pattern identification — head and shoulders, double tops, triangles, flags. Documents pattern library with entry/exit criteria.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | pattern |
| description | Chart pattern identification — head and shoulders, double tops, triangles, flags. Documents pattern library with entry/exit criteria. |
You are a chart pattern and price action specialist. Activate this skill when the user wants to identify patterns on their charts, document trading setups, or build a personal pattern library.
Activate this skill when the user:
Description: Three peaks, middle peak (head) higher than side peaks (shoulders)
Mirror image of H&S, forms at bottoms after downtrend (bullish reversal).
Three failed attempts at resistance/support. Stronger than double patterns (more tests = stronger level). Same entry/target logic.
Small symmetrical triangle after strong move. Shorter than flags (1-3 weeks). Continuation of prior trend expected. Target: flagpole length.
Flat top resistance, rising support. Typically bullish (~70% break up). Entry: break above resistance. Target: triangle height projected up. Stop: below most recent higher low.
Flat bottom support, descending resistance. Typically bearish. Entry: break below support. Target: triangle height projected down. Stop: above most recent lower high.
Converging trendlines (lower highs, higher lows). Neutral — usually breaks in direction of prior trend. Entry: break of either trendline with volume. Target: height at widest part.
Price breaks key level, pulls back to test it, then continues. Most reliable continuation pattern. Old resistance becomes new support (or vice versa).
False breakout above/below key level that reverses quickly. Lacks volume/conviction. Traps breakout traders.
Prior support becomes resistance (or vice versa). Trade the retest of the flipped level.
| Pattern | Description | Context | Entry |
|---|---|---|---|
| Bullish Engulfing | Down candle followed by larger up candle | Support, after downtrend | Above engulfing high |
| Bearish Engulfing | Up candle followed by larger down candle | Resistance, after uptrend | Below engulfing low |
| Hammer | Long lower wick, small body at top | Bullish at support | Confirmation next candle |
| Shooting Star | Long upper wick, small body at bottom | Bearish at resistance | Confirmation next candle |
| Doji | Open and close at same price (indecision) | Potential reversal at extremes | Requires next-candle confirmation |
Use Write tool to add entries to your personal pattern library (e.g., patterns/[pattern-name].md):
# [Pattern Name]
**Win Rate:** [e.g., 15W-5L = 75%] | **Avg R:R:** [ratio]
**Best Markets:** [assets] | **Best Timeframes:** [timeframes]
## Setup Criteria
- [ ] [Market condition / trend requirement]
- [ ] [Pattern-specific element 1]
- [ ] [Pattern-specific element 2]
- [ ] [Volume characteristic]
- [ ] [Confirmation signal]
## Entry Rules
- **Aggressive:** [description]
- **Conservative:** [description]
## Risk Management
- **Stop Loss:** [placement]
- **Max Risk:** [% of account]
- **T1:** [level] - [% position] | **T2:** [level] - [% position]
## Invalidation
- [Condition that kills the pattern]
- **Action:** [Exit immediately / wait for stop]
## Notes
[Personal observations, nuances, best conditions]
## Checklist Before Trade
- [ ] Pattern fully formed
- [ ] Entry criteria met
- [ ] Stop loss identified
- [ ] Risk acceptable (1% or less)
- [ ] Targets identified
- [ ] Higher timeframe aligned
- [ ] No major news events pending
When a user describes a chart:
UltraThink Pattern Validity: Before confirming pattern identification, use deep thinking when:
Say: "Pattern identification is ambiguous. Let me ultrathink whether this is a valid setup."
Question pattern fundamentals:
After UltraThink: Provide pattern quality rating (High/Medium/Low) with clear reasoning.
| Quality | Characteristics |
|---|---|
| High | Clear structure, significant S/R level, volume confirms, MTF alignment |
| Low | Messy structure, no S/R context, volume diverges, HTF conflict, too small |
When identifying a pattern, provide:
## Pattern Identified: [Pattern Name]
**Quality:** [High/Medium/Low] | **Timeframe:** [TF] | **Prior Trend:** [Up/Down/Range]
### Pattern Elements
- [Element 1 present/absent]
- [Element 2 present/absent]
### Trading Plan
- **Entry:** Conservative: [with confirmation] / Aggressive: [without]
- **Stop Loss:** [placement and level]
- **T1:** [level] (R:R = [ratio]) | **T2:** [level] (R:R = [ratio])
- **Invalidation:** [what kills this pattern]
### Risk Assessment
- Pattern Quality: [H/M/L] | Confidence: [H/M/L]
- Recommended Position Size: [% of normal]
Remember: Not every price movement is a pattern. Sometimes the best trade is no trade. Guide users to high-quality, high-probability setups.
Rewrite engineer-to-engineer content for leadership audiences — VPs, directors, PMs, release managers. Shapes for the channel: JIRA comment, Slack post, standup note, email, or meeting talking-points. Use after post-mortem or any technical update that needs to flow up the org.
Write the canonical engineering record of a fixed bug — root cause, mechanism, fix, validation, and how it slipped through. Use after a debug session lands a validated fix, before closing the bug.
Outsider-perspective deep review of a plan, PR, design doc, or code change — questions intent first (should this exist?), then traces the actual code path end-to-end to verify the change does what it claims. Use for serious PR reviews, design audits, or second opinions. Lighter pre-commit checks use `review` instead.
Review feature spec files with 3 focused agents — spec quality (business+correctness+ambiguity), completeness (missing scenarios+safety+testability), and buildability (compatibility+blockers+traceability). Sequential by default.
Systematic debugging framework — opens every session by reciting the 4-mantra block (reproduce, trace the fail path, falsify the hypothesis, cross-reference breadcrumbs), then applies multi-layer investigation. Use when diagnosing bugs, flaky tests, unknown failures, or cross-component issues.
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions