jd-docs
Scaffold, validate, and maintain Johnny.Decimal documentation structure for software projects. Use when user mentions "Johnny Decimal", "J.D docs", "docs structure", "organize docs", "documentation layout", "scaffold docs", "docs migration", "generate index", "docs index", "add area", "classify docs", "move doc", editing files in numbered directories (00-*, 10-*, 20-*), or discussing documentation organization.
What this skill does
# Johnny.Decimal Documentation
Scaffold, validate, and maintain [Johnny.Decimal](https://johnnydecimal.com/) documentation structure with sensible defaults and per-project customization.
## Quick Start
```bash
# Scaffold a new structure
uv run scripts/jd_init.py --dry-run # Preview first
uv run scripts/jd_init.py # Create docs/ with defaults
uv run scripts/jd_init.py --diataxis # Include Diataxis areas (41-44)
# Validate existing structure
uv run scripts/jd_validate.py --dir docs
# Regenerate README index
uv run scripts/jd_index.py --dir docs
# Day-2: Add a new area
uv run scripts/jd_add_area.py --prefix 40 --name operations --dry-run
# Day-2: Classify unorganized files
uv run scripts/jd_classify.py docs/*.md
uv run scripts/jd_classify.py docs/*.md --diataxis # With quadrant info
# Day-2: Move a file to an area
uv run scripts/jd_add.py docs/roadmap.md 00 --dry-run
```
See [WORKFLOW.md](WORKFLOW.md) for the full methodology.
## Capabilities
- **Scaffolding** (`jd_init.py`) — Create J.D directory tree with README templates; supports `--product` for monorepo sub-trees, `--init-config` to generate `.jd-config.json`, and `--diataxis` to include Diataxis quadrant areas (41-44)
- **Validation** (`jd_validate.py`) — Check `NN-kebab-case` naming, detect orphan files, verify README presence per area; `--strict` for CI enforcement
- **Index generation** (`jd_index.py`) — Generate/update root README with table or tree index; preserves custom content via `<!-- JD:INDEX:START/END -->` markers
- **Migration** (Claude-driven) — Classify flat docs into J.D areas using naming heuristics, present a move plan, execute interactively
## Day-2 Operations
- **Add area** (`jd_add_area.py`) — Create a new J.D area with prefix, name, README stub, config update, and auto re-index
- **Classify** (`jd_classify.py`) — Classify files into areas using keyword heuristics with confidence scoring (high/medium/low); `--diataxis` adds Diataxis quadrant column, `--diataxis-move` routes files to quadrant areas (41-44)
- **Add/move file** (`jd_add.py`) — Move a file to an area with auto-normalized kebab-case naming and cross-reference detection
## Default Area Scheme
| Prefix | Name | Purpose |
|--------|------|---------|
| `00-` | getting-started | Onboarding, setup, quick start, MVP |
| `10-` | product | Specs, features, roadmap, design, branding |
| `20-` | architecture | Tech decisions, system design, integration |
| `30-` | research | Spikes, investigations, reference material |
| `90-` | archive | Historical/deprecated docs |
Gap at 40-80 reserved for per-project customization (e.g., `40-operations`).
**With `--diataxis`**, areas 41-44 are added for Diataxis quadrants:
| `41-` | tutorials | Tutorials — step-by-step lessons (Diataxis) |
| `42-` | how-to | How-to guides — practical tasks (Diataxis) |
| `43-` | reference | Reference — technical descriptions (Diataxis) |
| `44-` | explanation | Explanation — conceptual discussions (Diataxis) |
## Config File (.jd-config.json)
Optional per-project override at project root:
```json
{
"version": 1,
"root": "docs",
"areas": { "00": "getting-started", "10": "product", "20": "architecture", "30": "research", "90": "archive" },
"products": [],
"ignore": ["adr", "*.pdf"],
"readme_format": "table"
}
```
Create with `uv run scripts/jd_init.py --init-config`. All fields have sensible defaults.
## Common Issues
| Issue | Fix |
|-------|-----|
| `uv` not found | `curl -LsSf https://astral.sh/uv/install.sh \| sh` or run with `python3 scripts/jd_init.py` |
| Orphan files in validation | Move to area dir, or add to `"ignore"` in `.jd-config.json` |
| Index appended at wrong position | Move `<!-- JD:INDEX:START/END -->` markers to desired location after first run |
| Low confidence on all files | Expand keywords in config or use Claude-driven classification |
See [TROUBLESHOOTING.md](TROUBLESHOOTING.md) for all error scenarios.
## References
- [WORKFLOW.md](WORKFLOW.md) — Full methodology (discovery, config, scaffold, validate, index, migrate, day-2)
- [EXAMPLES.md](EXAMPLES.md) — Real-world examples for all operations
- [TROUBLESHOOTING.md](TROUBLESHOOTING.md) — Error handling and debugging tips
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.