prompts/skills/prompts-documents/SKILL.md
Naming conventions for workflow documents in prompts/. Use when creating plans, PRDs, research reports, idea capture or other workflow documents. Triggers on (1) creating new planning documents, (2) naming PRDs or research reports, (3) questions about document organization in prompts/.
npx skillsauth add ramblurr/nix-devenv prompts-documentsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
All workflow documents live in prompts/ with a structured naming scheme.
These are not ADRs. ADRs are separate documentation that should be kept up to date. prompts/ docs are workflow docs that by their nature will get out of date.
They are (usually) not tracked in version control. Do not commit them.
Pattern: prompts/NNN-concept.md
| Component | Description | Example |
|-----------|-------------|---------|
| NNN | Three-digit sequence number | 025 |
| concept | Kebab-case description | compositor, event-parsing |
No underscores in the primary document name.
Examples:
prompts/025-compositor.mdprompts/010-event-parsing.md| Pattern | Purpose | Example |
|---------|---------|---------|
| NNN-concept_report.md | Research findings | 025-compositor_report.md |
| NNN-concept_library_report.md | Library-specific research | 025-compositor_textual_report.md |
| NNN-concept_idea.md | Some idea/brainstorm capture | 011-cli-api_idea2.md |
Check existing documents:
ls prompts/*.md | sort -t- -k1 -n | tail -5
Use the next available three-digit number.
tools
Use when working with Nixbot CI, forge commit statuses, Nix flake checks, nixbot.toml, Nixbot effects, or nixbot-cli - explains how Nixbot runs flake CI and how to inspect builds and logs.
testing
Use this OCP when executing or preparing to execute commands that change a live or important system, service reloads/restarts, package changes, deployments, migrations, firewall/network/access changes, credential rotation, NixOS switch/test/boot/deploy, or incident mitigation. It guides safe operations with a persisted ledger for scope, preflight, baseline, rollback, validation, and evidence.
development
Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.
testing
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.