Skip to content

docs: refresh AGENTS.md#257

Merged
epeicher merged 1 commit into
trunkfrom
docs/refresh-agents-md
May 20, 2026
Merged

docs: refresh AGENTS.md#257
epeicher merged 1 commit into
trunkfrom
docs/refresh-agents-md

Conversation

@epeicher
Copy link
Copy Markdown
Collaborator

@epeicher epeicher commented May 20, 2026

Summary

Refresh AGENTS.md to fix stale claims, surface workflow rules, and restructure for findability.

Factual fixes

  • Replace the stale "two bundles today" table with a pointer to package.json build:* scripts + vite.config.js. The repo now has ~17 build targets, not two.
  • Drop the "since 0.15.0" / "since 0.17.0" markers (referenced versions that don't exist; plugin is at 0.8.6) and the now-redundant "since 0.5.5" tags.
  • Replace the 134-line ASCII Doc Tree with a 19-row table that matches the actual docs/ contents. The old tree was missing roughly half the top-level docs and ~21 example pages.
  • Switch typecheck guidance from ./node_modules/.bin/tsc --noEmit to npm run typecheck.
  • Remove the dangling reference to docs/components-reference.md (does not exist; the static help block on each <wpd-*> class is the actual convention, verified across all 55 components).

Promoted workflow rules

Moved four standing rules from personal notes into the shared doc:

  • Run npm run build once at the end of a batch (not between intermediate edits).
  • Always branch + PR, never commit to trunk.
  • Use bin/sync-to-wp-develop.sh over raw rsync.
  • Don't regenerate POT/PO/JSON in feature PRs.

Structure

  • Reorder into Hard rules → Workflow → Process reminders → Contributor gotchas → Developer docs map, so the highest-bite rules (assets/js/ is build output, trackedFetch, wpdConfirm, wpd-*) come first.
  • Add a ## Contents TOC.
  • Reframe the opening (the "Short file" claim was broken at 333 lines). New framing: rulebook + cheatsheet for working inside the codebase, with docs/ as the public contract for plugin authors.

Net result: 327 lines → 327 lines (similar length), but with substantive content corrected and the high-frequency rules surfaced.

Test plan

  • Read through AGENTS.md and confirm the Doc map table matches your mental model of docs/.
  • Spot-check that the "Hard rules" surface the things you actually want to land first when an agent reads the file.
Open WordPress Playground Preview

Rewrite AGENTS.md to fix stale claims, promote workflow rules, and
restructure for findability.

- Replace stale 'two bundles today' table with a pointer to
  package.json build:* scripts + vite.config.js (now ~17 targets).
- Remove fictional 'since 0.15.0' / 'since 0.17.0' markers and the
  redundant 'since 0.5.5' tags (plugin is at 0.8.6; all are baseline).
- Replace the 134-line ASCII Doc Tree with a 19-row table that
  matches the actual docs/ contents. The prior tree was missing
  about half of the docs and around 21 examples.
- Switch typecheck guidance from ./node_modules/.bin/tsc --noEmit to
  npm run typecheck.
- Drop the reference to docs/components-reference.md (does not exist).
- Reorder into Hard rules -> Workflow -> Process reminders ->
  Contributor gotchas -> Developer docs map, so the highest-bite
  rules (assets/js/, trackedFetch, wpdConfirm, wpd-*) come first.
- Add a Contents TOC.
- Reframe the opening: drop the broken 'Short file' claim and
  describe the doc as the rulebook + cheatsheet for working inside
  the codebase, with docs/ as the public contract.
- Promote four standing workflow rules from personal notes into the
  shared doc: npm run build after a batch, branch + PR (never trunk),
  bin/sync-to-wp-develop.sh over raw rsync, and no POT/PO/JSON
  regeneration in feature PRs.
@github-actions
Copy link
Copy Markdown
Contributor

✅ WordPress Plugin Check Report

✅ Status: Passed

📊 Report

All checks passed! No errors or warnings found.


🤖 Generated by WordPress Plugin Check Action • Learn more about Plugin Check

@epeicher epeicher merged commit 5edd536 into trunk May 20, 2026
5 checks passed
@epeicher epeicher deleted the docs/refresh-agents-md branch May 20, 2026 15:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant