Guide architectural and collaboration decisions with engineering philosophy principles.
npx skills add https://github.com/alexanderguy/skills --skill philosophy-alexanderguy
Please help me install this Agent Skill. Skill: philosophy Source: https://github.com/alexanderguy/skills/tree/main/skills/philosophy Command: npx skills add https://github.com/alexanderguy/skills --skill philosophy-alexanderguy
Philosophy and work-culture guidelines reduce confusion and inconsistency when making architectural decisions, collaborating with teammates, and choosing what to build versus what to defer.
Load the philosophy skill when you need to make an architecture decision or align a proposed change with team work principles.
High-intent search queries and answers about installing and using this skill.
Engineering philosophy principles guide architectural decisions by promoting pragmatic tradeoffs, customer safety, and open communication norms. They establish clear expectations for resolving design questions and aligning team collaboration.
Handle backwards compatibility by fixing invariants in the layer that owns them and avoiding unnecessary shims. Clarify when compatibility matters most, separating refactors from feature work to maintain stability.
Adopt a testing mindset that frames tests as behavior verification when validating code changes. This approach focuses on expected outcomes rather than internal implementation details, ensuring robust validation.
The best way to structure commits is through clear storytelling, separating refactors from new features. This guideline ensures changes remain reviewable, logical, and aligned with team communication norms.
Yes, the framework supports building automation tools when appropriate and aligning engineering priority with business realities. It ensures technical decisions respect operational constraints and broader goals.
Constraint ownership matters because it requires fixing invariants in the layer that owns them, preventing scattered logic. This principle maintains system integrity and reduces confusion during collaboration.
rpelizzaSelect reasoning techniques for engineering tasks based on uncertainty and risk.
edwardmonteiroCreate a test strategy with coverage matrix, milestones, and risk prioritization.
burgebjAutomate testing, code review, pull request creation, and deployment workflows.
mfwarrenGenerates onboarding documents, including culture charters and feedback templates, for teams.
