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-test-fix/SKILL.md

@@ -396,7 +396,7 @@ Automatic commits at key checkpoints:
 
 ## Post-Completion Expansion
 
-**Auto-sync**: Execute `/workflow:session:sync -y "{summary}"` to update project-guidelines + project-tech.
+**Auto-sync**: Execute `/workflow:session:sync -y "{summary}"` to update specs/*.md + project-tech.
 
 After completion, ask user if they want to expand into issues (test/enhance/refactor/doc). Selected items call `/issue:new "{summary} - {dimension}"`.
 

.claude/skills/workflow-test-fix/phases/02-test-context-gather.md

@@ -346,7 +346,7 @@ Execute complete context-search-agent workflow for implementation planning:
 ### Phase 1: Initialization & Pre-Analysis
 1. **Project State Loading**:
    - Read and parse .workflow/project-tech.json. Use its overview section as the foundational project_context.
-   - Read and parse .workflow/project-guidelines.json. Load conventions, constraints, and learnings into a project_guidelines section.
+   - Read and parse .workflow/specs/*.md. Load conventions, constraints, and learnings into a project_guidelines section.
    - If files don't exist, proceed with fresh analysis.
 2. **Detection**: Check for existing context-package (early exit if valid)
 3. **Foundation**: Initialize CodexLens, get project structure, load docs
@@ -381,7 +381,7 @@ Execute all discovery tracks (WITH USER INTENT INTEGRATION):
    c. Generate dependency_order: Based on dependency graph + user goal sequence
    d. Document sorting_rationale: Explain prioritization logic
 4. **Populate project_context**: Directly use the overview from project-tech.json
-5. **Populate project_guidelines**: Load from project-guidelines.json
+5. **Populate project_guidelines**: Load from specs/*.md
 6. Integrate brainstorm artifacts (if .brainstorming/ exists, read content)
 7. Perform conflict detection with risk assessment
 8. **Inject historical conflicts** from archive analysis into conflict_detection
@@ -403,7 +403,7 @@ Execute all discovery tracks (WITH USER INTENT INTEGRATION):
 Complete context-package.json with:
 - **metadata**: task_description, keywords, complexity, tech_stack, session_id
 - **project_context**: description, technology_stack, architecture, key_components (from project-tech.json)
-- **project_guidelines**: {conventions, constraints, quality_rules, learnings} (from project-guidelines.json)
+- **project_guidelines**: {conventions, constraints, quality_rules, learnings} (from specs/*.md)
 - **assets**: {documentation[], source_code[], config[], tests[]} with relevance scores
 - **dependencies**: {internal[], external[]} with dependency graph
 - **brainstorm_artifacts**: {guidance_specification, role_analyses[], synthesis_output} with content

.claude/skills/workflow-test-fix/phases/05-test-cycle-execute.md

@@ -245,7 +245,7 @@ Task(
 
     ## PROJECT CONTEXT (MANDATORY)
     1. Read: .workflow/project-tech.json (tech stack, test framework, build system)
-    2. Read: .workflow/project-guidelines.json (constraints — apply as HARD CONSTRAINTS on fixes)
+    2. Read: .workflow/specs/*.md (constraints — apply as HARD CONSTRAINTS on fixes)
 
     ## MANDATORY FIRST STEPS
     1. Read test results: ${session.test_results_path}
@@ -454,7 +454,7 @@ The orchestrator automatically creates git commits at key checkpoints to enable
 
 #### Post-Completion Expansion
 
-**Auto-sync**: 执行 `/workflow:session:sync -y "{summary}"` 更新 project-guidelines + project-tech。
+**Auto-sync**: 执行 `/workflow:session:sync -y "{summary}"` 更新 specs/*.md + project-tech。
 
 完成后询问用户是否扩展为issue(test/enhance/refactor/doc)，选中项调用 `/issue:new "{summary} - {dimension}"`