3 posts tagged with "Prompt Engineering"

Those bolded words felt like a handle snapping onto a blurry intuition.

I asked a model how to make technical docs friendlier to AI.

It came back with a diagnosis that bolded these terms: Simplified Technical English, Action-Oriented Writing, Progressive Disclosure, Scannability, Call to Action.

My reaction, verbatim: I like these bolded bits. They're precise and concise, and they hand me names I didn't have. I actually learned something. So that's what the professional expression is. It said what I couldn't say.

I've been working with Agent Skills for a while now. The most frustrating discovery: it's not that AI can't write code. It's that the code it writes only works on localhost, and it keeps ignoring the rules you set.

This article covers two things:

1. Making AI-generated code actually deployable — AI writes demo-quality code, full of security holes. The root cause: AI doesn't understand production environments.
2. Fixing "AI has Skills but won't use them" — activation rates can be as low as 20%. Here's how we pushed that to 84%.

When I first started using AI image generation, I didn't pay much attention to style. Whatever Midjourney defaulted to, I used: rich lighting, flawless detail, vibrant colors. The result? Images that looked technically impressive but felt... wrong. They screamed "made by AI."

I spent months experimenting with prompts, stripping back parameters, testing different style combinations. After a lot of trial and error, I found the core principle: less is more, add texture, flatten, desaturate.

These three style recipes are the ones that worked best in practice. Just append the prompt suffix to your base prompt and you're good to go.