How Enciph works

Enciph is a community for vibe coders, people who build software by prompting AI. On Discord, the best prompts and configs scroll away forever. Here, they're the whole point: every project ships with the recipe that built it, and anyone can remix that recipe with attribution.

The atom of Enciph

What is a Ship?

A Ship is a project you actually built and are showing the community, a web app, a CLI tool, a bot, a game, anything. But unlike a normal portfolio post, a Ship carries its provenance: not just what you made, but how you prompted it into existence.

A Ship has two halves:

  • The showcase, title, a one-paragraph description, a demo URL, a screenshot, and stack tags (#nextjs, #claude-code, …).
  • The prompt journey, the artifacts that did the real work. This is what makes Enciph different.

What you actually paste

The prompt journey

Don't paste your entire chat log, paste the 3–5 artifacts that mattered. Three kinds are supported:

1. Prompts, the exact prompt that cracked a hard part of the build. The test: would someone else get a similar result pasting this into their own session?

The prompt that nailed the streak mathprompt
Build a streak calculator where each habit has N forgiveness
tokens per month. A missed day consumes a token instead of
resetting the streak. Edge cases: timezone boundaries (store
dates as YYYY-MM-DD in the user's tz), tokens regenerate on
the 1st, and show 'forgiven' days differently from completed.

2. CLAUDE.md / rules files, the standing instructions that kept your agent on the rails across a whole project. These are gold: they encode hard-won lessons.

CLAUDE.md that kept the agent honestclaude.md
# Loopling
- SQLite via Prisma; never suggest Postgres, this runs on a $4 VPS
- All dates are YYYY-MM-DD strings in user tz, no Date objects
  across API boundaries
- Tailwind only, no CSS files
- Every feature ships with seed data so the UI is never empty

3. Agent configs, settings, hooks, permissions, MCP setups: the machinery around the prompts (works for Claude Code, Cursor, Windsurf, or any tool).

Hooks that made iteration fastagent config
permissions:
  allow:
    - Bash(node *)
    - Bash(npm test*)
hooks:
  PostToolUse:
    - matcher: Edit
      command: npm test --silent

⚠ Strip secrets before pasting, no API keys, tokens, or customer data. Artifacts are public.

The growth loop

Remixing

Every ship has a ⑂ Remix this recipebutton. It forks the ship's prompt journey into your own draft you adapt the prompts, build your version, and ship it. The attribution chain is recorded automatically: the original shows “remixed by”, yours shows “remixed from”.

Reputation on Enciph = ships you posted + times your recipes were remixed. Not karma, not commit counts things that shipped and spread.

Knowledge that compounds

The Vault

Every artifact from every ship lands in the Vaultbrowsable by kind (prompt / CLAUDE.md / config) and tag. It's the reference library Discord can't be: when someone solves “tz-safe streak math” once, the recipe stays findable forever.

Find your people

Vibe Together

Vibe Together is the founder directory. Turn on “open to collab”in your profile, pitch what you're building, tag what you're looking for (cofounder, design, sales…), and link your LinkedIn/GitHub. Your ships are your credibility, people see what you've made before they reach out.

Ship faster together

Sprint rooms

Rooms are public accountability races. Join a room, declare a task, the clock starts the moment you add it, and hit ✓ DONE when it's live. The leaderboard ranks racers by completions, ties broken by speed.

Slow conversation

Threads

Threads are persistent discussions, release news, tool talk, build journals. Unlike chat, they stay findable.

Keep it shippable

House rules

  • Post things you actually built, vaporware gets remixed by nobody.
  • Share prompts that worked, not transcripts of everything you tried.
  • Remix generously, credit always (the chain does it for you).
  • No secrets in artifacts. Ever.

Ready? Post your first ship →