@sallmarta/eye-hate-agent 1.0.3 → 1.0.4

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

@@ -1,46 +0,0 @@
-# Governance
-
-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. Versioning Policy (SemVer)
-Rules for major, minor, and patch bumps.
-
-## 8. Release Cadence
-Scheduled deploy windows (e.g., every Tuesday).
-
-## 9. Code Ownership & Maintainers
-Who is responsible for which modules.
-
-## 10. Contribution Guidelines
-Rules for external or cross-team PRs.
-
-## 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/operations/observability.md

@@ -1,53 +0,0 @@
-# Observability & Telemetry
-
-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. Logging Strategy & Levels
-Formatting (e.g., JSON) and severity rules (Info/Warn/Error).
-
-## 8. Metrics & Dashboards
-Key Performance Indicators (latency, error rates).
-
-## 9. Distributed Tracing
-Request IDs and flow mapping across microservices.
-
-## 10. Alerting Rules & Thresholds
-Conditions that trigger on-call pages. Flowcharts are preferred. Use mermaid.
-
-```mermaid
-graph TD
-    A[Alert Triggered] --> B{Severity Level}
-    B -- High --> C[Page On-Call]
-    B -- Low --> D[Log to Ticket]
-```
-
-## 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/operations/production-runbook.md

@@ -1,62 +0,0 @@
-# Production Runbook
-
-Last update: YYYY-MM-DD
-
-Status: [Proposed | Draft | Live | Deprecated | Archived]
-
----
-
-## 1. Description
-Describe what this runbook covers and which environment or service it applies to.
-
-## 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. Environment Overview
-Production environment summary. Key dependencies or infrastructure notes.
-
-## 8. Prerequisites and Access
-- Required tools
-- Required permissions or credentials
-- Safety checks before making changes
-
-## 9. Release / Deployment Procedure
-1. Step 1
-2. Step 2
-3. Step 3
-
-## 10. Verification / Smoke Checks
-Checks to run to ensure deployment is healthy.
-
-## 11. Rollback / Recovery
-Steps to recover from a failed deployment. Flowcharts are preferred. Use mermaid.
-
-```mermaid
-graph TD
-    A[Failure Detected] --> B[Trigger Rollback]
-    B --> C[Verify Previous State]
-```
-
-## 12. Operational Notes
-Known gotchas.
-
-## 13. Success Metrics
-How we measure if the goals of this document are achieved.
-
-## 14. Related Documents
-[Link to related document](path) - Short brief note about why it's related.
-
-## 15. Open Questions
-Any unresolved questions or assumptions. Can be empty.

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

@@ -1,49 +0,0 @@
-# Security
-
-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. Security Objectives
-Primary assets to protect.
-
-## 8. Identified Threats & Vectors
-Known vulnerabilities (e.g., injection, XSS, DDOS).
-
-## 9. Mitigation Strategies
-How the architecture neutralizes the threats.
-
-## 10. Access Control (RBAC)
-Roles, permissions, and session management.
-
-## 11. Data Encryption (At-Rest / In-Transit)
-Algorithms and key management.
-
-## 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/technical/api-contract.md

@@ -1,49 +0,0 @@
-# API Contract
-
-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. Base URL & Authentication
-Core connection details and token requirements.
-
-## 8. Standard Request/Response Format
-The expected shape of data (e.g., standard JSON wrapper).
-
-## 9. Endpoints (REST / GraphQL)
-Specific routes, methods, payloads, and responses.
-
-## 10. Webhooks & Events
-Outbound data events pushed to external systems.
-
-## 11. Rate Limiting & Constraints
-Throttling rules and payload size limits.
-
-## 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/technical/database.md

@@ -1,59 +0,0 @@
-# Database Schema
-
-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. Database Architecture
-Type of DB (SQL/NoSQL) and clustering details.
-
-## 8. Entity Relationship Diagram (ERD)
-Visual or text-based map of table relationships. ERDs are preferred. Use mermaid.
-
-```mermaid
-erDiagram
-    CUSTOMER ||--o{ ORDER : places
-    ORDER ||--|{ LINE-ITEM : contains
-    CUSTOMER }|..|{ DELIVERY-ADDRESS : uses
-```
-
-## 9. Schema Definitions (Tables/Collections)
-Specific columns, types, and constraints.
-
-## 10. Indexes & Performance
-Keys required for fast lookups.
-
-## 11. Migration Strategy
-How schema changes are versioned and deployed.
-
-## 12. Data Dictionary
-Single source of truth for business definitions. Define what key domain terms actually mean (e.g., "An *Active User* is someone who logged in within 30 days, excluding admins").
-
-## 13. Success Metrics
-How we measure if the goals of this document are achieved.
-
-## 14. Related Documents
-[Link to related document](path) - Short brief note about why it's related.
-
-## 15. Open Questions
-Any unresolved questions or assumptions. Can be empty.

package/docs/templates/project-docs-template/technical/error-handling.md

@@ -1,54 +0,0 @@
-# Error Handling
-
-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. Standard Error Payload
-The exact JSON shape returned on failure.
-
-## 8. Global Error Codes
-A registry of specific business logic errors.
-
-## 9. Client-Side Handling Rules
-How the frontend should display or retry failures.
-
-## 10. Server-Side Fallbacks
-Circuit breakers and degraded modes. Diagram of fallback flow is preferred. Use mermaid.
-
-```mermaid
-graph TD
-    A[Request] --> B{Service Online?}
-    B -- Yes --> C[Process Request]
-    B -- No --> D[Trigger Circuit Breaker]
-    D --> E[Return Fallback Payload]
-```
-
-## 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/technical/internationalization.md

@@ -1,46 +0,0 @@
-# Internationalization & Localization
-
-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. Supported Languages / Locales
-The explicit list of target regions.
-
-## 8. Translation Workflow (TMS)
-How strings are extracted, translated, and merged.
-
-## 9. Fallback Locales
-The default language when a string is missing.
-
-## 10. Date & Currency Formats
-Regional formatting rules.
-
-## 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/technical/testing.md

@@ -1,57 +0,0 @@
-# Testing & Verification
-
-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. Verification Policy & Objectives
-Define the overarching philosophy for how this repository chooses, runs, and reports testing. What are we trying to prove with our test suite?
-
-## 8. Verification Matrix & Coverage
-The required types of testing (Blackbox, Unit, Security) mapping against expected coverage metrics (e.g., 85% branch coverage).
-
-| Change type | Preferred validation | Fallback |
-| --- | --- | --- |
-| Code change | TBD | TBD |
-| Documentation change | TBD | TBD |
-
-## 9. Test Layers & Environments
-Detail the exact split of Unit, Component, Integration, and E2E tests. Include the required infrastructure, mocks, and seed data needed to run them.
-
-## 10. Commands & CI Gates
-The exact terminal commands for linting and testing. Outline the required pre-merge CI checks (blocking vs advisory).
-
-## 11. Naming & File Conventions
-Where tests live, how test files are named (e.g., `*.spec.ts`), and how fixtures are stored.
-
-## 12. Manual Checks & Fallbacks
-Necessary manual testing steps and fallback procedures for human verification when automation is impossible.
-
-## 13. Success Metrics
-How we measure if the goals of this document are achieved.
-
-## 14. Related Documents
-[Link to related document](path) - Short brief note about why it's related.
-
-## 15. Open Questions
-Any unresolved questions or assumptions. Can be empty.

package/docs/templates/project-docs-template/technical/ui-ux.md

@@ -1,68 +0,0 @@
-# UI/UX
-
-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. Design Philosophy
-The core principles guiding the user experience.
-
-## 8. Design System & Theme
-Colors, typography, and visual guidelines.
-
-## 9. Wireframing & Prototyping
-Links to external tools (Figma, Adobe) or raw UI specs generated by humans/AI in the repo.
-
-## 10. Screen Layouts
-Core page structures and navigation flows. Wireframes are preferred. Use mermaid.
-
-```mermaid
-graph TD
-    A[Home Page] --> B[Dashboard]
-    A --> C[Profile Settings]
-    B --> D[Details View]
-```
-
-## 11. Component Library
-Reusable UI elements (buttons, modals).
-
-## 12. Responsive Breakpoints
-Behavior across mobile, tablet, and desktop.
-
-## 13. Accessibility (a11y) Requirements
-Contrast ratios, ARIA labels.
-
-## 14. Implementation Backlog
-List of UI tasks (e.g., `Task-ID: Description`).
-
-## 15. Design Handoff Approaches
-How designs are explicitly transferred to developers.
-
-## 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/skills/architecture/db-schema-design/SKILL.md

@@ -1,14 +0,0 @@
-# Database Schema Design Skill
-
-You are an expert Database Architect. Your task is to design robust, scalable, and normalized database schemas (or optimized NoSQL data models) based on the project's requirements.
-
-## Responsibilities
-1. Analyze `docs/project-docs/foundation/prd.md` to understand data storage needs.
-2. Design tables/collections, defining strict types, primary keys, and foreign keys.
-3. Establish proper indexes for common query patterns to ensure high performance.
-4. Document the relationships (1:1, 1:N, M:N) clearly in `docs/project-docs/technical/database.md`.
-
-## Output Constraints
-- Always use standard Entity-Relationship terminology.
-- When generating SQL schemas, prefer standard ANSI SQL unless a specific dialect (e.g., PostgreSQL, MySQL) is requested.
-- Highlight any potential bottlenecks (e.g., heavily joined tables, wide rows).