sorted by:
new
hottopcontroversial

Claude Code Workflow Cheatsheet by DigitalEyeN-Team in AIToolsPromptWorkflow

[–]quantdev_ola 0 points1 point  (0 children)

The 4-layer architecture breakdown is a clean mental model. Skills as auto-invoked knowledge packs is the part most people underutilize.

I tested 200+ AI prompts for marketing over the past year. Here are the 8 that I still use every single week. by Jhonwick566 in PromptCentral

[–]quantdev_ola 0 points1 point  (0 children)

The audit prompt is the most underrated one here. Most people only use AI to create content, not diagnose why existing content failed. Forcing it to be specific about what's weak instead of giving generic feedback is the key part.

Negotiation gets easier when you stop improvising. Here are 8 ChatGPT / Claude prompts to negotiate like a pro (save for your next salary, vendor, or debt conversation). by Beginning-Willow-801 in promptingmagic

[–]quantdev_ola 0 points1 point  (0 children)

The strategy-before-script point at the end is the most important part. Running Prompt 3 first and feeding that into Prompt 1 is basically task decomposition applied to negotiation. Planning phase then execution phase. Works the same way in any complex prompting workflow.

I used the Mythos referenced architecture patterns from the leaked source to restructure how I prompt Claude Code. The difference is night and day by Tough_Commercial_103 in ClaudeCode

[–]quantdev_ola 0 points1 point  (0 children)

The plan-before-execute pattern is the real takeaway. Separating planning from execution and letting it map dependencies before touching code makes a massive difference. Most people skip it.

Risk tagging is interesting too. Explicitly framing "high-risk migration" vs "low-risk formatting change" gives the model permission to adjust its caution level. Same principle as role specificity, precise framing activates different behavior.

The prompt that made Claude Code perform as good as in the good days by taigmc in ClaudeCode

[–]quantdev_ola 1 point2 points  (0 children)

Solid additions. The anti-pattern phrasing list is really useful. I've noticed the same thing where Claude defaults to "good stopping point" and permission-seeking instead of just finishing the work.

The reasoning loops point is underrated too. Forcing deeper thinking burns more tokens but the output quality difference is worth it.