HN user

surferbayarea

272 karma

anusheel - Builder at imagine.ai, etc

Posts14
Comments98
View on HN

Forge brings rigorous, adversarial architectural planning and reliable step-by-step execution to AI-assisted development. It works with Claude Code, Codex CLI, Cursor, or directly via API — the provider is pluggable.

How It Works

Planning — Two independent AI architects design competing solutions. Adversarial critics tear each design apart. Refiners address the critiques. A judge synthesizes the best elements into a final plan. The result: plans that have been stress-tested before a single line of code is written.

Execution — A deterministic pipeline runs your plan through configurable steps (code, build, lint, test, review, PR) with evidence-based validation at each stage. State lives on disk, not in LLM memory — every step gets a fresh agent with zero context rot.

[dead] 5 years ago

Awesome re: supporting both TypeORM and Sequelize

Thanks. While we began with Express, we intend to add support for more ORMs, so that users can pick the one they want. We did come across Prisma and we are exploring supporting it.

For now, we support MySQL, PostgreSQL and SQLite, but are also planning to add support for Mongo. Do you have Mongo/NoSQL databases on your roadmap?

It would be great to connect on a zoom - I'm the co-founder of imagine, my email is anusheel@imagine.ai

Hey :) it’s not multiple accounts - this post is by one of the core contributors to the project who is a functional programming expert and I thought it would be helpful if he shared his perspective on why Haskell was chosen for this!

(I couldn’t see my earlier post for some reason on Show HN and I thought I accidentally deleted it, so I thought rather than me reposting it, it would be nice to have one of our contributors share his perspective).

Imagine is a labor of love for my co-founder and me. I’ve been a software engineer for over a decade and we’ve overseen the build out of several (80+) software products over the years.

Each time we were acutely reminded of how much redundancy there exists while writing code, especially for commonly used components and features in software applications. Also, while we believe the current version of the no-code movement is awesome, we found it hard to scale these solutions for applications that required any reasonable level of custom logic.

So we built Imagine - a configurable, cross-framework platform for developers to easily generate high-quality code for common application components, which they can seamlessly integrate into their projects, without any lock-in - and allowing them to focus on writing custom business logic. Our goal has been to make the generated code clean, readable and following known software best practices (we love the 12—factor app philosophy!) - basically indistinguishable from what a skilled engineer would write.

To build the Imagine code generator, we initially considered building with regexes, but discarded that approach as it would have been highly error-prone. Given the high configurability we wanted to offer, we needed to be obsessed with correctness. To achieve this, we decided to use Haskell to build the code generator, as we were able to use Haskell’s built-in type system to represent rules to ensure correctness of the generated code. It also allowed us to enforce various constraints across an app’s specification using static checks.

In terms of features, our beta release allows you to define your starter settings, data models and relations via a UI and we instantly generate code for a dockerized project starter, ORMs, REST & GraphQL CRUD APIs and tests in both Django & Node.js.

We also have the following features on our roadmap: - Backend frameworks: - Node/Typescript - Backend features: - NoSQL databases (MongoDB, DynamoDB) - Support for migrations - Kubernetes deployment scripts - Logging and monitoring - Authentication (via multiple providers) - Payments integration (via multiple providers) - Frontend frameworks: - React (incl Redux, Hooks) - React native - Frontend features: - API calling - Views & components - Storybooks

We’d like to thank you in advance for trying our product out - we’re still early in development, and would love your feedback and suggestions as we push to make Imagine better everyday!

Well the reason FB/Foursquare/Google etc add these to 3rd party apps is so they can get data. Example if you visit a website which has a Facebook like button, your browser fetches the js files/which maybe even makes an API call to let FB know your IP (and hence location). All this data is fed to the giant system that feeds you ads. Adding their SDK to other apps/sites (even if there is no user facing need) is a common strategy used by most big companies to get data. In return the app that puts in the SDK gets $ from the company.

Also learn generic problem solving VS just pattern matching on how to do a specific thing. Frameworks, languages and patterns themselves will keep changing. Core problem solving skills and understanding will stay relevant always.

A skill of knowing how to use React in a particular way to create simple views is something that will be redundant in a few years. These people will unfortunately be out of jobs. The mundane work of converting sketch files to react views will be automated soon

The US would have gone down the same route if WhatsApp or Instagram had happened to be acquired by a Chinese company (and hence under control of Chinese govt). Having your citizens data and communication under control of a foreign government is not something any government would be ok with in the long term. It will be interesting to see the reaction of the US government(and of Silicon Valley) when the next TikTok becomes the major communication tool in the US.

It's because they did some weird integration with a common payments system that is broken. If you call their customer support, they will bounce you from the cloud Dept to the wallet team to payments and so on...it's a classic big company issue trying to consolidate things like payments across many products.

The next shock that Silicon Valley and US government will face in the near future is when the next social media monopoly or communication service is from a Chinese owned company. Imagine if wechat had won the messaging war vs whatsapp. This is bound to happen sooner than later - eq Tiktok is coming close to disrupting Youtube/Instagram.

"attract the talent"...this is no longer the case. I talk to 50+ (new) senior engineers/month (for the past 6 years) and there has been a serious mind shift in the last couple years. I now hear things like "hasn't immigration become impossible to the US" and with increasing remote work, people are happy/prefer working from their home countries (better tax structures, they actually make more money). While this won't hurt US in the short term, the next generation of top startups might not be in Silicon Valley.