feat: add SpecDialog component for editing spec frontmatter

- Implement SpecDialog for managing spec details including title, read mode, priority, and keywords.
- Add validation and keyword management functionality.
- Integrate SpecDialog into SpecsSettingsPage for editing specs.

feat: create index file for specs components

- Export SpecCard, SpecDialog, and related types from a new index file for better organization.

feat: implement SpecsSettingsPage for managing specs and hooks

- Create main settings page with tabs for Project Specs, Personal Specs, Hooks, Injection, and Settings.
- Integrate SpecDialog and HookDialog for editing specs and hooks.
- Add search functionality and mock data for specs and hooks.

feat: add spec management API routes

- Implement API endpoints for listing specs, getting spec details, updating frontmatter, rebuilding indices, and initializing the spec system.
- Handle errors and responses appropriately for each endpoint.

.claude/skills/team-lifecycle-v3/roles/analyst/role.md

@@ -93,9 +93,14 @@ EXPECTED: JSON with: problem_statement, target_users[], domain, constraints[], e
 **discovery-context.json** → `<session-folder>/spec/discovery-context.json`:
 - session_id, phase=1, seed_analysis (all fields), codebase_context (or null), recommendations
 
+**design-intelligence.json** → `<session-folder>/analysis/design-intelligence.json` (UI mode only):
+- Produced when frontend keywords detected (component, page, UI, React, Vue, CSS, 前端) in seed_analysis
+- Fields: industry, style_direction, ux_patterns, color_strategy, typography, component_patterns
+- Consumed by architect (for design-tokens.json) and fe-developer
+
 **Report**: complexity, codebase presence, problem statement, exploration dimensions, output paths.
 
-**Success**: Both JSON files created, report sent.
+**Success**: Both JSON files created; design-intelligence.json created if UI mode.
 
 ---