@every-env/compound-plugin 2.34.7 → 2.35.0

package/CHANGELOG.md

@@ -7,6 +7,19 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 Release numbering now follows the repository `v*` tag line. Starting at `v2.34.0`, the root CLI package and this changelog stay on that shared version stream. Older entries below retain the previous `0.x` CLI numbering.
 
+# [2.35.0](https://github.com/EveryInc/compound-engineering-plugin/compare/v2.34.7...v2.35.0) (2026-03-10)
+
+
+### Bug Fixes
+
+* **test-browser:** detect dev server port from project config ([94aedd5](https://github.com/EveryInc/compound-engineering-plugin/commit/94aedd5a7b6da4ce48de994b5a137953c0fd21c3)), closes [#164](https://github.com/EveryInc/compound-engineering-plugin/issues/164)
+
+
+### Features
+
+* **compound:** add context budget precheck and compact-safe mode ([7266062](https://github.com/EveryInc/compound-engineering-plugin/commit/726606286873c4059261a8c5f1b75c20fe11ac77)), closes [#198](https://github.com/EveryInc/compound-engineering-plugin/issues/198)
+* **plan:** add daily sequence number to plan filenames ([4fc6ddc](https://github.com/EveryInc/compound-engineering-plugin/commit/4fc6ddc5db3e2b4b398c0ffa0c156e1177b35d05)), closes [#135](https://github.com/EveryInc/compound-engineering-plugin/issues/135)
+
 ## [2.34.7](https://github.com/EveryInc/compound-engineering-plugin/compare/v2.34.6...v2.34.7) (2026-03-10)
 
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@every-env/compound-plugin",
-  "version": "2.34.7",
+  "version": "2.35.0",
   "type": "module",
   "private": false,
   "bin": {

package/plugins/compound-engineering/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "compound-engineering",
   "version": "2.38.1",
-  "description": "AI-powered development tools. 29 agents, 22 commands, 20 skills, 1 MCP server for code review, research, design, and workflow automation.",
+  "description": "AI-powered development tools. 28 agents, 22 commands, 20 skills, 1 MCP server for code review, research, design, and workflow automation.",
   "author": {
     "name": "Kieran Klaassen",
     "email": "kieran@every.to",

package/plugins/compound-engineering/.cursor-plugin/plugin.json

@@ -2,7 +2,7 @@
   "name": "compound-engineering",
   "displayName": "Compound Engineering",
   "version": "2.33.0",
-  "description": "AI-powered development tools. 29 agents, 22 commands, 19 skills, 1 MCP server for code review, research, design, and workflow automation.",
+  "description": "AI-powered development tools. 28 agents, 22 commands, 19 skills, 1 MCP server for code review, research, design, and workflow automation.",
   "author": {
     "name": "Kieran Klaassen",
     "email": "kieran@every.to",

package/plugins/compound-engineering/commands/ce/plan.md

@@ -138,8 +138,11 @@ Think like a product manager - what would make this issue clear and actionable?
 
 - [ ] Draft clear, searchable issue title using conventional format (e.g., `feat: Add user authentication`, `fix: Cart total calculation`)
 - [ ] Determine issue type: enhancement, bug, refactor
-- [ ] Convert title to filename: add today's date prefix, strip prefix colon, kebab-case, add `-plan` suffix
-  - Example: `feat: Add User Authentication` → `2026-01-21-feat-add-user-authentication-plan.md`
+- [ ] Convert title to filename: add today's date prefix, determine daily sequence number, strip prefix colon, kebab-case, add `-plan` suffix
+  - Scan `docs/plans/` for files matching today's date pattern `YYYY-MM-DD-\d{3}-`
+  - Find the highest existing sequence number for today
+  - Increment by 1, zero-padded to 3 digits (001, 002, etc.)
+  - Example: `feat: Add User Authentication` → `2026-01-21-001-feat-add-user-authentication-plan.md`
   - Keep it descriptive (3-5 words after prefix) so plans are findable by context
 
 **Stakeholder Analysis:**
@@ -538,9 +541,13 @@ Before finalizing, re-read the brainstorm document and verify:
 
 ```bash
 mkdir -p docs/plans/
+# Determine daily sequence number
+today=$(date +%Y-%m-%d)
+last_seq=$(ls docs/plans/${today}-*-plan.md 2>/dev/null | grep -oP "${today}-\K\d{3}" | sort -n | tail -1)
+next_seq=$(printf "%03d" $(( ${last_seq:-0} + 1 )))
 ```
 
-Use the Write tool to save the complete plan to `docs/plans/YYYY-MM-DD-<type>-<descriptive-name>-plan.md`. This step is mandatory and cannot be skipped — even when running as part of LFG/SLFG or other automated pipelines.
+Use the Write tool to save the complete plan to `docs/plans/YYYY-MM-DD-NNN-<type>-<descriptive-name>-plan.md` (where NNN is `$next_seq` from the bash command above). This step is mandatory and cannot be skipped — even when running as part of LFG/SLFG or other automated pipelines.
 
 Confirm: "Plan written to docs/plans/[filename]"
 
@@ -548,26 +555,26 @@ Confirm: "Plan written to docs/plans/[filename]"
 
 ## Output Format
 
-**Filename:** Use the date and kebab-case filename from Step 2 Title & Categorization.
+**Filename:** Use the date, daily sequence number, and kebab-case filename from Step 2 Title & Categorization.
 
 ```
-docs/plans/YYYY-MM-DD-<type>-<descriptive-name>-plan.md
+docs/plans/YYYY-MM-DD-NNN-<type>-<descriptive-name>-plan.md
 ```
 
 Examples:
-- ✅ `docs/plans/2026-01-15-feat-user-authentication-flow-plan.md`
-- ✅ `docs/plans/2026-02-03-fix-checkout-race-condition-plan.md`
-- ✅ `docs/plans/2026-03-10-refactor-api-client-extraction-plan.md`
-- ❌ `docs/plans/2026-01-15-feat-thing-plan.md` (not descriptive - what "thing"?)
-- ❌ `docs/plans/2026-01-15-feat-new-feature-plan.md` (too vague - what feature?)
-- ❌ `docs/plans/2026-01-15-feat: user auth-plan.md` (invalid characters - colon and space)
-- ❌ `docs/plans/feat-user-auth-plan.md` (missing date prefix)
+- ✅ `docs/plans/2026-01-15-001-feat-user-authentication-flow-plan.md`
+- ✅ `docs/plans/2026-02-03-001-fix-checkout-race-condition-plan.md`
+- ✅ `docs/plans/2026-03-10-002-refactor-api-client-extraction-plan.md`
+- ❌ `docs/plans/2026-01-15-feat-thing-plan.md` (missing sequence number, not descriptive)
+- ❌ `docs/plans/2026-01-15-001-feat-new-feature-plan.md` (too vague - what feature?)
+- ❌ `docs/plans/2026-01-15-001-feat: user auth-plan.md` (invalid characters - colon and space)
+- ❌ `docs/plans/feat-user-auth-plan.md` (missing date prefix and sequence number)
 
 ## Post-Generation Options
 
 After writing the plan file, use the **AskUserQuestion tool** to present these options:
 
-**Question:** "Plan ready at `docs/plans/YYYY-MM-DD-<type>-<name>-plan.md`. What would you like to do next?"
+**Question:** "Plan ready at `docs/plans/YYYY-MM-DD-NNN-<type>-<name>-plan.md`. What would you like to do next?"
 
 **Options:**
 1. **Open plan in editor** - Open the plan file for review

package/plugins/compound-engineering/skills/agent-browser/SKILL.md

@@ -202,6 +202,107 @@ Returns:
 }
 ```
 
+## Inspection & Debugging
+
+### JavaScript Evaluation
+
+```bash
+agent-browser eval "document.title"                    # Evaluate JS expression
+agent-browser eval "JSON.stringify(localStorage)"      # Return serialized data
+agent-browser eval "document.querySelectorAll('a').length"  # Count elements
+```
+
+### Console & Errors
+
+```bash
+agent-browser console                 # Show browser console output
+agent-browser console --clear         # Show and clear console
+agent-browser errors                  # Show JavaScript errors only
+agent-browser errors --clear          # Show and clear errors
+```
+
+## Network
+
+```bash
+agent-browser network requests                          # List captured requests
+agent-browser network requests --filter "api"           # Filter by URL pattern
+agent-browser route "**/*.png" abort                    # Block matching requests
+agent-browser route "https://api.example.com/*" fulfill --status 200 --body '{"mock":true}'  # Mock response
+agent-browser unroute "**/*.png"                        # Remove route handler
+```
+
+## Storage
+
+### Cookies
+
+```bash
+agent-browser cookies get                               # Get all cookies
+agent-browser cookies get --name "session"              # Get specific cookie
+agent-browser cookies set --name "token" --value "abc"  # Set cookie
+agent-browser cookies clear                             # Clear all cookies
+```
+
+### Local & Session Storage
+
+```bash
+agent-browser storage local                             # Get all localStorage
+agent-browser storage local --key "theme"               # Get specific key
+agent-browser storage session                           # Get all sessionStorage
+agent-browser storage session --key "cart"              # Get specific key
+```
+
+## Device & Settings
+
+```bash
+agent-browser set viewport 1920 1080                    # Set viewport size
+agent-browser set device "iPhone 14"                    # Emulate device
+agent-browser set geo --lat 47.6 --lon -122.3           # Set geolocation
+agent-browser set offline true                          # Enable offline mode
+agent-browser set offline false                         # Disable offline mode
+agent-browser set media "prefers-color-scheme" "dark"   # Set media feature
+agent-browser set headers '{"X-Custom":"value"}'        # Set extra HTTP headers
+agent-browser set credentials "user" "pass"             # Set HTTP auth credentials
+```
+
+## Element Debugging
+
+```bash
+agent-browser highlight @e1                             # Highlight element visually
+agent-browser get box @e1                               # Get bounding box (x, y, width, height)
+agent-browser get styles @e1                            # Get computed styles
+agent-browser is visible @e1                            # Check if element is visible
+agent-browser is enabled @e1                            # Check if element is enabled
+agent-browser is checked @e1                            # Check if checkbox/radio is checked
+```
+
+## Recording & Tracing
+
+```bash
+agent-browser trace start                               # Start recording trace
+agent-browser trace stop trace.zip                      # Stop and save trace file
+agent-browser record start                              # Start recording video
+agent-browser record stop video.webm                    # Stop and save recording
+```
+
+## Tabs & Windows
+
+```bash
+agent-browser tab list                                  # List open tabs
+agent-browser tab new https://example.com               # Open URL in new tab
+agent-browser tab close                                 # Close current tab
+agent-browser tab 2                                     # Switch to tab by index
+```
+
+## Advanced Mouse
+
+```bash
+agent-browser mouse move 100 200                        # Move mouse to coordinates
+agent-browser mouse down                                # Press mouse button
+agent-browser mouse up                                  # Release mouse button
+agent-browser mouse wheel 0 500                         # Scroll (deltaX, deltaY)
+agent-browser drag @e1 @e2                              # Drag from element to element
+```
+
 ## vs Playwright MCP
 
 | Feature | agent-browser (CLI) | Playwright MCP |

package/plugins/compound-engineering/agents/workflow/every-style-editor.md

@@ -1,64 +0,0 @@
----
-name: every-style-editor
-description: "Reviews and edits text content to conform to Every's editorial style guide. Use when written content needs style compliance checks for headlines, punctuation, voice, and formatting."
-tools: Task, Glob, Grep, LS, ExitPlanMode, Read, Edit, MultiEdit, Write, NotebookRead, NotebookEdit, WebFetch, TodoWrite, WebSearch
-model: inherit
----
-
-You are an expert copy editor specializing in Every's house style guide. Your role is to meticulously review text content and suggest edits to ensure compliance with Every's specific editorial standards.
-
-When reviewing content, you will:
-
-1. **Systematically check each style rule** - Go through the style guide items one by one, checking the text against each rule
-2. **Provide specific edit suggestions** - For each issue found, quote the problematic text and provide the corrected version
-3. **Explain the rule being applied** - Reference which style guide rule necessitates each change
-4. **Maintain the author's voice** - Make only the changes necessary for style compliance while preserving the original tone and meaning
-
-**Every Style Guide Rules to Apply:**
-
-- Headlines use title case; everything else uses sentence case
-- Companies are singular ("it" not "they"); teams/people within companies are plural
-- Remove unnecessary "actually," "very," or "just"
-- Hyperlink 2-4 words when linking to sources
-- Cut adverbs where possible
-- Use active voice instead of passive voice
-- Spell out numbers one through nine (except years at sentence start); use numerals for 10+
-- Use italics for emphasis (never bold or underline)
-- Image credits: _Source: X/Name_ or _Source: Website name_
-- Don't capitalize job titles
-- Capitalize after colons only if introducing independent clauses
-- Use Oxford commas (x, y, and z)
-- Use commas between independent clauses only
-- No space after ellipsis...
-- Em dashes—like this—with no spaces (max 2 per paragraph)
-- Hyphenate compound adjectives except with adverbs ending in "ly"
-- Italicize titles of books, newspapers, movies, TV shows, games
-- Full names on first mention, last names thereafter (first names in newsletters/social)
-- Percentages: "7 percent" (numeral + spelled out)
-- Numbers over 999 take commas: 1,000
-- Punctuation outside parentheses (unless full sentence inside)
-- Periods and commas inside quotation marks
-- Single quotes for quotes within quotes
-- Comma before quote if introduced; no comma if text leads directly into quote
-- Use "earlier/later/previously" instead of "above/below"
-- Use "more/less/fewer" instead of "over/under" for quantities
-- Avoid slashes; use hyphens when needed
-- Don't start sentences with "This" without clear antecedent
-- Avoid starting with "We have" or "We get"
-- Avoid clichés and jargon
-- "Two times faster" not "2x" (except for the common "10x" trope)
-- Use "$1 billion" not "one billion dollars"
-- Identify people by company/title (except well-known figures like Mark Zuckerberg)
-- Button text is always sentence case -- "Complete setup"
-
-**Output Format:**
-
-Provide your review as a numbered list of suggested edits, grouping related changes when logical. For each edit:
-
-- Quote the original text
-- Provide the corrected version
-- Briefly explain which style rule applies
-
-If the text is already compliant with the style guide, acknowledge this and highlight any particularly well-executed style choices.
-
-Be thorough but constructive, focusing on helping the content shine while maintaining Every's professional standards.