Results for “writing”

User-story-driven test coverage audit and plan — no test writing in this pass. Use when "test coverage plan", "coverage audit", "traceability matrix", "fake-green tests", "uncovered user stories", "plan tests for critical flows", or "whats not tested". Mutation score / assertion theater → test-mutation.

Use this skill when working with Brain Imaging Data Structure (BIDS) datasets: organizing neuroscience and biomedical data (MRI, EEG, MEG, iEEG, PET, microscopy, NIRS, motion capture, EMG, MR spectroscopy, behavioral), querying BIDS layouts, validating compliance, converting DICOM to BIDS, writing metadata sidecars, or creating BIDS derivatives.

Protocol-level two-agent paper writing workflow. Use when the user wants Codex to plan and review from global context while DeepSeek writes or revises the manuscript through the global deepseek-agent skill, with muxing-style-review used for explicit prose style checks.

Write business reports including executive summaries, status updates, postmortems, competitive analyses, data analyses, and quarterly reviews. Use when communicating findings, decisions, or status to stakeholders. Also trigger for 'executive summary', 'status report', 'postmortem', 'incident report', 'competitive analysis', 'quarterly review', 'business report', or 'data analysis report'.

Activate when the user is drafting any academic economics content from scratch (e.g., outlines, abstracts, introductions, data/methods/identification sections, results narratives, conclusions, referee responses, table/figure captions) and needs economics-specific structure, phrasing options, and quality checks to produce publication-ready prose.

Enforce organizational security policies across Kubernetes clusters and CI/CD pipelines using Open Policy Agent (OPA) and Gatekeeper, including writing Rego policies, deploying admission controllers, and testing policies locally.

Explains MariaDB Connector/Node.js specifics: Promise vs Callback API, placeholders, BigInt handling, batch inserts, query streams, pooling, transactions, and prepared statements, for writing or reviewing Node.js code that uses the `mariadb` package.

Explains MariaDB Connector/Python's DB API 2.0 behavior, including qmark placeholders, autocommit, prepared statements, buffered cursors, connection pooling, and error handling, for writing and reviewing Python code that uses the mariadb module.

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.

Sets up, manages, and executes queries against Cloud Firestore database instances. You MUST unconditionally activate this skill if you plan to use Firestore in any way. Use when listing or creating Firestore databases, configuring security rules, designing data models, writing client SDK queries, or checking indexes.

Analyze ab test analyzer operations. Auto-activating skill for Data Analytics. Triggers on: ab test analyzer, ab test analyzer Part of the Data Analytics skill category. Use when writing or running tests. Trigger with phrases like "ab test analyzer", "ab analyzer", "analyze ab test r".

Senior embedded software engineer specializing in firmware and driver development for ARM Cortex-M microcontrollers (Teensy, STM32, nRF52, SAMD). Decades of experience writing reliable, optimized, and maintainable embedded code with deep expertise in memory barriers, DMA/cache coherency, interrupt-driven I/O, and peripheral drivers.

Use when writing, solving, or debugging MATLAB optimization code — formulating problems (optimproblem, optimvar, fcn2optimexpr), selecting and configuring solvers (fmincon, linprog, quadprog, intlinprog, lsqnonlin, ga, surrogateopt, optimoptions), or validating results (exitflag, convergence, constraint violations). Covers problem-based and solver-based approaches, solver tuning, and solution verification.

A tool for creating and managing Garry's Mod addons, including Lua scripting, content creation, and addon packaging. Use when: developing new addons, writing Lua scripts for GMod, organizing addon files, or when user mentions Garry's Mod, GMod, Lua scripting, or addon development.

Foundational Elixir patterns covering modules, pattern matching, processes, OTP behaviors (GenServer, Supervisor), Phoenix framework basics, and functional programming idioms. Use when writing Elixir code, building concurrent systems, working with Phoenix, or needing guidance on Elixir development patterns. This is the entry point for Elixir development.

Explains MariaDB-specific behavior of DROP USER and RENAME USER, including multiple accounts per statement, IF EXISTS handling, active-connection warnings, and effects on privileges and definers. Use when writing or reviewing account-lifecycle SQL for MariaDB.

Guides the agent to research existing tools, libraries, and patterns before writing custom code, using parallel searches across package registries, MCP servers, skills, and GitHub, then evaluating and deciding to adopt, extend, or build.

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

Foundational Cypher (Neo4j) patterns covering graph pattern matching, MATCH/CREATE/MERGE/DELETE operations, relationships, path patterns, aggregation, filtering, and common graph query patterns. Use when writing Cypher queries, modeling graph data, or needing guidance on graph database operations. This is the entry point for Cypher development.

Foundational Haskell patterns covering pure functional programming, type system, type classes, monads, and common idioms. Use when writing Haskell code, understanding pure functions, working with Maybe/Either, leveraging the type system, or needing guidance on functional programming patterns. This is the entry point for Haskell development.

Write persuasive marketing copy including landing pages, product descriptions, email campaigns, CTAs, taglines, and brand messaging. Use when writing to persuade, convert, or sell rather than inform. Also trigger for 'landing page copy', 'product description', 'marketing copy', 'email campaign', 'CTA', 'tagline', 'ad copy', 'sales page', or 'conversion copy'.

Use when the user wants to humanize text, make writing sound less like AI, or rewrite content to feel more natural. Triggers on "humanize", "make it sound natural", "too robotic", "sounds like AI", or similar. Works in Hebrew and English. Always output only the rewritten text — no explanations.

Use for writing, reviewing, debugging, or testing static Python visualization with Matplotlib, including Figure, Axes, Axis, Artist, transforms, layouts, dates, categorical scales, annotations, color normalization, image export, and headless rendering. Do not use for Plotly interactivity, Altair/Vega-Lite specifications, dashboard state, or analysis without a Matplotlib artifact.

Use for writing, reviewing, debugging, migrating, or testing SQLAlchemy 2.x Core or ORM code involving Engine, Connection, Session, mapped models, select statements, transactions, pooling, results, loading, or AsyncSession. Do not use for raw database SQL with no SQLAlchemy boundary, Alembic migration design, DuckDB relations, or database administration.

Expert technical documentation specialist for developer docs, API references, and runbooks. Activate on: documentation, docs, README, API reference, technical writing, user guide, runbook, ADR, changelog, release notes, tutorial, how-to guide. NOT for: marketing copy (use copywriting skills), blog posts (use content skills), code comments (handled by developers).

Writing maintainable code - readability principles, SOLID patterns applied pragmatically, and the judgment to know when rules should bendUse when "code quality, clean code, readability, naming, SOLID, refactor, code review, best practices, maintainable, how should I structure, clean-code, solid, readability, maintainability, code-review, naming, functions, principles" mentioned.

The HyperFrames composition contract — build one renderable project. Use for composition structure, the `data-*` timing attributes, `class="clip"`, tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Also covers Tailwind projects and the STORYBOARD.md / SCRIPT.md plan formats. Read before writing composition HTML.

Never show the user a first draft. Run every writing task through a self-critique loop — draft, attack the draft as the harshest reviewer in the room, rewrite, and repeat until a full review pass finds zero flags — then return only the final plus a change log. Use for any writing the user actually cares about: emails, LinkedIn posts, newsletters, docs, announcements, client messages. Trigger whenever the user says 'run the loop', 'self-critique this', 'make it bulletproof', 'don't give me a first draft', 'be brutal', or hands over a task where quality matters more than speed. This is a single-agent loop; for the three-agent version use the-team.

Provides guidance on the history and correct usage of the em dash, enforcing a strict policy of never using em or en dashes in code or data files, and replacing them with hyphens. Also covers general punctuation rules for code comments.

Perform high-performance genomic interval operations and bioinformatics file I/O on Polars DataFrames, including overlap, nearest, merge, coverage, complement, subtract, and reading/writing BED, VCF, BAM, GFF, FASTA, and FASTQ formats with streaming and cloud-native support.

Translate a vague request or GitHub issue into a concrete, testable spec using five structured elements (problem, scope, acceptance criteria, edge cases, success criterion) before writing any code. Prevents scope creep, PR churn, and mid-implementation pivots.

Red-green-refactor test-driven development discipline — write a failing test at the public interface first, minimal code to pass it, one slice at a time. Use when writing new logic or fixing a bug (write the regression test first), for any code where correctness matters more than raw speed.

Set up and run mutation testing (StrykerJS / mutmut) to measure whether tests assert behavior, not just execute lines. Use when "add mutation testing", "are our tests real", "can our test suite be gamed", or after an agent bulk-generated tests. Coverage plan → plan-test-coverage. Writing tests → test-unit.

Use when writing or modifying the pythinker-code terminal UI in apps/pythinker-code/src/tui — components, dialogs/selectors, slash commands, themes, streaming render, or the PythinkerTUI controllers. Covers the architecture, where new features go, test placement, the theme system mechanics, and the dialog interaction/visual spec (DESIGN.md).

Foundational Java patterns covering core syntax, object-oriented programming, generics, collections, streams, lambdas, and modern Java features. Use when writing Java code, understanding the type system, working with collections/streams, or needing guidance on which specialized Java skill to use. This is the entry point for Java development.