Use for explicit web eco-design audits, Green IT, code ecological impact, carbon footprint, or /ecocode requests. Proactive guidance is injected separately at session start by design and development.
Use when analyzing the ecological impact of back-end code: database queries, API payloads, server-side cache, background jobs, data transfers, N+1 queries, missing indexes, or server energy consumption from a green IT perspective.
Use when analyzing the ecological impact of front-end code: assets weight, HTTP requests, JavaScript bundles, CSS, images, fonts, browser rendering, lazy loading, caching, or web performance from a green IT perspective.
Use when generating a prioritized action plan from EcoCode audit results. Writes a markdown file with checkboxes, P1→P4 priorities, before/after code, and exact commands.
Use when writing EcoCode audit results to markdown files. Formats front-end and back-end audit data into separate timestamped files in docs/ecocode/audits/.
Use when resuming from an existing EcoCode audit. Reads existing audit files in docs/ecocode/audits/, extracts problems and scores, then routes to plan generation or fix suggestion without re-running the analysis.
Passive eco-design guidelines. Apply them when defining a product, user journey, data model, or dependency. Loaded automatically at session start.
Passive eco-design implementation guidelines. Apply them when writing or modifying front-end, back-end, build, or cache configuration. Loaded automatically at session start.