Trace Normix design decisions through documentation and git history.
npx skills add https://github.com/xshi19/normix --skill why-xshi19
Please help me install this Agent Skill. Skill: why Source: https://github.com/xshi19/normix/tree/main/.cursor/skills/why Command: npx skills add https://github.com/xshi19/normix --skill why-xshi19
This Skill addresses the need for understanding the historical context and motivations behind Normix's design choices, enabling users to grasp the 'why' behind specific features and decisions.
To find out why the GeneralizedHyperbolic distribution in Normix was implemented with specific parameters, use the 'why' skill with the question: "Why were the parameters for the GeneralizedHyperbolic distribution chosen?"
High-intent search queries and answers about installing and using this skill.
To find design rationale, you can trace historical context using internal documentation, design proposals, technical notes, and git history to understand the motivations behind specific software features and decisions.
Tracing chosen technical parameters involves following the decision-making process through design records and git history to uncover the reasoning and alternative evaluations that led to the final implementation choices.
Yes, you can identify rejected design alternatives by searching through historical design proposals and technical notes to evaluate the alternative approaches that were ultimately bypassed during development.
You need to analyze git history for decision analysis when you want to understand why a particular function behaves in a certain way or why specific design choices were made across various stages of development.
No, this approach specifically utilizes internal documentation and design records to trace back the reasoning behind features, focusing exclusively on the project's own design decisions rather than external frameworks.
chainkemistsSearch historical Git-backed incidents and rejected designs in CkFoundation.
reez455GCreate ADRs and technical documentation following established templates.
gkganesh12Audit source code against documentation and test suites for architectural drift.
Prompt-or-Die-LabsCapture architectural decisions and rationale in standardized ADR documents.
