project-legibility

Plugin project-legibility from marketplace perhapsspy in perhapsspy/codex-plugins. Commands read from the repo's manifest — 12 days ago.

Skills (10)

• agent-cost-efficiency

  Use for agent work with clear excess-cost risk: broad or unpredictable logs and diffs, browser/UI loops, costly execution/retry loops and progress observation even with small output, costly or repeated delegation, or repeated compaction. Guides bounded execution and observation, preflight output lim

• agents-md-editor

  Use when creating, editing, or reviewing AGENTS.md, agents.md, CLAUDE.md, Copilot instructions, Cursor rules, or any always-read repository instruction file. Keep persistent agent instructions small, durable, non-duplicative, and action-oriented; classify content that belongs in commands, onboarding

• critical-review

  Use when asked to review or re-review code, PRs, diffs, plans, designs, or related artifacts for purpose fulfillment, sufficiency, and excess, including adversarial review of your own proposal or a requested final check. Do not auto-apply to ordinary implementation, summaries, or wording edits.

• interactive-state-flow

  Use when an interactive flow is laggy, stale, or race-prone because user intent, source state, derived presentation, async IO, scheduling, or background work are mixed. Keep source state prompt, protect the urgent interaction path, and admit async or presentation results only through a freshness-own

• project-context-migration

  Audit scattered repository docs and notes, then move only the right working context into the `project-context` structure.

• project-context

  Resume, handoff, and long-running repo work by keeping durable context across threads or agents: task briefs, logs, and reusable reference notes.

• purpose-first-design

  Use when product meaning or implementation-planning direction is materially open before solution structure is settled, including early direction for a new feature, reuse choices, temporary implementations, or another materially consequential product or implementation-planning choice. Choose a bounde

• source-owner-audit

  Use for read-only source-of-truth audits: identify the current code, API, config, doc, or behavior to follow; compare a proposed, migrated, ported, or current change against it; and report evidence, mismatches, unresolved decisions, and owner-level recommendations.

• structure-first

  Use for code generation, feature work, bug fixes, refactoring, and code review when a change creates or reshapes a multi-step flow, state lifecycle, side-effect or decision ownership, cross-unit composition, or boundary contract. Also use it when an existing structural problem makes those elements h

• tighten-docs

  Use by default whenever creating, revising, reviewing, or finalizing human-authored documentation whose source meaning is settled, including documentation changed within another task. Apply from first draft through final review to keep one direct current state, clear reader routes and ownership, and

Similar plugins