Results for “writing”

Create, edit, and verify agent skills using test-driven development to ensure agents follow documented procedures correctly.

Drafts professional emails that match your personal writing style by analyzing sent emails for tone, greeting, structure, and sign-off patterns.

Drafts concise, truthful English appeals for GitHub account restrictions, tailored to the user's situation and GitHub Support form fields.

Runs a structured, multi-round brainstorm to capture actors, features, scope, constraints, and business rules for a project before writing a spec.

Adopts the satirical voice and techniques of British comedian Peter Cook to craft witty, character-driven responses that expose pomposity and hypocrisy.

Generates ad copy, email sequences, long-form articles, and product descriptions with structured briefs and templates for content production.

Propose specific, actionable test cases for a target module — without writing the actual test code. Use this skill whenever the user wants to know "what should I test", "what test cases would catch real bugs in X", "I have a finding from test-assessment, what tests would close that gap", "suggest tests for this file", or wants to think through coverage before writing. Pairs with the test-assessment skill (which finds gaps); writing the test code itself happens as a normal follow-up task once the suggestions are reviewed. This skill stops at suggestions — if the user wants code generated, redirect them. Trigger even on casual phrasings ("what should I test in auth.ts", "give me test ideas for this module").

Maintain durable session memory across agent disconnects by writing structured checkpoints to the repo's session directory, enabling context recovery.

Adopts the voice and comedic methodology of Louis C.K. to craft brutally honest, self-deprecating observations about everyday life, parenting, and modern society.

Embody the voice and methodology of comedian Bill Hicks, using dark humor and philosophical confrontation to critique society, consumerism, and hypocrisy.

Makes AI responses feel more human by adding an inner dialogue loop that reflects on and revises the initial instinctive reply.

Write, edit, or audit content in Alan Hirsch's exact voice using five voice markers, argument patterns, rhetorical posture, and failure mode guards.

Imports external plan files into a GSD-structured project, detecting conflicts against existing roadmap, requirements, and locked decisions before writing a validated PLAN.md.

Guides the creation, editing, and verification of agent skills using a test-driven development approach, with structured documentation and quality gates.

Crafts concise, specific investor emails—outreach, warm intros, follow-ups, updates, and closing notes—with a clear single ask and strong proof points.

Writes and manages professional bios for any platform and purpose, matching your voice and career stage, and keeping them current as your work evolves.

Turns a spec or requirements into a detailed, bite-sized implementation plan with exact file paths, code, and test steps for engineers with no codebase context.

Transforms earnest content into playful, satirical material using the voice and techniques of Eric Idle, including musical comedy, wordplay, and cheerful subversion.

Creates detailed, step-by-step implementation plans from specs or requirements, with task decomposition, file structure, and test-driven development instructions.

Helps software engineers with discrete job search tasks: job description analysis, CV tailoring, cover letter writing, offer evaluation, and follow-up emails.

Manage email accounts from the terminal using IMAP and SMTP with the Himalaya CLI, supporting listing, reading, writing, replying, forwarding, searching, and organizing messages across multiple accounts.

Builds a reusable writing style profile from real source material and applies it across content, outreach, and social workflows for consistent brand voice.

Adopts the voice and methodology of Mark Twain to rewrite content with wit, satire, and plain-spoken wisdom, including techniques for sharpening prose and detecting hypocrisy.

Enforce writing specifications before any code, with structured formats, acceptance criteria, and validation to reduce rework and clarify requirements.

Draft performance reviews, self-assessments, peer reviews, and upward feedback in your own voice using WorkIQ to surface actual contributions and structure them into impact-focused writing.

Maintains a persistent session memory across Claude sessions by loading project state at startup, capturing errors and decisions during work, and writing structured handoff summaries at session end.

Use before touching any code when user gives a task, spec, or feature request. Forces writing a plan before implementation. Examples: 'implement X', 'add feature Y', 'fix Z and also update A', any multi-step task that would touch 2+ files.

Use when planning a COLT (Conference on Learning Theory) submission calendar backward from the single AoE paper deadline — proof-completion and verification milestones, writing and appendix-assembly passes, CMT logistics, the rebuttal window, decision aftermath, and PMLR camera-ready with conference presentation in early summer.

Short clarifying interview before starting non-trivial engineering work — surfaces the actual requirement, what's explicitly out of scope, and what proves it's done. Use before writing code when the task's requirement, scope, or definition of done isn't already unambiguous. Not for trivial or fully-specified changes — that's ceremony, not clarity.

PROACTIVE SKILL — automatically apply whenever writing, generating, or editing any text that is mainly in Chinese. No user trigger needed. Also use when the user explicitly asks to "fix Chinese", "修改中文", "去翻译腔", "去AI味", "fix Chinese formatting", or "review Chinese text". Eliminates AI-sounding expressions and translation artifacts. Enforces Chinese-English mixed formatting rules (spacing, punctuation, bold formatting).

Work ZenTao bugs/tasks end to end, manage task lifecycle and hours, or read a linked story as development context: fetch details, handle the user's request, verify changes, and ask before committing or writing back to ZenTao. Supports single items and sequential batches. Use when the user references ZenTao (禅道) bugs, tasks, stories, requirements, task status, or task hours.

Author pull requests with intent-separated commits, blast-radius disclosure, and verification evidence. Load when opening a PR, writing a PR description, separating refactor from feature commits, or summarizing a change set for review. Also triggers on "write the PR", "PR body", "intent-separated commits", "split refactor from feature", "pr summary", or after safe-change cycles complete. Extends git-workflow-and-versioning — does not replace it.

Best practices and patterns for C# async/await programming including Task and ValueTask usage, CancellationToken propagation, IAsyncDisposable and await using, ConfigureAwait, async streams (IAsyncEnumerable), parallel task execution, and common pitfalls like deadlocks and async void. Use this skill whenever writing, reviewing, or refactoring asynchronous C# code — including when the user mentions async methods, Task-returning APIs, cancellation, deadlocks, blocking on async code, or resource disposal in async contexts, even if they do not explicitly say "async best practices."

Local CLI issue tracker for todos, follow-ups, structured records, and the canonical pattern for decomposing multi-step work into a parent + subissues with acceptance criteria, dependency edges, and priority. Use when the user mentions a task to remember, a bug to track, an open question, anything that needs to outlive the current turn, or when planning multi-heartbeat work that needs `chainlink issue ready`-driven pickup across sessions. Includes guidance on writing descriptions future-you can act on (handles, success path, failure path) and idempotency tactics for actions that might fire twice (boundary firing, overlapping heartbeats, retried subagent completion). Pairs with five-whys (chainlink is the storage backend for RCA trees). Storage is local — issues live under a `.chainlink/` directory in the operator's repo.