principles_skill

Overview

This skill provides development principles, high-level guidelines, and VibeCoder-style guidance for planning and reviewing changes. It focuses on design intent, safety constraints, and diff-aware editing practices rather than producing executable code. Do not use this skill to implement changes—use the implementation skill for actual code edits.

How this skill works

When you ask about principles or guidelines, the skill classifies the request and reads relevant internal references for general principles, diff-aware editing, repository context reading, and VibeCoder guidance. It synthesizes clear, actionable recommendations, checklists, and review criteria tailored to your request. For concrete code changes or patches, it will point you to use the implementation skill instead.

When to use it

• When you mention principles, best practices, or design guidelines
• When you need diff-aware editing guidance or change-scope advice
• When you want VibeCoder-style behavioral guidance or persona tuning
• When you need safety, security, or risk-mitigation constraints for a change
• When preparing a review checklist or design rationale summary

Best practices

• Keep recommendations high-level and rationale-driven; avoid providing implementation-level diffs here
• Focus on observable behavior, compatibility, and minimal blast radius for changes
• Use diff-aware advice: prefer small, reversible commits and clear intent-bearing messages
• Explicitly call out safety and rollback criteria when proposing risky changes
• If you need exact code edits, request the implementation skill and link to the diff or files

Example use cases

• Request a checklist for safe API changes across services
• Ask for diff-aware strategies to refactor a module with minimal runtime impact
• Get VibeCoder guidance for setting an agent’s editing persona and decision rules
• Ask for safety constraints and testing requirements before a large refactor
• Request a concise design rationale to include with a pull request