The field guide / 0.2.0
Shared knowledge.
Clear sources.
Find the convention that fits the task. Every entry carries its scope, source, and review date.
13 entries
reference
The santi020k way of working
A practical guide: understand the project, write clear code, collaborate, verify, and deliver safely.
Reviewed 2026-10-12standard
Shared working agreements
The essential defaults for evidence, implementation, safety, and delivery.
Reviewed 2026-10-12reference
Full global instruction reference
The complete original Codex working agreements, preserved for traceability.
Reviewed 2026-10-12standard
Design and brand
The Sculpted visual direction, semantic tokens, Lumen, and accessibility.
Reviewed 2026-10-12standard
Preferred tools and package boundaries
Choose Santiago-owned tools with practical setup, examples, verification, and scoped exceptions.
Reviewed 2026-10-12standard
Architecture decisions
Keep reusable contracts and consumer business rules in their correct owners.
Reviewed 2026-10-12standard
Agent configuration
Global entry points, safe setup, versioned references, and local runtime settings.
Reviewed 2026-10-12standard
Quality without a mute button
Zero-warning lint, accurate types, and executable validation.
Reviewed 2026-10-12standard
Release engineering
Package, native, and website delivery with review and reproducible artifacts.
Reviewed 2026-10-12standard
Pull request standard
Reviewable scope, semantic titles, and clear validation evidence.
Reviewed 2026-10-12standard
Repository presentation
Useful READMEs and accurate package metadata.
Reviewed 2026-10-12decision
Share sources; adapt delivery
Why Way uses a local catalog, generated plugins, and a Turborepo.
Reviewed 2026-10-12decision
Keep machine configuration local
Why setup preserves user content and uses reviewed, reversible changes.
Reviewed 2026-10-12No matching standards. Try a broader term, such as “design” or “release”.