The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Neko Jinja is an interactive prototype of a hidden cat shrine where English names are reimagined as poetic Japanese kanji interpretations.
The problem I explored was not only how to create a charming cultural experience, but also how to keep an AI-assisted creative project coherent across many tools, sessions, and agents. When working with AI, ideas can drift, design decisions can disappear, and new sessions often lose the original context.
To solve that, I organized the project around a shared markdown context system called the World Tree. It stores the concept, visual rules, character settings, architecture, asset notes, and design decisions so AI agents can quickly understand the project and continue in the same direction.
Figma became the bridge between imagination and implementation. I used Figma Make to generate and iterate on interactive prototypes, Figma Design to explore desktop and mobile experience flows, and Figma MCP to connect local AI coding agents directly with the design process. Much of the Figma work was agent-driven through MCP, rather than manually recreated by hand.
Local AI agents including Codex, Google Antigravity, and Claude Code helped with implementation, review, asset direction, and polish. I also used a markdown “letter system” to coordinate agents: requests, reviews, and decisions were passed as readable letters, making the workflow traceable and easier to emulate.
The final prototype lets visitors enter a name, receive a poetic kanji interpretation, explore a shrine map, draw fortunes, discover haiku, watch the sacred tree change with the seasons, and take home a keepsake card.
Design doesn’t end on the canvas — Neko Jinja was shaped, built, and refined together with an AI team.
Adding the project links here since I forgot to include them in the original post:
Live prototype:
Figma working file:
Figma...
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
Pip is a zero-friction health companion built to turn tracking your health (SYMPTOMS, DIET AND MORE) into clinical clarity. It abandons rigid 0–10 numeric scales and replaces them with a compassionate, glanceable interface.
❤ Why It Was Built
Pip was born out of pure personal necessity. I built it because it was something I desperately needed, and something a few close friends and someone incredibly close to my heart needed too. I wanted to strip away the clinical coldness of modern software and create something beautifully simple that could be truly, deeply helpful on someone's hardest days
⚠️ The Problem
Traditional health apps suffer from "Data Collection Theater." They force users suffering from chronic illness or fatigue to rate dozens of variables daily, causing severe decision fatigue.
Worse, they act as data sinks, dumping raw, chaotic charts onto doctors. In a high-stakes, 15-minute medical consultation, physicians don't have the time to audit raw logs. They need high-yield, synthesized clinical signals, not noise. Pip bridges this gap by assuming "bad days are the default," capturing symptoms effortlessly, and compiling them into a clean, one-page summary sheet.
🛠 The Figma Workflow Pipeline
To bring Pip to life, I leveraged the Figma ecosystem:
Figma Weave: Used to iterate and generate the visual asset layers for Pip’s mascot.
Figma Agent: Brainstormed layouts directly on the canvas, instantly pairing elegant fonts and organizing simple, stress-free forms.
Figma Make: Instantly turned those canvas designs and components into a live, fully working, and responsive web application while allowing rapid iteration.
Which of these two designs is better? I was creating a scrapbook web app, but Figma Make rejected my design and generated its own design instead. What should I do now?
16 voted
70%
7 voted
30%
23 votes
Closed
Went with your original Figma design. The spiral notebook layout has actual scrapbook energy that Figma Make's version loses completely. That said, might be worth borrowing the cleaner content area from the generated version and mixing it into your layout.
What if you could see the world through the eyes of a local? 🧐
A quick search doesn't always cut it. We get funneled toward the same generic spots, and half the time we don't even know why something's being recommended to us.
Incola fixes that. Just ask someone who actually knows the place you're heading to. 🧳
Where should I go if I love history and I've got 2 days in New York? Where do I find open-air house music events in Tokyo? Ask a local. And while you're at it, help other travelers by answering the open questions about your own city.
Try it now! The more people jump in, the faster we leave the cold start problem behind. 😄
Can't believe I'm saying this, but all of this was built in Figma Make.
Try Incola: https://vary-mac-30681003.figma.site
More insights coming soon.
Trending
Claude
Claude has entered the design space. How are you using Claude Design?
Contra University
Learn from expert creatives how to earn more using next-gen AI tools.
MagicPath
The canvas is infinite, and exploration is becoming the workflow. How are you using MagicPath?
creativeaiflow
Creative AI workflows are evolving. What tools do you use, and what are their strengths and weaknesses?
freelancerlife
Freelancer life is wins, pivots, and everything in between. What’s yours right now?