Start · a tiny useful thing
Your first deck.
Create a repo in the app, add a .ij file, check it, then save a version. Keep work private until you are ready to share.
Give every Jude a purpose, sample inputs and expected output. Name simulated actions plainly.
Try a welcome intention
Grow · a reusable pattern
From simple to thoughtful.
Build a starter deck for greetings; a workflow deck for event checks and memory; an engineering deck for filtered batches and approval boundaries.
These are project prompts, not claims of existing members or activity. A beautiful community starts with useful, honest work.
Explore real source examples
Contribute · Jude and everyone
One change someone can review.
Start a branch from the current source, reproduce the issue with a small input, then change the smallest useful part.
Run the parser, engine and site checks; include failing cases, before/after output and any host permission changes in your pull request.
Keep API keys and private account data out of files; ask a maintainer to review before merging. Label AI assistance and test fixtures honestly.
Care · for the next builder
Make trust part of the craft.
Credit authors, choose a licence for shared code, explain how to reproduce problems, and critique the code kindly.
Show what your actions can access and what needs approval. Never publish credentials, real people's private data or invented testimonials.
For a security concern, share a minimal private reproduction with the repository maintainer; avoid publishing secrets in an issue.
Understand the engine's boundaries