feat: 데모 템플릿 수정

[baeyc0510]

feat: Enhance policy editor and add AI coding tool instructions

Overview

This PR enhances the policy editor with improved UX and adds automatic instructions file generation for AI coding tools during sym init.

Changes

1. AI Coding Tool Instructions Auto-Generation

When users register MCP servers during sym init, Symphony now automatically creates instructions files for AI coding tools to ensure they properly use Symphony conventions.

Supported Tools:

• Claude Code: Appends to claude.md
• Cursor: Creates .cursor/rules/symphony.mdc with MDC frontmatter
• VS Code Copilot: Creates .github/instructions/symphony.instructions.md with proper frontmatter

Instructions Content:

All instructions files include concise, essential guidelines:

1. Before Writing Code

   • Verify Symphony MCP server is active
   • Query conventions using symphony/query_conventions tool
   • Available categories: security, style, documentation, error_handling, architecture, performance, testing

2. After Writing Code

   • Validate all changes using symphony/validate_code tool
   • Fix violations before committing

2. Improved sym init Completion Message

Before:

• Verbose "Next steps" with git commands
• Dashboard info shown mid-process
• Interrupts setup flow

After:

• Concise dashboard usage guide
• Shows features: Manage roles, Edit policies, Test validation
• Displayed only after all initialization is complete (MCP + API key setup)

3. Policy Editor Enhancements

• Added demo template management
• Enhanced RBAC change detection
• Fixed file handling issues
• Removed auto-save feature for better control
• Improved policy editor UI stability

Technical Details

Files Modified

• internal/cmd/mcp_register.go - Added instructions generation logic (+187 lines)
• internal/cmd/init.go - Improved completion message and reordered output
• Policy editor UI enhancements (previous commits)

Implementation

Instructions Generation Flow:

MCP Registration
    ↓
Check if project-specific (not global)
    ↓
Create instructions file based on app type
    ↓
Check if file exists
    ↓
Append (Claude Code) or Create/Backup (others)

File Formats:

• Claude Code: Plain Markdown, appends if exists
• Cursor: MDC format with YAML frontmatter (globs, alwaysApply)
• VS Code: Instructions format with YAML frontmatter (applyTo pattern)

Testing

• Built successfully with make build
• All existing tests pass (failures are pre-existing Windows issues)
• Manual testing of sym init flow
• Instructions files generated correctly for each tool

Breaking Changes

None. All changes are backward compatible.

Documentation

Instructions files are auto-generated with inline documentation. Users can customize them after generation.

Screenshots/Examples

New sym init completion message:

🎯 What's Next: Use Symphony Dashboard

Start the web dashboard:
  sym dashboard

Dashboard features:
  📋 Manage roles - Add/remove team members, configure permissions
  📝 Edit policies - Create and modify coding conventions
  ✅ Test validation - Check rules against your code in real-time

After setup, commit and push .sym/ folder to share with your team.

Generated .cursor/rules/symphony.mdc:

---
description: Symphony code convention validation
globs:
  - "**/*"
alwaysApply: true
---

# Symphony Code Conventions

**This project uses Symphony MCP for code convention management.**

## Required Steps

### Before Code Generation
1. **Verify Symphony MCP is active** - If not available, stop and warn user
2. **Query conventions** - Use `symphony/query_conventions` with appropriate category and language

### After Code Generation
1. **Validate all changes** - Use `symphony/validate_code`
2. **Fix violations** - Address issues before committing
...