Total 54,046 skills, Documentation & Writing has 1524 skills
Showing 12 of 1524 skills
Use this skill when writing, reviewing, or structuring technical documentation for software projects. Triggers on API documentation, tutorials, architecture decision records (ADRs), runbooks, onboarding guides, README files, or any developer-facing prose. Covers documentation structure, writing style, audience analysis, and doc-as-code workflows for engineering teams.
Drafts irrevocable third-party Special Needs Trusts funded by parents, grandparents, or other non-beneficiary parties to supplement government benefits without triggering Medicaid payback obligations. Use when drafting supplemental needs trusts, third-party SNTs, estate planning disability trusts, special needs trust agreements, or any trust intended to preserve SSI/Medicaid eligibility for a disabled beneficiary using third-party assets. Also trigger when the user asks about permissible SNT distributions, in-kind support and maintenance rules, ABLE account coordination, or remainder beneficiary planning for disability trusts.
Use when writing blog posts, X/Twitter threads, newsletters, or any founder-voice content — raw, specific, no fluff
Generate blog post topic ideas through problem mining, gap analysis, and technology expansion. Use when user needs content ideas, wants to brainstorm articles, asks "what should I write about", or needs to fill content gaps. Use for "brainstorm", "topic ideas", "what to write", "content gaps", or "blog ideas". Do NOT use for writing posts, creating outlines, or SEO optimization without a specific ideation need.
Map an existing codebase into an as-is Memory Bank without inventing roadmap items.
Draft a technical Request for Comments (RFC) or technical proposal document based on a rough idea or scattered requirements. Triggers when the user asks to write an RFC, draft a technical proposal, or structure an architecture design.
Audit top-level documentation (README, SPEC, PRODUCT) against recent git history to find drift — shipped features missing from docs or features listed as upcoming that already landed. Proposes minimal edits, creates a branch, and opens a PR. Use when asked to review docs for accuracy, after major feature merges, or on a periodic schedule.
Run a structured discovery session to build an Allium specification through conversation. Use when the user wants to create a new spec from scratch, elicit or gather requirements, capture domain behaviour, specify a feature or system, define what a system should do, or is describing functionality and needs help shaping it into a specification.
Use when drafting or revising human-facing prose such as docs, essays, prompts, UI copy, reports, commit messages, PR text, or polished long-form writing. Combines anti-AI-trope editing with clear and concise style rules for stronger, more natural prose.
Use when writing or editing markdown files. Covers headings, text formatting, lists, links, images, code blocks, and blockquotes.
Write implementation-ready project specifications from ideas, plans, architecture discussions, repo research, or high-level requirements. Use when Codex needs to create, refine, audit, or structure a concrete spec with explicit contracts, boundaries, data models, lifecycle behavior, failure handling, observability, and validation criteria.
Dada WeChat Moments Copywriting Tool. Quickly convert any material into high-quality WeChat Moments posts, and output multiple ready-to-send versions. Trigger methods: /dada-moments, /moments, "Help me write a Moments post" WeChat Moments copywriting tool. Turns any raw material into ready-to-post Moments. Trigger: /dada-moments, "Help me write a Moments post", "How to write a Moments post"