feat: initialize AI agent harness
This commit is contained in:
13
sources/project-types/internal-service.md
Normal file
13
sources/project-types/internal-service.md
Normal file
@@ -0,0 +1,13 @@
|
||||
## Internal Service Project Rules
|
||||
|
||||
- Internal-only usage does not reduce security, privacy, compatibility, or validation requirements.
|
||||
- Preserve authentication, authorization, role boundaries, auditability, and personal-data protections.
|
||||
- Identify affected user workflows before changing visible behavior.
|
||||
- Treat Frontend and Backend repositories as separate deployable systems with an explicit API contract between them.
|
||||
- Coordinate request, response, authentication, error, and versioning changes across both sides when the approved scope includes both repositories.
|
||||
- Do not silently require a simultaneous Frontend and Backend deployment.
|
||||
- Prefer backward-compatible transitions when deployments may occur independently.
|
||||
- Include migration and rollback considerations for database, API, and configuration changes.
|
||||
- Do not modernize legacy code as an unrelated side effect.
|
||||
- Apply Classic ASP text-safety rules only when the project profile declares the `classic-asp` stack.
|
||||
- Do not access or modify production data merely because the service is internal.
|
||||
13
sources/project-types/library.md
Normal file
13
sources/project-types/library.md
Normal file
@@ -0,0 +1,13 @@
|
||||
## Library Project Rules
|
||||
|
||||
- Treat exported code, configuration keys, registry schemas, generated artifacts, package coordinates, and documented behavior as consumer-facing contracts.
|
||||
- Before changing a public surface, classify the change as internal, backward-compatible, deprecating, or breaking.
|
||||
- Do not remove, rename, relocate, or materially change a public API without an approved compatibility and migration plan.
|
||||
- Preserve consumer override points and optional integrations.
|
||||
- Do not make an optional peer, compile-only, or runtime dependency mandatory without reviewing consumer impact.
|
||||
- Prefer additive evolution and deprecation over immediate removal.
|
||||
- When a public contract changes, update tests, human documentation, and the library's consumer contract in the same approved change.
|
||||
- Validate both the source and the distributable artifact when supported.
|
||||
- Inspect known consumers when available, but do not modify consumer repositories unless they are included in the approved scope.
|
||||
- Version changes, publication, registry deployment, and package replacement require separate authorization.
|
||||
- Keep repository-maintainer rules in `.agent/project.md` and downstream usage rules in `.agent/consumer.md`.
|
||||
14
sources/project-types/requested-project.md
Normal file
14
sources/project-types/requested-project.md
Normal file
@@ -0,0 +1,14 @@
|
||||
## Requested Project Rules
|
||||
|
||||
- Treat the approved requirements, acceptance criteria, and recorded decisions as the primary scope boundary.
|
||||
- Do not infer a requirement solely from a file name, folder date, or apparently newer document.
|
||||
- When requirements conflict, report the exact sources and request a decision.
|
||||
- Preserve original customer, partner, and planning documents as read-only evidence unless document editing is explicitly approved.
|
||||
- Summarize durable implementation requirements inside the repository rather than relying only on files outside the repository.
|
||||
- Do not expand the deliverable with speculative features, infrastructure, or architectural changes.
|
||||
- Record material assumptions and unresolved decisions in the project-specific rules or existing project documentation.
|
||||
- Define observable acceptance criteria before implementation.
|
||||
- Treat separately managed Frontend and Backend repositories as independent deliverables with a coordinated contract.
|
||||
- Protect customer, partner, survey, and field data as sensitive information.
|
||||
- Keep handoff, operation, configuration, and validation instructions usable by the requesting team.
|
||||
- Report deviations from the requested scope and obtain approval before proceeding.
|
||||
14
sources/project-types/scaffold-cli.md
Normal file
14
sources/project-types/scaffold-cli.md
Normal file
@@ -0,0 +1,14 @@
|
||||
## Scaffold CLI Project Rules
|
||||
|
||||
- Treat both the CLI interface and the generated project structure as public contracts.
|
||||
- Preserve existing command names, flags, defaults, prompts, exit behavior, and generated paths unless a breaking change is explicitly approved.
|
||||
- Keep generation deterministic for the same input and template version.
|
||||
- Do not embed credentials, user-specific absolute paths, local machine state, or uncommitted source files in templates.
|
||||
- Never overwrite a non-empty target directory unless the user explicitly selected and authorized the supported force behavior.
|
||||
- Validate template changes by generating a project in a newly created, disposable directory.
|
||||
- Validate the generated project with its own type-check, build, or compile commands when practical.
|
||||
- Inspect generated output for unresolved placeholders, accidental secrets, invalid encodings, machine-specific paths, and unexpected files.
|
||||
- Keep README usage, CLI help, templates, and implementation synchronized.
|
||||
- Preserve operation when the central Agent Harness is not installed.
|
||||
- Generate the committed Agent Harness file set by default for every new project.
|
||||
- Updating embedded harness templates does not authorize publishing the CLI package.
|
||||
13
sources/project-types/shared-service.md
Normal file
13
sources/project-types/shared-service.md
Normal file
@@ -0,0 +1,13 @@
|
||||
## Shared Service Project Rules
|
||||
|
||||
- Treat APIs, message formats, callback behavior, identifiers, error responses, and operational defaults as contracts used by multiple consumers.
|
||||
- Prefer backward-compatible API and schema evolution.
|
||||
- Identify all externally visible side effects before changing a request flow.
|
||||
- Design retryable operations to be idempotent where duplicate execution could send multiple notifications, create duplicate records, or generate inconsistent results.
|
||||
- Define explicit timeout, retry, and failure behavior for external dependencies.
|
||||
- Do not send real email, SMS, notifications, callbacks, or business requests during development or validation.
|
||||
- Use mocks, fakes, test recipients, or disposable local integrations only when their safety is verified.
|
||||
- Do not expose credentials, message contents, personal data, shortened target URLs, or authentication material in logs.
|
||||
- Preserve authentication, authorization, rate limits, validation, and abuse controls when modifying endpoints.
|
||||
- Review database and rollout compatibility before changing persisted data or shared service behavior.
|
||||
- Include consumer impact and rollback considerations in the completion report.
|
||||
Reference in New Issue
Block a user