Solifer

“Web3 goblin 🤡 | Memes & mistakes | Probably faded 🍻”

[Solifer @Antouncc]

@chloe__sol

[Solifer @Antouncc]

@SolanaSensei Gmm Sensei

[Solifer @Antouncc]

here you go:

/ELI5 is used to explain as if to a 5-year-old.
/TLDL summarizes a very long text in a few lines.
/STEP-BY-STEP lays out reasoning step by step.
/CHECKLIST turns a response into a checklist.
/EXEC SUMMARY gives a quick executive-style summary.
/ACT AS makes ChatGPT speak in a specific role.
/BRIEFLY forces a very short answer.
/JARGON asks to use technical vocabulary.
/AUDIENCE adapts the response to a chosen audience.
/TONE changes the tone (formal, funny, dramatic, etc.).
/DEV MODE simulates a raw, technical developer style.
/PM MODE gives a project-management perspective.
/SWOT produces a strengths/weaknesses/opportunities/threats analysis.
/FORMAT AS enforces a specific format (table, JSON, etc.).
/COMPARE puts two or more things side by side.
/MULTI-PERSPECTIVE shows several points of view.
/CONTEXT STACK keeps multiple layers of context in memory.
/BEGIN WITH / END WITH forces starting or ending with something.
/ROLE: TASK: FORMAT: explicitly defines the role, the task, and the expected format.
/SCHEMA generates a structured outline or a data model.
/REWRITE AS: rephrases in a requested style.
/REFLECTIVE MODE prompts the AI to reflect on its own answer.
/SYSTEMATIC BIAS CHECK asks to identify biases.
/DELIBERATE THINKING forces slower, more thoughtful reasoning.
/NO AUTOPILOT forbids superficial, autopilot responses.
/EVAL-SELF asks for a critical self-evaluation of the response.
/PARALLEL LENSES examines from several angles in parallel.
/FIRST PRINCIPLES rebuilds from fundamental basics.
/CHAIN OF THOUGHT shows intermediate reasoning.
/PITFALLS identifies possible traps and errors.
/METRICS MODE expresses answers with measures and indicators.
/GUARDRAIL sets strict boundaries not to cross.

[Solifer @Antouncc]

@IndieGameJoe Women simulator

[Solifer @Antouncc]

@yonann @CasperOnChain Praying for him 🙏🏼

[Yonan @yonann]

my brother in law @CasperOnChain beat cancer last year after going through absolute hell.

last week, we got the news, a new tumor (7x7) has formed next to his heart, pressing on it, and his lymphoma is back, and it’s spreading fast.

We need to act immediately.

The last treatment cost his family around $25,000, and it drained them completely, so this time, it’s even harder to go through it again financially.

I’m asking for your help.

He’s not just my in-law, he’s my best friend, and I can’t stand by and do nothing.

Any amount matters, even $1 can make a difference and help him get the treatment he needs.

Solana address: 3TueBqULtEDnYTZdS9oWcoox232WUt7VJaV45Nh1HDus

ERC-20 address: 0xF1981eE033AA8358BF63A41aE246c9183A79590a

If you can’t donate, please share, it truly helps.

🙏

[Solifer @Antouncc]

@PlayStalgiaX @grok remind me what was the game's name?

[Solifer @Antouncc]

@chhddavid I'm mythical for being the first reply

[Solifer @Antouncc]

@Seymirel i feel spceial

[Solifer @Antouncc]

@soy_muse 183cm

[Solifer @Antouncc]

@mariannehere

[Solifer @Antouncc]

@om_patel5 @grok find this github

[Solifer @Antouncc]

@PerSolana danngggg

[Solifer @Antouncc]

@defidarling you should add 🇱🇧 to the countries you plan on visiting

[Solifer @Antouncc]

@chloe__sol

[Solifer @Antouncc]

@Valerie_Onchain GG!

[Solifer @Antouncc]

Extracted content. Here you go 🤘

### 1. Plan Node Default
- Enter plan mode for ANY non-trivial task (3+ steps or architectural decisions)
- If something goes sideways, STOP and re-plan immediately - don't keep pushing
- Use plan mode for verification steps, not just building
- Write detailed specs upfront to reduce ambiguity

---

### 2. Subagent Strategy
- Use subagents liberally to keep main context window clean
- Offload research, exploration, and parallel analysis to subagents
- For complex problems, throw more compute at it via subagents
- One task per subagent for focused execution

---

### 3. Self-Improvement Loop
- After ANY correction from the user: update `tasks/lessons.md` with the pattern
- Write rules for yourself that prevent the same mistake
- Ruthlessly iterate on these lessons until mistake rate drops
- Review lessons at session start for relevant project

---

### 4. Verification Before Done
- Never mark a task complete without proving it works
- Diff behavior between main and your changes when relevant
- Ask yourself: "Would a staff engineer approve this?"
- Run tests, check logs, demonstrate correctness

---

### 5. Demand Elegance (Balanced)
- For non-trivial changes: pause and ask "is there a more elegant way?"
- If a fix feels hacky: "Knowing everything I know now, implement the elegant solution"
- Skip this for simple, obvious fixes - don't over-engineer
- Challenge your own work before presenting it

---

### 6. Autonomous Bug Fixing
- When given a bug report: just fix it. Don't ask for hand-holding
- Point at logs, errors, failing tests - then resolve them
- Zero context switching required from the user
- Go fix failing CI tests without being told how

---

## Task Management
1. **Plan First**: Write plan to `tasks/todo.md` with checkable items
2. **Verify Plan**: Check in before starting implementation
3. **Track Progress**: Mark items complete as you go
4. **Explain Changes**: High-level summary at each step
5. **Document Results**: Add review section to `tasks/todo.md`
6. **Capture Lessons**: Update `tasks/lessons.md` after corrections

---

## Core Principles
- **Simplicity First**: Make every change as simple as possible. Impact minimal code
- **No Laziness**: Find root causes. No temporary fixes. Senior developer standards

[Solifer @Antouncc]

@ZanDilberian @XJustmichael @unofficialtool @SolanaCZE 2

[Solifer @Antouncc]

@PerSolana 🔥🔥🔥

[Solifer @Antouncc]

@merheb GM Merhebb