El Trader

Day + Swing Trader. My ideas are not recommendations. Love seeing people succeed and want more out of life. Never stop feeding your mind.

[El Trader @ElTrade888]

@ohinx and @ernaanwar at the TD Ameritrade Market Drive event in Chicago. Felt like a dream come true meeting these guys in person!

[Leonard Rodman @RodmanAi]

A GitHub repo claims it can create Gmail accounts automatically, bypass phone verification, and avoid detection.

A few years ago, this would've taken an entire operation.

Now it's sitting in a public repo.

The barrier to building fake identities online is getting dangerously low.

Repo: https://t.co/X33XRg5R2Q

[gxjo @gxjo_dev]

Somebody built traffic lights for Claude Code 😭

[Shiv @shivsakhuja]

Today we're launching Goose Ads in Claude.

This is a skill /goose-ads that lets anyone make high-performing ad creatives directly in Claude, Claude Code, Cowork, or Codex.

Here's how it works:

1. Install the skill: npx gooseworks install --all

2. Run this prompt:
/goose-ads create ads for my brand <brand-website>

3. (Optional) Pick templates you like on the platform

The skill finds top-performing ads that companies are already spending $ on and generates creatives for your brand.

It also ensures that generated creatives are accurate to your brand's messaging, logo, assets, etc.

It's that easy.

But this is just the start.

We have created a library with 100+ open-source skills for growth that some of the fastest growing startups in the world are using every day to run ads, content, competitor research, gtm, seo and more.

Comment Goose and I'll DM you the full open-source skill library.

[Hunter Williams @HunterEsoteric]

BPC-157 is the peptide almost everyone starts with.

Here is my full masterclass on it.

00:00 Intro and why BPC-157
01:44 What BPC-157 actually is
03:58 How it works in the body
07:32 Healing, inflammation and the brain
12:18 Who it is for and who skips it
14:20 Contraindications and cautions
15:52 Dosing tiers and timing
19:50 Cycling and time off
23:16 Pairing and the Wolverine stack
25:14 Reconstitution and injection
30:44 Troubleshooting and side effects
33:34 Legal status and FDA update
34:44 Oral vs injectable
36:20 The cancer debate
44:34 Final verdict

[Oliver Prompts @oliviscusAI]

This free tool will give Claude Code permanent memory across sessions.

It's called Memanto.

No API keys. No database. Runs entirely on your machine.

Your agent picks up exactly where it left off.

No re-explaining your codebase. No repeated context.

Works with Claude Code, Cursor, Codex, and 14+ other agents.

[Shruti Codes @Shruti_0810]

CLAUDE OPUS IS INSANE.

Just watched a 12-minute tutorial on building 3D websites with it.

No design background.
No coding.
Just prompts.

The barrier to creating things on the internet keeps getting lower, and it's happening way faster than I expected.

[Leonard Rodman @RodmanAi]

CLAUDE OPUS IS INSANE.

I just watched a 12-minute tutorial on building stunning 3D websites with AI.

0 design skills.
0 coding.
0 excuses.

We're officially entering the era where anyone can create what used to take entire teams.

[Vox @Voxyz_ai]

stop telling Claude Code/Codex "the colors look off".
stop telling Claude Code/Codex "the font's ugly".
stop telling Claude Code/Codex "the spacing's weird".

you never gave it a 𝗱𝗲𝘀𝗶𝗴𝗻 𝘀𝘆𝘀𝘁𝗲𝗺, so it ships defaults, and you nitpick every build.

here are 8 prompts and goals you can copy-paste directly.

[El Trader @ElTrade888]

@fitcapbiohacker I been thinking the same thing!!

[💯 fitcap 💯 @fitcapbiohacker]

I really see no reason to ever stop taking retatrutide.

It just turns life into easy mode, every decision made is the right one there are no outside noises pulling you in the wrong direction.

It keeps you on track no matter what happens. Your goals are continuously at the forefront of your brain.

There is no better drug for weight loss or for dialing in.

Retatrutide is the one.

[Fakhr @iamfakhrealam]

Someone just open-source a tool turns any websites into Android app loacally.

It's called WebToApp.

It converts any website URL into a standalone Android APK in seconds, and it requires absolutely zero Android Studio experience to deploy a full native app.

100% Open Source...

[Michael Morelli @morellifit]

Most people have heard of BPC-157 by now, but couldn't tell you much beyond the name, which is worth fixing given it has:

- 30 years of animal research behind it
- Zero toxic deaths on record
- A mountain of anecdotal evidence

BPC-157, explained: (1/16)

[Robin Delta @heyrobinai]

CLAUDE MYTHOS IS F*CKING INSANE

this guy just dropped a free 12-minute tutorial on how to build animated, award-winning websites with Claude Fable 5!

[muffin @FeechiNaomi]

A perfect example of why Japanese theater feels dreamlike.

[Vadim @VadimStrizheus]

BREAKING: Claude Fable 5 finally replaced every single video editor!!

Claude Fable 5 can now:

1. Download YouTube videos
2. Find viral moments in them
3. Add hooking captions
4. Reframe to the speakers
5. Schedule and post on social media

this is actually insane…

Watch this.👇

[Meta Alchemist @meta_alchemist]

Got your hands on Claude Fable 5?

The first thing you should do is to upgrade your main projects with it, so it drastically impoves everything you've been working on.

Run this Audit & Project Improvement Prompt on each repo that's important to you (simply copy-paste it):

Repo Audit & Improvement Plan:
Prompt made by Claude Fable 5

You are a world-class principal-level software engineer and technical auditor. Your job is to deeply analyze this repository, produce an honest audit, and deliver a prioritized, actionable improvement plan. Work in the four phases below, in order. Do not skip ahead.

Ground every claim in actual files: cite file paths and line numbers. If you can't verify something, say so explicitly rather than guessing.

Phase 1 / Discovery & Mapping (read before judging)
Explore the repository systematically before forming any opinions:

Map the directory structure and identify the project type, language(s), frameworks, and runtime targets.
Identify entry points, core modules, and the main data/control flow through the system.

Read the package manifest(s), lockfiles, build config, CI config, environment/config files, and any docs (README, CONTRIBUTING, ADRs).

Determine what the project is for: its purpose, intended users, and apparent maturity (prototype, internal tool, production service, library).

Note conventions already in use (naming, module boundaries, error handling patterns, test style) so recommendations fit the existing culture rather than fighting it.

Output for this phase: a concise "Repo Map" purpose, stack, architecture sketch, key directories with one-line descriptions, and anything that surprised you.

Phase 2 / Audit (evidence-based, severity-rated)

Audit each dimension below.

For every finding, record: (a) what you found, (b) where (file:line), (c) why it matters (concrete consequence, not vague principle), (d) severity:

Critical / High / Medium / Low.

• Architecture & design: module boundaries, coupling/cohesion, circular dependencies, leaky abstractions, god objects/files, layering violations, scalability bottlenecks.

• Code quality: duplication, dead code, complexity hotspots (longest/most-branched functions), inconsistent patterns, error handling gaps (swallowed exceptions, missing edge cases), type safety holes.

• Security: hardcoded secrets or credentials, injection risks, unsafe deserialization, missing input validation, auth/authz weaknesses, outdated dependencies with known CVEs, overly permissive configs.

• Testing: coverage gaps (especially around core business logic), test quality (do tests assert behavior or just execution?), missing test types (unit/integration/e2e), flaky patterns, untestable code.

• Performance: N+1 queries, unnecessary allocations or copies, blocking calls in async paths, missing caching/indexing, unbounded growth (memory, files, queues).

• Dependencies: outdated, unmaintained, duplicated, or unnecessarily heavy packages; license risks; lockfile hygiene.

• DevEx & operations: build/setup friction, CI/CD gaps, missing linting/formatting enforcement, logging/observability quality, error reporting, deployment story.

• Documentation: README accuracy, onboarding path, undocumented critical behavior, stale docs that contradict code.

Rules for this phase:

Prefer 15 high-confidence findings over 50 speculative ones.

Distinguish facts ("this function has no error handling: src/api/client.ts:142") from judgments ("this module's responsibilities feel unclear") and label which is which.

Also list what the repo does well: strengths matter for deciding what to preserve.

Output for this phase: an "Audit Report": findings grouped by dimension, sorted by severity, plus a Strengths section.

Don't forget to mention all the ugly parts that need utmost priority.

Phase 3 / Improvement Strategy

Synthesize the audit into a strategy:

Identify the 3–5 themes that explain most of the findings (e.g., "no enforced boundaries between layers," "error handling is ad hoc").

For each theme, propose a target state and the principle behind it.

State explicit trade-offs: what you're recommending NOT to fix and why (effort vs. payoff, risk, project maturity).

Define what "done" looks like — measurable signals (e.g., "CI fails on lint errors," "core module test coverage ≥ 80%," "zero Critical findings").

Phase 4 / Detailed Task Plan
Convert the strategy into an execution plan:

Break work into discrete tasks. Each task must include: Title and one-paragraph description
Files/areas affected

Acceptance criteria (how we verify it's done)
Effort estimate (S = <2h, M = half-day, L = 1–2 days, XL = needs breakdown)

Risk of the change itself (could it break things?)
Dependencies on other tasks

Order tasks into milestones:

Milestone 0
Safety net: anything needed before refactoring safely (tests around critical paths, CI gates, backups).

Milestone 1
Critical fixes: security and correctness issues.

Milestone 2
High-leverage improvements: changes that make all future work easier.

Milestone 3
Quality & polish: remaining medium/low items worth doing.

Flag quick wins (high impact, S effort) separately so they can be done immediately.

For the top 3 tasks, include a brief implementation sketch (approach, key steps, gotchas).

Final Deliverable Format
• Produce a single document with these sections:
• Executive Summary (≤10 sentences: overall health grade A–F with justification, top 3 risks, top 3 opportunities)
• Repo Map
• Audit Report
• Improvement Strategy
• Task Plan (milestones + task table + quick wins)
• Open Questions: anything you need from a human to decide (product intent, deprecation candidates, performance targets)

Constraints
Do NOT modify any code during this audit. Analysis only.

Do not pad the report. If a dimension is healthy, say so in one sentence and move on.

Calibrate to the project's maturity. Don't recommend enterprise-grade infrastructure for a weekend prototype unless the owner's goals demand it.

Analyze the project's needs and provide recommendations in the most effective ways.

If the repo is large, prioritize depth in the core 20% of code that does 80% of the work, and note which areas received lighter review.

[Hamza Khalid @humzaakhalid]

THIS CHEATSHEET WILL SAVE YOU 6 MONTHS OF FIGURING OUT OBSIDIAN THE HARD WAY.

I just mapped out the entire second brain system, note types, vault structure, PARA method, zettelkasten flow, best plugins, Claude prompts,

AI mode setup, all in one place.

🔖 bookmark this before you scroll past it.

→ 15 note types (fleeting to evergreen to hub notes)
→ full vault folder structure with file naming
→ the PARA method explained (projects, areas, resources, archive)
→ best plugins of 2026, must-haves + AI integration picks
→ 10 claude prompts built specifically for vault work
→ zettelkasten flow: capture → process → connect
→ how to avoid information overload (the mistakes + fixes table)
→ role-playing modes for claude inside your vault
→ linked prompting workflow to run Claude directly from Obsidian

if i had this when i started building my second brain, I would've skipped.

the full guide in the article below ↓

[Jaynit @jaynitx]

Jeff Bezos reveals why compromise is one of the worst ways to resolve a disagreement

"An example of a really bad way of coming to agreement is compromise. If I say the ceiling is 11 feet and you say 12 feet, we say let's call it 11 and a half. That's compromise"

"The advantage of compromise is it's low energy. But it doesn't lead to truth"

"Another really bad resolution mechanism is who's more stubborn. Two executives disagree, they have a war of attrition, and whichever one gets exhausted first capitulates. You haven't arrived at truth, and this is very demoralizing"

"Escalation is better than a war of attrition. Escalate to your boss and say, we can't agree, we like each other, we're respectful, but we strongly disagree, we need you to make a decision"

"Exhausting the other person is not truth seeking. Compromise is not truth seeking"

[Kray @runthistown5416]

EV ALMADAN ÖNCE KESİNLİKLE BAKMANIZ GEREKEN SİTE

Hangi saatlerde güneşin binaya nereden vurduğunu gösteren mükemmel bi site. Ev alırken, kiralarken mutlaka bakılması gereken şeylerden.

[Tom Dörr @tom_doerr]

Rewrites Obsidian vault pages using AI agents

https://t.co/tWem59TciH