Prompt guide: NeuraLayer build & analysis

Context

This lesson is a practical guide to writing prompts so NeuraLayer can do better work in build sessions and quick analysis. It complements Build sessions vs. quick analysis and Data, engine, LLM.

Not investment advice: NeuraLayer output is not personal financial, tax, or legal advice. Use it only as a learning and workflow aid and assess risk yourself — see also the disclaimer.

Learning goals

• You separate iterative build from a single focused analysis question.
• You write prompts with goal, context, constraints, and desired output shape.
• You know how to caption chart uploads so they are useful.

Build sessions: what strong prompts do

Build means you iterate over several steps on a strategy, setup, or hypothesis — not everything at once.

1. State the goal first (one sentence)
   Example: “I want a rule-based swing approach on BTC with a clear invalidation rule.”

2. Set the frame
   Name asset(s), preferred timeframe, whether you want a conservative vs. exploratory tone, and whether you want ideas only or concrete levels (never as binding recommendations).

3. Go stepwise, not “do everything”
   Instead of “analyze everything”: e.g. market structure first, then risk, then scenarios. That keeps context manageable for the model.

4. Add constraints
   e.g. “No leverage”, “spot only”, “at most two scenarios”, “please state uncertainties explicitly”.

5. Close the loop
   If an answer missed the mark, briefly say what was wrong (“Stop logic too vague”, “ignored timeframe”) and ask for one concrete revision.

Quick analysis: one clear question wins

Here you want one well-scoped question plus minimal context.

• One main question per run (e.g. “How would you frame the current range if …?”).
• Add symbol + timeframe when it matters.
• Say how you will use the answer (e.g. “sanity-check against my own thesis”) to reduce overfitting.
• Expect risk and uncertainty: good answers often say what is unknown or what data is missing — that is a feature.

Charts & screenshots

If you upload images, add a short text:

• What the chart should show (pair, timeframe).
• What to focus on (trend, levels, indicator).
• Your one-sentence hypothesis (“I read this as X — does structure support that?”).

That anchors vision-style processing without oversharing sensitive data.

Example prompts (templates)

Replace bracketed parts.

Build — kickoff:

Goal: [e.g. swing rules for ETH on 4h].
Frame: spot, no leverage. Risk posture: conservative.
First, only: market structure (higher highs/lows) in 5–7 sentences,
then questions for me before you expand scenarios.

Build — iteration:

Previous answer in short: [summary].
Please adjust only: [e.g. sharper stop logic, clearer invalidation].
Do not change: [what must stay].

Quick analysis:

Question: [one concrete question].
Context: [symbol], [timeframe], I hold [position / no position].
Please: scenario A/B, what would invalidate each, and what data are you missing?

Checklist before you send

• Is there one clear goal or one main question?
• Are symbol/timeframe included when needed?
• Are constraints clear (spot/leverage, risk, depth)?
• Am I asking for one step or the whole book? (Split the latter.)
• Do I understand the disclaimer and act accordingly?

Limits

• NeuraLayer cannot replace binding price calls or personal investment decisions.
• For policy, security, and legal topics, use the platform’s official documents — not this guide.

Links

• Build sessions vs. quick analysis
• Data, engine, LLM
• UI flow and symbols
• Limits and troubleshooting

Takeaways

• Build: goal, frame, small steps, constraints, iterate.
• Analysis: one clear question, context, accept stated uncertainty.
• Images: short caption + focus question improves usefulness a lot.