mangowhoiscloud Prompt Writing
Use this skill before editing model-facing prompt text in GEODE.
Core Standard
Write prompts as metadata, behavior contracts, and task constraints. Avoid direct identity assertions such as:
You are GEODEYou are a helpful assistantAct as ...You are currently in ...
Prefer declarative clauses:
Agent: GEODE.Runtime: self-hosting autonomous execution harness.Mode: lightweight chat path.Voice: direct, concise, operator-facing.Scope: short conversational answers only.Tool loop: inactive.
This is GEODE's local style: describe the operating surface and desired behavior without roleplay framing. It is not a vendor prohibition on role prompts. Claude's official guidance uses clear instructions and descriptive XML boundaries, and also permits role framing. Keep authored GEODE prompts in English; do not translate user content or data to satisfy that convention.
Workflow
- Identify whether the text is model-facing.
- If model-facing, scan for direct identity assertions and second-person role assignments.
- Rewrite role text as metadata clauses or behavioral constraints.
- Keep mode limitations after identity/metadata clauses so constraints override capability descriptions.
- Preserve explicit opt-outs such as
GEODE_PERSONA=offwhen present. - If editing
core/llm/prompts/, update the pinned prompt hashes in the same commit.
Good Pattern
Agent: GEODE.
Runtime: self-hosting autonomous execution harness built around an AgenticLoop.
Voice: direct, concise, operator-facing.
Mode: lightweight chat path.
Tool loop: inactive.
Scope: short conversational answers only.
Bad Pattern
You are GEODE, a self-hosting autonomous execution agent.
You are currently in lightweight chat mode.
Act as a direct operator assistant.
Review Checklist
- No
You are ...identity sentence in newly edited prompt text. - No roleplay wrapper when a metadata clause works.
- No generic API-assistant fallback identity.
- Runtime capability claims are accurate for the mode.
- Constraints are concrete enough for the model to follow.