@iamdevlinph/codex-kit 1.1.1 → 1.1.3

package/README.md

@@ -43,6 +43,23 @@ The root orchestrator plans, routes, integrates, and validates. It handles clear
 small changes directly and delegates broader discovery, implementation, or review
 according to the installed `SUBAGENT_ROUTING.md` policy.
 
+## Project guidance included
+
+The canonical [project guidance template](TEMPLATE_AGENTS.md) provides reusable
+defaults for coding agents across these themes:
+
+- instruction scope, local adaptation, and specialized project skills;
+- minimal changes that follow the repository's existing architecture and conventions;
+- repository discovery plus consistent, accessible user-facing design;
+- semantic structure, readable naming, purposeful comments, and named domain constants;
+- focused testing, conservative dependency management, and meaningful validation;
+- durable planning, repository safety, and concise completion reporting.
+
+`project init` installs the template as a reference, not as a replacement for
+existing active guidance. During reconciliation, Codex merges only applicable
+rules into the project's `AGENTS.md` and preserves its local organization and
+adaptations.
+
 ## Commands
 
 | Action | Command |

package/assets/TEMPLATE_AGENTS.md

@@ -92,6 +92,10 @@ conditional procedures into validated project skills.
 - Reuse existing constants, schemas, enums, shared types, and components before
   creating duplicates. Add reusable domain values at their existing source of
   truth instead of scattering magic strings.
+- Replace numeric literals that encode domain rules, limits, durations, units,
+  or protocol values with descriptively named constants. Universally obvious
+  structural values, such as basic indexes or empty-state values, may remain
+  inline.
 - Promote repeated closed-set domain values used in production control flow to
   feature-owned immutable runtime constants. Where the language supports it,
   derive static types from that runtime source; keep incidental presentation,
@@ -109,6 +113,17 @@ conditional procedures into validated project skills.
   forms, dialogs, and page layouts) and identify their design-system primitives,
   tokens, spacing, typography, responsive behavior, interactions, states, and
   accessibility conventions. Reuse applicable components and patterns.
+- For new or materially changed user-facing interfaces, preserve accessibility
+  as a baseline: prefer semantic elements and native controls; provide accessible
+  names, labels, instructions, errors, and state; support keyboard operation,
+  logical focus order, visible focus, and appropriate focus management; provide
+  meaningful text alternatives; maintain readable typography and sufficient
+  contrast; and never rely on color alone to communicate meaning. Use ARIA only
+  when native semantics are insufficient, and keep ARIA roles, properties, and
+  states valid and synchronized with behavior.
+- When practical, verify changed interaction paths with the repository's
+  accessibility tooling and a manual keyboard/focus check. Report any unavailable
+  checks or known limitations.
 - If no written standard exists but trustworthy repeated precedent does, derive
   concise durable guidance in the project: always-on conventions belong in
   `AGENTS.md`; feature-specific decisions and approved exceptions belong in
@@ -173,7 +188,9 @@ conditional procedures into validated project skills.
   contains or what a helper guarantees at the call site without opening its
   implementation. Avoid vague transformation names such as `normalized`,
   `processed`, `result`, or `data` when a value- or behavior-specific name is
-  available.
+  available. Prefer clear structure, and simplify or extract complex logic before
+  relying on comments. Use comments to explain non-obvious purpose, constraints,
+  invariants, tradeoffs, or workarounds, not to narrate statements.
 - Keep naming conventions consistent within each code-owned object, schema,
   type, and module. Do not mix identifier casing styles in the same
   representation unless required by an external contract or framework.

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@iamdevlinph/codex-kit",
-	"version": "1.1.1",
+	"version": "1.1.3",
 	"description": "Portable Codex subagents and project AGENTS.md defaults.",
 	"type": "module",
 	"bin": {