Prompt file imported from othonhugo/vulnerability-explorer (.github/prompts/new-concept.prompt.md). Copyright stays with the author.

Prompt: Create a New Concept File

Name: new-concept
Author: othonhugo

Prerequisites

Before starting, you need:

The category slug (from docs/contributing/references/taxonomy.md)
The mechanism slug (kebab-case, e.g. sql-injection)
Confirmation that data/catalog/<category>/<mechanism>/README.md does not already exist

Procedure

Step 1 — Verify the category exists

Check docs/contributing/references/controlled-vocabularies.yaml to confirm the category slug is registered. If it's a new category, follow the extension process in docs/contributing/references/taxonomy.md.

Step 2 — Create the directory

data/catalog/<category>/<mechanism>/

Step 3 — Derive the ID

The id is <category>.<mechanism>. Example: injection.sql-injection. See docs/contributing/guides/naming-and-ids.md for the full derivation rules.

Step 4 — Write the file

Copy docs/contributing/templates/concept.md and fill in every section.

Frontmatter fields:

Field	Value
`schema_version`	`1`
`type`	`concept`
`id`	`<category>.<mechanism>`
`title`	Human-readable mechanism name
`category`	category slug
`mechanism`	mechanism slug
`status`	`draft`
`tags`	kebab-case list, relevant to this mechanism
`aliases`	common alternate names
`external_refs`	CWE/CAPEC/OWASP if useful, never structural

Body sections (in order):

Summary — 2-4 sentences. Dense technical prose.
Root Cause — The mechanical reason this class of bug exists.
Common Manifestations — Use ### sub-headings for each axis of variation. The axes are FLEXIBLE — choose the ones that matter for THIS mechanism. Examples: By Visibility, By Technique, By Timing, By Sink API.
Related Concepts — List format (- ). Each item: concept name + one-sentence distinction.
References — List format (- ). Markdown links.

Step 5 — Validate

Run make lint and fix any errors before finalizing.

Depth Requirement

Write with the depth of a professional security audit report:

Explain the mechanical why, not just the what
In Root Cause, trace the exact trust boundary or runtime behavior
In Common Manifestations, describe each axis with enough detail that a reader understands the shape of the tree without seeing individual files
In Related Concepts, explain the precise boundary that distinguishes this mechanism from each related one

# Prompt: Create a New Concept File ## Prerequisites Before starting, you need: 1. The **category** slug (from `docs/contributing/references/taxonomy.md`) 2. The **mechanism** slug (kebab-case, e.g. `sql-injection`) 3. Confirmation that `data/catalog/<category>/<mechanism>/README.md` does not already exist ## Procedure ### Step 1 — Verify the category exists Check `docs/contributing/references/controlled-vocabularies.yaml` to confirm the category slug is registered. If it's a new category, follow the extension process in `docs/contributing/references/taxonomy.md`. ### Step 2 — Create the directory ``` data/catalog/<category>/<mechanism>/ ``` ### Step 3 — Derive the ID The `id` is `<category>.<mechanism>`. Example: `injection.sql-injection`. See `docs/contributing/guides/naming-and-ids.md` for the full derivation rules. ### Step 4 — Write the file Copy `docs/contributing/templates/concept.md` and fill in every section. **Frontmatter fields:** | Field | Value | | ---------------- | ------------------------------------------- | | `schema_version` | `1` | | `type` | `concept` | | `id` | `<category>.<mechanism>` | | `title` | Human-readable mechanism name | | `category` | category slug | | `mechanism` | mechanism slug | | `status` | `draft` | | `tags` | kebab-case list, relevant to this mechanism | | `aliases` | common alternate names | | `external_refs` | CWE/CAPEC/OWASP if useful, never structural | **Body sections (in order):** 1. **Summary** — 2-4 sentences. Dense technical prose. 2. **Root Cause** — The mechanical reason this class of bug exists. 3. **Common Manifestations** — Use `###` sub-headings for each axis of variation. The axes are FLEXIBLE — choose the ones that matter for THIS mechanism. Examples: By Visibility, By Technique, By Timing, By Sink API. 4. **Related Concepts** — List format (`- `). Each item: concept name + one-sentence distinction. 5. **References** — List format (`- `). Markdown links. ### Step 5 — Validate Run `make lint` and fix any errors before finalizing. ## Depth Requirement Write with the depth of a professional security audit report: - Explain the mechanical _why_, not just the _what_ - In Root Cause, trace the exact trust boundary or runtime behavior - In Common Manifestations, describe each axis with enough detail that a reader understands the shape of the tree without seeing individual files - In Related Concepts, explain the precise boundary that distinguishes this mechanism from each related one

{ "prompt": "# Prompt: Create a New Concept File\n\n## Prerequisites\n\nBefore starting, you need:\n\n1. The **category** slug (from `docs/contributing/references/taxonomy.md`)\n2. The **mechanism** slug (kebab-case, e.g. `sql-injection`)\n3. Confirmation that `data/catalog/<category>/<mechanism>/README.md` does not already exist\n\n## Procedure\n\n### Step 1 — Verify the category exists\n\nCheck `docs/contributing/references/controlled-vocabularies.yaml` to confirm the category slug is registered. If it's a new category, follow the extension process in `docs/contributing/references/taxonomy.md`.\n\n### Step 2 — Create the directory\n\n```\ndata/catalog/<category>/<mechanism>/\n```\n\n### Step 3 — Derive the ID\n\nThe `id` is `<category>.<mechanism>`. Example: `injection.sql-injection`. See `docs/contributing/guides/naming-and-ids.md` for the full derivation rules.\n\n### Step 4 — Write the file\n\nCopy `docs/contributing/templates/concept.md` and fill in every section.\n\n**Frontmatter fields:**\n\n| Field | Value |\n| ---------------- | ------------------------------------------- |\n| `schema_version` | `1` |\n| `type` | `concept` |\n| `id` | `<category>.<mechanism>` |\n| `title` | Human-readable mechanism name |\n| `category` | category slug |\n| `mechanism` | mechanism slug |\n| `status` | `draft` |\n| `tags` | kebab-case list, relevant to this mechanism |\n| `aliases` | common alternate names |\n| `external_refs` | CWE/CAPEC/OWASP if useful, never structural |\n\n**Body sections (in order):**\n\n1. **Summary** — 2-4 sentences. Dense technical prose.\n2. **Root Cause** — The mechanical reason this class of bug exists.\n3. **Common Manifestations** — Use `###` sub-headings for each axis of variation. The axes are FLEXIBLE — choose the ones that matter for THIS mechanism. Examples: By Visibility, By Technique, By Timing, By Sink API.\n4. **Related Concepts** — List format (`- `). Each item: concept name + one-sentence distinction.\n5. **References** — List format (`- `). Markdown links.\n\n### Step 5 — Validate\n\nRun `make lint` and fix any errors before finalizing.\n\n## Depth Requirement\n\nWrite with the depth of a professional security audit report:\n\n- Explain the mechanical _why_, not just the _what_\n- In Root Cause, trace the exact trust boundary or runtime behavior\n- In Common Manifestations, describe each axis with enough detail that a reader understands the shape of the tree without seeing individual files\n- In Related Concepts, explain the precise boundary that distinguishes this mechanism from each related one", "variables": [], "notes": "Create a new concept file (README.md) for a vulnerability mechanism.", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/othonhugo/vulnerability-explorer", "path": ".github/prompts/new-concept.prompt.md", "ref": "c0ad7e1bd3857f079c921a1f20f65656649856a7", "url": "https://github.com/othonhugo/vulnerability-explorer/blob/c0ad7e1bd3857f079c921a1f20f65656649856a7/.github/prompts/new-concept.prompt.md", "key": "othonhugo/vulnerability-explorer/.github/prompts/new-concept.prompt.md" } } }

new-concept

About

Prompt: Create a New Concept File

Prerequisites

Procedure

Step 1 — Verify the category exists

Step 2 — Create the directory

Step 3 — Derive the ID

Step 4 — Write the file

Step 5 — Validate

Depth Requirement

Use it

Manifest

Reviews