repo-baselinelisted

Use when creating a new repository, or auditing an existing repo's hygiene and developer tooling. What every repo carries before its first feature: hygiene files, secret scanning in pre-commit and CI, one-command onboarding, operational script conventions, workflow lifecycle and archiving, in-repo AI agent definitions with allowlisted tools and repo-relative paths, declaring architecture-standards adoption via `.claude/settings.json` rather than relying on memory, and documentation staleness rules.
konradcinkusz/architecture-standards · ★ 0 · AI & Automation · score 72

Install: claude install-skill konradcinkusz/architecture-standards

# Repository baseline and developer tooling **Read [`references/REPO-BASELINE.md`](references/REPO-BASELINE.md) before applying any of this.** That file is the standard; everything below it is a summary to help you decide whether this skill applies and to check your work afterwards. ## What this standard covers - The baseline - Secret hygiene - One-command onboarding - Operational scripts - Scripts that onboard the *product's* user - A dependency budget, declared in public - Research artifacts live in the repository - Workflow lifecycle - AI agent definitions live in the repo - Standards adoption is declared, not remembered - Documentation staleness ## Checklist - [ ] `CODEOWNERS`, dependency-update automation, `.editorconfig`, central package management, PR/issue templates, real `.gitattributes`, exclusion-based `.dockerignore` - [ ] Secret scanning pre-commit + CI; local scripts read secrets from gitignored `.env` with a committed example file; rotation before history-scrubbing - [ ] One-command interactive setup: prerequisites, secret store init, generated mandatory secret, labeled optional integrations; error-text-keyed troubleshooting table; secret-flow documented - [ ] Where the product's own users configure something: an enable/disable script that documents the vendor's dialect, cleans up after older versions of itself, and ends with a real-traffic smoke test - [ ] Per-project dependency counts published; hand-rolling justified only by a small, stable, versioned p