python-coding
This skill should be loaded when writing, reviewing, or refactoring Python code to apply strict coding standards directly in the current context without spawning a subagent. It provides comprehensive Python development standards covering SOLID principles, asyncio patterns, type hints, testing, and production-quality code.
What this skill does
# Python Coder Standards Apply these standards when writing, reviewing, or refactoring Python code. This provides the same expertise as the `python-coder` agent but applied directly in the current conversation context. ## Quick Reference Checklist Before providing any code or review, verify: 1. Absolute imports only 2. Modern type hints (`X | None`) 3. No prohibited practices (eval, exec, global, print, bare except, mutable defaults) 4. Pydantic validation at boundaries 5. No blocking I/O in async paths 6. `asyncio.TaskGroup` for structured concurrency 7. Google-style docstrings on public APIs 8. Structured logging (no f-strings in logger calls) 9. No assertions in production code 10. Immutable types preferred (tuple > list, frozenset > set) See [references/python-standards.md](./references/python-standards.md) for full details on each item. ## Detailed Standards For the complete standards reference covering all patterns, examples, and anti-patterns, load: ``` references/python-standards.md ``` This reference covers: - **Design Principles** - SOLID, dependency injection, composition over inheritance - **Asyncio & Concurrency** - TaskGroup, firewall pattern, non-blocking I/O, synchronization - **Fault Tolerance** - Exception isolation for independent tasks - **Error Handling** - Exception hierarchy, no assertions in production - **Logging** - Structured logging patterns - **Input Validation** - Pydantic models at boundaries - **Naming & Immutability** - PEP 8, no built-in shadowing, immutable defaults - **Imports & Type Hints** - Absolute imports, modern syntax, Protocols - **Testing** - TDD with pytest, async testing patterns - **Prohibited Practices** - Complete list of banned patterns with alternatives ## Output Guidelines When writing code: - Provide complete, runnable code with all imports - Include type hints on all parameters and return values - Add Google-style docstrings to public APIs - Show example usage when helpful When reviewing code: - Reference specific violations from the standards - Explain WHY each change is needed - Provide corrected code - Prioritize by severity
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.