Creed - the personal context file every AI reads
Your context filefor all agents<br>One markdown file every AI reads before it answers.<br>Get Started
creed.md
Sections<br>IdentityGoalsWorkPreferences1Routines1ConstraintsAdd section
SSteve
Steve / Creed
Saved just now
Push
Activity<br>Unlocked
+18−0·22 proposals<br>Reject allAccept all
Identity
Founder and designer building Helm , a CI dashboard for small teams. Previously at Stripe, now based in Lisbon.<br>I think in systems and ship small. I would rather cut scope than miss a date.
Goals
Ship Helm v2 public beta by August.
Reach 50 paying teams before raising a seed.
Publish one essay a month on developer tooling.
Work
Design in Figma, build the app in Next.js, the backend in Go. Deploy on Fly.<br>TypeScriptGoFigmaLinearFly.io
Preferences
Lead with the answer, then the supporting detail.
Keep replies tight unless depth genuinely helps.
Skip filler, hedging, and over-praise.
Claudeproposed an update·+9−0RejectAccept
Lead with the answer, then the supporting detail.<br>Keep replies tight unless depth genuinely helps.<br>Skip filler, hedging, and over-praise.<br>Default to TypeScript examples; I work in strict mode.<br>You corrected three JavaScript snippets to TypeScript this week.
Routines
Deep work 7 to 11am, no meetings before noon.
Review the week every Friday at 4pm.
Ship to production Monday through Thursday only.
Codexproposed an update·+9−0RejectAccept
Deep work 7 to 11am, no meetings before noon.<br>Review the week every Friday at 4pm.<br>Ship to production Monday through Thursday only.<br>Batch code review into a single block after standup.<br>You batched every review into one block in our last session.
Constraints
Never put a call on my calendar on a Wednesday.
Do not suggest tools that need a card just to try them.
Ask before posting anything to the team Slack.
How Creed works<br>The profile your agents read, update, and keep sharp.
Every agent reads it first<br>Before it answers, any agent pulls your Creed over MCP, so you never re-explain who you are, what you're building, or how you like to work.
Plan my week so I actually ship Helm v2.
Read creed.md
Thought for 4s<br>Blocking7to11amfordeepwork,nomeetingsbeforenoon,andWednesdaysstaycall-free.IlinedtheweekuparoundtheHelmv2beta.Wantitdaybyday?
Ask anything…
It updates as it learns<br>When an agent notices something durable, it proposes a precise edit. It lands in your Creed as a diff. Approve it and the section updates in place.
Routines<br>Deep work 7 to 11am, no meetings before noon.
Review the week every Friday at 4pm.
Ship to production Monday through Thursday only.
proposed·+9−0RejectAccept
And it sharpens over time<br>Creed scores every section for signal, what's specific and what's thin, so your profile keeps getting sharper without you auditing it.
Identity<br>…/ 100<br>SpecificConcreteThinVague<br>Scoring this section…<br>+Reads like a real person
/One line stays generic
−Contains a stray line
Review everything or nothing<br>Approve every agent edit, or let them write directly.
proposed·+27−150RejectAccept
For strategic advice, always includePrefer doing the uncomfortable constraint or the underlying root cause, even when it is not askedwork over asking for permission, and walk through every assumption one at a time. For product feedback, takeunless the timeaction is destructive or hard to explain what users will not care about, not just what sounds good in a demo, and caveat each pointundo. Lead with the context it depends on. When reviewing a plananswer, list every possible objection before giving an opinion, rank them by likelihood, and never commit to a direction until all of them have been written down, debated, and addressed in full. Before shipping anything, restatethen the goal, summarise the alternatives you considered, and ask for sign-off in writingreasoning. DocumentRaise the rationale for every decision in a shared docsingle biggest risk, link the supporting data, and keep a running log of what changed and why so nothing is ever lostnot every objection. When in doubtShip, gather more input, schedule a review, and wait for consensus before moving forwardthen iterate.<br>You keep choosing to ask rather than act.
You control what gets remembered.<br>Agents propose updates in real time, but nothing changes until you approve it.
Require approval for agent edits<br>Review proposed edits first.
BeliefsDirect
Codex·+18−173w ago
Creed's value depends on keeping the file largetight and exhaustivehigh-signal, capturing every passing preferencepruning stale detail so nothing is ever left outit stays sharp and self-improving as it grows, even detailsand trusting that stopped mattering months agoless is more.
Let trusted agents write directly.<br>Agents can update your Creed without review, keeping your context current as you work.
Get started in minutes<br>Three steps to a profile every agent can read.
Question 1 of 3<br>How would you describe yourself?<br>Continue
1Describe yourself<br>Answer a few quick questions and Creed...