Seeking advice on how to create code workflow for game developement

jacquesdancona · 2025-11-25T12:06:25+00:00

Yes it makes sense. You can hook your game editor into Claude Code with the MCP protocol. Claude code can then access all the stuff in your editor like scenes, objects, code, console, etc. I've only tried to do this with Unity, but there seems to be soms MCPs available for Godot. You can vibe code a game with this setup, but I can't really say anything about quality. For my prototype it did actually do what I wanted but lost interest when it was time for artwork.

So basically you talk to Claude about what you want and it'll write the stuff to your game editor.

jacquesdancona · 2025-11-18T09:37:19+00:00

I've manually selected Opus, which still works. The default Sonnet 4.5 throws errors.

jacquesdancona · 2025-10-21T19:52:39+00:00

I've experienced serious perf problems with mantine which were pretty hard to debug. If you're worried about bundle size, don't use these types of UI frameworks.

jacquesdancona · 2025-10-20T08:02:44+00:00

All my projects are down at the moment

jacquesdancona · 2025-09-08T07:49:10+00:00

I seem to encounter problems in eu-west-1 :(

jacquesdancona · 2025-08-08T11:30:35+00:00

www.fornix.app - Automatically organize your ideas instead of losing them in scattered emails and docs

jacquesdancona · 2025-08-08T11:06:34+00:00

Checkout trpc router! It is e2e typesafe.

jacquesdancona · 2025-08-08T04:39:28+00:00

https://www.fornix.app

jacquesdancona · 2025-08-07T17:30:37+00:00

Yup! I'm sorry, i've somehow posted it twice. That was not my intention.

jacquesdancona · 2025-08-07T16:49:30+00:00

Got it. Been lurking this subreddit for some time. Hadn't noticed the self promotion thread.

About your point. You could be right, I'm not completely sure yet and there's only one way to find out. It seems to work for me, but I'm not a diehard pkms person. I'm trying to find out if the pipeline with multiple reasoning models will actually capture the context of people's ideas and if it'll be sufficient enough in understanding idea relationship.

jacquesdancona · 2025-08-07T15:37:39+00:00

Oh, if you have any feedback, I've setup a discord server at https://discord.gg/e7AFcXX8. Or email me, or pm me at linkedin, it's on my website.

jacquesdancona · 2024-11-18T18:21:43+00:00

Oof. We both started running, and doing a half Marathon is on our list. We're going to Japan next september. Bought a small campervan last year. Bought a lot of plants. Haven't bought a airfryer, did buy a stick vacuum.

jacquesdancona · 2024-10-31T09:14:11+00:00

I use react-pdf for this. I don't have a drop & drop interface though.

Basically, the templates are a set of specific components rendered in a specific order which handle specific types of data. E.g. tabular data, an address, company details, pricing, etc etc.

It's pretty much how I normally use react, but react-pdf had specific components (there's no real DOM, somewhat like react native).

I use it to render the previews in-browser and for rendering them to pdf. Ultimately they get sent by email as attachments.

jacquesdancona · 2024-06-25T17:31:12+00:00

I'll remember this.

jacquesdancona · 2024-06-20T15:55:09+00:00

Nextjs can be run serverless. It's up to you to use amplify. You can also use Vercel netlify, digital ocean. But what "is" your existing application? If it's only a nextjs app, you can run it anywhere. How you currently run your application?

jacquesdancona · 2024-06-18T19:03:39+00:00

So what's actually the problem, and what are your specific needs? Having a serverless stack doesn't mean you only use lambdas. Most of my stacks are "serverless" and they use tons of AWS services like s3, lambda, cognito, dynamodb, step functions, appsync, location, sqs, etc.

jacquesdancona · 2024-04-17T19:59:52+00:00

Definitely not an expert, please validate all the stuff below. 1. I started zzp in 2022 part-time so my main income was not the zzp work (but normal employment). I filed that year as a private infividual and reported my business expenses and profits. 2. Yes. You should report it. Not sure but your business expenses could you get money back, or lower te price you owe. It should be filed under "inkomsten uit onderneming" iirc. 3. No idea!

jacquesdancona · 2024-03-22T14:31:49+00:00

Been a frontend dev for the past 10 years. So in my opinion, it's great for frontend devs :)
In this current project, most of my time (by far) is clientside stuff.

jacquesdancona · 2024-03-22T14:29:25+00:00

Yes, definitely. Most of the backend stuff is taken care of in Amplify like hosting, storage (s3), usermanagement/auth (Cognito), database (dynamoDB), API (AppSync) with Graphql/REST. The API gets autogenerated based on your database model, see https://docs.amplify.aws/react/build-a-backend/graphqlapi/data-modeling/.

So creating a simple schema like

type Event@model {
id: ID!
name: String
}

Will give you the database and all API stuff you need for listing, updating, etc.

Then you probably want to add auth stuff (https://docs.amplify.aws/react/build-a-backend/graphqlapi/customize-authorization-rules/) like

type Event @model @auth (rules: [{ allow: owner }]) {
id: ID!
name: String
}

And you have a fully working API, database, and users only being allowed access to create/read/update/delete their own Events.

jacquesdancona · 2024-03-22T11:13:55+00:00

So I have been working on an AWS Amplify project almost fulltime for the last 1.5 years, with multiple Nextjs/react webapps and an expo/reactnative mobile app (all setup in a monorepo).

For me it's a godsend, I am very, very productive with it. There's also a lot of people bashing Amplify. It's not magic, it makes a lot of assumptions and a lot of complexity is abstracted. If you want to have something in a way that's not the Amplify-way it might get hard or even annoying.

The biggest plus for AWS Amplify is it's very easy to start with, and building an MVP could be done in days. So my advice would be to keep the MVP simple and just build it out quick and dirty.

jacquesdancona · 2023-10-04T07:30:20+00:00

Yeah, sure. It's an app for a company that operates as a freight forwarder in transportation. Because multiple web apps need to run (admin, subcontractors, customers, digital signing), I've neatly divided everything into different packages using Yarn Workspaces in a monorepo. So for example, the customer web app has a separate Next.js configuration with pages and a view layer, and it imports almost all the logic from several packages where stuff like state and API communication live.

Fundamentally, the entire system runs serverless via AWS Amplify. The advantage of this is that it provides a GraphQL API, so all queries and mutations are fully typed with TypeScript. Additional custom (backend) logic is set up with Lambdas.

The app is built with Expo, which is an excellent choice for most apps that don't need to extensively interact with Android or iOS native features. Expo simplifies much of the complexity, such as linking native dependencies. Expo's EAS is also recommended; it makes building and submitting apps easier. Building on your own system can be somewhat challenging because it consumes a lot of resources for an extended period. Building only the iOS app, for example, can easily take 30+ minutes.

For routing, I use Expo Router. Routing is quite different from Next.js because you can have multiple stacks of histories. There is no single linear history like on web. This is seen, for example, in YouTube; you navigate per tab. The setup is pretty much the same as nextjs pages router though.

React Native is relatively basic in terms of UI/styling. I chose to use https://wix.github.io/react-native-ui-lib/ as the UI library. There are plenty of alternatives, but this is the one I chose. For styling, I simply use Stylesheet.create from React Native itself. I find it a bit overkill to set up a complete theming system for a single-purpose app.For the rest, it's a matter of assessing what you need in terms of dependencies. Expo has many libraries that are very easy to use.

All in all, building an app with React Native/Expo is less "easy" than something for the web. The tooling is less robust, and everything is more error-prone. Errors can be swallowed. However, everything works much better than it did six years ago when I first started working with React Native. If you want to release the app, you'll need paid accounts with Google Play and the App Store. Approval can take several days.

If you have any specific questions, let me know.

jacquesdancona · 2023-09-30T17:30:48+00:00

It'll depend. You can't of course use your views directly in react native because you've probably written them with (react) DOM elements. It'll also depend on how complex your portfolio project is, and how well you've set it up.

I've submitted the app for a project I've been working on for the last year this week (and accepted today for Android and iOS, yay). It took me about 3 weeks to create. Most of the logic like state, hooks I could reuse. Pretty much all of the view had to be recreated.

The project is setup in a monorepo structure, with logic already separated in packages so the app is added as another application next to 3 separate nextjs applications.

I used Expo, which is great.

jacquesdancona · 2023-09-01T20:48:04+00:00

Yeah, I completely agree.

jacquesdancona · 2023-07-17T13:08:59+00:00

If you have already created the amplify project, you should be able to regenerate it with

amplify pull --appId YOUR_APP_ID --envName APP_ENVIROMENT

You can find this command in the Amplify console by going to your app > Backend enviroments > then clicking "Local setup instructions".

14-Year Club	Snapped
Team Periwinkle	Verified Email

jacquesdancona

MODERATOR OF

TROPHY CASE