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-multi-cli-plan/SKILL.md

@@ -102,14 +102,14 @@ After collecting preferences, enhance context and dispatch:
 ```javascript
 // Step 1: Check for project context files
 const hasProjectTech = fileExists('.workflow/project-tech.json')
-const hasProjectGuidelines = fileExists('.workflow/project-guidelines.json')
+const hasProjectGuidelines = fileExists('.workflow/specs/*.md')
 
 // Step 2: Log available context
 if (hasProjectTech) {
   console.log('Project tech context available: .workflow/project-tech.json')
 }
 if (hasProjectGuidelines) {
-  console.log('Project guidelines available: .workflow/project-guidelines.json')
+  console.log('Project guidelines available: .workflow/specs/*.md')
 }
 
 // Step 3: Dispatch to phase (workflowPreferences available as context)

.claude/skills/workflow-multi-cli-plan/phases/01-multi-cli-plan.md

@@ -373,7 +373,7 @@ ${JSON.stringify(contextPackage, null, 2)}
 
 ## Execution Process
 1. Read plan-overview-base-schema.json + task-schema.json for output structure
-2. Read project-tech.json and project-guidelines.json
+2. Read project-tech.json and specs/*.md
 3. Parse context-package fields:
    - solution: name, feasibility, summary
    - implementation_plan: tasks[], execution_flow, milestones

.claude/skills/workflow-multi-cli-plan/phases/02-lite-execute.md

@@ -487,7 +487,7 @@ ${(t.test?.success_metrics || []).length > 0 ? `\n**Success metrics**: ${t.test.
     context.push(`### Artifacts\nPlan: ${executionContext.session.artifacts.plan}`)
   }
   // Project guidelines (user-defined constraints from /workflow:session:solidify)
-  context.push(`### Project Guidelines\n@.workflow/project-guidelines.json`)
+  context.push(`### Project Guidelines\n@.workflow/specs/*.md`)
   if (context.length > 0) sections.push(`## Context\n${context.join('\n\n')}`)
 
   sections.push(`Complete each task according to its "Done when" checklist.`)
@@ -672,7 +672,7 @@ if (hasUnresolvedIssues(reviewResult)) {
 
 **Trigger**: After all executions complete (regardless of code review)
 
-**Operation**: Execute `/workflow:session:sync -y "{summary}"` to update both `project-guidelines.json` and `project-tech.json` in one shot.
+**Operation**: Execute `/workflow:session:sync -y "{summary}"` to update both `specs/*.md` and `project-tech.json` in one shot.
 
 Summary 取值优先级：`originalUserInput` → `planObject.summary` → git log 自动推断。
 
@@ -767,7 +767,7 @@ Appended to `previousExecutionResults` array for context continuity in multi-exe
 
 ## Post-Completion Expansion
 
-**Auto-sync**: 执行 `/workflow:session:sync -y "{summary}"` 更新 project-guidelines + project-tech（Step 6 已触发，此处不重复）。
+**Auto-sync**: 执行 `/workflow:session:sync -y "{summary}"` 更新 specs/*.md + project-tech（Step 6 已触发，此处不重复）。
 
 完成后询问用户是否扩展为issue(test/enhance/refactor/doc)，选中项调用 `/issue:new "{summary} - {dimension}"`