remvoed unneeded files

sdgos/wayshell/AGENTS.md

@@ -1,38 +0,0 @@
-# Wayshell Module System Agent Instructions
-
-## Overview
-
-This document provides instructions for the Wayshell Module System agent. The agent is responsible for managing the different module types and handling events.
-
-## Module Types
-
-### Zone Module
-
-- **Initialization**: Initialize the Zone module by parsing the configuration files.
-- **Event Handling**: Handle events for entering and exiting zones.
-
-### Layout Module
-
-- **Initialization**: Initialize the Layout module by parsing the configuration files.
-- **Event Handling**: Handle events for activating and deactivating layouts.
-
-### Focused Module
-
-- **Initialization**: Initialize the Focused module by parsing the configuration files.
-- **Event Handling**: Handle events for focusing and unfocusing clients.
-
-## Configuration Files
-
-- **wayshell.conf**: General configuration file.
-- **wayshell.modules**: Defines the modules.
-
-## Performance Optimization
-
-- **Efficient Parsing**: Optimize the parsing of configuration files to minimize CPU usage.
-- **Event Debouncing**: Implement debouncing for events to avoid unnecessary triggers.
-
-## Testing
-
-- **Unit Tests**: Write unit tests for each module type.
-- **Integration Tests**: Write integration tests to ensure the modules work together correctly.
-- **Performance Tests**: Conduct performance tests to ensure the system meets the CPU usage constraints.

sdgos/wayshell/GUIDELINES.md

@@ -1,38 +0,0 @@
-# Wayshell Module System Design Guidelines
-
-## Overview
-
-The Wayshell Module System is designed to be flexible, efficient, and easy to use. This document outlines the design guidelines for the system.
-
-## Module Types
-
-### Zone Module
-
-- **Definition**: Allows defining zones and triggers for entering and exiting these zones.
-- **Implementation**: Use efficient data structures to manage zones and triggers.
-
-### Layout Module
-
-- **Definition**: Allows triggering actions based on the activation or deactivation of specific layout types.
-- **Implementation**: Use event-driven architecture to handle layout changes.
-
-### Focused Module
-
-- **Definition**: Allows triggering actions based on focusing or unfocusing specific client types.
-- **Implementation**: Use efficient event handling to manage focus changes.
-
-## Configuration Files
-
-- **wayshell.conf**: General configuration file.
-- **wayshell.modules**: Defines the modules.
-
-## Performance Optimization
-
-- **Efficient Parsing**: Optimize the parsing of configuration files to minimize CPU usage.
-- **Event Debouncing**: Implement debouncing for events to avoid unnecessary triggers.
-
-## Testing
-
-- **Unit Tests**: Write unit tests for each module type.
-- **Integration Tests**: Write integration tests to ensure the modules work together correctly.
-- **Performance Tests**: Conduct performance tests to ensure the system meets the CPU usage constraints.

sdgos/wayshell/PLAN.md

@@ -1,50 +0,0 @@
-# Wayshell Module System Plan
-
-## Overview
-
-The Wayshell Module System is designed to provide a flexible and efficient way to manage different types of modules in a Wayland environment. The system will parse configuration files and trigger actions based on specific events.
-
-## Module Types
-
-1. **Zone Module**: Allows defining zones and triggers for entering and exiting these zones.
-2. **Layout Module**: Allows triggering actions based on the activation or deactivation of specific layout types.
-3. **Focused Module**: Allows triggering actions based on focusing or unfocusing specific client types.
-
-## Configuration Files
-
-- **wayshell.conf**: General configuration file.
-- **wayshell.modules**: Defines the modules.
-
-## Design Constraints
-
-- Minimize CPU usage to less than 3% when running as a daemon.
-- Avoid constantly running expensive commands.
-
-## Implementation Plan
-
-### Phase 1: Initial Setup
-
-1. **Parse Configuration Files**: Implement parsers for `wayshell.conf` and `wayshell.modules`.
-2. **Module Initialization**: Initialize the different module types (Zone, Layout, Focused).
-
-### Phase 2: Event Handling
-
-1. **Zone Module**: Implement event triggers for entering and exiting zones.
-2. **Layout Module**: Implement event triggers for activating and deactivating layouts.
-3. **Focused Module**: Implement event triggers for focusing and unfocusing clients.
-
-### Phase 3: Performance Optimization
-
-1. **Efficient Parsing**: Optimize the parsing of configuration files to minimize CPU usage.
-2. **Event Debouncing**: Implement debouncing for events to avoid unnecessary triggers.
-
-### Phase 4: Testing
-
-1. **Unit Tests**: Write unit tests for each module type.
-2. **Integration Tests**: Write integration tests to ensure the modules work together correctly.
-3. **Performance Tests**: Conduct performance tests to ensure the system meets the CPU usage constraints.
-
-## Next Steps
-
-1. Review the plan and provide feedback.
-2. Proceed with the implementation based on the approved plan.

sdgos/wayshell/screenshot.state

@@ -1,3 +1,3 @@
 mode=editor
-save_dir=/home/den/Pictures/temp
+save_dir=/home/den/Pictures/Screenshots
 editor=satty --filename