Add comprehensive documentation for ObjectStack schema rules

- Introduced detailed guides for data lifecycle hooks, indexing strategies, naming conventions, relationship patterns, and validation rules.
- Created a structure for evaluation tests to validate adherence to defined rules.
- Added view types and patterns documentation for UI design in ObjectStack.
- Included examples, best practices, and common mistakes for each rule type to enhance understanding and implementation.

Author: hotlong

.agents/skills/objectstack-ai/evals/README.md

@@ -0,0 +1,46 @@
+# Evaluation Tests (evals/)
+
+This directory is reserved for future skill evaluation tests.
+
+## Purpose
+
+Evaluation tests (evals) validate that AI assistants correctly understand and apply the rules defined in this skill when generating code or providing guidance.
+
+## Structure
+
+When implemented, evals will follow this structure:
+
+```
+evals/
+├── naming/
+│   ├── test-object-names.md
+│   ├── test-field-keys.md
+│   └── test-option-values.md
+├── relationships/
+│   ├── test-lookup-vs-master-detail.md
+│   └── test-junction-patterns.md
+├── validation/
+│   ├── test-script-inversion.md
+│   └── test-state-machine.md
+└── ...
+```
+
+## Format
+
+Each eval file will contain:
+1. **Scenario** — Description of the task
+2. **Expected Output** — Correct implementation
+3. **Common Mistakes** — Incorrect patterns to avoid
+4. **Validation Criteria** — How to score the output
+
+## Status
+
+⚠️ **Not yet implemented** — This is a placeholder for future development.
+
+## Contributing
+
+When adding evals:
+1. Each eval should test a single, specific rule or pattern
+2. Include both positive (correct) and negative (incorrect) examples
+3. Reference the corresponding rule file in `rules/`
+4. Use realistic scenarios from actual ObjectStack projects

.agents/skills/objectstack-ai/rules/agent-patterns.md

@@ -0,0 +1,69 @@
+# Agent Design Patterns
+
+Guide for designing AI agents in ObjectStack.
+
+## Agent Types
+
+- **Data Chat** — Natural language query interface for data
+- **Metadata Assistant** — Schema design and modification helper
+- **Custom Agents** — Domain-specific AI assistants
+
+## Agent Configuration
+
+```typescript
+{
+  name: 'customer_support_agent',
+  model: 'gpt-4',
+  systemPrompt: 'You are a helpful customer support agent...',
+  tools: ['query_records', 'create_record', 'send_email'],
+  context: {
+    objects: ['account', 'contact', 'case'],
+  },
+}
+```
+
+## Tool Definition
+
+```typescript
+{
+  name: 'query_records',
+  description: 'Query records from an object',
+  parameters: {
+    object: { type: 'string', required: true },
+    filter: { type: 'object' },
+    limit: { type: 'number', default: 10 },
+  },
+}
+```
+
+## Incorrect vs Correct
+
+### ❌ Incorrect — Vague Tool Description
+
+```typescript
+{
+  name: 'get_data',  // ❌ Vague name
+  description: 'Gets data',  // ❌ Vague description
+}
+```
+
+### ✅ Correct — Clear Tool Definition
+
+```typescript
+{
+  name: 'query_account_records',  // ✅ Specific name
+  description: 'Query account records with optional filters and pagination',  // ✅ Clear description
+}
+```
+
+## Best Practices
+
+1. **Use clear, descriptive tool names** — Agent must understand purpose
+2. **Provide detailed tool descriptions** — Include examples
+3. **Limit tool count** — 5-10 tools per agent max
+4. **Define parameter schemas** — Validate input
+5. **Handle errors gracefully** — Return user-friendly messages
+
+---
+
+See parent skill for complete documentation: [../SKILL.md](../SKILL.md)