A—Z / symbolic geometry
Live system
01
Sigilize
Turning a dense symbolic system into a usable creative tool without sanding off its strangeness.
- Product design
- Interaction
- Web engineering
Independent web design + development / Frontier AI
Make the
strange legible.
I design and build distinctive websites with frontier AI. Art direction, expressive interaction, and lightweight engineering, developed together—from the first sketch to the live site.
Web design with frontier AI✶Interactive publishing✶Digital products✶Applied AI✶Editorial design✶
✶✶✶✶✶
Web design / A wider field of possibility
Complex in motion.
Light in the browser.
Frontier AI opens up the design space. Experience turns that range into a website with a point of view.
I use frontier models to explore visual directions, prototype interactions, and develop production code. You work directly with me, Jude O’Neill, on the decisions that make the site yours: its voice, its structure, and how it feels to use.
01
Find the character.
Art direction, typography, and composition shaped around what your work needs to communicate.
02
Make it behave.
Purposeful motion and interaction, tested across touch, keyboard, and different screen sizes.
03
Keep it fast.
Lean code, carefully chosen assets, and a site you can maintain and develop after launch.
Campaign sites. Company websites. Interactive publications. Custom digital experiences.
See the publishing system behind this siteSelected work / 01—04
Work built around difficult ideas.
Current studio work moves between product, publishing, systems, and symbolism. Different outputs; the same demand for coherence.
Work / compared at the system level
Four outputs. Four different operating models.
The visible work changes because the underlying problem changes. These projects share a method, not a house style.
Sigilize
Open case study
Operating problem
A coherent symbolic grammar existed, but reference text alone made composition slow and abstract.
Interface consequence
The geometry became the control surface: relationships are learned while the user composes, not before.
Interactive reader
Open case study
Operating problem
Three books contain arguments that cross chapter and book boundaries; linear reading hides those relationships.
Interface consequence
Reading position, evidence, guided paths, and metatext become one navigable state rather than separate reference layers.
Lattice
Open case study
Operating problem
Agents can generate work faster than teams can preserve truth, authority, verification, and consequence boundaries.
Interface consequence
The product organizes around active frontier, evidence, exceptions, and human decisions instead of a growing task pile.
AI Native CMS
Open case study
Operating problem
Human editing, agent changes, repository state, database content, generated pages, and hosting can all drift into rival truths.
Interface consequence
Each layer receives explicit authority: Git owns structure, MySQL owns accepted mutable state, and public files remain deterministic projections.
Studio principle / 01Closer to the source
The surface is usually the last problem.
Good digital work starts by finding the operating idea underneath the brief: the logic people need to understand, the behavior the interface should make possible, the story the system is already trying to tell.
The interface follows from that structure.
Capabilities / not departments
Built around the problem.
Web design with frontier AI
Custom websites, from art direction and responsive interaction to production code, publishing, and launch.
Interactive publishing
Books, essays, archives, evidence, and ideas reimagined as navigable digital experiences.
Products + prototypes
Useful software from first interaction model through working interface and release-ready front end.
AI-native experiences
AI products with clear boundaries for what a model can decide, what people control, and how the result is checked.
Editorial + narrative
Complex ideas given structure, voice, and enough editorial pressure to become clear without becoming generic.
A brief is a starting observation
The requested object rarely defines the real job.
Choose a familiar request. The useful questions begin one layer underneath it.
Website / first question
What must become easier to understand, choose, or do?
Before page templates or visual direction, identify the change the site has to create in a visitor’s understanding or behavior. The information architecture follows that consequence.
Working method
Find the gravity.
Build around it.
- 01Frame the real problem.
Separate the request from the consequence it is meant to create.
- 02Make the system visible.
Map the content, behaviors, constraints, and relationships that determine the experience.
- 03Ship the sharp edge first.
Prototype the part that proves whether the idea actually works.
- 04Earn the finish.
Polish follows coherence. Nothing decorative has to carry a broken idea.
New work / collaborations / strange problems
Bring us the idea
that won’t behave.
Perihelion is assembling a small number of ambitious collaborations across digital products, publishing, identity, and experimental media.
hello@perihelioncreative.com