Centralize business and domain rules into a single traceable document.
npx skills add https://github.com/ejoongseok/claude-settings --skill biz-rules
Please help me install this Agent Skill. Skill: biz-rules Source: https://github.com/ejoongseok/claude-settings/tree/main/claude-code/skills/biz-rules Command: npx skills add https://github.com/ejoongseok/claude-settings --skill biz-rules
비즈니스 규칙과 도메인/상태 전이 규칙이 코드 곳곳에 흩어져 변경 시 영향 범위가 불명확해지는 문제를, 한 문서로 단일 소스 오브 트루스로 정리해 추적 가능하게 해결합니다.
§4 도메인 점검 카테고리가 채워지면 /review, /qa 계열 스킬들이 더 도메인 특화된 점검을 자동으로 강화합니다.CLAUDE.md, bot/INDEX.md(.local 클론 포함), .local.claude/biz-rules.md 같은 문서와 코드 탐색을 기반으로 운영됩니다./biz-rules를 실행해 프로젝트의 상태 전이 규칙과 비즈니스 규칙을 단일 문서로 초기 생성하거나 기존 문서를 업데이트하세요.
High-intent search queries and answers about installing and using this skill.
You consolidate scattered business and domain rules into a single traceable document by defining state transition rules and domain inspection categories, creating a single source of truth for project-wide rule management across review, QA, SRS, and deployment workflows.
Scattered business logic causes unclear impact analysis because rules are not centralized. Centralizing business, domain, and state transition rules into a single traceable document with accumulated change history clarifies the impact scope when modifications occur.
Track change history for domain modeling rules by maintaining a centralized document that records when, what, and why a rule was added, modified, or deleted. This ensures explicit, consistent, and change-tracked rule management across your codebase.
Yes, you can manage codebase governance using YAML frontmatter with name and description fields. This structures your business rules document to support tiered domain-specific checks and maintain fallback behavior when external inputs like CLAUDE.md are missing.
Centralizing domain inspection categories improves quality assurance by enabling tiered domain-specific checks. When the domain inspection category section is populated, review and QA workflows automatically strengthen their domain-specific validation against the centralized rules.
When optional external inputs like CLAUDE.md or module docs are missing, the rule generation process maintains fallback behavior. It continues to centralize business and state transition rules by relying on the available code and document-based dependency structure.
studyplusCheck and update system_high_level_design.md against the current codebase.
cody-hutsonAutomate review of operational outputs against explicit quality gates.
williamzujkowskiEnforce HIPAA compliance for PHI handling in healthtech systems.
alexsandrocruzCodify domain entities, business rules, and permissions using structured templates.