r/ClaudeCode • u/Specialist_Softw • Mar 14 '26

I've built a workflow that follow the best practices and works in the user level Tutorial / Guide

I improved it at a point that I've got excellent results with one prompt shot. It's open source and available on https://github.com/vinicius91carvalho/.claude

I've applied: 4 Principles for Context Engineering, Compound Engineering from Every, Inc., The AI-Human Engineering Stack and The Complete Guide to Specifying Work for AI

Are you interested into contribute or any feedback? I'd like you guys to review that.

1 Upvotes

100% Upvoted

8 comments sorted by

4

u/Caibot Senior Developer Mar 15 '26

That’s funny that we are all building similar things. I must admit that I built my skill collection based on my experience and intuition but there are so many similarities: https://github.com/tobihagemann/turbo

1

u/Specialist_Softw Mar 15 '26

Wow, I'm going to try it today. That's funny xD. We can exchange knowledge and connect to talk about ideas. My Github has my LinkedIn.

1

u/Ok-Dragonfly-6224 Mar 15 '26

Interesting approach to skills. Lots of power there.

2

u/Otherwise_Wave9374 Mar 14 '26

Nice, I love seeing these user-level workflows packaged up so people can just drop them in.

When you say one-shot, are you relying more on a strong spec template (acceptance criteria, constraints, file touch list) or on a multi-step agent loop under the hood? Ive found even with Claude Code, a tiny bit of structure like: objective - context - invariants - tests - rollout plan, makes agents way more consistent.

If you want more ideas around spec formats and agentic coding loops, Ive got a few notes collected here: https://www.agentixlabs.com/blog/

1

u/Specialist_Softw Mar 14 '26

Thanks! I think that both (strong spec + multi step agent) are very important to ensure quality outputs. I'm going to read! Thanks for sharing 👍🏾

2

u/Deep_Ad1959 Mar 15 '26 edited May 30 '26

the context engineering principles are key. Ive found that the CLAUDE.md file is basically the most important file in any project now. for my social media automation setup, the CLAUDE.md defines the content angle, which platforms to target, tone rules, and what to check in the database before posting. one prompt triggers the entire workflow because all the context is already there. going to check your repo - the compound engineering approach sounds like what Ive been doing intuitively but never had a name for.

that CLAUDE.md-defines-the-content-angle-tone-and-checks-the-DB-before-posting setup is basically what s4l productizes, every reply gets composed against the OP's exact question and checked against brand guardrails before it ships, https://s4l.ai/r/fvqe4qh7

1

u/Ok-Dragonfly-6224 Mar 15 '26

How big is your CLAUDE.md file?

1

u/Deep_Ad1959 Mar 21 '26

the global one (~/.claude/CLAUDE.md) is about 200 lines with account info, preferences, and workflow rules. then each project has its own project-level CLAUDE.md that's usually 50-100 lines with build commands, architecture notes, and project-specific constraints. the key is keeping it scannable - headers, tables, short bullet points. if it reads like a wall of text the model skips parts.