Activity
Mon
Wed
Fri
Sun
Jun
Jul
Aug
Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
What is this?
Less
More

Owned by Peter

Memberships

Clief Notes

26.3k members โ€ข Free

7 contributions to Clief Notes
I was asked about my process: I didn't hire 3 teams. I built an architecture :)
On April 10 I was trying to clean up my Instagram.Tighten the cover graphics. Build a repeatable system. Stop redesigning the same template every week. A one-afternoon job. What actually happened was the first real test of an architecture I had been sketching for writing work โ€” and I tested it on design. I built a sandbox, gave it a governing file, separated references from working material, wrote one clean briefโ€ฆ and let it run. Fifty covers came back in minutes. Same palette. Same typography. Same visual language. None off-brand. That was the moment something shifted. Not because of the output โ€” but because of what it proved: Once an architecture is clear enough, the question is no longer โ€œwhat can I delegate?โ€It becomes โ€œwhat is now worth building?โ€ In 21 days, that small test turned into: - Three working teams (orchestrator, content, design) - Four books shipped or shippable - A new website - Two additional teams already scoped Same operator. Same hours in the day. For those who asked about mindset and process โ€” this is the real answer: 1. I stopped thinking in prompts and started thinking in systems.The model is not the asset. The structure around it is. 2. I separated thinking from doing.The orchestrator doesnโ€™t write. It reads, structures, briefs, and validates.The workers execute. They donโ€™t improvise outside their lane. 3. Everything moves through briefs.No direct โ€œdo thisโ€ requests. Every handoff is:task โ†’ context โ†’ scope โ†’ acceptance โ†’ return checklist.That alone removed most iteration cycles. 4. Context is layered, not dumped.Reference material lives separately from working material.The model doesnโ€™t have to โ€œfigure out what mattersโ€ โ€” itโ€™s already decided. 5. The human sits outside the system.Not inside prompting.Outside โ€” validating outputs and deciding what ships. The clearest proof this wasnโ€™t theory came from the hardest task Iโ€™ve ever tried to coordinate: Mapping TCM meridians, Thai Sen lines, and Anatomy Trains on the human body โ€” in one consistent visual language.
1 like โ€ข 2h
This is excellent, and helps confirm the idea that the folder system IS ITSELF THE APP
0 likes โ€ข 2h
by the way, concerning design - one thing I did with my claude cowork setup was to tell claude to go out and do deep research on graphic design standards... white space, font treatment, color palettes etc...and the coached him on how to apply to specific outputs.. then claude wrote an .md file it referenced everytime we need a graphic output. That worked quite well.
Win! Getting the go ahead to rebuild our website
Wanted to share that today my boss came to me and asked seriously "Is this really possible?" and I was able to confidently say absolutely and we can make it whatever we want. Probably gonna be some discussions about what needs to go on the website but really happy that after last week's proof of concept website we're actually gonna move forward on our branding, nice end of the week
1 like โ€ข 2h
congrats!!
0 likes โ€ข 2h
@Carl Gutierrez I'm working on it... I already have a content creation system I built inside of cowork, but realized that I was letting the actual core - the folder structure - stay hidden in the background, and that's what caused my problems. to be clear, claude did a great job doing this on my local folder, and inside the claude folder, but there were these minor errros that came up a lot, about 10% of the time. Because for me this is not a drill, I actually have clients to whom I need to ship excellent content, this was a huge stressball. So working hard to get the folder structure setup in a way that I know exactly what's going on. I'm a marketer by trade, not a dev or coder, so it's a bit of a learning curve for me, moving to cursor and managing an IDE.... Work in progress, but getting more understanding everyday.....How about you?
0 likes โ€ข 2h
I guess I'm old enough to have one thing on my side mentally, I'm well aware that the chaos and overwhelm at the beginning of a learning curve is completely normal. Might as well enjoy the ride and laugh a little when it gets a bit overwhelming.....it helps to not be impressed with overwhelm, it's all part of the journey. You'll break through it soon enough...
Trying to get Andrej Karpathy to come talk to us.
If any of you have his twitter/linked in, totally comment and tell him to respond to my email. Want him to come chat with all of us and I think he would be happy to just need him to get eyes on, as someone who gets thousands of emails a day I would not be surprised if he never sees it even if it is valuable.
Trying to get Andrej Karpathy to come talk to us.
1 like โ€ข 1d
NICE!
๐Ÿ Foundations 3.2 Check-In
You just saw how the folder structure adapts to different use cases. Vote below, then drop your customized setup in the comments. What did you name your workspaces and why?
Poll
339 members have voted
0 likes โ€ข 4d
@D A Totally true, my friend...it's the chaos that teaches us where the organization is.
0 likes โ€ข 1d
@Ernest G yeah, that's a bit confusing. I'm sure I'm not completely right about this, still thinking.... but right now the way I think about it is that it doesn't matter what you call it; at the end of the day it's just a folder on your computer that contains a "workflow," starting with claude.md which is the map (or "SOP") for that workflow. To me, it's important for each--let's call it a "workflow folder" (or workspace)-- to have a *key output* that somehow brings value to the world, whether a business service, product, or business enablement. In my situation, that is usually some kind of content output that some demographic want to read. Having been looking into Jake's ideas for a few weeks now, I keep coming back to something really important. At the end of the day, if you're a business owner, knowing your key workflows, SOPs, and goals for each SOP like QA and other things is more important than ever. This doesn't mean Claude or another AI could not figure this out. But if you *start* with a crisp and clear SOP and you use that to map the claude.md, you'll save a lot of time on AI hallucinating, context bloat, etc So I've been asking this question - what does this "workspace/workflow" folder produce that brings value to a client? How do we shepherd that workflow to the Highest quality output? Where are the HITL humans in the loop? What do they do?
1-7 of 7
Peter Sukonek
2
5points to level up
@peter-smith-2684
Korea-focused marketing specialist. Naver & Kakao. Verticals: Tourism & hospitality, destinations; and Korean market entry (marketing enablement).

Active 44m ago
Joined Apr 26, 2026
Danang, Vietnam
Powered by