insforge__insforge-skills/AGENTS.md

AI Agent Guidance

This document helps AI coding agents work effectively with the InsForge Agent Skills repository.

Repository Structure

agent-skills/
├── skills/
│   └── insforge/           # InsForge BaaS development skill
│       ├── SKILL.md        # Skill manifest and overview
│       ├── database/       # Database operations
│       ├── auth/           # Authentication flows
│       ├── storage/        # File storage
│       ├── functions/      # Serverless functions
│       ├── ai/             # AI/ML operations
│       ├── realtime/       # Real-time messaging
│       ├── payments/       # Stripe and Razorpay app payment flows
│       └── email/          # Transactional email
│   └── insforge-cli/       # InsForge CLI project management
│       ├── SKILL.md        # Skill manifest and command reference
│       └── references/     # CLI command reference
│           ├── database/   # Database migrations, query, RLS, vector, import/export
│           ├── auth.md
│           ├── create.md
│           ├── login.md
│           ├── functions-deploy.md
│           ├── payments/   # Shared payments routing plus provider references
│           │   ├── overview.md
│           │   ├── stripe.md
│           │   └── razorpay.md
│           ├── deployments/
│           │   ├── deploy.md
│           │   └── domains.md
│           └── ...
├── AGENTS.md               # This file
├── CONTRIBUTING.md         # Contribution guidelines
├── LICENSE                 # Apache License 2.0
└── README.md               # Repository documentation

Skill Format

This repository follows the Agent Skills Open Standard.

SKILL.md Structure

Each skill contains a SKILL.md with:

1. YAML Frontmatter: Required name and description fields, optional license. No metadata: block — the OpenAI plugin submission portal rejects it; interface settings go in the skill's agents/openai.yaml
2. Markdown Body: Instructions, examples, and references to module documentation

Documentation Pattern

Most InsForge skill modules use focused app-facing guides:

File	Purpose	When to Use
sdk-integration.md	App-facing SDK/API usage, usually through @insforge/sdk	Implementing features in user's app code
Specialized guides such as storage/postgres-rls.md, s3-gateway.md, CLI references like references/database/access-control.md, references/database/integrity.md, references/database/vector.md, or payment provider files	Backend, security, payment-provider, protocol, or infrastructure-specific patterns	When the task needs that capability

The AI module is capability-based instead: start at skills/insforge/ai/overview.md, then load only the needed OpenRouter guide (chat-completions.md, image-generation.md, video-generation.md, audio.md, embeddings-and-rag.md, or models-list.md).

Working with This Repository

Adding a New Module

1. Create a directory under skills/insforge/ with the module name
2. Add sdk-integration.md for client-side SDK usage, or use a focused capability guide when the module spans multiple APIs
3. Add specialized guides only when a capability needs separate backend, security, protocol, or workflow documentation
4. Update the module reference table in skills/insforge/SKILL.md

For payments, keep app guides provider-specific (payments/stripe.md, payments/razorpay.md) and keep CLI routing/provider docs in skills/insforge-cli/references/payments/.

Updating Existing Documentation

1. Locate the relevant file in the module directory
2. Maintain the existing format: Setup, Usage Examples, Best Practices, Common Mistakes
3. Keep code examples concise and runnable
4. Include both correct and incorrect examples where helpful

Validation Checklist

Before committing changes:

• SKILL.md frontmatter is valid YAML
• Skill name matches directory name (lowercase, hyphens only)
• Description is clear and includes keywords for agent discovery
• Code examples are syntactically correct
• All internal links are valid relative paths

Key InsForge Patterns

When working with InsForge skills, remember:

1. Backend First: Most features require backend configuration before SDK integration
2. Metadata Endpoint: Always fetch /api/metadata before making changes
3. Auth References: Use auth.users(id) for user foreign keys, auth.uid() in RLS policies
4. Auth Profile Metadata: auth.users.profile is JSONB; read profile->>'name' / profile->>'avatar_url' in triggers.
5. Array Inserts: Database inserts require array format: insert([{...}])
6. Storage Keys: Save both url and key for storage operations