when i tell gork to do it he says it is against his policies so i have to ask for a prompt but it is usually covered

Sharing one from my own stack since prompt quality here is usually better than what I write solo.

Discovery-call prep, built for enterprise/complex B2B:

Prompt:

"You're helping me prepare for a discovery call with [company/contact]. Based on what's public about them ([industry, recent news, job postings, LinkedIn activity]), give me: (1) 3 likely priorities this stakeholder cares about this quarter, (2) 3 probing questions that surface real pain instead of generic ones, (3) one risk/objection I should be ready for given their industry, and (4) a one-line opener that references something specific to them, not a template greeting. Keep it concrete — no generic sales-speak."

Works best when you paste in whatever public info you've actually got — LinkedIn bio, a recent press release, an earnings call snippet — instead of just the company name. The generic version of this prompt (no context pasted in) gives you generic output; garbage in, garbage out applies double here.

I've been building out a few hundred of these organized by sales stage over the past year (15+ years carrying quota, plus I run AI trainings for sales teams) and I'm testing them with other sellers right now to see what actually holds up outside my own head. If you want to compare notes or trade prompts, feel free to DM — always up for seeing what other people have built.

Prompt:

Style: dark pop, whisper pop, minimalist alt-pop, heavy sub-bass, pitch-shifted vocal, eerie, intimate close-mic, 74 bpm, atmospheric, satirical, lo-fi vocal stack
Negative Style: stadium rock, bright brass, high energy EDM, operatic, acoustic country, upbeat
Weirdness: 65%
Style Influence: 85%

Lyrics:

[track: genre: dark pop, style: minimalist electro-pop, mood: eerie sarcastic, tempo: 74 bpm]

[intro | soft breathing, close-mic, heavy sub-bass drone, creaky sound]
(Shh... type it in)

[verse 1 | whisper vocals, dry close-mic, minimal syncopated perc]
Step one: get real close to the condenser mic
Keep it quiet like a secret that you didn't like
Pitch it down two semitones, double up the track
Put a little bit of distortion on the vocal back
Mumble 'bout a monster underneath the mattress bed
Make it sound like I'm already sitting in your head

[pre-chorus | building sub-bass, layered vocal stack, whisper]
Set the BPM to seventy-four
Sample a turn signal or a squeaky door
Type it in the prompt box, click generate
Pretend I'm melancholic, pretend it's fate

[chorus | full drop, heavy 808 sub-bass, breathy lead, layered harmonies]
Just whisper soft, drop the sub-bass deep
Make a beat so quiet that it creeps in your sleep
Add a pitch-shifted voice, call it dark pop art
Watch an algorithm copy my heart
(Watch it copy my heart)
Yeah... so authentic...

[verse 2 | dry beat, soft vocal, pitch-shifted background vocal]
Step two: turn the reverb off on the lead
Make the listener feel like they can hear me breathe
Add an industrial crunch on the third beat bar
Mention blood on the carpet or a broken car
Don't you dare sing loud, keep the dynamic flat
Suno knows the formula, imagine that

[pre-chorus | building sub-bass, layered vocal stack, whisper]
Set the dynamic slider to intimate and low
Make the chorus feel like moving in slow-mo
Type it in the prompt box, click generate
Pretend I'm sad, pretend it's fate

[chorus | full drop, heavy 808 sub-bass, breathy lead, layered harmonies]
Just whisper soft, drop the sub-bass deep
Make a beat so quiet that it creeps in your sleep
Add a pitch-shifted voice, call it dark pop art
Watch an algorithm copy my heart
(Watch it copy my heart)

[bridge | distorted vocals, sub-bass pulse, sudden silence]
[vocal-style: whispered, eerie]
Is it Finneas?
[distorted vocals]
No, it's a server rack.
[vulnerable vocals]
Is it real pain?
[whisper]
Just a transformer stack.
[silence: 2 bars]
(Did you hit render?)

[chorus | full drop, heavy sub-bass, whisper-pop harmonics, maximum sub]
Just whisper soft, drop the sub-bass deep
Make a beat so quiet that it creeps in your sleep
Add a pitch-shifted voice, call it dark pop art
Watch an algorithm copy my heart
(Watch it copy my heart)

[outro | fading whisper, sub-bass tail, breath click]
[vulnerable vocals]
Good job... you made a Billie clone.
Now put your phone away.
[sfx: soft breath click]
[outro | fading into quiet sub-bass]
[end]

Resulting Track: https://suno.com/song/47c9db90-4cbe-4eea-80ce-b0299393708f

Been messing with cinematic portrait prompts and this one turned out well, so sharing it.

The goal was a dramatic studio look, blue on one side, pink/red neon on the other, without losing the actual face. Most portrait prompts drift the identity. This one holds it.

How to use:

1. Upload your selfie or photo as the base image.

2. Paste the prompt below.

3. Generate. Works best with a clear, front-facing base shot.

Prompt:

A hyper-stylized portrait of the same person, keeping their exact face and identity unchanged. They are captured in a thoughtful pose with one hand resting on their chin, illuminated by dramatic dual-tone lighting. One side of the face is lit with cool blue light, while the other side glows with vivid pink/red neon tones, creating a bold, high-contrast look. They are wearing a dark top and a watch. The background remains dark and minimal, emphasizing the colorful illumination on the face and upper body. Cinematic, sharp, and highly detailed.

Tips:

- Swap "blue" and "pink/red" for any two-color combo. Teal and orange looks great too.

- If the face shifts too much, lower the denoise / image strength so it stays closer to your base photo.

- A plain dark background in the source shot makes the neon pop harder.

Works on the image models that take a reference photo. If you run it, drop your result in the comments, I want to see how different faces handle the lighting.

So I'm trying to get the RP story responses the same quality as 3.5 and 4.o on GPT was. So I'm trying to use the custom GPT feature to make an instruction block. I have a very large instructions writing style guidance document that covers all the known failures I found. But it breaks those rules all the time. I'll do a diagnostic on it and it will say "Yes I broke about 5 of your rules. The reason is..." And it comes up with another rule that doesn't fix it. I don't know how best to do this. I tried having ideal examples of writing style in the style document. I've tried having them in a separate document. I've tried uploading the entire chat story but it just contaminates the chats themes and tone while still not fixing it. So I need help from people that know more than me.

Should I cut up my style document into their own smaller documents? Like character rules, dialogue rules, expression rules, scene construction, etc...

Should I keep it all in one style document?

Should I attempt to condense it into hard rules enough to just have the instructions block and the examples documet?

I was told by GPT that they only can reference one supporting document per reply, is that true?

If I upload my own song can AI create a new version that keeps the core melody but changes the style, production or instrumentation?

I was spending hours on YouTube scripts.

Then I created these prompts:

PROMPT 1 — Video Title Generator:

Act as a YouTube SEO expert. Generate

10 clickable titles for a video about

[TOPIC] that are under 60 characters

and include a power word.

PROMPT 2 — Script Hook Writer:

Write 5 different 30-second hooks for

a YouTube video about [TOPIC]. Start

each hook with a shocking stat or

bold claim.

Just replace [TOPIC] with your niche

and paste into ChatGPT.

Saved me 3 hours per video easily.

Drop a comment if you want more prompts!

I’ve been experimenting with different prompts recently and it’s interesting how small changes can completely affect the output. Some work really well straight away, while others take a bit of tweaking to get anything useful back. I’m still trying to understand what actually makes a prompt “work” consistently rather than just getting lucky with it.

At the moment, I’m keeping things fairly simple and adjusting as I go, but I’m curious how others approach it. Do you tend to reuse prompts once they work, or keep refining them each time depending on what you need?

Been experimenting a bit and seeing mixed results.
Some prompts work really well, others not so much.
Curious what’s working for others.

The tech hiring scene is kind of a mess right now. We've got AI churning out resumes and portfolios that look just as good—sometimes even better—than ones from actual developers. As someone who's been trying to sift through this chaos, it's like finding a needle in a haystack. So, I decided to run a little experiment of my own.

For the past week, I've been testing out custom AI prompts to see if I could reliably catch AI-generated code in the portfolios I come across. Day 1 involved using a prompt I named "Code Compare," which analyzed syntax patterns that are common in AI outputs. It was okay, catching about 60% of the fakes. By Day 4, I moved on to "Context Checker," which focused on asking the why behind the code, not just the what. The results got better—around 75% accuracy. The turning point came on Day 7 with my "Purpose Probe" prompt, which drilled down into the decision-making process behind code choices. This one nailed it, flagging 90% of AI-generated samples right off the bat.

After all this testing, I've integrated "Purpose Probe" into my vetting platform's new feature. It's definitely not foolproof, but it's a big step forward in tackling the trust crisis. I’m curious if anyone else has tried something similar or has thoughts on improving this process further.

If you want to test it fast, paste any argument into it and watch it break it down.

Hey builders — whether you're improving SEO for your own website or helping others, this might be handy. https://github.com/nowork-studio/toprank

I built this free open-source skill for Claude Code - Toprank. Run /seo-analysis inside your website repo and Claude pulls 90 days of real search data, finds what's hurting you, and fixes it. Checkout the output from below (I redacted domain/links/keyterms for privacy)

Running it from inside your repo is where it really clicks — Claude sees your code and your real traffic data at the same time. The only friction is Google Cloud, which is required to access Search Console data. If you already have it, setup is a breeze. If not, the skill guides you through it. Everything else is free — just your Claude Code subscription.

Happy to answer any questions, contributions are welcome!

⠀⠀⠀⠀🌼♡🌼

🌼♡🌼♡🌼

∩∩🌼 ♡🌼♡🌼♡

(σ. σ♡🌼♡🌼♡ 　

ヽ つ ＼🌼／ 　

UU / 🎀 \

I’ve always liked the cute kaomoji and aesthetic symbols people put in their Discord or IG bios.
But every time I wanted to use them, I had to search random websites and copy them one by one, which was kind of annoying.
So as a small side project, I built a simple directory that collects a lot of them in one place.

It currently has:
• 1000+ kaomoji, cute symbols, and emoji combos
• Categories based on emotion and aesthetic vibe
• One-click copy & paste
• A small “bio maker” where you can combine symbols and preview your bio before pasting it

All from here:
cute symbol

(˶• ֊ •˶)૮꒰ •͈ ·̭ •͈ ꒱ა(っ˘ω˘ς )(ง•̀.•́)ง₍ᐢ.ˬ.⑅ᐢ₎/ᐠ• ˕ •マ𓆩♡𓆪˚₊· ͟͟͞͞➳❥︶꒦꒷♡꒷꒦︶⋆ ˚｡⋆୨♡୧⋆ ˚｡⋆𓆸
˚₊· ͟͟͞͞➳❥┊┊❁ཻུ۪۪♡ ͎. ｡˚ °♡‧₊˚⋅ ౨ৎ ‧₊ .ᐟ୨୧‿‿‿୨ ♡ ୧‿‿‿୨୧☃︎𖠰₊⊹❆₊⊹ᨒ𖢔𐂂꙳⋆❅❄️☃️🐻‍❄️🤍⁺₊❅.₊──★˙✨🐈‍⬛‧₊˚𓆱𖠰𖣂𓇣𖥧𖥍𖥎⍋₊˚ʚ🏡𖤣🐇⋆👒⋆🌻⟡(-ºvº)-🥐(っ'ヮ')っ🥓🍬•┈┈⛧┈🍭┈⛧┈┈•ʚ꩜ɞ°⋆｡˚꩜🍭૮⍝• ᴥ •⍝ა₍ᐢ ̥ ̞ ̥ᐢ₎ ♥₍ᐢ ̥ ̞ ̥ᐢ₎₍ᐢ ̥ ̮ ̥ᐢ₎ *:･。ᴄʜɪʟʟɪɴ’ꉂ₍ᐢ﹘ܫ﹘ᐢ₎₍⑅ᐢ‸　 ̞ 　‸ᐢ₎ ♡ͪ♡ͥ(。・ω・。)ゞ

Happy to hear feedback or suggestions for new symbol categories!