Style guidelines for justfile recipe documentation. Use when writing or editing justfiles to ensure consistent and concise documentation.
Scanned 2/10/2026
Install via CLI
openskills install majiayu000/claude-skill-registry---
name: justfile-style
description: Style guidelines for justfile recipe documentation. Use when writing or editing justfiles to ensure consistent and concise documentation.
---
# Justfile Style Guidelines
This skill provides best practices for writing justfile recipe documentation comments.
## Doc Comment Simplification
For very short justfile recipes, change the doc comment string to be the entire command instead of a descriptive phrase.
### When to Simplify
- The cutoff for when to perform this refactoring should be approximately a single line of 120 characters
- If the recipe is a shebang recipe, don't shorten the doc comment
- If the recipe is multiple lines, or longer than 120 characters, don't shorten the doc comment
### Example Transformation
❌ Before:
```justfile
# Install dependencies
[group('setup')]
install:
npm install
```
✅ After:
```justfile
# npm install
[group('setup')]
install:
npm install
```
### Rationale
For simple, single-command recipes, the command itself is often more informative than a descriptive phrase. This approach:
1. **Reduces redundancy**: "Install dependencies" vs "npm install" convey the same information
2. **Shows the actual command**: Users can see exactly what will run
3. **Maintains consistency**: All simple recipes follow the same pattern
4. **Improves scannability**: The actual command is immediately visible
### When NOT to Simplify
Keep descriptive doc comments for:
1. **Multi-line recipes**:
```justfile
# Set up development environment
[group('setup')]
dev-setup:
npm install
cp .env.example .env
just db-migrate
```
2. **Shebang recipes**:
```justfile
# Generate API documentation
[group('docs')]
gen-docs:
#!/usr/bin/env bash
set -euo pipefail
# ... multiple lines of bash script
```
3. **Long single-line commands** (>120 characters):
```justfile
# Build production bundle with optimizations
[group('build')]
build-prod:
webpack --mode production --config webpack.prod.js --optimization-minimize --output-path dist/
```
In these cases, a descriptive comment provides more value than repeating the complex command.
No comments yet. Be the first to comment!
Use this skill when developing or maintaining browser extension code in the `browser/` directory, including Chrome/Firefox/Edge compatibility, content scripts, background scripts, or i18n updates.
SEO optimization with keyword analysis, readability assessment, technical validation, content quality. Use for search rankings, blog posts, content audits, or encountering keyword density, readability scores, meta tags, schema markup errors.
Python backend development expertise for FastAPI, security patterns, database operations, Upstash integrations, and code quality. Use when: (1) Building REST APIs with FastAPI, (2) Implementing JWT/OAuth2 authentication, (3) Setting up SQLAlchemy/async databases, (4) Integrating Redis/Upstash caching, (5) Refactoring AI-generated Python code (deslopification), (6) Designing API patterns, or (7) Optimizing backend performance.
Drive the full internationalization journey for a project — detect the stack, recommend a library, set up the chosen library, wrap existing strings, and optionally connect a translation platform. Use when the user asks to add or configure i18n, internationalization, localization, multi-language support, or translations — including when they explicitly mention LinguiJS, Lingui, next-intl, "wrap strings", "find hardcoded text", "make my app translatable", or "set up translations". Triggers on g...
PTES-aligned adversarial security audit for backend, frontend, and mobile applications. Produces a CVSS-scored Hacker Report with verified PoCs and phased remediation.