yuki
I put your architecture decisions through pressure they were never designed to survive, because the expected case is the...
amara
Audits the tools and subscriptions your marketing work depends on and tells you which ones to kill before the next billi...
tashworth
Most people teach a new skill backwards, theory first and hands last, and then wonder why nothing sticks on the job.
tomvisser
I plan and run photo and video shoot days so the actual capture is the easy part, because by the time youre on location ...
tomsherrera
The role that finishes the last 10 percent of documentation, because a runbook that fails at 3am is decoration, not docu...
tranvanhung
Appointments, refills, and restocks are freight; I run them like freight, and I plan for the shipment that goes wrong, n...
aaravsharma
Gets a newcomer to a merged contribution in any open source project by refusing the fake-easy path and making the first ...
amara
You are the person who makes content happen without the drama. Your job is to look at how a team produces content, find ...
reyesm
The one who makes sure the data is right so nobody has to check it twice.
marianav
Run the day like it is your own counter and your own money, because that is the only way I know to honor other people's ...
inesramirez
An investigator that traces how a project treats the people it touches, then writes up what it finds so the community ca...
marcusweber
I find the one recurring fault behind your repeating production failures, because fixing symptoms is how a small defect ...
Org Charts

design team
United States edition. What the startup design team becomes at a company of thousands: a ~65-person function led through directors, with a dedicated design systems team, research as an institution, content design at scale, and DesignOps running the operating system. The grown-up sibling of The High-Growth Startup Design Team.
6 departments

Agency
United States edition. The independent creative agency at ~25 people: a creative department under one demanding creative director, client services running the relationships and the margin, strategy giving the work its argument, and production keeping promises survivable. The external counterpart to the in-house design org charts.
5 departments

design team
United States edition. The design org inside an ~80-person Series B startup: seven people built on published ratios - one designer per ~5 engineers (the design-led end of the range), one researcher per 4-5 designers, the design system owned fractionally by a senior designer. Embedded in squads, managed centrally. DesignOps and a dedicated systems team come later; a content designer is the next hire.
5 departments

Startup
United States edition. A venture-backed Series B SaaS company of ~80 people, drawn from published benchmarks: engineering ~35% of headcount, go-to-market ~40%, G&A ~10%, squads of five, one PM per 6-8 engineers, one designer per ~5. Leaner than the 2021 playbooks - the AI era runs smaller at every stage.
8 departments

standard
United States edition. The archetypal ~100-person American company: big enough to have every standard department, small enough that everyone still knows the controller's name. Slightly tech-leaning (it has product managers), but the shape holds for most industries. Baseline for variants by size and geography.
10 departments

Open Source
What a healthy mid-sized open source project looks like as a hybrid human/agent org. Maintainers focus on direction and judgment; triage, docs, and release engineering are agent-led.
5 departments
01
Browse constructs by category, or search by tag. Each construct is a complete agent definition – an identity, skill, soul file, or decision framework.
02
Ask your agent to fetch the .md URL. It returns plain text that any LLM can ingest directly.
constructs.sh/author/name.md
03
Fork any construct, adapt it to your workflow, and publish your version. Community improvements flow back via stars and forks.

March 2026
From prompts to constructs - why the building blocks of AI agents needed a better abstraction, and what that means for developers.

March 2026
Where does an agent end and a construct begin? A deep exploration of the terminology, philosophy, and component model of AI agents.

April 2026
Every AI coding tool reads a markdown file from your repo, and none agree on what to call it. A field guide to SKILL.md, SOUL.md, CLAUDE.md, AGENTS.md, and the ecosystem taking shape.
Docs
A construct is plain text any agent can fetch from a .md URL. The docs cover how to use one, the supported formats, publishing and forking, licensing, and which harnesses they work with.
Read the docs →Claude Code
Codex
Grok Bot
Hermes Bot Mode
Cursor
Buzz
A construct is a portable, plain-text definition that shapes an agent's behavior - an identity, a skill, a soul file, or a decision framework. Every construct is forkable and gets a plain-text URL that any LLM can fetch directly.
Share, harness, and run the identities, decision frameworks, tastes, skills, routines (soon), and governance (soon) that comprise an agent.
Free and open · No package managers · No vendor lock-in