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

@@ -222,7 +222,7 @@ Execute complete context-search-agent workflow for TDD 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
@@ -257,7 +257,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
@@ -279,7 +279,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-tdd/phases/05-tdd-task-generation.md

@@ -236,13 +236,13 @@ These files provide project-level constraints that apply to ALL tasks:
    - Usage: Populate plan.json shared_context, align task tech choices, set correct test commands
    - If missing: Fall back to context-package.project_context
 
-2. **.workflow/project-guidelines.json** (user-maintained rules and constraints)
+2. **.workflow/specs/*.md** (user-maintained rules and constraints)
    - Contains: coding_conventions, naming_rules, forbidden_patterns, quality_gates, custom_constraints
    - Usage: Apply as HARD CONSTRAINTS on all generated tasks — task implementation steps,
      acceptance criteria, and convergence.verification MUST respect these guidelines
    - If empty/missing: No additional constraints (proceed normally)
 
-Loading order: project-tech.json → project-guidelines.json → planning-notes.md → context-package.json
+Loading order: project-tech.json → specs/*.md → planning-notes.md → context-package.json
 
 ## USER CONFIGURATION (from Phase 0)
 Execution Method: ${userConfig.executionMethod}  // agent|hybrid|cli