insforge 0.3.3 → 1.3.0

package/.prettierignore

@@ -1,65 +1,65 @@
-# Dependencies
-node_modules/
-**/node_modules/
-
-# Build outputs
-dist/
-**/dist/
-build/
-**/build/
-.next/
-**/.next/
-
-# Coverage
-coverage/
-**/coverage/
-
-# Turbo
-.turbo/
-**/.turbo/
-
-# Public assets
-public/
-**/public/
-
-# Lock files
-package-lock.json
-**/package-lock.json
-yarn.lock
-**/yarn.lock
-pnpm-lock.yaml
-**/pnpm-lock.yaml
-
-# Generated files
-*.min.js
-*.min.css
-
-# Logs
-*.log
-
-# IDE
-.vscode/
-.idea/
-
-# OS
-.DS_Store
-Thumbs.db
-
-# Environment
-.env
-.env.*
-
-# Git
-.git/
-.gitignore
-
-# File types to ignore
-*.md
-*.yaml
-*.yml
-*.json
-
-# Folders to ignore
-docs/
-examples/
+# Dependencies
+node_modules/
+**/node_modules/
+
+# Build outputs
+dist/
+**/dist/
+build/
+**/build/
+.next/
+**/.next/
+
+# Coverage
+coverage/
+**/coverage/
+
+# Turbo
+.turbo/
+**/.turbo/
+
+# Public assets
+public/
+**/public/
+
+# Lock files
+package-lock.json
+**/package-lock.json
+yarn.lock
+**/yarn.lock
+pnpm-lock.yaml
+**/pnpm-lock.yaml
+
+# Generated files
+*.min.js
+*.min.css
+
+# Logs
+*.log
+
+# IDE
+.vscode/
+.idea/
+
+# OS
+.DS_Store
+Thumbs.db
+
+# Environment
+.env
+.env.*
+
+# Git
+.git/
+.gitignore
+
+# File types to ignore
+*.md
+*.yaml
+*.yml
+*.json
+
+# Folders to ignore
+docs/
+examples/
 openapi/

package/CHANGELOG.md

@@ -1,3 +1,44 @@
-# Changelog
-
-# [0.3.0](https://github.com/InsForge/InsForge/compare/v0.2.9-fix...v0.3.0) (2025-09-26)
+# Changelog
+
+## [1.2.8](https://github.com/InsForge/InsForge/compare/v1.2.6...v1.2.8) (2025-12-05)
+
+## [1.2.6](https://github.com/InsForge/InsForge/compare/v1.2.4...v1.2.6) (2025-11-22)
+
+## [1.2.4](https://github.com/InsForge/InsForge/compare/v1.2.3...v1.2.4) (2025-11-22)
+
+## [1.2.2](https://github.com/InsForge/InsForge/compare/v1.2.1-e2e...v1.2.2) (2025-11-18)
+
+# [1.2.0](https://github.com/InsForge/InsForge/compare/v1.1.7-Nov13...v1.2.0) (2025-11-15)
+
+## [1.1.2](https://github.com/InsForge/InsForge/compare/v1.1.0-posthog-9...v1.1.2) (2025-10-28)
+
+
+### Bug Fixes
+
+* addressing coderabbit comments ([97dd933](https://github.com/InsForge/InsForge/commit/97dd9339269991955d8c644f88e77efa6c3f6da2))
+* macOS compatibility and AI config cleanup for e2e tests ([2e04d79](https://github.com/InsForge/InsForge/commit/2e04d7920b00a2b19eed1f0aa3072a6ea937f41a))
+* removing package-lock ([9df772d](https://github.com/InsForge/InsForge/commit/9df772dcadd3a91e2fa70507d8f2779f6910d484))
+* removing package-lock ([222dfc1](https://github.com/InsForge/InsForge/commit/222dfc1231504ce8e7d14d5ab79e57c1b00785c7))
+* update the frontend to use the bulk-upsert exising API ([2b9b3b2](https://github.com/InsForge/InsForge/commit/2b9b3b23c4cc2d401781ba5504c54db07bb84af0))
+
+
+### Features
+
+* added tests for ai configs ([2a4e93a](https://github.com/InsForge/InsForge/commit/2a4e93acf145699511bd0ea49e29926f2d585b36))
+* added tests for functions and secrets ([a985f03](https://github.com/InsForge/InsForge/commit/a985f035ffc1c1152999b317cf4e03e0f45ba34e))
+* added tests for logs ([81f7734](https://github.com/InsForge/InsForge/commit/81f7734f3586e03ae2be5694b63d2a3417ae7339))
+* fixed all the tests with correct format ([1242d13](https://github.com/InsForge/InsForge/commit/1242d133efd4398ae672e1e6c71ae1431aa9ba62))
+* fixed secret tests ([5703836](https://github.com/InsForge/InsForge/commit/5703836ecee0ffeb27bfca9b0d785b95e68f1688))
+* updated the backend and the service to update the csv parsing and validating ([e7ffd29](https://github.com/InsForge/InsForge/commit/e7ffd292fd93381ae2eebde17c16e3996241f15c))
+* updated the frontend to display the button and the respective functions ([50613d8](https://github.com/InsForge/InsForge/commit/50613d8d972b88cf28b147bb7a44901c23d77e79))
+
+# [1.1.0](https://github.com/InsForge/InsForge/compare/v1.0.1-ai-2...v1.1.0) (2025-10-11)
+
+
+### Bug Fixes
+
+* typo in docs ([d2a0efc](https://github.com/InsForge/InsForge/commit/d2a0efc56ab77560597dc2ee46c5f8a669fbd71d))
+
+# [1.0.0](https://github.com/InsForge/InsForge/compare/v0.3.3...v1.0.0) (2025-09-29)
+
+# [0.3.0](https://github.com/InsForge/InsForge/compare/v0.2.9-fix...v0.3.0) (2025-09-26)

package/CLAUDE_PLUGIN.md

@@ -0,0 +1,104 @@
+# InsForge Claude Code Plugin
+
+Official plugin for building with InsForge in Claude Code.
+
+## Installation
+
+### Option 1: Install from InsForge Marketplace (Recommended)
+
+In Claude Code, run:
+
+```
+/plugin marketplace add InsForge/InsForge
+```
+
+Then install the plugin:
+
+```
+/plugin install insforge
+```
+
+### Option 2: Install Directly from Repository
+
+```
+/plugin install https://github.com/InsForge/InsForge/claude-plugin
+```
+
+### Option 3: Local Installation (Development)
+
+```bash
+cd ~/.claude-plugins
+git clone https://github.com/InsForge/InsForge.git
+ln -s InsForge/claude-plugin insforge
+```
+
+## What's Included
+
+### Skill: `insforge-schema-patterns`
+
+Automatically activates when designing database schemas. Includes:
+
+- **Social Graph Patterns** - Follows, likes, and social relationships
+- **Junction Tables** - Many-to-many relationships with proper indexes
+- **Nested Comments** - Self-referential hierarchical data
+- **Multi-Tenant Patterns** - Organization-scoped data with RLS
+- **Best Practices** - Foreign keys, indexes, Row Level Security
+
+## Usage
+
+Once installed, the skill automatically loads when relevant:
+
+**Example:**
+```
+You: "I need to build a social media app with follows and likes"
+
+Claude: [Automatically loads insforge-schema-patterns]
+"I'll use the Social Graph pattern from InsForge best practices:
+
+CREATE TABLE follows (
+  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
+  follower_id UUID REFERENCES users(id) ON DELETE CASCADE,
+  following_id UUID REFERENCES users(id) ON DELETE CASCADE,
+  created_at TIMESTAMPTZ DEFAULT NOW(),
+  UNIQUE(follower_id, following_id)
+);
+..."
+```
+
+No special commands needed - Claude knows when to use it based on your conversation!
+
+## What Are Skills?
+
+Skills are folders containing instructions and examples that Claude automatically loads when they're relevant to the task. Think of them as giving Claude domain expertise in specific areas.
+
+The `insforge-schema-patterns` skill teaches Claude:
+- Proven database design patterns for common use cases
+- How to write efficient PostgREST queries with the InsForge SDK
+- Best practices for security (RLS policies)
+- Performance optimization (indexes, query patterns)
+
+## Future Skills (Coming Soon)
+
+We're planning to add:
+- `insforge-fullstack-templates` - Complete app templates (Instagram, Todo, Blog)
+- `insforge-edge-functions` - Serverless function recipes
+- `insforge-realtime` - WebSocket and live collaboration patterns
+
+## Contributing
+
+Want to improve the skills or add new ones?
+
+1. Fork the repository
+2. Edit or add skills in `claude-plugin/skills/`
+3. Test locally by installing from your fork
+4. Submit a PR
+
+Skills are just Markdown files with YAML frontmatter - easy to contribute!
+
+## Feedback
+
+Found an issue or have a suggestion? [Open an issue](https://github.com/InsForge/InsForge/issues) or join our [Discord](https://discord.com/invite/MPxwj5xVvW).
+
+## License
+
+MIT - Same as InsForge

package/CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+tony.chang@insforge.dev.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 3.0, available at
+[https://www.contributor-covenant.org/version/3/0/code_of_conduct/](https://www.contributor-covenant.org/version/3/0/code_of_conduct/)
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.

package/CONTRIBUTING.md

@@ -1,126 +1,126 @@
-# Contributing to InsForge
-
-Thank you for your interest in contributing to InsForge. This guide will help you get started with the contribution process.
-
-## Table of Contents
-- [Code of Conduct](#code-of-conduct)
-- [Project Structure](#project-structure)
-- [Prerequisites](#prerequisites)
-- [Getting Started](#getting-started)
-- [Development Workflow](#development-workflow)
-- [Testing](#testing)
-- [Pull Request Process](#pull-request-process)
-- [Code Style](#code-style)
-
-## Code of Conduct
-
-This project and everyone participating in it is governed by our Code of Conduct. By participating, you are expected to uphold this code.
-
-## Project Structure
-
-The InsForge monorepo is organized as follows:
-
-- `/backend` - Core backend service with Express.js, PostgreSQL, and Better Auth integration
-- `/frontend` - React-based admin dashboard for managing databases, users, and storage
-- `/shared-schemas` - Zod schemas and TypeScript types shared between frontend and backend
-- `/docs` - MCP documemtation
-- `/functions` - Serverless edge functions for custom business logic
-- `docker-compose.yml` - Docker config file to start the project
-
-## Prerequisites
-
-Before you start development, ensure you have the following:
-- [Docker](https://www.docker.com/get-started)
-- [Node.js](https://nodejs.org/) (LTS version recommended)
-
-## Getting Started
-
-1. Fork the repository to your GitHub account
-2. Clone your fork locally:
-   ```bash
-   git clone https://github.com/insforge/insforge.git
-   cd insforge
-   ```
-3. Install Docker
-4. Open Docker App
-5. Install Node.js (LTS version recommended)
-6. Create a .env file from the example:
-   
-   On Unix-based systems:
-   ```bash
-   cp .env.example .env
-   ```
-   
-   On Windows:
-   ```bash
-   copy .env.example .env
-   ```
-7. Run the project
-   ```bash
-   docker compose up
-   ```
-
-## Development Workflow
-
-1. Create a new branch for your changes:
-   ```bash
-   git checkout -b type/description
-   # Example: git checkout -b feat/site-deployment
-   ```
-
-   Branch type prefixes:
-   - `feat/` - New features
-   - `fix/` - Bug fixes
-   - `docs/` - Documentation changes
-   - `refactor/` - Code refactoring
-   - `test/` - Test-related changes
-   - `chore/` - Build process or tooling changes
-
-2. Make your changes following the code style guidelines
-3. Add tests for your changes (see test README for guidelines)
-4. Run the test suite:
-   ```bash
-   npm test:e2e
-   ```
-5. Run linter:
-   ```bash
-   npm run lint
-   ```
-6. Ensure all tests pass and the code is properly formatted
-7. Commit your changes with a descriptive message following the Conventional Commits format:
-   ```
-   type(scope): description
-   
-   [optional body]
-   [optional screenshots / videos]
-   [optional footer(s)]
-   ```
-8. Push your branch to your fork
-9. Open a pull request against the main branch
-
-## Testing
-
-All contributions must include appropriate tests. Follow these guidelines:
-- Write unit tests for new features
-- Ensure all tests pass before submitting a pull request
-- Update existing tests if your changes affect their behavior
-- Follow the existing test patterns and structure
-- Test across different environments when applicable
-
-## Pull Request Process
-
-1. Create a draft pull request early to facilitate discussion
-2. Reference any related issues in your PR description (e.g., 'Closes #123')
-3. Ensure all tests pass and the build is successful
-4. Update documentation as needed
-5. Keep your PR focused on a single feature or bug fix
-6. Be responsive to code review feedback
-
-## Code Style
-
-- Follow the existing code style
-- Use TypeScript types and interfaces effectively
-- Keep functions small and focused
-- Use meaningful variable and function names
-- Add comments for complex logic
+# Contributing to InsForge
+
+Thank you for your interest in contributing to InsForge. This guide will help you get started with the contribution process.
+
+## Table of Contents
+- [Code of Conduct](#code-of-conduct)
+- [Project Structure](#project-structure)
+- [Prerequisites](#prerequisites)
+- [Getting Started](#getting-started)
+- [Development Workflow](#development-workflow)
+- [Testing](#testing)
+- [Pull Request Process](#pull-request-process)
+- [Code Style](#code-style)
+
+## Code of Conduct
+
+This project and everyone participating in it is governed by our Code of Conduct. By participating, you are expected to uphold this code.
+
+## Project Structure
+
+The InsForge monorepo is organized as follows:
+
+- `/backend` - Core backend service with Express.js, PostgreSQL, and Better Auth integration
+- `/frontend` - React-based admin dashboard for managing databases, users, and storage
+- `/shared-schemas` - Zod schemas and TypeScript types shared between frontend and backend
+- `/docs` - MCP documentation
+- `/functions` - Serverless edge functions for custom business logic
+- `docker-compose.yml` - Docker config file to start the project
+
+## Prerequisites
+
+Before you start development, ensure you have the following:
+- [Docker](https://www.docker.com/get-started)
+- [Node.js](https://nodejs.org/) (LTS version recommended)
+
+## Getting Started
+
+1. Fork the repository to your GitHub account
+2. Clone your fork locally:
+   ```bash
+   git clone https://github.com/insforge/insforge.git
+   cd insforge
+   ```
+3. Install Docker
+4. Open Docker App
+5. Install Node.js (LTS version recommended)
+6. Create a .env file from the example:
+   
+   On Unix-based systems:
+   ```bash
+   cp .env.example .env
+   ```
+   
+   On Windows:
+   ```bash
+   copy .env.example .env
+   ```
+7. Run the project
+   ```bash
+   docker compose up
+   ```
+
+## Development Workflow
+
+1. Create a new branch for your changes:
+   ```bash
+   git checkout -b type/description
+   # Example: git checkout -b feat/site-deployment
+   ```
+
+   Branch type prefixes:
+   - `feat/` - New features
+   - `fix/` - Bug fixes
+   - `docs/` - Documentation changes
+   - `refactor/` - Code refactoring
+   - `test/` - Test-related changes
+   - `chore/` - Build process or tooling changes
+
+2. Make your changes following the code style guidelines
+3. Add tests for your changes (see test README for guidelines)
+4. Run the test suite:
+   ```bash
+   npm test:e2e
+   ```
+5. Run linter:
+   ```bash
+   npm run lint
+   ```
+6. Ensure all tests pass and the code is properly formatted
+7. Commit your changes with a descriptive message following the Conventional Commits format:
+   ```
+   type(scope): description
+   
+   [optional body]
+   [optional screenshots / videos]
+   [optional footer(s)]
+   ```
+8. Push your branch to your fork
+9. Open a pull request against the main branch
+
+## Testing
+
+All contributions must include appropriate tests. Follow these guidelines:
+- Write unit tests for new features
+- Ensure all tests pass before submitting a pull request
+- Update existing tests if your changes affect their behavior
+- Follow the existing test patterns and structure
+- Test across different environments when applicable
+
+## Pull Request Process
+
+1. Create a draft pull request early to facilitate discussion
+2. Reference any related issues in your PR description (e.g., 'Closes #123')
+3. Ensure all tests pass and the build is successful
+4. Update documentation as needed
+5. Keep your PR focused on a single feature or bug fix
+6. Be responsive to code review feedback
+
+## Code Style
+
+- Follow the existing code style
+- Use TypeScript types and interfaces effectively
+- Keep functions small and focused
+- Use meaningful variable and function names
+- Add comments for complex logic
 - Update relevant documentation when making API changes