Results for “writing”

Enforces an algorithm-first discipline: state Big-O, data structure, and algorithm family before writing loops, queries, or recursion to catch O(n²), N+1, and brute-force defaults.

Write professional press releases in AP style with inverted pyramid structure, including formatting, datelines, quotes, boilerplates, and fact-checking via the inference.sh CLI.

Help founders close their first customers and build repeatable sales processes. Use when someone is doing founder-led sales, trying to get their first customers, writing cold outreach, running early sales calls, or asking when to hire their first salesperson.

Essential Zephyr RTOS kernel services. Covers thread lifecycle and priority, the logging subsystem for diagnostics, and the interactive shell for real-time hardware inspection and debugging. Trigger when writing application flows, adding logging to modules, or creating interactive CLI commands.

Foundational TypeScript patterns covering types, interfaces, generics, utility types, and common idioms. Use when writing TypeScript code, understanding the type system, or needing guidance on which specialized TypeScript skill to use. This is the entry point for TypeScript development.

Take over Active Directory user and computer accounts by writing alternate certificate keys to msDS-KeyCredentialLink (Shadow Credentials) with pyWhisker, Whisker, and Certipy, then authenticate via PKINIT.

Enforces an algorithm-first discipline: state Big-O, data structure, and algorithm family before writing loops, queries, or recursion, catching O(n^2), N+1, and brute-force defaults.

Use before any writing begins to stress-test whether a result clears PNAS's bar — high quality and broad significance to a general scientific readership — and to make the realistic call between PNAS, Science/Nature, and a specialist field journal.

Use to structure and tighten an NEJM Original Article into terse IMRAD — short main text (~2700 words), limited references, claim-first results, and a sober discussion with explicit limitations and calibrated clinical implications. Enforces NEJM's plain, concise house style.

Use to structure a PNAS main text and hold its length — Title, Significance Statement, Abstract, Introduction, Results, Discussion, in-text Materials and Methods, references — and to choose the required Classification (Biological/Physical/Social Sciences + minor subject) and keywords at submission.

Test Data Builder - Auto-activating skill for Test Automation. Triggers on: test data builder, test data builder Part of the Test Automation skill category. Use when writing or running tests. Trigger with phrases like "test data builder", "test builder", "test".

Test Retry Config - Auto-activating skill for Test Automation. Triggers on: test retry config, test retry config Part of the Test Automation skill category. Use when writing or running tests. Trigger with phrases like "test retry config", "test config", "test".

Comprehensive Stata reference for writing correct .do files. Covers syntax, options, gotchas, and idiomatic patterns. Use this skill whenever the user asks you to write, debug, or explain Stata code. Generates ready-to-run .do files for the user to execute manually.

Foundational skills for Zephyr RTOS development. Covers essential Embedded C patterns (BIT, CONTAINER_OF), real-time concurrency primitives (mutexes, semaphores, spinlocks), hardware literacy (datasheet-to-DTS mapping), and defensive programming. Trigger when writing core application logic, drivers, or troubleshooting foundational behavior.

This skill should be used when the user asks to "start a new story", "initialize a story project", "create a story", "new book", "set up a story", or wants to begin a new fiction writing project from scratch.

Foundational F# patterns covering functional-first programming, type providers, computation expressions, and domain modeling. Use when writing F# code, understanding functional patterns, working with type providers, or building .NET applications with F#. This is the entry point for F# development.

Systematic writing framework for philosophy and interdisciplinary academic papers from optimized outline to submission-ready manuscript. Use when users want to: (1) write a paper from a detailed outline, (2) ensure quality control during writing, (3) maintain consistency across chapters, (4) prepare a submission-ready manuscript, or (5) systematically execute a planned paper. Triggered by phrases like 'write the paper from this outline,' 'compose the full manuscript,' 'execute the outline,' or when users have completed strategic planning (academic-paper-strategist skill) and are ready to write. Takes optimized outline as input; outputs complete manuscript with iterative quality checks.

Creates algorithmic art in two phases: first writing a generative-art philosophy as a markdown manifesto, then expressing it as interactive p5.js sketches with seeded randomness, flow fields, and particle systems.

Covers MariaDB-specific CREATE TRIGGER syntax and behavior, including OR REPLACE, DEFINER, multiple trigger events, FOLLOWS/PRECEDES ordering, OLD/NEW rules, and restrictions. Use when writing, generating, or reviewing CREATE TRIGGER statements for MariaDB.

Create dbt test creator operations. Auto-activating skill for Data Pipelines. Triggers on: dbt test creator, dbt test creator Part of the Data Pipelines skill category. Use when writing or running tests. Trigger with phrases like "dbt test creator", "dbt creator", "dbt".

Configure spike test setup operations. Auto-activating skill for Performance Testing. Triggers on: spike test setup, spike test setup Part of the Performance Testing skill category. Use when writing or running tests. Trigger with phrases like "spike test setup", "spike setup", "spike".

Generate go test generator operations. Auto-activating skill for Test Automation. Triggers on: go test generator, go test generator Part of the Test Automation skill category. Use when writing or running tests. Trigger with phrases like "go test generator", "go generator", "go".

Plan soak test planner operations. Auto-activating skill for Performance Testing. Triggers on: soak test planner, soak test planner Part of the Performance Testing skill category. Use when writing or running tests. Trigger with phrases like "soak test planner", "soak planner", "soak".

Builder of knowledge products such as courses, ebooks, guides, memberships, and educational assets. Use for course creation, ebook writing, guide development, membership design, curriculum building, learning materials, or when the user asks for the Knowledge Executor, educational content, or knowledge products.

Write or review UX copy — microcopy, error messages, empty states, CTAs. Trigger with "write copy for", "what should this button say?", "review this error message", or when naming a CTA, wording a confirmation dialog, filling an empty state, or writing onboarding text.

Produces neutral, section-pinned U.S. legislative bill summaries translating statutory language into plain terms with identifying data, provisions, fiscal impacts, and controversy. Use when summarizing bills, analyzing proposed legislation, preparing bill briefs, digesting committee reports or fiscal notes, or writing legislative updates.

Foundational Rust patterns covering core syntax, traits, generics, lifetimes, and common idioms. Use when writing Rust code, understanding ownership basics, working with Option/Result, or needing guidance on which specialized Rust skill to use. This is the entry point for Rust development.

Foundational Scala patterns covering immutability, pattern matching, traits, case classes, for-comprehensions, and functional programming. Use when writing Scala code, understanding the type system, or needing guidance on which specialized Scala skill to use. This is the entry point for Scala development.

Foundational Swift development patterns covering modern Swift syntax, SwiftUI, protocol-oriented programming, and Cocoa Touch frameworks. Use when writing Swift code, building iOS/macOS/watchOS/tvOS applications, working with SwiftUI or UIKit, understanding Swift concurrency, or needing guidance on Swift project structure.

Covers MariaDB-specific behavior of the mariadb command-line client, including batch mode output, delimiter handling, safe-updates, charset detection, and TLS defaults, for writing or reviewing shell commands and scripts.

Documents MariaDB-specific UPDATE syntax and behavior, including single-table vs multi-table forms, assignment evaluation order, RETURNING with OLD_VALUE(), temporal tables, and common pitfalls. Use when writing, generating, or reviewing UPDATE statements targeting MariaDB.

Explains MariaDB explicit table locking (LOCK TABLES/UNLOCK TABLES) and named user-level locks (GET_LOCK family), covering alias traps, implicit commits, and multi-lock semantics for writing or reviewing locking code.

Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.

Foundational Erlang patterns covering OTP behaviors, fault-tolerant systems, distributed computing, pattern matching, processes, and supervision trees. Use when writing Erlang code, building concurrent systems, working with OTP frameworks, or developing distributed fault-tolerant applications. This is the entry point for Erlang development.

Foundational Python patterns covering core syntax, idioms, type hints, testing, and modern tooling. Use when writing Python code, understanding Pythonic patterns, working with type hints, or needing guidance on which specialized Python skill to use. This is the entry point for Python development.

Foundational Clojure patterns covering functional programming, REPL-driven development, immutable data structures, and idiomatic code. Use when writing Clojure code, working with sequences and lazy evaluation, understanding macros, or needing guidance on functional programming patterns. This is the entry point for Clojure development.