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/workflow-plan/phases/02-context-gathering.md

@@ -203,10 +203,10 @@ This is the PRIMARY context source - all subsequent analysis must align with use
 Execute complete context-search-agent workflow (Phase 1-3) for implementation planning.
 
 Key emphasis:
-- Load project-tech.json and project-guidelines.json FIRST (per your spec Phase 1.1b)
+- Load project-tech.json and specs/*.md FIRST (per your spec Phase 1.1b)
 - Synthesize exploration results with project context
 - Generate prioritized_context with user_intent alignment
-- Apply project-guidelines.json constraints during conflict detection
+- Apply specs/*.md constraints during conflict detection
 
 Input priority: User Intent > project-tech.json > Exploration results > Code discovery > Web examples