From scribe
Generates or remediates Markdown documentation with style rules: grounded claims, active voice, imperative docstrings, no jargon or filler. For new docs, AI rewrites, style profiles.
npx claudepluginhub athola/claude-night-market --plugin scribeThis skill uses the workspace's default tool permissions.
Documentation must be grounded in specific claims rather than abstract adjectives. We avoid filler phrases like "In today's fast-paced world" and focus on delivering useful information directly. Each claim should be supported by evidence, such as specific version numbers or request rates, rather than vague descriptors like "comprehensive."
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Retrieves current documentation, API references, and code examples for libraries, frameworks, SDKs, CLIs, and services via Context7 CLI. Ideal for API syntax, configs, migrations, and setup queries.
Uses ctx7 CLI to fetch current library docs, manage AI coding skills (install/search/generate), and configure Context7 MCP for AI editors.
Documentation must be grounded in specific claims rather than abstract adjectives. We avoid filler phrases like "In today's fast-paced world" and focus on delivering useful information directly. Each claim should be supported by evidence, such as specific version numbers or request rates, rather than vague descriptors like "comprehensive."
We prioritize authorial perspective and active voice to maintain a consistent team tone. This involves explaining the reasoning behind technical choices, such as selecting one database over another, rather than providing neutral boilerplate. Bullets should be used sparingly for actionable summaries; multi-line bullet waterfalls should be converted to short paragraphs to preserve nuance.
Avoid business jargon and linguistic tics like mirrored sentence structures or excessive em dashes. We use the imperative mood for docstrings (e.g., "Validate input") and strictly avoid humanizing non-living constructs like code.
| Instead of | Use |
|---|---|
| fallback | default, secondary |
| leverage | use |
| utilize | use |
| facilitate | help, enable |
| comprehensive | thorough, complete |
"Lives under," "speaks to," and similar phrases only make sense for living things.
"Validate" not "Validates" (per PEP 257, pydocstyle, ruff).
doc-generator:scope-defined - Target files and type identifieddoc-generator:style-loaded - Style profile applied (if available)doc-generator:content-drafted - Initial content createddoc-generator:slop-scanned - AI markers checkeddoc-generator:quality-verified - Principles checklist passeddoc-generator:user-approved - Final approval receivedFor new documentation:
## Generation Request
**Type**: [README/Guide/API docs/Tutorial]
**Audience**: [developers/users/admins]
**Length target**: [~X words or sections]
**Style profile**: [profile name or "default"]
If a style profile exists:
cat .scribe/style-profile.yaml
Apply voice, vocabulary, and structural guidelines.
Follow the 10 core principles above. For each section:
Skill(scribe:slop-detector)
Fix any findings before proceeding.
Verify against checklist:
For cleaning up existing content:
Load: @modules/remediation-workflow.md
# Get slop score
Skill(scribe:slop-detector) --target file.md
For large files (>200 lines), edit incrementally:
## Section: [Name] (Lines X-Y)
**Current slop score**: X.X
**Issues found**: [list]
**Proposed changes**:
1. [Change 1]
2. [Change 2]
**Before**:
> [current text]
**After**:
> [proposed text]
Proceed? [Y/n/edit]
Never change WHAT is said, only HOW. If meaning is unclear, ask.
After edits, re-run slop-detector to confirm improvement.
When editing code comments:
modules/generation-guidelines.md for content creation patternsmodules/quality-gates.md for validation criteria| Skill | When to Use |
|---|---|
| slop-detector | After drafting, before approval |
| style-learner | Before generation to load profile |
| sanctum:doc-updates | For broader doc maintenance |