Sailtech Engineering Playbook

This repository is the shared, repo-neutral home for Sailtech engineering standards used by people and coding agents across agent-driven repositories.

It is a reference source, not a distribution mechanism. Downstream repositories should point people and agents here for shared conventions, then keep only local overlays in their own repos.

Intended Consumers

• Engineers looking for company-wide engineering expectations.
• Coding agents working in Sailtech repositories.
• Reviewers checking whether repo-local guidance aligns with shared standards.
• Maintainers evolving standards that should apply across more than one repository.

Navigation

• Agent Guidance: How agents should consume this playbook and interact with repo-local overlays.
• Engineering Standards: Shared engineering principles, architecture expectations, and review norms.
• Frontend Standards: Shared frontend experience, accessibility, and implementation guidance.
• Testing Standards: Shared testing strategy and validation expectations.
• Operations Standards: Shared operational, release, and incident guidance.
• Execution Plans: Standards for implementation plans and multi-step agent work.
• Templates: Reusable document and workflow templates.
• Skills: Documentation for globally installed Sailtech agent skills.
• Scripts: Documentation for shared scripts when they are introduced.

Consumption Model

The selected consumption model is human and agent reference only.

• Do reference this repository from downstream repo guidance.
• Do keep downstream repo guidance limited to local overlays and exceptions.
• Do update this repository when a standard applies across multiple repositories.
• Do not copy or sync these files into downstream repositories.
• Do not consume this repository as a submodule or subtree.
• Do not add synchronization tooling for this playbook.

Skill Model

Sailtech agent skills remain globally installed. This repository may document those skills and their intended use, but it does not install them and downstream repositories should not copy them into local .agents/skills folders.

The sailtech-* prefix is retained for shared skills because Sailtech is the company name. The prefix does not mean a skill belongs to one specific repository.

Non-Goals

• Defining repo-specific policy for any downstream product or service.
• Replacing repo-local AGENTS.md files or local overlays.
• Installing, packaging, copying, syncing, or vendoring global Codex skills.
• Adding sync, submodule, subtree, or generated-doc distribution workflows.
• Storing application-specific implementation details in shared standards.