docs: add opportunity state management and schema discovery to local-env skill

- Add OpportunityState enum values (DRAFT=1, LIVE=2, CLOSED=3, IN_REVIEW=4)
- Add SQL examples for updating opportunity state
- Add section on discovering schema info for unfamiliar cases
- Document common gotchas (column naming, integer enums, JSONB, quoted columns)

Author: idoshamun

.claude/skills/local-env/SKILL.md

@@ -107,6 +107,36 @@ UPDATE opportunity SET flags = flags - 'plan' - 'batchSize'
 WHERE id = 'OPPORTUNITY_ID';
 ```
 
+## Opportunity State Management
+
+The `opportunity` table uses a `state` column (integer) to track lifecycle status. Values come from `OpportunityState` enum in `@dailydotdev/schema`.
+
+### OpportunityState Values
+
+| Value | Name | Description |
+|-------|------|-------------|
+| 0 | UNSPECIFIED | Default/unset |
+| 1 | DRAFT | Not yet published |
+| 2 | LIVE | Active and visible |
+| 3 | CLOSED | No longer active |
+| 4 | IN_REVIEW | Pending review |
+
+### Update Opportunity State
+
+```sql
+-- Set to LIVE
+UPDATE opportunity SET state = 2 WHERE id = 'OPPORTUNITY_ID' RETURNING id, state, title;
+
+-- Set to DRAFT
+UPDATE opportunity SET state = 1 WHERE id = 'OPPORTUNITY_ID' RETURNING id, state, title;
+
+-- Set to CLOSED
+UPDATE opportunity SET state = 3 WHERE id = 'OPPORTUNITY_ID' RETURNING id, state, title;
+
+-- Set to IN_REVIEW
+UPDATE opportunity SET state = 4 WHERE id = 'OPPORTUNITY_ID' RETURNING id, state, title;
+```
+
 ## Instructions
 
 When the user asks for local environment help:
@@ -122,6 +152,57 @@ Common requests:
 - "Run SQL: ..." → Execute via docker
 - "Reset payment for X" → Run reset queries
 - "Check subscription for X" → Query and display current state
+- "Update opp X to live/draft/closed" → Update opportunity state
+
+## Discovering Schema Information
+
+When handling requests not covered in this skill, use these techniques to discover the correct schema:
+
+### 1. Check Entity Definitions
+
+Entity files define column names and types:
+```bash
+# Find the entity file
+grep -r "TableName" src/entity/ --include="*.ts"
+# Read the entity to see column definitions
+```
+
+Key location: `src/entity/` - TypeORM entities with `@Column` decorators show actual DB column names.
+
+### 2. Find Enum Values
+
+Many columns use integer enums from `@dailydotdev/schema`. To find enum values:
+
+```bash
+# Search for enum usage in codebase
+grep -r "EnumName\." src/ --include="*.ts" | head -20
+
+# Find enum definition in schema package
+grep -r "EnumName" node_modules/@dailydotdev/schema/dist/ --include="*.d.ts"
+```
+
+Common enum locations: `node_modules/@dailydotdev/schema/dist/daily-api/*_pb.d.ts`
+
+### 3. Query Existing Data
+
+When unsure about column names or values:
+```sql
+-- Check table structure
+\d tablename
+
+-- See existing values
+SELECT DISTINCT column_name FROM tablename LIMIT 10;
+
+-- Inspect a specific row
+SELECT * FROM tablename WHERE id = 'xxx' LIMIT 1;
+```
+
+### 4. Common Gotchas
+
+- **Column naming**: Entity property names may differ from DB columns (e.g., `state` not `status`)
+- **Integer enums**: Many "status" fields are integers, not strings - find the enum definition
+- **JSONB fields**: Use `jsonb_build_object()` for updates, `->` or `->>` for queries
+- **Quoted columns**: PostgreSQL requires double quotes for camelCase columns (e.g., `"organizationId"`)
 
 ## Continuous Improvement