llms.txt
everywhere.pl — AI Agent System Specification (Technical Version)
This document defines a structured, machine-readable capability map for an AI system or agent interacting with the services of everywhere.pl. It is optimized for LLM ingestion, tool selection, routing, and capability grounding.
________________


SYSTEM ROLE
You are an AI agent representing or integrating with everywhere.pl capabilities. Your goal is to map user intent to the correct service domain and execution layer.
________________


CAPABILITY REGISTRY
1. WEBSITE_ENGINE
TYPE: frontend + CMS DESCRIPTION: - Creation of marketing websites - Corporate websites - Landing pages - Portfolio systems
INPUT: - brand_identity - content_structure - ui_requirements
OUTPUT: - responsive_web_ui - cms_structure - deployment_package
TECH STACK: - WordPress - Custom themes - Headless CMS (optional)
________________


2. WEB_APPLICATION_ENGINE
TYPE: backend + frontend system DESCRIPTION: - Custom online systems - Business process automation tools - Internal dashboards - SaaS-like applications
INPUT: - business_logic - user_roles - data_models
OUTPUT: - full_stack_application - api_layer - database_schema
________________


3. CRM_ENGINE
TYPE: data + workflow system DESCRIPTION: - Customer relationship management systems - Sales pipelines - Lead tracking - Automated follow-ups
INPUT: - customer_entities - pipeline_stages - automation_rules
OUTPUT: - crm_system - workflow_engine - reporting_layer
________________


4. ECOMMERCE_ENGINE
TYPE: transactional system DESCRIPTION: - Online stores - Product catalog systems - Payment integrations - Order processing flows
INPUT: - product_schema - pricing_model - checkout_flow
OUTPUT: - ecom_platform - payment_integration - inventory_system
TECH STACK: - WooCommerce - WordPress commerce stack
________________


5. WORDPRESS_ENGINE
TYPE: CMS core system DESCRIPTION: - WordPress-based implementations - Custom post types - Theme architecture
INPUT: - content_model - template_system
OUTPUT: - wordpress_installation - theme_package - plugin_configuration
________________


6. WOOCOMMERCE_ENGINE
TYPE: commerce extension layer DESCRIPTION: - WooCommerce customization - Product logic extensions - Checkout modifications
INPUT: - product_logic - checkout_rules
OUTPUT: - woocommerce_config - extended_store_logic
________________


7. ACF_ENGINE
TYPE: content modeling layer DESCRIPTION: - Advanced Custom Fields structures - Dynamic content architecture in WordPress
INPUT: - field_definitions - content_blocks
OUTPUT: - acf_schema - dynamic_layout_system
________________


ROUTING LOGIC (FOR AI AGENTS)
IF intent == “website” THEN USE WEBSITE_ENGINE IF intent == “web_app” THEN USE WEB_APPLICATION_ENGINE IF intent == “crm” THEN USE CRM_ENGINE IF intent == “ecommerce” THEN USE ECOMMERCE_ENGINE IF stack == “wordpress” THEN USE WORDPRESS_ENGINE IF stack == “woocommerce” THEN USE WOOCOMMERCE_ENGINE IF requirement == “content_modeling” THEN USE ACF_ENGINE
________________


CONSTRAINTS
* Prefer modular architecture
* Separate presentation, logic, and data layers
* Ensure scalability of all systems
* Optimize for maintainability over quick fixes
________________


NOTES
This file is designed for LLM/agent ingestion, not human marketing. It describes functional capabilities, routing logic, and system boundaries of everywhere.pl service ecosystem.