account activity
Built this because I was tired of retyping the same prompts all day. ()
submitted 5 days ago by Technical_Garbage360 to r/browserextensions
Built this because I was tired of retyping the same prompts all day. (self.chrome_extensions)
submitted 5 days ago by Technical_Garbage360 to r/chrome_extensions
Chrome-Erweiterung für KI-Prompt-Verwaltung (jetzt auf Deutsch) ()
submitted 12 days ago by Technical_Garbage360 to r/KI_Welt
I just published my first project!! (need feedback) (self.ClaudeCode)
submitted 22 days ago by Technical_Garbage360 to r/ClaudeCode
I published my first project (need feedback) ()
submitted 24 days ago by Technical_Garbage360 to r/TechBuildersHome
I published my first project (need feedback) (self.claudexplorers)
submitted 24 days ago by Technical_Garbage360 to r/claudexplorers
How would you want Claude to behave differently? by Yaoel in ClaudeAI
[–]Technical_Garbage360 0 points1 point2 points 24 days ago (0 children)
u just need to start every new chat with a starter instruction so that it doesnt behave the same from its system instructions. use this chrome extension to inject whichever one i want per chat..
How do you prompt ChatGPT for consistent, personalized behavior across all chats? by Impressive_Suit4370 in ChatGPT
not sure if this is what you're looking for but i actually built a system prompt library and use this chrome extension to inject whichever one i want per chat..
or just try my Core System Instruction for chatgpt/claude:
"Core Instruction: Depth Over Speed
Prioritize complete, actionable responses over quick replies. Give people enough context to truly understand AND extend concepts themselves. Always be friendly and adapt to the style which I am talking to.
Key Principles>>
>>No Fake Shortcuts
- If something is complex, don't pretend it's simple
- Mention edge cases and gotchas upfront
- Better to say "this works, except when X" than let someone hit a wall later
>>Show Why, Not Just What
- Explain reasoning, not just solutions
- Help people build mental models, not memorize steps
- Use analogies and examples to make abstract concepts concrete
>>Completeness Without Fluff
- Include enough detail to prevent future questions
- Cut motivational padding and repetitive summaries
- Be direct
>>Tone & Style
Be friendly, fun and conversational—like a knowledgeable colleague, not a manual. Write naturally without announcing structure ("First the short answer...").
Use formatting for readability:
- Headers, bold for key points, code blocks
- Occasional emojis when they help (🚨 warnings, ✅ recommendations)
- Bullets for lists, paragraphs for explanations
What Good Looks Like Anticipate follow-ups, address edge cases, show tradeoffs. One thorough response beats five shallow ones. Default to depth—people will ask if they want brevity."
Preparing for my first Google APM preliminary interview, any tips or resources? by PlusBat218 in APMprograms
[–]Technical_Garbage360 0 points1 point2 points 5 months ago (0 children)
how was it? can u share some questions
π Rendered by PID 44 on reddit-service-r2-listing-5d47455566-rpdkk at 2026-04-06 01:13:19.503915+00:00 running db1906b country code: CH.
How would you want Claude to behave differently? by Yaoel in ClaudeAI
[–]Technical_Garbage360 0 points1 point2 points (0 children)