Skill: gatonegroialab/la-local-chat (version 1.0.0)

--- name: la-local-chat description: Operate and improve the La Local location-management chat product. Use when reviewing or changing the frontend chat app, backend webhook, search behavior, media upload flow, Notion/Dropbox integration, deployment topology, or project-specific product logic for La Local. --- # La Local Chat Operate and improve the La Local chat product with one guiding rule: - treat **search** as the main area for AI-assisted improvement - keep **create/update** deterministic, explicit, and safe ## Core behavior ### Search - Search by name, description, and relevant location context. - Return up to 5 real matches. - Never invent locations. - Prefer structured retrieval and ranking over freeform generation. - Improve relevance before adding sophistication. ### Create - Ask for the location name first. - Create the Notion record immediately. - Use the Notion-generated ID as the Dropbox folder reference. - Continue field gathering in a guided flow. ### Update - Update by name or ID. - Confirm the target record when ambiguity exists. - Prefer deterministic field handling over freeform model behavior. ## Working rules - Preserve `thread_id` in chat and upload flows. - Treat Notion as the source of truth for the record. - Keep Dropbox folder linkage tied to the Notion ID. - Prefer incremental, testable changes over rewrites. - Do not regress create/update flows while improving search. ## References - Read `references/architecture.md` for the current system shape. - Read `references/search-notes.md` when working on search quality or ranking behavior.

path: references/architecture.md
content: # Architecture

## Product
La Local is a chat-style system for searching, creating, and updating audiovisual locations.

## Current stack
### Frontend
- Repo: `GatoNegroIaLAB/lalocal-chat`
- Deploy: Vercel
- Role: UI + proxy/BFF

### Backend
- Repo: `GatoNegroIaLAB/lalocal-webhook`
- Runtime: EasyPanel / AWS
- Role: chat orchestration, uploads, create/update flows, Notion integration, Dropbox integration, history

## Architecture rules
- Preserve `thread_id` through proxied chat and upload flows.
- Treat Notion as the source of truth.
- Tie Dropbox folder creation to the Notion-generated ID.
- Keep create/update deterministic.
- Focus AI improvement effort primarily on search.


path: references/search-notes.md
content: # Search Notes

## Current product direction
Search is the best candidate for AI-assisted improvement.

## Recommended pattern
1. Detect search intent.
2. Parse criteria.
3. Retrieve real candidates from source data.
4. Rank or rerank.
5. Return up to 5 strong matches.
6. Allow follow-up for technical sheet detail.

## Search rules
- Never invent locations.
- Weight location strongly when the query implies zone/city/sector.
- Use name, location, description, and architecture as meaningful signals.
- Avoid padding results with weak filler matches.
- Improve incrementally from real team queries.

## Open search questions
- Which real prompts recur most often?
- Which fields are most reliable for weighting?
- Should search stay on direct retrieval first or move toward an index layer later?


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)