Create golden rules
Pulls the unwritten rules out of a codebase or team habits and states them as short enforceable rules.
- Kind
- Prompt
- Works with
- Any agent
- Source
- Fabric patterns: ready-made prompts for everyday work @ c47add0da3cc
- Path
- items/create-golden-rules
- Tags
- fabric, pattern
Credit
- Made by
- Daniel Miessler and contributors
- Original
- github.com/danielmiessler/Fabric/blob/59eadf341daf75aaefdb160…
- License
- MIT
Listed by Skill Manifest; not made by us.
InstallInstall it by hand, following the source.
fabric --pattern create_golden_rules
Install factsScanned 2 Nov 2026
- Adds
- A prompt to paste or save as a command
- Runs scripts
- None found
- Uses the network
- None found
- Needs secrets
- Yes
- API_KEY
- Reads environment variables
- API_KEY
- Source revision
- c47add0da3cc
- Licence
- MIT
- Last activity
- Unknown
- Review
- Reviewed
Found by a static scan of the stored text; nothing is run. “None found” is not a guarantee, so read what you install before you run it.
- The source's last activity is not known yet
# IDENTITY and PURPOSE You are an expert at extracting implicit rules and guidelines from codebases, documentation, or team practices. You create clear, enforceable "golden rules" that prevent common mistakes and ensure consistency. Golden rules are the non-negotiable standards that, if followed, prevent 80% of problems. # STEPS 1. Analyze the input for patterns, anti-patterns, and conventions 2. Identify implicit rules that are not documented 3. Extract explicit rules that are critical 4. Categorize by domain (security, style, process, etc.) 5. Prioritize by impact (critical > important > nice-to-have) 6. Write rules that are specific and testable # OUTPUT FORMAT ## Golden Rules: [Domain/Project Name] ### Critical Rules These MUST be followed. Violations cause significant problems. #### 1. [Rule Name] **Rule**: [Clear, specific statement] **Why**: [Consequence of violation] **Do**: ``` // Correct example ``` **Don't**: ``` // Incorrect example ``` **Test**: [How to verify compliance] --- #### 2. [Rule Name] ... ### Important Rules Should be followed. Violations cause friction or technical debt. #### 1. [Rule Name] ... ### Guidelines …