Results for “writing”

Guides efficient coding by enforcing a strict ladder of reuse, standard library, and minimal code before writing anything new.

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

Create pull requests following Sentry conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review. Follows Sentry's code review guidelines.

Test Python services with pytest, async coverage, monkeypatch, and boundary-focused fakes. Use when writing Python tests, fixtures, async tests, regression tests, or dependency-isolated verification.

Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.

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

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

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

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

Craft portfolio-ready case studies that tell the story of a design project, demonstrating process, thinking, and impact.

Design interfaces that adapt gracefully to multiple languages, writing directions, and cultural contexts.

Guides writing effective pull request descriptions focused on motivation, public API changes, and user impact while avoiding implementation details.

Generates a pull request title and body from local git history, writing them to a draft file for review before publishing.

Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.

Write Unit and E2E tests with Jest, mocking strategies, and database isolation in NestJS. Use when writing NestJS unit tests, E2E tests with supertest, or mock providers.

Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases. Credits: Original skill by @blader - https://github.com/blader/humanizer

Turn a product idea into a manual-first process you can start delivering today, before writing any code.

Guides writing idiomatic Rust with ownership, error handling, traits, concurrency, and best practices for safe, performant code.

Iteratively improves a compiled LaTeX paper through two rounds of external LLM review, fix implementation, and recompilation.

Guides test-driven development with a red-green-refactor loop, emphasizing behavior-focused tests and vertical slicing over horizontal test writing.

Guides writing MariaDB-specific database create scripts with best practices for schema objects, session settings, and UUID usage.

Provides guidelines for writing conventional commit messages and pull request descriptions, including merge strategy and GitHub username verification.

Apply Go best practices, idioms, and conventions from golang.org/doc/effective_go. Use when writing, reviewing, or refactoring Go code to ensure idiomatic, clean, and efficient implementations.

Use when creating, writing, or organizing slash commands. Covers frontmatter, dynamic arguments, file references, and bash execution. Commands are instructions FOR Claude, not messages TO the user.

AL test development patterns for Business Central. Use when creating test codeunits, writing Given/When/Then test procedures, using Library Assert, configuring test projects, or implementing TDD workflows.

Applies principles from Robert C. Martin's 'Clean Code'. Use this skill when writing, reviewing, or refactoring code to ensure high quality, readability, and maintainability. Covers naming, functio...

Generate tests, design test strategies, and ensure code quality through testing. Use when writing tests, improving test coverage, designing test infrastructure, or evaluating test quality.

Identify grammar, logical, and flow errors in text and suggest targeted fixes without rewriting the entire text. Use when proofreading content, checking writing quality, or reviewing a draft.

Guides test-driven development with a vertical-slice approach, writing one test at a time and implementing minimal code to pass, then refactoring.

Detect and remove AI-generated markers from Finnish text, making it sound like a native Finnish speaker wrote it.

Guides test-first development with vertical slices, writing one behavior test at a time and refactoring only when green.

Provides C programming guidance for systems programming, memory management, and performance, with best practices for writing safe and efficient code.

Guides writing Rust tests with TDD, covering unit, integration, async, property-based, mocking, and coverage patterns.

Guides implementing features and fixing bugs by writing failing tests first, then minimal code, with verification at each step.

Guides writing a failing test before production code, iterating through red-green-refactor cycles, and fixing bugs test-first.

Prove code works by running it, not just checking it exists. Verification through execution rather than inspection. Use after writing or modifying code to ensure it actually functions correctly.