project-config-and-tests
Project Config And Tests
This is a composable overlay, not a standalone workflow. Use alongside the repo's principle skill (e.g. coding-guidance-cpp) when the main task is config behavior or test coverage.
When to use
The task involves config parsing, defaults, path resolution, normalization, or adding deterministic test coverage around these seams.
Not for
General feature work (use project-core-dev), vendored dependency changes (use project-vendor-boundary), or release/packaging work (use project-release-maintainer).
Rules
- keep config parsing non-fatal where that preserves recovery/help paths
- keep defaults, example config, and docs aligned
- prefer deterministic tests around parsing, normalization, and helper seams using the repo's test framework
- keep WHAT/HOW/WHY commentary current in repo-owned tests
- add benchmarks for performance-sensitive helpers using the repo's benchmark framework when available
- use the repo's coverage tooling to verify test coverage for new code when it exists; otherwise state the manual or structural evidence used
Examples
- config default changed but docs/examples still show the old value
- path helper normalization needs deterministic tests across relative, absolute, missing, and platform-specific paths
More from n-n-code/n-n-code-skills
project-vendor-boundary
Overlay for app-owned versus vendored dependency boundaries. Portable across repos that vendor third-party code. Use when work touches vendored dependencies or their integration seam.
19coding-guidance-cpp
C++ implementation and review skill. Use when writing, modifying, refactoring, or reviewing C++ code, especially modern C++17/20/23 code that needs strong ownership, type safety, and testable design. Portable across C++ repos and build systems.
18project-platform-diagnose
Overlay for environment-sensitive diagnosis — service startup, install issues, platform integration, headless/container behavior, and runtime smoke checks. Portable across repos where build, install, or runtime behavior depends on the local platform.
18documenter
Baseline overlay for substantial documentation authoring or restructuring: README, specs, ADRs, tutorials, how-to guides, reference docs, explanations, API docs, code comments, changelogs, and agent-facing docs. Use when the agent should classify doc type, ground claims in repo truth, and validate examples before finishing.
18security
Security workflow skill for repo-grounded threat modeling, exploit-focused security review, and secure-by-default implementation guidance. Use when the user explicitly asks for security work, or when security properties are the primary concern in a high-risk change. Do not trigger for ordinary code review, routine endpoint work, or general backend implementation just because a repo contains APIs, auth, or secrets.
18project-release-maintainer
Overlay for release-facing docs, install layout, workflows, licenses, and hygiene scripts. Portable across repos with a release/packaging pipeline. Use for publication-facing changes.
17