00 About

Energy Flow Knowledge Base

Welcome! I'm Charlie Ellington and this small site is my living knowledge hub—an ever-evolving collection of notes, plans and guiding principles that keep me (and collaborators) in energy flow.

Energy flow is the sweet spot where work is challenging, skill-building and genuinely valuable for people and planet—while still leaving room for family, health and community.

What I'm working on

  1. No Bad Parts Collective
    Building a peer-to-peer community where people practise Internal Family Systems sessions together, assisted by AI listening tools while keeping a warm human presence.
    • Public site → nobadpartscollective.com (opens in a new tab)
    • Docs → Project brief

  2. Sunni.be
    A membership gallery bringing limited-edition ocean photography into your home. Hand-finished frames, gallery-grade prints, swap each year—or buy and credit your fees.
    • Public site → sunni.be (opens in a new tab)
    • Docs → Sunni project page

  3. Waitlist Kit
    A ready-to-ship Next.js × Supabase template that spins up a "Coming soon → Join the wait-list" page in minutes (used across my projects).
    • GitHub → charlieellington/waitlist-kit (opens in a new tab)
    • Docs → Waitlist app

  4. Zebra Design
    Fractional product-design partner for founder-led teams—uniting bold aesthetics with user-centred research to accelerate product-market fit.
    • Site → zebradesign.io (opens in a new tab)
    • Docs → Zebra Design brief

What you'll find here

• Project dossiers – bullet-proof context for each active venture (Zebra Design, IFS Community, Children's Books Platform, Sunni.be and more).

• Systems & processes – short write-ups on 4-hour focus days, deep-work tactics, automation to slash shallow work, and tools that protect my time and health.

• Principles & philosophy – the three core questions I live by, plus notes on compassionate productivity, building evergreen assets, and what "wealth" really means.

Everything is pure markdown so it can be loaded directly into Cursor for contextual coding sessions or served publicly as docs.

Why this exists

  1. Single source of truth
    No more scattered Google Docs or Notion pages. One repo → one deployment.
  2. Context for pair programming
    When I invite an AI assistant (or a human collaborator) into a codebase, they can pull rich project context instantly.
  3. Public transparency
    Friends, clients and future teammates can peek at how I think, plan and ship.

Feel free to explore, fork ideas, or reach out on LinkedIn (opens in a new tab) if something resonates 🌱

01 Doing Next