principles

Best practices for editing involve reading repository context before making changes, ensuring edits are minimal and precise for easy review. This Skill provides diff-aware guidance that promotes surgical, safety-conscious code modifications aligned with development standards.

Clear communication requires translating technical constraints into actionable steps using plain language. This Skill offers templates and guidance for explaining next steps and technical issues in ways non-technical founders and collaborators can understand and act on.

Safety and consistency come from embedding guidelines into every development action. This Skill provides core principles for editing, repository analysis, and communication that automatically guide safe practices and reduce risk across both technical and non-technical contexts.

Yes. This Skill applies development principles, safety guidelines, and communication standards to software tasks requiring consistent, high-quality practices. It works in both technical and non-technical contexts, from code reviews to stakeholder communication.

Before editing, read repository context to understand the existing structure and patterns. This Skill enforces the read-before-edit principle to ensure changes are minimal, precise, and aligned with project guidelines, making reviews and maintenance easier.

Principles-driven development produces minimal, targeted changes that are easier to review, understand, and maintain. This Skill guides precise edits that reduce cognitive load on reviewers and lower the risk of introducing bugs or inconsistencies.