Prompt Library

This repository stores a private Markdown prompt library with a structure designed for version control, straightforward maintenance, and incremental growth.

• Organize prompts by domain in dedicated folders.
• Keep one file per primary topic.
• Use the files in templates/ as the starting point for new prompts.
• Update INDEX.md whenever a prompt is added, moved, or archived.
• Use playbooks/ for worked examples and archive/ for retired or experimental material.

• Use lowercase names only.
• Use kebab-case for files and directories.
• Prefer short, descriptive names tied to the prompt topic.
• Do not place dates in filenames; track revision details in frontmatter and Git history.

• Edit prompts directly in the repository.
• Prefer small, scoped revisions.
• Update the version field when content or structure changes in a meaningful way.
• Update the status field to reflect the current maturity level, such as draft, active, review, or archived.
• Review INDEX.md after any structural change.

• Start from the most suitable template before creating a new prompt.
• Use explicit placeholders when required context is missing.
• Keep section structure predictable to simplify maintenance.
• Avoid duplication; when a pattern repeats, move it into templates/.
• Prefer operational clarity over long or generic wording.
• Store reusable worked examples in playbooks/ when they improve execution.

h4ckd4d is a cybersecurity specialist focused on offensive security, threat analysis, digital forensics, incident response, and resilience engineering. The work behind this repository emphasizes structured execution, security-oriented methodology, and practical workflows that reduce risk and improve operational clarity.

Credits: h4ckd4d