- Created HS DollyCam HUD user manual (v1.3.0) detailing features, setup, commands, and troubleshooting. - Added FOV extension manual outlining FOV commands, usage in playlists, and dollyzoom functionality. - Introduced project context file for AI agents, specifying technology stack, critical implementation rules, and existing patterns.
2.4 KiB
2.4 KiB
| project_name | user_name | date | sections_completed | existing_patterns_found | |||
|---|---|---|---|---|---|---|---|
| HS_DollyCam | mita | Wed May 06 2026 |
|
7 |
Project Context for AI Agents
This file contains critical rules and patterns that AI agents must follow when implementing code in this project. Focus on unobvious details that agents might otherwise miss.
Technology Stack & Versions
- Language: LSL (Linden Scripting Language)
- Platform: Second Life
- Core Communication:
llMessageLinked(Linkset Message) - Configuration:
.propertiesfiles (e.g.,HS_CamEngine.properties) - Key Components: Specialized LSL scripts (
Controller,Playlist,imEngineTour,Core, etc.)
Critical Implementation Rules
- Memory Management (CRITICAL):
- Avoid large or mixed-type lists to prevent memory pressure.
- Minimize the use of
llParseString2Listin hot paths (e.g., timer events or frequentllMessageLinkedreceivers). - Use targeted parsing (token-based or separator-based) for payloads like
CE_INT_SET_CAM. - Prefer short-lived data and targeted field extraction.
- Communication Protocol:
- Adhere to the defined
CE_INT_*andCE_CMD_*constants for inter-script communication. - Use
llRegionSayTofor marker communication when the target key is known to reduce region-wide listener wakeups.
- Adhere to the defined
- Parsing & Data Handling:
- For high-frequency updates (e.g., camera frames), use optimized parsing helpers as seen in
HS_CamEngineCore.lsl. - When reading presets, avoid full string splitting if only a subset of fields is required.
- For high-frequency updates (e.g., camera frames), use optimized parsing helpers as seen in
- Workflow Constraints:
- Keep continuous tour runtime lists in script memory (
HS_CamEngineTour.lsl) rather than Linkset Data to ensure performance during timer ticks.
- Keep continuous tour runtime lists in script memory (
Existing Patterns & Conventions
- Naming Conventions:
- Scripts follow the
HS_Cam[Name].lslpattern. - Communication constants use the
CE_CMD_,CE_INT_,MN_CMD, etc., prefixes.
- Scripts follow the
- Code Organization:
- Modules are split by responsibility (Controller, Playlist, Engine, etc.).
- Use specialized helper scripts for secondary workflows (e.s.
HS_CamTourCommands.lsl) to reduce memory pressure on main scripts.
- Error Handling/Validation:
- Local checks should include brace-balance and conflict marker searches.
- Use targeted
rgscans to detect accidental reintroductions of inefficientllParseString2Listcalls.