Documentation

Docs, README files, API references, tutorials, specs, and changelogs

skills in category: 13,976
pages available: 583

Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.

Open in full browser

Browse documentation skills

Showing 145–168 of 13,976 skills

Jev RulesAUse when a written rule should become a Jev rule check, or an existing one misbehaves — "turn this rule into a Jev rule", "add a rule check", "make this a Jev check", "calibrate this rule", "why does my rule not separate", "my rule fires on accepted work", "my rule never blocks", "the violating case scores 0.6", "park this rule", "wire this rule", "unwire it", "add a rule set for <workflow>", "add a real case for this rule". Use proactively whenever a reviewer or lens keeps re-judging the sam...documentationbackendVotes: 0GitHub stars: 22
Recovering From Verification FailuresADecide what happens after a failed check: feed evidence back, retry within bounds, escalate to a stronger model, or hand off to a human.documentationgodatabaseVotes: 0GitHub stars: 2
Formulating Typed Decision QuestionsAWrite Choice, Score and Noul questions that each ask one judgment about a state and return a typed answer your code can branch on.documentationpythonrustVotes: 0GitHub stars: 2
Translate Vietnamese FinanceATranslate supplied finance analysis to Vietnamese (vi-VN), Vietnamese number style in prose. For Parallax reports, use the analysis skill's lang=. NOT for new analysis or non-finance text.documentationpythongoVotes: 0GitHub stars: 5
Work An IssueAEnd-to-end workflow for resolving one GitHub issue in dynamic-neural-field-composer - branch, TDD, build, review, docs, PR. Use when asked to fix, implement, or close a specific issue number.documentationgobashVotes: 0GitHub stars: 16
Build ProgramAUse when building or editing a devopsdays event's schedule - adding talks, ignites, open spaces, breaks, and evening events to the program, or moving time slots around.documentationbashdevopsVotes: 0GitHub stars: 194
ReleaseAPrepare and ship a NAPT release. Phase 1 opens the release PR (version bump + changelog promotion). Phase 2 (after merge) tags and publishes the GitHub release. Detects phase automatically.documentationpythongoVotes: 0GitHub stars: 19
Mysword User DataAEspecialista nos 10 arquivos SQLite de dados do usuário MySword — os 9 arquivos em mydata/ (bookmarks.mybible, highlight.mybible, format.mybible, settings.mybible, tags.mybible, verselist.mybible, default.xrefs.twm, mapgeodata.mybible, peopledata.mybible) e notes/versenotes.mybible. Cobre: schemas SQLite de cada arquivo, Room entities com índices corretos, DAOs com queries otimizadas por capítulo, enum HighlightColor com as 11 cores exatas do MySword (light+dark), comportamento crítico do set...documentationtypescriptgoVotes: 0GitHub stars: 2
Mysword Format ParserAPipeline completo de 5 camadas para parsing de texto bíblico em Jetpack Compose AnnotatedString. Cobre DOIS formatos: GBF MySword (FR/FI/FO/FU/TS/WG/WH/WT/RF/RX/CM/PI/PF/Q) e tags HTML MyBible (<S><m><i><J><n><e><t><br/><pb/><f>). Implementação Kotlin completa: VerseRulesProcessor (TAB-separado, precompilado), GbfTagTokenizer (regex precompilado como object), GbfTagParser (máquina de estados completa com interlinear), MyBibleVerseParser (tags MyBible HTML), BibleAnnotatedStringBuilder com pus...documentationgokotlinVotes: 0GitHub stars: 2
Writing RouterARoute writing requests to the correct installed workflow. Use when a request could mean natural prose, technical documentation, repository agent instructions, or a post-draft style audit. Do not use when the user already named plain-english, simple-english, style-review, or writing-great-agents-md.documentationrustgoVotes: 0GitHub stars: 2
Style ReviewAReview existing technical Markdown for clarity, evidence, reader fit, structure, terminology, and common model-writing habits. Use for audits, A/B comparisons, or a write-beside polished draft. Uses a bundled dependency-free Node audit plus semantic judgment; do not use for fiction or voice-led prose.documentationrustshellVotes: 0GitHub stars: 2
Simple EnglishAWrite or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop. Use for documentation, READMEs, runbooks, procedures, error messages, release notes, incident reports, and API guides. Also use when the user says "STE", "Simplified Technical English", "ASD-STE100", "de-slop", "make this readable", "write for non-native readers", or asks for docs that translate well. Enforces the standard's 53 rules: 20/25-word sentence ...documentationrustgoVotes: 0GitHub stars: 2
Rust Best PracticesAGuide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook. Use this skill when: (1) writing new Rust code or functions, (2) reviewing or refactoring existing Rust code, (3) deciding between borrowing vs cloning or ownership patterns, (4) implementing error handling with Result types, (5) optimizing Rust code for performance, (6) writing tests or documentation for Rust projects.documentationrustgoVotes: 0GitHub stars: 2
Research RouterARoute technical research across the local repository, official documentation, Exa, Context7, DeepWiki, and GitHub code search. Use when coding decisions depend on current APIs, dependency versions, standards, external repositories, or public implementation evidence; not for questions answerable from the checked-out repository.documentationjavascriptjavaVotes: 0GitHub stars: 2
Plain EnglishATighten prose by stripping AI tics and applying Orwell/Gowers plain-English rules. Use when the user asks to rewrite, tighten, simplify, or detox writing — phrases like "plain English", "make this clearer", "cut the AI voice", "fix the writing", "rewrite plainly", "tighten this", "detox this". Also run as a self-audit pass before delivering long-form prose (essays, blog posts, articles, reports) so the output isn't recognisably AI-generated. Three modes: audit (flag + suggest), rewrite (deliv...documentationrustgoVotes: 0GitHub stars: 2
Git WorkflowAHandle Git commits, branches, merges, rebases, conflicts, pull requests, tags, and releases with inspect-first, non-destructive workflows. Use when a task changes repository history or asks for a Git or pull-request operation.documentationshellgitVotes: 0GitHub stars: 2
Comment AuditAAudit, prune, and standardize comments and API docstrings across TypeScript, JavaScript, Python, Go, C, and shell to match idiomatic industry standards (TSDoc, JSDoc, Google-style, Godoc, Doxygen) with zero code logic mutation. Use when the user asks to audit comments, clean up docstrings, remove redundant inline comments or banner noise, document functions or structs, or says 'yorumları temizle', 'docstring yaz', 'yorum denetimi yap', 'kod dokümantasyonu ekle', or mentions comment rot - even...documentationjavascripttypescriptVotes: 0GitHub stars: 2
doc-writerA从真实源码生成或维护技术文档：模块 API 参考、系统架构、项目上手与排障指南，以及分模块批量文档。适用于“给 X 写文档”“架构文档”“deepwiki”“项目指南”“更新文档”“文档漂移”等请求。不用于没有源码依据的产品方案或营销文案。documentationbashnodeVotes: 0GitHub stars: 2
Include Point CloudsAMake generated point clouds official built-ins of mdeck. Use when Kristofer says to include, add, promote or ship point clouds (pictures, .mdpc files) he has created (typically the .mdpc files in ./point-clouds/ at the repo root, or files he names), or to pull a point cloud someone contributed.documentationgobashVotes: 0GitHub stars: 8
Docs ManagerA[Documentation] Use when a workflow step or the user asks for a documentation update of docs impacted by code/spec/test changes (--mode=update), or first-time init of the reference-doc set from project-config (--mode=init).documentationgodocumentationVotes: 0GitHub stars: 3
Docs ManagerA[Documentation] Use when a workflow step or the user asks for a documentation update of docs impacted by code/spec/test changes (--mode=update), or first-time init of the reference-doc set from project-config (--mode=init).documentationgodocumentationVotes: 0GitHub stars: 3
Praxis CommitAExecute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/praxis-commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical groupingdocumentationbashgitVotes: 0GitHub stars: 3
WwasACreate product backlog items in Why-What-Acceptance format — independent, valuable, testable items with strategic context. Use when writing structured backlog items, breaking features into work items, or using the WWA format.documentationgoVotes: 0GitHub stars: 46
Product NameABrainstorm 5 unique, memorable product names with rationale aligned to brand values and target audience. Use when naming a new product, rebranding, or exploring product name ideas.documentationtestingVotes: 0GitHub stars: 46