@sallmarta/eye-hate-agent 1.0.3 → 1.0.5

package/src/engine/skill-registry.js

@@ -4,57 +4,62 @@ const SKILL_DEFINITIONS = {
   'system-analysis': {
     id: 'system-analysis',
     commandName: 'system-analysis',
-    repoRelativePath: path.join('docs', 'templates', 'skills', 'architecture', 'system-analysis', 'SKILL.md'),
+    repoRelativePath: path.join('docs', 'templates', 'skills', 'system-analysis', 'SKILL.md'),
   },
   'api-design': {
     id: 'api-design',
     commandName: 'api-design',
-    repoRelativePath: path.join('docs', 'templates', 'skills', 'architecture', 'api-design', 'SKILL.md'),
+    repoRelativePath: path.join('docs', 'templates', 'skills', 'api-design', 'SKILL.md'),
   },
   'db-schema-design': {
     id: 'db-schema-design',
     commandName: 'db-schema-design',
-    repoRelativePath: path.join('docs', 'templates', 'skills', 'architecture', 'db-schema-design', 'SKILL.md'),
+    repoRelativePath: path.join('docs', 'templates', 'skills', 'db-schema-design', 'SKILL.md'),
   },
-  'test-authoring': {
-    id: 'test-authoring',
-    commandName: 'test-authoring',
-    repoRelativePath: path.join('docs', 'templates', 'skills', 'engineering', 'test-authoring', 'SKILL.md'),
+  'ui-ux-design': {
+    id: 'ui-ux-design',
+    commandName: 'ui-ux-design',
+    repoRelativePath: path.join('docs', 'templates', 'skills', 'ui-ux-design', 'SKILL.md'),
   },
-  'ui-ux-implementation': {
-    id: 'ui-ux-implementation',
-    commandName: 'ui-ux-implementation',
-    repoRelativePath: path.join('docs', 'templates', 'skills', 'engineering', 'ui-ux-implementation', 'SKILL.md'),
+  'wireframing': {
+    id: 'wireframing',
+    commandName: 'wireframing',
+    repoRelativePath: path.join('docs', 'templates', 'skills', 'wireframing', 'SKILL.md'),
   },
-  'refactor-specialist': {
-    id: 'refactor-specialist',
-    commandName: 'refactor-specialist',
-    repoRelativePath: path.join('docs', 'templates', 'skills', 'engineering', 'refactor-specialist', 'SKILL.md'),
+  'code-audit': {
+    id: 'code-audit',
+    commandName: 'code-audit',
+    repoRelativePath: path.join('docs', 'templates', 'skills', 'code-audit', 'SKILL.md'),
+  },
+  'parity-audit': {
+    id: 'parity-audit',
+    commandName: 'parity-audit',
+    repoRelativePath: path.join('docs', 'templates', 'skills', 'parity-audit', 'SKILL.md'),
   },
   'security-audit': {
     id: 'security-audit',
     commandName: 'security-audit',
-    repoRelativePath: path.join('docs', 'templates', 'skills', 'auditing', 'security-audit', 'SKILL.md'),
+    repoRelativePath: path.join('docs', 'templates', 'skills', 'security-audit', 'SKILL.md'),
   },
-  'full-verification': {
-    id: 'full-verification',
-    commandName: 'full-verification',
-    repoRelativePath: path.join('docs', 'templates', 'skills', 'auditing', 'full-verification', 'SKILL.md'),
+  'system-tester': {
+    id: 'system-tester',
+    commandName: 'system-tester',
+    repoRelativePath: path.join('docs', 'templates', 'skills', 'system-tester', 'SKILL.md'),
   },
-  'parity': {
-    id: 'parity',
-    commandName: 'parity',
-    repoRelativePath: path.join('docs', 'templates', 'skills', 'auditing', 'parity', 'SKILL.md'),
+  'devops-ci-cd': {
+    id: 'devops-ci-cd',
+    commandName: 'devops-ci-cd',
+    repoRelativePath: path.join('docs', 'templates', 'skills', 'devops-ci-cd', 'SKILL.md'),
   },
-  'ci-cd-authoring': {
-    id: 'ci-cd-authoring',
-    commandName: 'ci-cd-authoring',
-    repoRelativePath: path.join('docs', 'templates', 'skills', 'operations', 'ci-cd-authoring', 'SKILL.md'),
+  'observability': {
+    id: 'observability',
+    commandName: 'observability',
+    repoRelativePath: path.join('docs', 'templates', 'skills', 'observability', 'SKILL.md'),
   },
-  'observability-setup': {
-    id: 'observability-setup',
-    commandName: 'observability-setup',
-    repoRelativePath: path.join('docs', 'templates', 'skills', 'operations', 'observability-setup', 'SKILL.md'),
+  'refactor': {
+    id: 'refactor',
+    commandName: 'refactor',
+    repoRelativePath: path.join('docs', 'templates', 'skills', 'refactor', 'SKILL.md'),
   },
 };
 

package/docs/templates/project-docs-template/foundation/architecture.md

@@ -1,79 +0,0 @@
-# Architecture
-
-Last update: YYYY-MM-DD
-
-Status: [Proposed | Draft | Live | Deprecated | Archived]
-
----
-
-## 1. Description
-Briefly describe the purpose of this document and what it contains.
-
-## 2. Important
-Notes of important findings or critical constraints. Can be empty.
-
-## 3. Table of Contents
-[Generate a hyperlinked table of contents here containing ALL headings in this file (1 through N). Use standard markdown links, e.g., - [1. Description](#1-description)]
-
-## 4. Scope
-The boundaries of what this document covers.
-
-## 5. Goals
-What we aim to achieve with this specific document.
-
-## 6. Non Goals
-What is explicitly excluded from the scope of this document.
-
-## 7. Tech Stack Overview
-| Area | Choice | Notes |
-| --- | --- | --- |
-| Application or service | TBD | |
-| Runtime or platform | TBD | |
-| Storage | TBD | |
-| External integrations | TBD | |
-
-## 8. Architecture Pattern
-Describe architecture design pattern, system topology, component boundaries, and foundational control flow.
-
-## 9. System Flow
-General overview of how the system work from start to end. Diagram or flowchart visual are preferred. Use mermaid.
-
-```mermaid
-graph TD
-    A[Start] --> B{Decision}
-    B -- Yes --> C[Result 1]
-    B -- No --> D[Result 2]
-```
-
-## 10. Data Flow
-General overview of inter-feature data flow, mapped against architectural patterns and system flow. Diagram or flowchart visual are preferred. Use mermaid.
-
-```mermaid
-sequenceDiagram
-    participant User
-    participant System
-    User->>System: Data Request
-    System-->>User: Data Response
-```
-
-## 11. Tools Integration
-Such as hardware or software or external api and relevant tools. Can be empty.
-
-| Integration | Purpose | Kind | Notes |
-| --- | --- | --- | --- |
-| TBD | TBD | TBD | *Software/Hardware/APIs/Other* |
-
-## 12. Global Parameters and Constraints
-Detail the system's global restrictions, such as performance requirements, caching policies, and error-handling mechanisms (e.g., "Supports offline execution for core features" or "Memory footprint restricted to 50MB").
-
-## 13. Architecture Decision Records (ADRs)
-A collection of ADRs documenting the rationale behind technical decision (e.g., "Choosing React over Vue for state management flexibility" or "Adopting Domain-Driven Design to leverage bounded contexts").
-
-## 14. Success Metrics
-How we measure if the goals of this document are achieved.
-
-## 15. Related Documents
-[Link to related document](path) - Short brief note about why it's related (e.g., [Guidelines](path) - technical implementation rules).
-
-## 16. Open Questions
-Unresolved architectural questions or assumptions. Can be empty.

package/docs/templates/project-docs-template/foundation/changelog.md

@@ -1,53 +0,0 @@
-# System Name Changelog
-
-Last update: YYYY-MM-DD
-
-Status: [Proposed | Draft | Live | Deprecated | Archived]
-
----
-
-## 1. Description
-Briefly describe the purpose of this document and what it contains.
-
-## 2. Important
-Notes of important findings or critical constraints. Can be empty.
-
-## 3. Table of Contents
-[Generate a hyperlinked table of contents here containing ALL headings in this file (1 through N). Use standard markdown links, e.g., - [1. Description](#1-description)]
-
-## 4. Scope
-The boundaries of what this document covers.
-
-## 5. Goals
-What we aim to achieve with this specific document.
-
-## 6. Non Goals
-What is explicitly excluded from the scope of this document.
-
-## 7. [Unreleased]
-### 7.1. Added
-TBD
-
-### 7.2. Changed
-TBD
-
-### 7.3. Deprecated
-TBD
-
-### 7.4. Removed
-TBD
-
-### 7.5. Fixed
-TBD
-
-### 7.6. Security
-TBD
-
-## 8. Success Metrics
-How we measure if the goals of this document are achieved.
-
-## 9. Related Documents
-[Link to related document](path) - Short brief note about why it's related.
-
-## 10. Open Questions
-Any unresolved questions or assumptions. Can be empty.

package/docs/templates/project-docs-template/foundation/feature-inventory.md

@@ -1,46 +0,0 @@
-# Feature Inventory
-
-Last update: YYYY-MM-DD
-
-Status: [Proposed | Draft | Live | Deprecated | Archived]
-
----
-
-## 1. Description
-Briefly describe the purpose of this document and what it contains.
-
-## 2. Important
-Notes of important findings or critical constraints. Can be empty.
-
-## 3. Table of Contents
-[Generate a hyperlinked table of contents here containing ALL headings in this file (1 through N). Use standard markdown links, e.g., - [1. Description](#1-description)]
-
-## 4. Scope
-The boundaries of what this document covers.
-
-## 5. Goals
-What we aim to achieve with this specific document.
-
-## 6. Non Goals
-What is explicitly excluded from the scope of this document.
-
-## 7. Feature Summary
-High-level overview of the active feature set.
-
-## 8. Core Functions (Epic-level)
-Major active functional blocks mapping directly to code.
-
-## 9. Sub-Functions (Task-level)
-Granular interactions and capabilities currently live.
-
-## 10. Deprecated / Removed Features
-Historical record of retired capabilities.
-
-## 11. Success Metrics
-How we measure if the goals of this document are achieved.
-
-## 12. Related Documents
-[Link to related document](path) - Short brief note about why it's related.
-
-## 13. Open Questions
-Any unresolved questions or assumptions. Can be empty.

package/docs/templates/project-docs-template/foundation/phases.md

@@ -1,60 +0,0 @@
-# Phases
-
-Last update: YYYY-MM-DD
-
-Status: [Proposed | Draft | Live | Deprecated | Archived]
-
----
-
-## 1. Description
-Briefly describe the purpose of this document and what it contains.
-
-## 2. Important
-Notes of important findings or critical constraints. Can be empty.
-
-## 3. Table of Contents
-[Generate a hyperlinked table of contents here containing ALL headings in this file (1 through N). Use standard markdown links, e.g., - [1. Description](#1-description)]
-
-## 4. Scope
-The boundaries of what this document covers.
-
-## 5. Goals
-What we aim to achieve with this specific document.
-
-## 6. Non Goals
-What is explicitly excluded from the scope of this document.
-
-## 7. Overall Project Timeline
-High-level estimate and major milestones. Visual timelines are preferred. Use mermaid.
-
-```mermaid
-gantt
-    title Project Timeline
-    dateFormat  YYYY-MM-DD
-    section Phase 1
-    Milestone 1 : 2024-01-01, 30d
-    section Phase 2
-    Milestone 2 : 2024-02-01, 30d
-```
-
-## 8. Phase Registry
-Links to individual markdown files in the `phases/` directory.
-
-## 9. Sprint Tracker
-### 9.1. Current Sprint (Date Range)
-TBD
-
-### 9.2. Active Tasks
-TBD
-
-### 9.3. Blockers
-TBD
-
-## 10. Success Metrics
-How we measure if the goals of this document are achieved.
-
-## 11. Related Documents
-[Link to related document](path) - Short brief note about why it's related.
-
-## 12. Open Questions
-Any unresolved questions or assumptions. Can be empty.

package/docs/templates/project-docs-template/foundation/prd.md

@@ -1,69 +0,0 @@
-# Product Requirements Document (PRD)
-
-Last update: YYYY-MM-DD
-
-Status: [Proposed | Draft | Live | Deprecated | Archived]
-
----
-
-## 1. Description
-Summarize the product, system, or major epic requirement set at a high level.
-
-## 2. Important
-Notes of important findings or critical constraints. Can be empty.
-
-## 3. Table of Contents
-[Generate a hyperlinked table of contents here containing ALL headings in this file (1 through N). Use standard markdown links, e.g., - [1. Description](#1-description)]
-
-## 4. Scope
-The boundaries of what this document covers.
-
-## 5. Goals
-What we aim to achieve with this specific document.
-
-## 6. Non Goals
-What is explicitly excluded from the scope of this document.
-
-## 7. Vision Statement
-A single, powerful sentence defining the ultimate end-state of the project.
-
-## 8. Target Personas
-Specific user types (e.g., Admin, Guest) to give the team empathy.
-
-## 9. Core Business Value
-The primary ROI, problem being solved, or operational improvement. Why does this project matter now?
-
-## 10. User Journeys & App Flow
-Flowcharts mapping the user's path through the app. Use mermaid.
-
-```mermaid
-journey
-    title User Journey Example
-    section Login
-      Enter credentials: 5: User
-      Authenticate: 5: System
-```
-
-## 11. Feature Workflows
-Step-by-step logic flows for individual features. Use mermaid flowcharts to map complex feature logic.
-
-## 12. Functional Requirements
-Detailed list of functional capabilities.
-
-## 13. Non-Functional Requirements
-Reliability, performance, security, compliance, or UX expectations.
-
-## 14. Acceptance Criteria
-Specific criteria to verify the requirements are met.
-
-## 15. External Dependencies & Partners
-Third-party vendors and manual bottlenecks.
-
-## 16. Success Metrics
-How we measure if the goals of this document are achieved.
-
-## 17. Related Documents
-[Link to related document](path) - Short brief note about why it's related.
-
-## 18. Open Questions
-Any unresolved questions or assumptions. Can be empty.

package/docs/templates/project-docs-template/foundation/status.md

@@ -1,57 +0,0 @@
-# Status
-
-Last update: YYYY-MM-DD
-
-Status: [Proposed | Draft | Live | Deprecated | Archived]
-
----
-
-## 1. Description
-Briefly describe the purpose of this document and what it contains. (Note: This dashboard is updated automatically by the EHA agent).
-
-## 2. Important
-Notes of important findings or critical constraints. Can be empty.
-
-## 3. Table of Contents
-[Generate a hyperlinked table of contents here containing ALL headings in this file (1 through N). Use standard markdown links, e.g., - [1. Description](#1-description)]
-
-## 4. Scope
-The boundaries of what this document covers.
-
-## 5. Goals
-What we aim to achieve with this specific document.
-
-## 6. Non Goals
-What is explicitly excluded from the scope of this document.
-
-## 7. Current State
-Summarize the current implementation state, maturity, and major constraints.
-
-## 8. Recent Accomplishments
-What was finished since the last update.
-
-## 9. Upcoming Focus
-What the team is tackling next week/month.
-
-## 10. Key Metrics Health
-Live data on project health (e.g., "Test Coverage: 85%", "Open Bugs: 12").
-
-## 11. Roadmap
-| Workstream | Status | Notes |
-| --- | --- | --- |
-| TBD | Planned | |
-
-## 12. Epics
-Active and upcoming epics.
-
-## 13. Risks / Blockers
-Immediate blockers holding up progress.
-
-## 14. Success Metrics
-How we measure if the goals of this document are achieved.
-
-## 15. Related Documents
-[Link to related document](path) - Short brief note about why it's related.
-
-## 16. Open Questions
-Any unresolved questions or assumptions. Can be empty.

package/docs/templates/project-docs-template/foundation/workflow.md

@@ -1,59 +0,0 @@
-# Workflow
-
-Last update: YYYY-MM-DD
-
-Status: [Proposed | Draft | Live | Deprecated | Archived]
-
----
-
-## 1. Description
-Briefly describe the purpose of this document and what it contains.
-
-## 2. Important
-Notes of important findings or critical constraints. Can be empty.
-
-## 3. Table of Contents
-[Generate a hyperlinked table of contents here containing ALL headings in this file (1 through N). Use standard markdown links, e.g., - [1. Description](#1-description)]
-
-## 4. Scope
-The boundaries of what this document covers.
-
-## 5. Goals
-What we aim to achieve with this specific document.
-
-## 6. Non Goals
-What is explicitly excluded from the scope of this document.
-
-## 7. Local Development Loop
-How to spin up and iterate.
-
-## 8. Branching Strategy
-GitFlow, Trunk-based, or custom rules. Diagram of branching logic is preferred. Use mermaid.
-
-```mermaid
-gitGraph
-    commit
-    branch develop
-    checkout develop
-    commit
-    branch feature
-    checkout feature
-    commit
-    checkout develop
-    merge feature
-```
-
-## 9. PR & Code Review Process
-Required approvers, templates, and conventions.
-
-## 10. Issue Tracking & Triage
-How bugs and features are logged.
-
-## 11. Success Metrics
-How we measure if the goals of this document are achieved.
-
-## 12. Related Documents
-[Link to related document](path) - Short brief note about why it's related.
-
-## 13. Open Questions
-Any unresolved questions or assumptions. Can be empty.

package/docs/templates/project-docs-template/getting-started.md

@@ -1,52 +0,0 @@
-# Getting Started
-
-Last update: YYYY-MM-DD
-
-Status: [Proposed | Draft | Live | Deprecated | Archived]
-
----
-
-## 1. Description
-Explain how to set up, run, and orient a new contributor or operator in this repository.
-
-## 2. Important
-Notes of important findings or critical constraints. Can be empty.
-
-## 3. Table of Contents
-[Generate a hyperlinked table of contents here containing ALL headings in this file (1 through N). Use standard markdown links, e.g., - [1. Description](#1-description)]
-
-## 4. Scope
-The boundaries of what this document covers.
-
-## 5. Goals
-What we aim to achieve with this specific document.
-
-## 6. Non Goals
-What is explicitly excluded from the scope of this document.
-
-## 7. Prerequisites
-Required tools, accounts, credentials, environment variables, or secrets handling.
-
-## 8. First Steps
-1. Clone or open the repository.
-2. Install dependencies or required tools.
-3. Configure local environment values.
-4. Run the standard startup or verification commands.
-
-## 9. Local Setup
-Detailed steps for install, environment bootstrap, and local run.
-
-## 10. Verification
-First validation command and where to find deeper testing guidance (e.g., `testing.md`).
-
-## 11. Troubleshooting
-List known setup issues and their solutions.
-
-## 12. Success Metrics
-How we measure if the goals of this document are achieved.
-
-## 13. Related Documents
-[Link to related document](path) - Short brief note about why it's related.
-
-## 14. Open Questions
-Any unresolved questions or assumptions. Can be empty.

package/docs/templates/project-docs-template/operations/ci-cd.md

@@ -1,56 +0,0 @@
-# CI/CD Configuration
-
-Last update: YYYY-MM-DD
-
-Status: [Proposed | Draft | Live | Deprecated | Archived]
-
----
-
-## 1. Description
-Briefly describe the purpose of this document and what it contains.
-
-## 2. Important
-Notes of important findings or critical constraints. Can be empty.
-
-## 3. Table of Contents
-[Generate a hyperlinked table of contents here containing ALL headings in this file (1 through N). Use standard markdown links, e.g., - [1. Description](#1-description)]
-
-## 4. Scope
-The boundaries of what this document covers.
-
-## 5. Goals
-What we aim to achieve with this specific document.
-
-## 6. Non Goals
-What is explicitly excluded from the scope of this document.
-
-## 7. Pipeline Architecture
-Overview of the branching and deployment flow. Flowcharts are preferred. Use mermaid.
-
-```mermaid
-graph LR
-    A[Commit] --> B[Build]
-    B --> C[Test]
-    C --> D[Deploy]
-```
-
-## 8. Build Steps
-Compilation, bundling, and artifact generation.
-
-## 9. Testing & Quality Gates
-Automated tests, linting, and security scans.
-
-## 10. Deployment Environments
-Staging, UAT, and Production definitions.
-
-## 11. Secrets & Environment Variables
-Required credentials (stored securely).
-
-## 12. Success Metrics
-How we measure if the goals of this document are achieved.
-
-## 13. Related Documents
-[Link to related document](path) - Short brief note about why it's related.
-
-## 14. Open Questions
-Any unresolved questions or assumptions. Can be empty.

package/docs/templates/project-docs-template/operations/compliance.md

@@ -1,46 +0,0 @@
-# Compliance
-
-Last update: YYYY-MM-DD
-
-Status: [Proposed | Draft | Live | Deprecated | Archived]
-
----
-
-## 1. Description
-Briefly describe the purpose of this document and what it contains.
-
-## 2. Important
-Notes of important findings or critical constraints. Can be empty.
-
-## 3. Table of Contents
-[Generate a hyperlinked table of contents here containing ALL headings in this file (1 through N). Use standard markdown links, e.g., - [1. Description](#1-description)]
-
-## 4. Scope
-The boundaries of what this document covers.
-
-## 5. Goals
-What we aim to achieve with this specific document.
-
-## 6. Non Goals
-What is explicitly excluded from the scope of this document.
-
-## 7. Data Privacy (GDPR / CCPA)
-PII handling and user consent.
-
-## 8. Data Retention Policy
-How long logs and backups are kept before deletion.
-
-## 9. Audit Logging
-Tracking who modified what, and when.
-
-## 10. Legal Disclaimers & Terms
-Required user agreements and copyright notices.
-
-## 11. Success Metrics
-How we measure if the goals of this document are achieved.
-
-## 12. Related Documents
-[Link to related document](path) - Short brief note about why it's related.
-
-## 13. Open Questions
-Any unresolved questions or assumptions. Can be empty.