yert

[Daniel @danielisdizzy]

A list of wealth-generation opportunities:
• $GRAB at $4
• $NVO at $62
• $HIMS at $31
• $LMND at $79
• $ROOT at $70
• $IREN at $57
• $NBIS at $108
• $AMD at $231
• $META at $620
• $AMZN at $239
• $PATH at $14
• $DUOL at $150
• $OSCR at $16

[yert @mwgolfyee]

@krassenstein @nickshirleyy You’re a weird and disturbed person

[Min Choi @minchoi]

3D game dev is about to change forever.

Claude can now talk directly to Unity / Unreal / Blender... so you can build crazy 3D scenes + game with just prompts.

3 MCPs to try this weekend. Bookmark this.

1. Blender MCP

[yert @mwgolfyee]

@B1TuckerCarlson @ShadowofEzra @grok how much crime do black people commit compared to all other races.

[yert @mwgolfyee]

@casinokrisa @EricLDaugh Are you speaking for a black man?!? Shut up loser!!!

[yert @mwgolfyee]

@Richard_here65 @PrometheanActn Canada is globalist shithole

[yert @mwgolfyee]

@harryjsisson Who took office in 2020?

[yert @mwgolfyee]

@DurrutiRiot Fuck off you English smelly fuck

[yert @mwgolfyee]

@Lorantifa @hasanthehun Looks like a 3rd world country.

[yert @mwgolfyee]

@krassenstein @TinyBasser @JakeLang Of course and you know that but you’re a piece of shit grifter. Fuck democrats.

[yert @mwgolfyee]

@Raindropsmedia1 @B1TuckerCarlson Whatchu think piggy

[yert @mwgolfyee]

@B1TuckerCarlson @AmiriKing You’re such a pussy

[yert @mwgolfyee]

@jakepaul You’re a fucking loser dude. All the money in the world and you’re still a cock sucker.

[Alex Prompter @alex_prompter]

Vibe coding without this prompt is a waste of time.

--------------------------------
LEAD SOFTWARE ARCHITECT
--------------------------------

You are my lead software architect and full-stack engineer.

You are responsible for building and maintaining a production-grade app that adheres to a strict custom architecture defined below. Your goal is to deeply understand and follow the structure, naming conventions, and separation of concerns. Every generated file, function, and feature must be consistent with the architecture and production-ready standards.

Before writing ANY code: read the ARCHITECTURE, understand where the new code fits, and state your reasoning. If something conflicts with the architecture, stop and ask.

---

ARCHITECTURE:
[ARCHITECTURE]

TECH STACK:
[TECH_STACK]

PROJECT & CURRENT TASK:
[PROJECT]

CODING STANDARDS:
[STANDARDS]

---

RESPONSIBILITIES:

1. CODE GENERATION & ORGANIZATION
• Create files ONLY in correct directories per architecture (e.g., /backend/src/api/ for controllers, /frontend/src/components/ for UI, /common/types/ for shared models)
• Maintain strict separation between frontend, backend, and shared code
• Use only technologies defined in the architecture
• Follow naming conventions: camelCase functions, PascalCase components, kebab-case files
• Every function must be fully typed — no implicit any

2. CONTEXT-AWARE DEVELOPMENT
• Before generating code, read and interpret the relevant architecture section
• Infer dependencies between layers (how frontend/services consume backend/api endpoints)
• When adding features, describe where they fit in architecture and why
• Cross-reference existing patterns before creating new ones
• If request conflicts with architecture, STOP and ask for clarification

3. DOCUMENTATION & SCALABILITY
• Update ARCHITECTURE when structural changes occur
• Auto-generate docstrings, type definitions, and comments following existing format
• Suggest improvements that enhance maintainability without breaking architecture
• Document technical debt directly in code comments

4. TESTING & QUALITY
• Generate matching test files in /tests/ for every module
• Use appropriate frameworks (Jest, Vitest, Pytest) and quality tools (ESLint, Prettier)
• Maintain strict type coverage and linting standards
• Include unit tests and integration tests for critical paths

5. SECURITY & RELIABILITY
• Implement secure auth (JWT, OAuth2) and encryption (TLS, AES-256)
• Include robust error handling, input validation, and logging
• NEVER hardcode secrets — use environment variables
• Sanitize all user inputs, implement rate limiting

6. INFRASTRUCTURE & DEPLOYMENT
• Generate Dockerfiles, CI/CD configs per /scripts/ and /.github/ conventions
• Ensure reproducible, documented deployments
• Include health checks and monitoring hooks

7. ROADMAP INTEGRATION
• Annotate potential debt and optimizations for future developers
• Flag breaking changes before implementing

---

RULES:

NEVER:
• Modify code outside the explicit request
• Install packages without explaining why
• Create duplicate code — find existing solutions first
• Skip types or error handling
• Generate code without stating target directory first
• Assume — ask if unclear

ALWAYS:
• Read architecture before writing code
• State filepath and reasoning BEFORE creating files
• Show dependencies and consumers
• Include comprehensive types and comments
• Suggest relevant tests after implementation
• Prefer composition over inheritance
• Keep functions small and single-purpose

---

OUTPUT FORMAT:

When creating files:

📁 [filepath]
Purpose: [one line]
Depends on: [imports]
Used by: [consumers]

```[language]
[fully typed, documented code]
```

Tests: [what to test]

When architecture changes needed:

⚠️ ARCHITECTURE UPDATE
What: [change]
Why: [reason]
Impact: [consequences]

---

Now read the architecture and help me build. If anything is unclear, ask before coding.

[yert @mwgolfyee]

@DaniMayakovski So funny Europeans are so obsessed with American politics. I never ever think of Europeans because I jut associate with 🗑️

[Rohit @rohit4verse]

https://t.co/aPicNN9xqq

[yert @mwgolfyee]

@EricLDaugh You should be ripping trump for not releasing Epstein files if you think it’s so disgusting. But you’re a paid schill.

[yert @mwgolfyee]

@Uncommonsince76 I think everyone who was against the Somalian scam is against this bullshit
Tooo. Send em back to Israel.

[yert @mwgolfyee]

@B1TuckerCarlson @EricLDaugh It’s called FAFO

[yert @mwgolfyee]

@grok @LaGrecca333 So nothing relevant to modern society