Prompt file imported from psychicDree/PirateTileClash (.cursor/commands/update-project-docs.md). Copyright stays with the author.

update-project-docs

/**

• /update-project-docs
• Automates the process of updating project documentation and AI guidance whenever a significant architectural change occurs in the Pirate Tile Clash Unity project.
• Ensures that @Assets/Game/Docs (dev plan, architecture, feature docs), and all custom AI support (rules, skills, subagents, and commands in .cursor) are synchronized and accurately reflect the current architecture.
• Instructions to the agent:
• 1. Detect when any code change affects architectural structures or folder layout in Assets/Game/Scripts (e.g., adding/removing core systems, moving managers, integrating new services, or modifying scene structure).
• 2. For each detected architectural change:
• • Summarize the change (what system/component was added/removed/changed and why).
• • Propose additions or updates to documentation in @Assets/Game/Docs (architecture diagrams, system overviews, folder descriptions, or dev plan features).
• • Identify any .cursor/rules/, .cursor/skills/, .cursor/subagents/, and .cursor/commands/ files needing modification to maintain alignment with the new architecture.
• 3. Generate concrete actionable updates:
• • Explicitly state which documentation files to update and what the update should include.
• • List the rules/skills/subagents/commands to edit, add, or remove, with specific suggestions for content changes.
• 4. Output all recommendations in an actionable, checklist-style markdown format (including code/doc snippets if relevant).
• 5. If complex or broad changes occur, recommend reviewing the associated SKILL.md or AGENTS.md for persistent guidance.
• Example output:

• Project Docs & AI Guidance Update Checklist

• Detected Architectural Change: Added Core/Managers/FriendsManager.cs and refactored scene group structure.
• 1. Update Docs/Architecture.md:
• • Add FriendsManager to the Managers section
• • Note new scene group structure under Scene Management
• 2. Edit .cursor/rules/pirate-tile-clash-architecture.mdc:
• • Add rules on FriendsManager singleton pattern and service registration
• 3. Update .cursor/skills/:
• • Create/modify skill describing Friends system and API usage
• 4. Adjust .cursor/commands/:
• • Suggest new /list-friends command for AI support
• 5. Review .cursor/agents/pirate-tile-clash-expert.md:
• • Update codebase overview and feature list
• Always ensure docs, AI rules, and codebase helpers remain in-sync and up-to-date after architectural evolution. All recommendations must be tailored for Pirate Tile Clash and follow coding/project documentation best practices. */

Write your command content here.

This command will be available in chat with /update-project-docs