agentsclimarketplace

House rules

Skill Studio-Moser/skills-n-stuff/plugins/pm/skills/house-rules

Product research, market intelligence, and content tools for AI-native teams

Install
npx -y skills add Studio-Moser/skills-n-stuff --skill house-rules

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when making any code change and you need Studio Moser conventions for branch naming, file/documentation naming, commit messages, PR format, testing discipline, or pre-commit security checks, or when you just need a quick convention lookup. Loaded by pm:dev-task and pm:sprint-dev.

SKILL.md

1.9 KB, 392 tokens by cl100k_base, as published. Nobody here has run it

House Rules

Studio Moser conventions for code changes. Canonical source: studio-baseline/House_Rules.md — the same rules every repo's AGENTS.md baseline block points at, so plugin and non-plugin devs follow one set. Read the canonical doc for the full text; the essentials:

  • Branches: never commit to main/master; branch {type}/{short-desc} (feature/bugfix/hotfix/release/chore). Sprint batches use pulse/{cluster}-{date}.
  • Commits: Conventional Commits, present tense, one logical change each.
  • PRs: imperative title < 72 chars; body always ## What / ## Why / ## Testing; one PR per task.
  • File naming: Title Case with spaces; underscores when spaces can't be used; dashes only for version/topic segments; never default to ALL CAPS; tooling-fixed names (README.md, SKILL.md, …) keep their form.
  • Implementation discipline: shortest diff that fully solves it; reuse existing code / stdlib / platform first; no speculative abstractions or unrequested refactors; fix the root cause, not the symptom.
  • Testing: baseline first, add tests for new behavior, show pasted output — never claim "passing" without evidence.
  • Verification: self-review is a first draft, not proof; an independent check reproduces the claimed result; dispute wrong findings rather than distorting correct code.
  • Pre-commit security: no secrets in the diff; validate input; don't disable a security feature to "make it work"; handle errors.
  • Project overrides: a repo's own CLAUDE.md/AGENTS.md wins.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.