Use when writing any document for external audience — Jira tickets, Confluence pages, IMS actions, GitLab MR descriptions, emails, or markdown reports
Für Dokumentenintake: ordnet Akte, Belege und Lücken; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: Word-Workflows für deutsche Juristen.
Gebruik deze skill wanneer de gebruiker vraagt om Nederlandse tekst te schrijven, herschrijven, redigeren, menselijker te maken of te polijsten zodat die natuurlijk, specifiek en…
Professional writing and editing principles for clear, concise documentation and prose. Use when asked to write, edit, rewrite, or review documents, README.
Wählt für einen konkreten juristischen Schreibauftrag den passenden Bearbeitungsweg: Vertragsänderung, Schriftsatz, Mandantenbrief oder zweisprachige Fassung.
Rédige des emails professionnels ou personnels adaptés au contexte et à l'objectif. À utiliser quand l'utilisateur veut écrire un email important.
Help users with technical documentation writing. Invoke when user asks for documentation help, API docs, or technical content drafting.
Expert-level guide to writing expert 179. Comprehensive coverage of advanced concepts, production implementation, and optimization strategies.
Expert-level guide to writing expert 203. Comprehensive coverage of advanced concepts, production implementation, and optimization strategies.
Expert-level guide to writing expert 53. Comprehensive coverage of advanced concepts, production implementation, and optimization strategies.
Expert-level guide to writing expert 77. Comprehensive coverage of advanced concepts, production implementation, and optimization strategies.
Expert-level guide to writing expert 89. Comprehensive coverage of advanced concepts, production implementation, and optimization strategies.
Use when writing documentation, guides, API references, or technical content for developers - enforces clarity, conciseness, and authenticity while avoiding AI writing patterns…
Internal writing discipline for artifacts consumed primarily by AI agents, including skills, AGENTS.md or CLAUDE.md, context pointers, plans, handoffs, intermediate working…
Use when writing prompts, agent instructions, SKILL.md, commands, system prompts, Task tool prompts, prompt engineering, or LLM-to-LLM content — from TechNickAI/ai-coding-config
Use when writing prompts, agent instructions, SKILL.md, commands, system prompts, Task tool prompts, prompt engineering, or LLM-to-LLM content — from…
Use when structuring prose so readers can skim it - drafting or restructuring READMEs, docs, PR or issue bodies, design docs, RFCs, or any long-form text where a wall of prose…
Conceptual guidance for writing functional specifications. Use when creating or reviewing functional.md files.
Use when committing changes, splitting work into commits, or writing commit messages - covers atomic commits, bisect-able history, separating concerns, and message style
Prepare, open, edit, or review evidence-rich GitHub pull requests under each repository's rules. Use for PR creation, drafting, write-ups, readiness checks, validation summaries,…
Use when writing or editing Go code in cc-port — any change to a `**/*.go` file that adds, modifies, or removes implementation logic, signatures, or comments.
Write tasks in the following format. You can exclude some parts if they do not make sense for the particular task.
Use when writing or reviewing tests - covers test philosophy, condition-based waiting, mocking strategy, and test isolation
Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable. — from sickn33/antigravity-awesome-skills
Review docs/prose for Writing Guidelines compliance. Use when asked to "review my docs", "check writing style", "audit prose", "review docs voice and tone", or "check this page…
Author a new Agent Skill for a Hive agent that conforms to the Agent Skills specification (SKILL.md with YAML frontmatter, optional scripts/references/assets directories).
How to write Claude Code hooks — lifecycle events, exit codes, profile system, shell patterns, best practices
Use when creating a new skill, editing an existing one, or verifying a skill triggers correctly and works standalone
Use when writing or editing human-readable prose such as docs, PRs, issues, release notes, errors, UI copy, commits, tooltips, or support replies, especially when text sounds…
Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact fi — from…
Compose a writing instruction from voice, tone, style, and format axis entries. Use when you need a precise writing instruction for a specific combination of voice, tone, style,…
Creates IC presentation materials with deal thesis, risk analysis, and recommendation structure. Use when preparing IC memos, presenting deal opportunities, or documenting…
Formulates structured bull/bear investment theses with variant perception and key risk identification.
Creates IRB submission packages with protocol summaries, consent forms, and risk-benefit analysis. Use when submitting to IRB, preparing ethics applications, or writing consent…
Logging and referencing writing issues: craft problems, tics, inconsistencies, and structural concerns found during analysis, critique, or review.
Shapes the body text when creating a GitHub issue or pull request, so the result is concise, plain-spoken, and leads with the bigger picture instead of reading like a robotic…
Help users write effective job descriptions. Use when someone is creating a job posting, defining a new role, preparing to hire, or trying to attract the right candidates for an…
Use when writing BDD specs, feature files, or acceptance tests in Given-When-Then format. Use when editing *.feature.md files or writing requirements with behavioral scenarios.
Reference for the microplan document format. Provides structure, naming conventions, and writing guidelines for creating microplan files. Use when creating microplan documents.
Use when the user asks to create or update the shared basing or miniature-base tutorial for a figurine project in this wiki.
Use when the user asks to create or update a miniature or figurine painting tutorial in this wiki, including paint recipes, project color schemes, basing, or an illustration of…
Use when starting or appending to a modpack project dev-log. Creates
/docs/dev-log.md if absent; appends a dated entry on subsequent calls.
새 Nova 스킬을 작성하거나 기존 스킬 description을 수정할 때. — MUST TRIGGER: skills/ 하위 신규 SKILL.md 생성, 기존 SKILL description 리팩터, 사용자가 'Nova 스킬 추가/수정' 요청 시.
Use when creating or editing a skill in this offensive-claude repo — for the SKILL.md conventions (trigger descriptions, technique map, runnable scripts, OPSEC/detection,…
Creates structured operative notes with findings, technique, specimens, and estimated blood loss. Use when dictating operative reports, documenting surgical procedures, or…
How to work in a Writing Pipeline project (the `writing-pipeline` starter pack): a three-stage drafting flow, ideas → drafts → published.
Create detailed implementation plans with bite-sized tasks for engineers with zero codebase context
Use when you have a spec or requirements for a multi-step task, before touching code — from bg-szy/TOP-SKILLS
Use when you have a spec or requirements for a multi-step task, before touching code — from bg-szy/TOP-SKILLS
Use when you have a spec or requirements for a multi-step task, before touching code — from bg-szy/TOP-SKILLS
Create detailed implementation plans with granular tasks. Use before implementing features or complex changes.
Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact fi — from…
Use when you have a spec or requirements for a multi-step task, before touching code — from bg-szy/TOP-SKILLS
Use when you have a spec or requirements for a multi-step task, before touching code — from bg-szy/TOP-SKILLS
Use when you have a spec or requirements for a multi-step task, before touching code — from bg-szy/TOP-SKILLS
Use when you have a spec or requirements for a multi-step task, before touching code. Codex-backed variant. — from mzored/superpowers-cc-to-codex
Use when you have a spec or requirements for a multi-step task that may benefit from parallel team execution, before touching code.
Use when you have a spec or requirements for a multi-step task, before touching code — from majiayu000/claude-skill-registry
Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact fi — from…
Provides patterns for writing maintainable E2E test scripts with Playwright, focusing on selector strategies, page objects, and wait handling for legacy application retrofitting.