AGENTS.md@.cf-studio/config · diff
git:20260810.73ed1e6 to git:20260811.1983b8c
8 added, 6 removed. Audit A to A.
# Custom Agent Navigation Rules
Add your project-specific WHEN rules here.
These rules are loaded alongside the generated rules in `{cf-studio-path}/.gen/AGENTS.md`.
---
## Contribution Workflow Binding
```pdsl
UNIT DevelopConflictResolution
PURPOSE:
Bind conflict resolution with `develop` to the contribution workflow in `CONTRIBUTING.md`.
WHEN:
- REQUIRE resolving conflicts with `develop` on any branch with a PR targeting `develop`
DO:
- LOAD the "Resolving Conflicts with `develop`" section of `CONTRIBUTING.md` and follow its procedure
```
```pdsl
UNIT CommitRequirements
PURPOSE:
Bind commit authoring to the commit requirements in `CONTRIBUTING.md`.
WHEN:
- REQUIRE creating commits or preparing a PR for merge in this repository
DO:
- LOAD the "Commit Requirements" section of `CONTRIBUTING.md` and follow its procedure
```
---
## FrontX Architecture Binding
`architecture/` is the authority on what the system is and why: PRD for intent,
DESIGN for structure and constraints, ADRs for decisions, and each FEATURE for
the behaviour its numbered instructions specify. The kit guideline
`packages/cyber-pilot-kit-frontx/guidelines/ecosystem-boundaries.md` condenses
the per-package boundary constraints. The units below bind these sources into
Constructor Studio code work; they route to them and enforce their workflow —
they do not restate their rules. Corrections go to the architecture artifacts
through their own review workflows, not to this file.
```pdsl
UNIT FrontXCodebaseRules
PURPOSE:
Bind FrontX repository architecture rules into every code implementation work
package (cf-coding / cf-sdlc-implement coder dispatches and any direct code change).
WHEN:
- REQUIRE implementing or revising code in this repository
DO:
- LOAD `architecture/DESIGN.md` §1.3 (Architecture Layers) and §2.2 (Constraints) before editing any code
- LOAD `packages/cyber-pilot-kit-frontx/guidelines/ecosystem-boundaries.md` and apply the boundary constraints for every touched package
- - LOAD the governing FEATURE.md — each lives with the package it describes, under `packages/*/architecture/features/` — before changing code that carries its `@cpt-` markers
- - RUN keep `@cpt-` traceability markers intact and aligned with the FEATURE instructions they cite
+ - LOAD `architecture/ADR/0033-template-territory-traceability.md` before changing template territory (any top-level directory carrying a `frontx-template.json` manifest)
+ - LOAD the governing FEATURE.md — each lives with the package it describes, under `packages/*/architecture/features/` — before changing ecosystem code that carries its `@cpt-` markers
+ - RUN keep `@cpt-` traceability markers intact and aligned with the FEATURE instructions they cite — in ecosystem code only
+ - RUN apply the template-territory marker policy from `cpt-frontx-adr-template-territory-traceability` to template code changes
RULES:
- ALWAYS read the named DESIGN constraint (MFES-*, GTS-PLUGIN-*, API-*, CLI-*, KIT-*) before editing code it governs; NEVER code from assumed rules
- ALWAYS stop and ask when a change would cross a DESIGN §2.2 constraint or a package boundary from `ecosystem-boundaries.md`
- - ALWAYS stop and ask when no FEATURE covers behaviour the change introduces
- - NEVER restate architecture rules in artifacts or prompts; reference `architecture/DESIGN.md` and the kit guideline instead
+ - ALWAYS stop and ask when no FEATURE covers behaviour the change introduces in ecosystem code; no ecosystem FEATURE covers template territory by decision, so template consumer-visible behaviour is governed by `cpt-frontx-adr-template-territory-traceability`
+ - NEVER restate architecture rules in artifacts or prompts; reference `architecture/DESIGN.md`, ADRs, and the kit guideline instead
```
```pdsl
UNIT FrontXCodeReviewChecks
PURPOSE:
Bind FrontX-specific review criteria into every code review pass
(cf-coding semantic review and cf-sdlc-pr-review Code Review), in addition
to the kit `{codebase_checklist}`.
WHEN:
- REQUIRE reviewing code changes in this repository
DO:
- - LOAD `architecture/DESIGN.md` §2.2 and `packages/cyber-pilot-kit-frontx/guidelines/ecosystem-boundaries.md`; NEVER review from memory of their rules
+ - LOAD `architecture/DESIGN.md` §2.2, `packages/cyber-pilot-kit-frontx/guidelines/ecosystem-boundaries.md`, and `architecture/ADR/0033-template-territory-traceability.md`; NEVER review from memory of their rules
- RUN FX-001 Constraints: every changed package complies with its named DESIGN §2.2 constraints and its package boundary in `ecosystem-boundaries.md`; ambiguous ownership was raised, not guessed
- - RUN FX-002 Traceability: changed code keeps `@cpt-` markers consistent with the governing FEATURE, and `cfs validate` passes
+ - RUN FX-002 Traceability: changed ecosystem code keeps `@cpt-` markers consistent with the governing FEATURE, and `cfs validate` passes; changed template territory (any top-level directory carrying a `frontx-template.json` manifest) follows the marker policy in `cpt-frontx-adr-template-territory-traceability`
- RUN FX-003 Architecture checks: `npm run arch:check` passes for the changed packages
RULES:
- ALWAYS treat every FX finding as HIGH severity in the review verdict
- ALWAYS run these checks in addition to, never instead of, the kit `{codebase_checklist}` and the generic code checklist
```