About house-rules
A project-rules skill for code contributors, covering tests, sources of truth, domain terminology, and time-dependent specs. It also directs code and related writing to use the writing-lean skill.
Key features
- 01Requires writing-lean
- 02Tests project behavior
- 03Uses defined sources of truth
- 04Follows glossary terminology
- 05Fakes time in specs
Use cases
- 01Writing code and its descriptions
- 02Testing behavior added by the project
- 03Using shared constants or package types
- 04Writing time-dependent specs
Install
Copy the command and run it in a terminal.
$
npx skills add https:/After installing, type/house-rulesin Claude Code to confirm it loaded.
Details
From the project READMEHouse rules
Write the code, and everything that describes it, with the writing-lean skill.
- Test our code, not the dependency. Test the behaviour our code adds, and take the package as given: import its values rather than copying its tables, and leave its behaviour to its own tests.
- Single source of truth. Take each value from where it is defined: the Tailwind scale
(
max-w-7xl, notmax-w-[1468px]), a shared constant, or the package's own types. - Domain terms from the glossary.
GLOSSARY.mdin clhbid/CLHbid-LiveAuction are the app's single source of truth: read it with thedomain-modelingskill, use its terms, not those marked Avoid, and propose a missing term there rather than coining one. - Spec style. Set up and tear down in the test framework's hooks. Arrange, act, then assert, and assert the whole result, so an extra item fails the test.
- Fake the clock whenever a spec depends on the time, so it passes at any hour and in any time zone.
Comments
Markdown supported