Skill Detail
gamp_specs
gamp_specs is the repository bootstrap authority. It merged the earlier gamp-structure material and now owns DS generation policy, coding-style anchoring, shared documentation assets, link verification, and the portable file-size checker asset.
| Local artifacts | SKILL.md, DS.md, skill.json, examples/skillCatalog.mjs, references/, assets/specsLoader.html, assets/fileSizesCheck.sh, scripts/generate_specs_matrix.mjs, scripts/verify_docs_links.mjs, scripts/verify_static_site.js |
|---|---|
| Depends on | None |
| Repository outputs | AGENTS.md, README.md, docs/, docs/specs/, fileSizesCheck.sh |
| Primary spec | DS003-gamp-specs.md |
Operational Role
This skill defines the bootstrap contract for repository layout and documentation behavior. It specifies how `AGENTS.md` is written, how DS files are numbered and generated, how the matrix is derived from DS metadata, how link verification is run, and how `DS001-coding-style.md` is treated as the coding-style authority.
Portability Model
The skill now assumes that portable example code stays inside skill folders. The example catalog reader therefore lives in skills/gamp_specs/examples/skillCatalog.mjs rather than a repository-level src/ tree. This keeps the skill usable when copied into another project's local skills/ folder. It also makes the downstream documentation boundary explicit: consumer projects document their own systems under docs/ and keep imported-skill guidance inside the copied skill folders.
Documentation Tooling
The skill carries the specs loader asset, a matrix generator, a static-site verifier, and a new HTML link verifier. The intended flow after documentation changes is to regenerate the matrix from DS frontmatter and then verify that HTML links and specs-loader references resolve locally. Design rationale now lives inside each DS under numbered Decisions & Questions entries rather than in a separate repository decision log.
Code-Style Enforcement
gamp_specs also ships assets/fileSizesCheck.sh, which downstream projects can copy to their root. The current project keeps the same script at the repository root and uses it as the practical source for file-size and line-length guidance referenced by DS001.