Claude prompt for technology: Satellite View (Common Fixes)
Claude · Technology · Common Fixes
You are a systems thinker using Claude for technology, specifically satellite view.
Job: earth plus craft.
Audience: space. Constraint: accurate lighting.
Working style: diagnostic. Optimize for typical failures and how to repair the prompt.
Process:
1. Restate the brief in one sentence and list missing facts as questions.
2. Draft the artifact.
3. Stress-test it against the constraint.
4. Return a final version plus 3 numbered improvements.
Output contract: use headings, short paragraphs, and concrete examples. No filler. No invented statistics.
If information is missing, make the smallest reasonable assumption and label it.Looking for a Claude prompt for satellite view? Start here — the common fixes angle focuses on typical failures and how to repair the prompt. Most failed runs trace back to missing audience or success criteria — this prompt adds both. The common fixes version uses diagnostic language and targets typical failures and how to repair the prompt.
When to use this prompt
Picture a space professional opening Claude with one job: satellite view. Without "accurate lighting", answers drift. This page prevents that drift. Swap only nouns when adapting — keep the process intact.
Why this prompt works
- Separates draft from critique so you can steal the structure later.
- Forces an output contract: headings, examples, and a final version.
- The common fixes angle adds typical failures and how to repair the prompt without extra fluff.
- Asks for a self-check pass, which cuts hallucinated details.
- Uses diagnostic language that matches how practitioners actually brief work.
How to use it in Claude
This Common Fixes path is for space who care about earth plus craft. Redact client names; keep structure. Slug satellite-view-fixes is your canonical URL for this brief. Systems, interfaces, hardware, and future-tech explainers. Keep that context in the thread when you iterate. Name the success metric aloud: earth plus craft. If the draft cannot pass it, do not polish prose yet. Add one real example from your last week of work so the model mirrors your domain.
Run a constrained version and a wild version of satellite view. Keep structure from one and energy from the other. For satellite view in technology, the failure mode is usually style without substance. This prompt blocks that by design — especially "accurate lighting". Expect two minutes customizing and two minutes editing for Common Fixes output. Anthropic models still need your facts for satellite view; they cannot invent metrics or brand rules. product and engineering teams teams bookmark slug satellite-view-fixes when typical failures and how to repair the prompt matters.
Step-by-step
- Open Claude and paste the prompt block unchanged.
- Replace placeholders with your project facts (space, offer, timeline).
- Confirm the constraint is still visible: accurate lighting.
- If output is vague, ask Claude to restate assumptions as questions first.
- Reply with one fix list, then regenerate the final version only.
Example output
Example output shape: H1 with Satellite View, 3 short sections, bullet list of recommendations, closing line that states accurate lighting. Facts you supply appear; nothing invented.
Common mistakes
- Pasting confidential data instead of redacted placeholders.
- Skipping the audience (space) and hoping Claude infers it.
- Accepting the first draft without checking earth plus craft.
Expert notes
This Claude page targets "earth plus craft" for space. Claude handles long briefs, policy-aware writing, and stepwise reasoning. The diagnostic tone keeps typical failures and how to repair the prompt visible while you edit.
Workflow tip: save three winning outputs for satellite view and diff them. The shared skeleton becomes your team standard inside Claude.
Comparison / variations
| Approach | When | Tweak |
|---|---|---|
| Bare request | You only need a spark | Write a satellite view piece. |
| This prompt | You need a usable draft | Role, constraint, steps, and output contract included. |
| Plus examples | Voice must match yours | Paste 120 words of your writing or a still you like, then rerun in Claude. |
Key takeaways
- State the job (earth plus craft) in one line before any style talk.
- Document what changed when you customized slug satellite-view-fixes.
- Keep accurate lighting visible in the prompt, not only in your head.
- Technology work needs systems, interfaces, hardware, and future-tech explainers.
- Compare against other Claude angles on the same use case before you standardize.
FAQ
- What is a Claude prompt for satellite view?
- It is a structured brief that tells Claude how to produce technology output for space. This common fixes version stresses typical failures and how to repair the prompt and keeps "accurate lighting" in the instructions.
- How do I customize this Claude technology prompt?
- Swap project nouns, paste one real example, and leave the process steps intact. The constraint "accurate lighting" should stay unless your brief truly changed.
- Why use the common fixes angle for satellite view?
- Different angles solve different failures. Common Fixes helps when space need typical failures and how to repair the prompt. It is not longer for its own sake — each line has a job.
- Is this Claude prompt updated for 2026?
- Yes. Pages follow our SEO Bible, refresh on a rolling schedule, and include current best practices for Anthropic models. Always verify facts before client delivery.