From forge-core
Fix indentation, fence language tags, heading depth, and frontmatter fields to match forge conventions. USE WHEN an adopted community skill or any prompt-shaped document fails a forge convention check (indent, fence, heading, schema).
npx claudepluginhub n4m3z/forge-coreThis skill is limited to using the following tools:
Bring a prompt-shaped document into forge convention without changing its meaning. Referenced by [ForgeAdopt](../ForgeAdopt/SKILL.md) as the `align` transform.
Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.
Processes PDFs: extracts text/tables/images, merges/splits/rotates pages, adds watermarks, creates/fills forms, encrypts/decrypts, OCRs scans. Activates on PDF mentions or output requests.
Share bugs, ideas, or general feedback.
Bring a prompt-shaped document into forge convention without changing its meaning. Referenced by ForgeAdopt as the align transform.
| Axis | Forge convention |
|---|---|
| Indentation | Four spaces. No tabs. Applies to markdown, YAML, TOML, JSON, code blocks. |
| Fence tags | Every fenced code block carries a language tag. Use sh, not bash. |
| Heading depth | Max depth 3. No skipped levels (no H1 to H3 without H2 between). |
| Heading style | One H1 per document, matching the skill name in PascalCase. |
| Frontmatter keys | name, description, version. Strip upstream fields forge does not use. |
| Skill name | PascalCase, two words, scope plus focus (for example SecurityBestPractices). |
| Table alignment | Pipes line up vertically; pad cells with spaces to the widest column. |
| Trailing newline | Every text file ends with a single \n. |
| Wikilinks / paths | Spaces literal, not URL-encoded. |
argument-hint, allowed-tools, hooks)