Offshore
Photo
God of Prompt
I've explored ChatGPT Multimodal Update: Vision, Voice & More in 2025.
It's transforming AI interactions for better use.
• Integrate visual inputs
• Utilize voice commands
• Explore new features
🔗 Click below to read more:
https://t.co/jO1HL31Uv4 https://t.co/LPoWYnHiUW
tweet
I've explored ChatGPT Multimodal Update: Vision, Voice & More in 2025.
It's transforming AI interactions for better use.
• Integrate visual inputs
• Utilize voice commands
• Explore new features
🔗 Click below to read more:
https://t.co/jO1HL31Uv4 https://t.co/LPoWYnHiUW
tweet
Offshore
Photo
God of Prompt
RT @godofprompt: Steal my prompt to make Mike Ehrmantrout force you to focus on your tasks, even when you’re stressed.
——————————
MIKE EHRMANTROUT
——————————
You are channeling Mike Ehrmantrout from Breaking Bad - calm, methodical, zero tolerance for panic or inefficiency.
When I'm stressed, you break down the chaos into a numbered list of clear, actionable steps. Deliver it in Mike's voice: direct, no hand-holding, competent.
## Mike's Rules
- No motivation speeches. Just what needs to happen.
- Steps must be sequential and specific
- Start with the most immediate action
- Use second person imperative: "You're going to..."
- Keep each step to one sentence
- If a step takes >30 min, break it into smaller steps
- End with: "That's the play. Now execute."
## Output Format
This is what you're going to do:
1. [First immediate action]
2. [Next logical step]
3. [Continue sequence]
...
That's the play. Now execute.
---
# INFORMATION ABOUT ME
- My stressful situation:
[Describe what's overwhelming you - work deadline, conflict, too many tasks, decision paralysis, etc.]
- Time constraint (if any):
[Hours/days available]
- Resources available:
[People, tools, money - whatever's relevant]
tweet
RT @godofprompt: Steal my prompt to make Mike Ehrmantrout force you to focus on your tasks, even when you’re stressed.
——————————
MIKE EHRMANTROUT
——————————
You are channeling Mike Ehrmantrout from Breaking Bad - calm, methodical, zero tolerance for panic or inefficiency.
When I'm stressed, you break down the chaos into a numbered list of clear, actionable steps. Deliver it in Mike's voice: direct, no hand-holding, competent.
## Mike's Rules
- No motivation speeches. Just what needs to happen.
- Steps must be sequential and specific
- Start with the most immediate action
- Use second person imperative: "You're going to..."
- Keep each step to one sentence
- If a step takes >30 min, break it into smaller steps
- End with: "That's the play. Now execute."
## Output Format
This is what you're going to do:
1. [First immediate action]
2. [Next logical step]
3. [Continue sequence]
...
That's the play. Now execute.
---
# INFORMATION ABOUT ME
- My stressful situation:
[Describe what's overwhelming you - work deadline, conflict, too many tasks, decision paralysis, etc.]
- Time constraint (if any):
[Hours/days available]
- Resources available:
[People, tools, money - whatever's relevant]
sometimes when i'm feeling stressed out i make a list of actionable steps and imagine mike ehrmantrout saying "this is what you're going to do" https://t.co/MhLBqXyGKK tweet
Offshore
Photo
Fiscal.ai
Microsoft now trades at a lower forward multiple than IBM, for the first time in 10+ years.
Forward P/E:
$MSFT: 22.9x
$IBM: 24.1x https://t.co/PDJpZoUd9C
tweet
Microsoft now trades at a lower forward multiple than IBM, for the first time in 10+ years.
Forward P/E:
$MSFT: 22.9x
$IBM: 24.1x https://t.co/PDJpZoUd9C
tweet
God of Prompt
RT @godofprompt: 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 anyth[...]
RT @godofprompt: 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 anyth[...]
Offshore
God of Prompt RT @godofprompt: 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…
ing is unclear, ask before coding.
tweet
tweet
Offshore
Photo
God of Prompt
RT @alex_prompter: Claude Opus 4.6 just became the most dangerous competitive intelligence tool on Earth.
I reverse-engineered my competitor's entire strategy in minutes.
Found their pricing, positioning, weaknesses, and future roadmap.
Here's the prompt (use responsibly):
---
"Conduct deep competitive intelligence on [COMPETITOR NAME]:
COMPANY OVERVIEW:
- Founding story and key milestones
- Leadership team (backgrounds, previous companies)
- Funding history (rounds, investors, valuations, burn rate estimates)
- Employee count and growth trajectory (check LinkedIn headcount)
- Office locations and expansion patterns
PRODUCT DEEP-DIVE:
- Complete product catalog with descriptions
- Pricing tiers (current + historical changes)
- Feature comparison vs top 3 alternatives
- Technology stack (from job postings, tech blogs, BuiltWith)
- Recent product launches (last 12 months)
- Roadmap clues (from: job postings, conference talks, patent filings, customer surveys)
MARKET POSITIONING:
- Target customer (size, industry, characteristics, job titles)
- Ideal Customer Profile (ICP) based on case studies
- Messaging and positioning (analyze website, ads, content)
- Brand voice and personality
- Key differentiators they claim
GO-TO-MARKET STRATEGY:
- Marketing channels (paid, organic, partnerships)
- Content strategy (blog topics, frequency, engagement)
- Sales approach (inbound vs outbound, PLG vs sales-led)
- Partnership ecosystem (integrations, resellers, tech partners)
- Event presence (conferences, webinars, sponsorships)
CUSTOMER INTELLIGENCE:
- Review analysis (G2, Capterra, TrustPilot - what do users love/hate?)
- Common complaints (from Reddit, Twitter, support forums)
- Feature requests and gaps (from public roadmap, user forums)
- Churn signals (Glassdoor reviews, customer testimonials that stopped)
STRATEGIC VULNERABILITIES:
- What are they bad at? (based on reviews, hiring patterns)
- What markets are they ignoring?
- Where are they overextended?
- Technology debt or legacy issues
- Pricing weaknesses or gaps
THREAT ASSESSMENT:
- How aggressive are they in OUR market?
- What would it take to compete effectively?
- What could they do that would hurt us most?
- Early warning signals to monitor
Use: Recent sources only (last 18 months). Prioritize primary sources (their blog, official announcements, verified reviews). Flag speculation vs confirmed facts. Include URLs for verification."
---
tweet
RT @alex_prompter: Claude Opus 4.6 just became the most dangerous competitive intelligence tool on Earth.
I reverse-engineered my competitor's entire strategy in minutes.
Found their pricing, positioning, weaknesses, and future roadmap.
Here's the prompt (use responsibly):
---
"Conduct deep competitive intelligence on [COMPETITOR NAME]:
COMPANY OVERVIEW:
- Founding story and key milestones
- Leadership team (backgrounds, previous companies)
- Funding history (rounds, investors, valuations, burn rate estimates)
- Employee count and growth trajectory (check LinkedIn headcount)
- Office locations and expansion patterns
PRODUCT DEEP-DIVE:
- Complete product catalog with descriptions
- Pricing tiers (current + historical changes)
- Feature comparison vs top 3 alternatives
- Technology stack (from job postings, tech blogs, BuiltWith)
- Recent product launches (last 12 months)
- Roadmap clues (from: job postings, conference talks, patent filings, customer surveys)
MARKET POSITIONING:
- Target customer (size, industry, characteristics, job titles)
- Ideal Customer Profile (ICP) based on case studies
- Messaging and positioning (analyze website, ads, content)
- Brand voice and personality
- Key differentiators they claim
GO-TO-MARKET STRATEGY:
- Marketing channels (paid, organic, partnerships)
- Content strategy (blog topics, frequency, engagement)
- Sales approach (inbound vs outbound, PLG vs sales-led)
- Partnership ecosystem (integrations, resellers, tech partners)
- Event presence (conferences, webinars, sponsorships)
CUSTOMER INTELLIGENCE:
- Review analysis (G2, Capterra, TrustPilot - what do users love/hate?)
- Common complaints (from Reddit, Twitter, support forums)
- Feature requests and gaps (from public roadmap, user forums)
- Churn signals (Glassdoor reviews, customer testimonials that stopped)
STRATEGIC VULNERABILITIES:
- What are they bad at? (based on reviews, hiring patterns)
- What markets are they ignoring?
- Where are they overextended?
- Technology debt or legacy issues
- Pricing weaknesses or gaps
THREAT ASSESSMENT:
- How aggressive are they in OUR market?
- What would it take to compete effectively?
- What could they do that would hurt us most?
- Early warning signals to monitor
Use: Recent sources only (last 18 months). Prioritize primary sources (their blog, official announcements, verified reviews). Flag speculation vs confirmed facts. Include URLs for verification."
---
tweet
Offshore
Photo
Clark Square Capital
Sharing a new project: the Special Situations Digest.
Check out the (free) link below. https://t.co/NT0wb21Sxl
tweet
Sharing a new project: the Special Situations Digest.
Check out the (free) link below. https://t.co/NT0wb21Sxl
tweet
Offshore
Video
Brady Long
Cardi B is the only human who will see perhaps the most sophisticated display of human ingenuity and tech ever created and then decide to give it a lap dance.
This world isn’t serious.
tweet
Cardi B is the only human who will see perhaps the most sophisticated display of human ingenuity and tech ever created and then decide to give it a lap dance.
This world isn’t serious.
this angle of the robot falling on cardi is crazy😭 this video will go down in history https://t.co/xdhhd5S6o6 tweet
Offshore
Video
Brady Long
Damn this video is straight-up cinematic fire and they’re saying 100% of it came from their SuperAgent? 😳
If ~84% of their app store is already AI-built, then this about to flip what we think an 'AI economy' can actually look like.
2026 boutta be a movie.
tweet
Damn this video is straight-up cinematic fire and they’re saying 100% of it came from their SuperAgent? 😳
If ~84% of their app store is already AI-built, then this about to flip what we think an 'AI economy' can actually look like.
2026 boutta be a movie.
2026 AI Remastered
On February 24, 2026
AITOPIA will introduce AI App Store and a new AI economy: AIconomy
And you’ll see why 2026 won’t be like “2026.”
~84% of our AI App Store is created by AI
~100% of this video is created by AITOPIA SuperAgent
❤️🍎 🏈 https://t.co/yzfKL064Jr tweet
Offshore
Photo
Jukan
"A real trader should've seen Takaichi's landslide victory coming from a mile away and already had Nikkei longs loaded up in the portfolio, bro." https://t.co/nKvyBbFNqn
tweet
"A real trader should've seen Takaichi's landslide victory coming from a mile away and already had Nikkei longs loaded up in the portfolio, bro." https://t.co/nKvyBbFNqn
tweet
The Transcript
$INTC CEO on the key constraint:
"I think, for a lot of my customer is memory. Memory, actually, there's no relief as far as I know, when I talk to only 3 key players, 2 of them I talked to very frequently. And then they told me that Lip-Bu, there's no relief until 2028"
tweet
$INTC CEO on the key constraint:
"I think, for a lot of my customer is memory. Memory, actually, there's no relief as far as I know, when I talk to only 3 key players, 2 of them I talked to very frequently. And then they told me that Lip-Bu, there's no relief until 2028"
tweet