[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C1TNAANT8RS9XKB2F3JF3E":3,"skill-same:01M6C1TNAANT8RS9XKB2F3JF3E":61},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":30,"linkOnly":31,"markdownContent":32,"markdownBody":33,"frontMatter":34,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":14,"repositoryHtmlUrl":38,"repositoryHomepageUrl":6,"ownerHtmlUrl":39,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":40,"install":41,"resources":54},"01M6C1TNAANT8RS9XKB2F3JF3E","python-best-practices",null,"Comprehensive Python coding conventions and best practices. Use when the user asks about Python conventions, coding patterns, best practices, code style, anti-patterns, or \"how should I write this\" in Python.","cartaorobbin\u002Fpyramid-temporal","cartaorobbin","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F133803757?v=4","01M6C1SVA1FFVXFG0QTK8ZRNDV","robbin Pagamentos","01M6C1SVEDYW8ZDTP82V7DF2BQ",0,"MIT","https:\u002F\u002Fgithub.com\u002Fcartaorobbin\u002Fpyramid-temporal\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fpython-best-practices\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29],"python","best practices","python best practices","code style","code","how","coding","write","user","use","anti-patterns","2026-11-10 10:12:30",false,"---\nname: python-best-practices\ndescription: Comprehensive Python coding conventions and best practices. Use when the user asks about Python conventions, coding patterns, best practices, code style, anti-patterns, or \"how should I write this\" in Python.\n---\n\n> **MANAGED SKILL** — Do not edit this file here. It is managed from an external source repository.\n> To make changes, update the source and run \"update my skills\" to sync.\n\n\n# Python Best Practices\n\nThe canonical reference for Python coding conventions in this project. When in doubt about how to write Python, consult this skill.\n\n---\n\n## Philosophy\n\nThe Zen of Python is not decoration — it drives real decisions:\n\n- **Beautiful is better than ugly** — Name things clearly. Structure code so it reads top-down without jumping around.\n- **Explicit is better than implicit** — Don't hide behavior in magic methods, decorators, or metaclasses unless the abstraction genuinely simplifies understanding.\n- **Simple is better than complex** — If a function needs a paragraph to explain, it does too much. Split it.\n- **Flat is better than nested** — Use early returns to avoid deep indentation. Prefer guard clauses over nested `if\u002Felse` trees.\n- **Readability counts** — Code is read far more often than written. Optimize for the reader, not the writer.\n- **Errors should never pass silently** — Catch specific exceptions. Log or re-raise. Never use bare `except:` or `except Exception: pass`.\n\nWhen two principles conflict, prefer the one that makes the code easier to understand six months from now.\n\n---\n\n## Project Layout\n\n- Use the **src layout**: source code in `src\u002F{package_name}\u002F`, tests in `tests\u002F`.\n- Never put package code at the repository root.\n- Test files mirror the source structure: `src\u002Fmyapp\u002Fservices\u002Fuser.py` → `tests\u002Ftest_services\u002Ftest_user.py` or `tests\u002Ftest_user_service.py`.\n- Keep `__init__.py` minimal — use it for public API re-exports, not logic.\n\n---\n\n## Imports\n\n- **Always at the top of the module.** Never inside functions, methods, or conditional blocks.\n- Use **absolute imports**: `from myapp.services.user import UserService`, not relative imports.\n- Import order (enforced by ruff with isort rules):\n  1. Standard library\n  2. Third-party packages\n  3. Local application imports\n- Each group separated by a blank line.\n- Import specific names (`from os.path import join`) rather than entire modules when only one or two names are needed. Import the module (`import os.path`) when using many names from it.\n\n---\n\n## Naming\n\n- **Variables and functions**: `snake_case`\n- **Classes**: `PascalCase`\n- **Constants**: `UPPER_SNAKE_CASE`\n- **Private**: prefix with single underscore (`_internal_helper`)\n- **Avoid abbreviations** unless universally understood (`db`, `url`, `id` are fine; `usr_svc_mgr` is not).\n- **Boolean variables and functions**: use `is_`, `has_`, `can_`, `should_` prefixes. A boolean named `active` is ambiguous; `is_active` is clear.\n\n---\n\n## Functions and Methods\n\n- **Single responsibility**: each function does one thing. If you describe it with \"and\", split it.\n- **Type hints on public APIs**: all public functions and methods must have parameter and return type annotations.\n- **Docstrings on public APIs**: one-line summary. Add detail only when the behavior is non-obvious.\n- **Prefer returning values** over mutating arguments. If mutation is necessary, make it obvious in the function name (`update_user_status`, not `process_user`).\n- **Keep functions short** — if a function exceeds ~30 lines, consider extracting helpers.\n- **Default arguments**: never use mutable defaults (`def f(items=[]):`). Use `None` and initialize inside.\n\n---\n\n## Error Handling\n\n- **Catch specific exceptions**, never bare `except:` or `except Exception:`.\n- **Never swallow exceptions silently** — at minimum, log the error. Prefer re-raising or converting to a domain-specific exception.\n- **Use custom exceptions** for domain errors. Inherit from a project-level base exception so callers can catch broadly when needed.\n- **Fail fast** — validate inputs at the boundary (function entry, API endpoint, CLI argument parsing). Don't let invalid data propagate deep into the system.\n- **Context managers** (`with` statements) for resource cleanup — files, connections, transactions.\n\n```python\n# Good: specific exception, clear message, re-raise\ntry:\n    response = client.fetch(url)\nexcept ConnectionError as exc:\n    logger.error(\"Failed to fetch %s: %s\", url, exc)\n    raise ServiceUnavailableError(f\"Upstream unreachable: {url}\") from exc\n\n# Bad: swallowing everything\ntry:\n    response = client.fetch(url)\nexcept Exception:\n    pass\n```\n\n---\n\n## Code Quality\n\n- **Type hints** on all new functions and class attributes. Use `from __future__ import annotations` for modern syntax in older Python versions.\n- **No obvious comments** — comments explain \"why\", never \"what\". If the code needs a comment to explain what it does, rewrite the code to be clearer.\n- **No dead code** — remove commented-out code, unused imports, unreachable branches. Version control is the history.\n- **DRY within reason** — extract duplicated logic into functions, but don't over-abstract. Two occurrences may be coincidence; three is a pattern.\n- **Constants over magic values** — `if retries > MAX_RETRIES:` is clearer than `if retries > 3:`.\n\n---\n\n## Testing\n\n- **Framework**: pytest (always).\n- **Real objects over mocks** — exercise actual code paths whenever possible. Mocks are a last resort, not a convenience.\n- **Testing priority** (strictly enforced):\n  1. Real integrations and real code paths\n  2. `responses` library for external HTTP calls (`@responses.activate`)\n  3. `factory-boy` for test data generation (`SQLAlchemyModelFactory`)\n  4. Pytest fixtures for reusable setup\n  5. `unittest.mock.patch` only as absolute last resort (gRPC clients, etc.)\n- **One test, one behavior** — each test function verifies exactly one thing.\n- **No conditional logic in tests** — no `if\u002Felse`, `try\u002Fexcept`, `for`, `while`, ternary operators inside test functions.\n- **Descriptive test names**: `test_\u003Caction>_\u003Cscenario>` or `test_\u003Cwhat>_\u003Cexpected_outcome>`.\n- **Use `parametrize`** to avoid copy-paste duplication when multiple inputs share the same test logic.\n- **Use `hypothesis`** for property-based testing on validators, numeric calculations, and data parsing.\n- **Tests are deterministic** — no randomness, no dependency on external state, no time-sensitive assertions without freezing time.\n- **Keep test files under ~200 lines** — split by concern when they grow.\n\nFor the full testing workflow (research, discuss, write), see the **write-pytest** skill.\n\n---\n\n## Formatting and Linting\n\n- **Formatter**: black (line length 88).\n- **Linter**: ruff.\n- Both are non-negotiable. Run them before every commit.\n- Do not fight the formatter — if black produces output you dislike, restructure the code rather than adding `# fmt: off`.\n- Ruff rules include: pyflakes (`F`), pycodestyle (`E`), isort (`I`), and additional checks as configured in `pyproject.toml`.\n\n---\n\n## Dependency Management\n\n- **Never install packages without using the project's package manager** (uv or poetry).\n- **Always update the lockfile** after adding or removing dependencies.\n- Use **dev dependency groups** for test\u002Flint\u002Fdoc packages — they should not be in production dependencies.\n- Pin versions in the lockfile, use compatible ranges in `pyproject.toml` (e.g., `requests>=2.28,\u003C3`).\n\nFor the full dependency management workflow, see the **manage-dependencies** skill.\n\n---\n\n## Forbidden Patterns\n\nThese are hard rules, not suggestions:\n\n- **Never use pydantic** — not in any form (BaseModel, validators, Field, etc.).\n- **Never use FastAPI** — not as a framework, not for a single endpoint.\n- **Never put imports inside functions or methods** — all imports at module top level.\n- **Never use bare `except:`** — always catch specific exceptions.\n- **Never use mutable default arguments** — `def f(items=[]):` is a bug waiting to happen.\n- **Never use `from module import *`** — explicit imports only.\n\n---\n\n## Anti-Patterns Catalog\n\n### Stringly-typed code\n\n```python\n# Bad: status is a string, typos are silent bugs\nif user.status == \"actve\":  # typo, no error\n    grant_access(user)\n\n# Good: use an enum or constant\nclass UserStatus:\n    ACTIVE = \"active\"\n    INACTIVE = \"inactive\"\n\nif user.status == UserStatus.ACTIVE:\n    grant_access(user)\n```\n\n### God function\n\n```python\n# Bad: one function doing everything\ndef process_order(order):\n    validate_items(order.items)\n    calculate_totals(order)\n    check_inventory(order.items)\n    charge_payment(order.payment)\n    send_confirmation(order.customer)\n    update_analytics(order)\n    # ... 200 more lines\n\n# Good: orchestrator delegates to focused functions\ndef process_order(order):\n    validated = validate_order(order)\n    charged = charge_order(validated)\n    fulfill_order(charged)\n    notify_customer(charged)\n```\n\n### Nested conditionals\n\n```python\n# Bad: deep nesting\ndef get_discount(user, order):\n    if user is not None:\n        if user.is_premium:\n            if order.total > 100:\n                return 0.2\n            else:\n                return 0.1\n        else:\n            return 0.0\n    else:\n        return 0.0\n\n# Good: guard clauses, flat structure\ndef get_discount(user, order):\n    if user is None:\n        return 0.0\n    if not user.is_premium:\n        return 0.0\n    if order.total > 100:\n        return 0.2\n    return 0.1\n```\n\n### Silent exception swallowing\n\n```python\n# Bad: errors vanish\ndef fetch_user(user_id):\n    try:\n        return db.query(User).get(user_id)\n    except Exception:\n        return None\n\n# Good: explicit handling\ndef fetch_user(user_id):\n    try:\n        return db.query(User).get(user_id)\n    except SQLAlchemyError as exc:\n        logger.error(\"Failed to fetch user %s: %s\", user_id, exc)\n        raise\n```\n\n### Mock-heavy tests\n\n```python\n# Bad: testing the mocks, not the code\ndef test_create_user():\n    mock_db = Mock()\n    mock_validator = Mock(return_value=True)\n    mock_hasher = Mock(return_value=\"hashed\")\n    service = UserService(mock_db, mock_validator, mock_hasher)\n    service.create_user(\"test@example.com\", \"password\")\n    mock_db.save.assert_called_once()\n\n# Good: real objects, real behavior\ndef test_create_user(dbsession):\n    service = UserService(dbsession)\n    user = service.create_user(\"test@example.com\", \"password\")\n    assert user.email == \"test@example.com\"\n    assert dbsession.query(User).count() == 1\n```\n","> **MANAGED SKILL** — Do not edit this file here. It is managed from an external source repository.\n> To make changes, update the source and run \"update my skills\" to sync.\n\n\n# Python Best Practices\n\nThe canonical reference for Python coding conventions in this project. When in doubt about how to write Python, consult this skill.\n\n---\n\n## Philosophy\n\nThe Zen of Python is not decoration — it drives real decisions:\n\n- **Beautiful is better than ugly** — Name things clearly. Structure code so it reads top-down without jumping around.\n- **Explicit is better than implicit** — Don't hide behavior in magic methods, decorators, or metaclasses unless the abstraction genuinely simplifies understanding.\n- **Simple is better than complex** — If a function needs a paragraph to explain, it does too much. Split it.\n- **Flat is better than nested** — Use early returns to avoid deep indentation. Prefer guard clauses over nested `if\u002Felse` trees.\n- **Readability counts** — Code is read far more often than written. Optimize for the reader, not the writer.\n- **Errors should never pass silently** — Catch specific exceptions. Log or re-raise. Never use bare `except:` or `except Exception: pass`.\n\nWhen two principles conflict, prefer the one that makes the code easier to understand six months from now.\n\n---\n\n## Project Layout\n\n- Use the **src layout**: source code in `src\u002F{package_name}\u002F`, tests in `tests\u002F`.\n- Never put package code at the repository root.\n- Test files mirror the source structure: `src\u002Fmyapp\u002Fservices\u002Fuser.py` → `tests\u002Ftest_services\u002Ftest_user.py` or `tests\u002Ftest_user_service.py`.\n- Keep `__init__.py` minimal — use it for public API re-exports, not logic.\n\n---\n\n## Imports\n\n- **Always at the top of the module.** Never inside functions, methods, or conditional blocks.\n- Use **absolute imports**: `from myapp.services.user import UserService`, not relative imports.\n- Import order (enforced by ruff with isort rules):\n  1. Standard library\n  2. Third-party packages\n  3. Local application imports\n- Each group separated by a blank line.\n- Import specific names (`from os.path import join`) rather than entire modules when only one or two names are needed. Import the module (`import os.path`) when using many names from it.\n\n---\n\n## Naming\n\n- **Variables and functions**: `snake_case`\n- **Classes**: `PascalCase`\n- **Constants**: `UPPER_SNAKE_CASE`\n- **Private**: prefix with single underscore (`_internal_helper`)\n- **Avoid abbreviations** unless universally understood (`db`, `url`, `id` are fine; `usr_svc_mgr` is not).\n- **Boolean variables and functions**: use `is_`, `has_`, `can_`, `should_` prefixes. A boolean named `active` is ambiguous; `is_active` is clear.\n\n---\n\n## Functions and Methods\n\n- **Single responsibility**: each function does one thing. If you describe it with \"and\", split it.\n- **Type hints on public APIs**: all public functions and methods must have parameter and return type annotations.\n- **Docstrings on public APIs**: one-line summary. Add detail only when the behavior is non-obvious.\n- **Prefer returning values** over mutating arguments. If mutation is necessary, make it obvious in the function name (`update_user_status`, not `process_user`).\n- **Keep functions short** — if a function exceeds ~30 lines, consider extracting helpers.\n- **Default arguments**: never use mutable defaults (`def f(items=[]):`). Use `None` and initialize inside.\n\n---\n\n## Error Handling\n\n- **Catch specific exceptions**, never bare `except:` or `except Exception:`.\n- **Never swallow exceptions silently** — at minimum, log the error. Prefer re-raising or converting to a domain-specific exception.\n- **Use custom exceptions** for domain errors. Inherit from a project-level base exception so callers can catch broadly when needed.\n- **Fail fast** — validate inputs at the boundary (function entry, API endpoint, CLI argument parsing). Don't let invalid data propagate deep into the system.\n- **Context managers** (`with` statements) for resource cleanup — files, connections, transactions.\n\n```python\n# Good: specific exception, clear message, re-raise\ntry:\n    response = client.fetch(url)\nexcept ConnectionError as exc:\n    logger.error(\"Failed to fetch %s: %s\", url, exc)\n    raise ServiceUnavailableError(f\"Upstream unreachable: {url}\") from exc\n\n# Bad: swallowing everything\ntry:\n    response = client.fetch(url)\nexcept Exception:\n    pass\n```\n\n---\n\n## Code Quality\n\n- **Type hints** on all new functions and class attributes. Use `from __future__ import annotations` for modern syntax in older Python versions.\n- **No obvious comments** — comments explain \"why\", never \"what\". If the code needs a comment to explain what it does, rewrite the code to be clearer.\n- **No dead code** — remove commented-out code, unused imports, unreachable branches. Version control is the history.\n- **DRY within reason** — extract duplicated logic into functions, but don't over-abstract. Two occurrences may be coincidence; three is a pattern.\n- **Constants over magic values** — `if retries > MAX_RETRIES:` is clearer than `if retries > 3:`.\n\n---\n\n## Testing\n\n- **Framework**: pytest (always).\n- **Real objects over mocks** — exercise actual code paths whenever possible. Mocks are a last resort, not a convenience.\n- **Testing priority** (strictly enforced):\n  1. Real integrations and real code paths\n  2. `responses` library for external HTTP calls (`@responses.activate`)\n  3. `factory-boy` for test data generation (`SQLAlchemyModelFactory`)\n  4. Pytest fixtures for reusable setup\n  5. `unittest.mock.patch` only as absolute last resort (gRPC clients, etc.)\n- **One test, one behavior** — each test function verifies exactly one thing.\n- **No conditional logic in tests** — no `if\u002Felse`, `try\u002Fexcept`, `for`, `while`, ternary operators inside test functions.\n- **Descriptive test names**: `test_\u003Caction>_\u003Cscenario>` or `test_\u003Cwhat>_\u003Cexpected_outcome>`.\n- **Use `parametrize`** to avoid copy-paste duplication when multiple inputs share the same test logic.\n- **Use `hypothesis`** for property-based testing on validators, numeric calculations, and data parsing.\n- **Tests are deterministic** — no randomness, no dependency on external state, no time-sensitive assertions without freezing time.\n- **Keep test files under ~200 lines** — split by concern when they grow.\n\nFor the full testing workflow (research, discuss, write), see the **write-pytest** skill.\n\n---\n\n## Formatting and Linting\n\n- **Formatter**: black (line length 88).\n- **Linter**: ruff.\n- Both are non-negotiable. Run them before every commit.\n- Do not fight the formatter — if black produces output you dislike, restructure the code rather than adding `# fmt: off`.\n- Ruff rules include: pyflakes (`F`), pycodestyle (`E`), isort (`I`), and additional checks as configured in `pyproject.toml`.\n\n---\n\n## Dependency Management\n\n- **Never install packages without using the project's package manager** (uv or poetry).\n- **Always update the lockfile** after adding or removing dependencies.\n- Use **dev dependency groups** for test\u002Flint\u002Fdoc packages — they should not be in production dependencies.\n- Pin versions in the lockfile, use compatible ranges in `pyproject.toml` (e.g., `requests>=2.28,\u003C3`).\n\nFor the full dependency management workflow, see the **manage-dependencies** skill.\n\n---\n\n## Forbidden Patterns\n\nThese are hard rules, not suggestions:\n\n- **Never use pydantic** — not in any form (BaseModel, validators, Field, etc.).\n- **Never use FastAPI** — not as a framework, not for a single endpoint.\n- **Never put imports inside functions or methods** — all imports at module top level.\n- **Never use bare `except:`** — always catch specific exceptions.\n- **Never use mutable default arguments** — `def f(items=[]):` is a bug waiting to happen.\n- **Never use `from module import *`** — explicit imports only.\n\n---\n\n## Anti-Patterns Catalog\n\n### Stringly-typed code\n\n```python\n# Bad: status is a string, typos are silent bugs\nif user.status == \"actve\":  # typo, no error\n    grant_access(user)\n\n# Good: use an enum or constant\nclass UserStatus:\n    ACTIVE = \"active\"\n    INACTIVE = \"inactive\"\n\nif user.status == UserStatus.ACTIVE:\n    grant_access(user)\n```\n\n### God function\n\n```python\n# Bad: one function doing everything\ndef process_order(order):\n    validate_items(order.items)\n    calculate_totals(order)\n    check_inventory(order.items)\n    charge_payment(order.payment)\n    send_confirmation(order.customer)\n    update_analytics(order)\n    # ... 200 more lines\n\n# Good: orchestrator delegates to focused functions\ndef process_order(order):\n    validated = validate_order(order)\n    charged = charge_order(validated)\n    fulfill_order(charged)\n    notify_customer(charged)\n```\n\n### Nested conditionals\n\n```python\n# Bad: deep nesting\ndef get_discount(user, order):\n    if user is not None:\n        if user.is_premium:\n            if order.total > 100:\n                return 0.2\n            else:\n                return 0.1\n        else:\n            return 0.0\n    else:\n        return 0.0\n\n# Good: guard clauses, flat structure\ndef get_discount(user, order):\n    if user is None:\n        return 0.0\n    if not user.is_premium:\n        return 0.0\n    if order.total > 100:\n        return 0.2\n    return 0.1\n```\n\n### Silent exception swallowing\n\n```python\n# Bad: errors vanish\ndef fetch_user(user_id):\n    try:\n        return db.query(User).get(user_id)\n    except Exception:\n        return None\n\n# Good: explicit handling\ndef fetch_user(user_id):\n    try:\n        return db.query(User).get(user_id)\n    except SQLAlchemyError as exc:\n        logger.error(\"Failed to fetch user %s: %s\", user_id, exc)\n        raise\n```\n\n### Mock-heavy tests\n\n```python\n# Bad: testing the mocks, not the code\ndef test_create_user():\n    mock_db = Mock()\n    mock_validator = Mock(return_value=True)\n    mock_hasher = Mock(return_value=\"hashed\")\n    service = UserService(mock_db, mock_validator, mock_hasher)\n    service.create_user(\"test@example.com\", \"password\")\n    mock_db.save.assert_called_once()\n\n# Good: real objects, real behavior\ndef test_create_user(dbsession):\n    service = UserService(dbsession)\n    user = service.create_user(\"test@example.com\", \"password\")\n    assert user.email == \"test@example.com\"\n    assert dbsession.query(User).count() == 1\n```\n",{"name":5,"description":7},"main","ea5172c58cf8fe53f20b59482e62cc45741da12d",".cursor\u002Fskills\u002Fpython-best-practices","https:\u002F\u002Fgithub.com\u002Fcartaorobbin\u002Fpyramid-temporal","https:\u002F\u002Fgithub.com\u002Fcartaorobbin","2026-10-24 04:09:32",{"source":8,"skillName":5,"commands":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add cartaorobbin\u002Fpyramid-temporal --skill python-best-practices",{"tool":47,"command":48},"bunx","bunx skills add cartaorobbin\u002Fpyramid-temporal --skill python-best-practices",{"tool":50,"command":51},"pnpm","pnpm dlx skills add cartaorobbin\u002Fpyramid-temporal --skill python-best-practices","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcartaorobbin\u002Fpyramid-temporal\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fpython-best-practices\u002FSKILL.md",true,[55],{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},".managed-skill.md","REFERENCE","参考文档",251,"https:\u002F\u002Fgithub.com\u002Fcartaorobbin\u002Fpyramid-temporal\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fpython-best-practices\u002F.managed-skill.md",[62,85,103,125,139,156],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":76,"publishedAt":30},"01M6C1TXVJXMQ0VWWGMHD7PKG9","write-pytest","Write pytest tests for any Python codebase. Use when the user asks to write tests, create tests, add tests, or test a module\u002Fservice\u002Fendpoint\u002Ffunction. Framework-agnostic; routes to framework-specific helpers when signals are detected. Follows a research-then-discuss-then-write flow.","https:\u002F\u002Fgithub.com\u002Fcartaorobbin\u002Fpyramid-temporal\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fwrite-pytest\u002FSKILL.md",[68,73],{"categoryNo":69,"categoryName":70,"taxonomyType":71,"taxonomyTypeDesc":72},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":74,"categoryName":75,"taxonomyType":71,"taxonomyTypeDesc":72},"01JBSEEDCAT000000000000021","资料检索与研究",[77,26,28,27,78,79,80,81,82,19,83,84],"write pytest","endpoint","write tests","flow","framework","create","research","test",{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":94,"publishedAt":30},"01M6C1TTVR96XWX68FQY37S2QZ","quality-assurance","Run quality assurance checks on the current chat session — pre-task validation, post-task checklist, and code review. Use when finishing a task, before committing, or when the user asks for a QA review.","https:\u002F\u002Fgithub.com\u002Fcartaorobbin\u002Fpyramid-temporal\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fquality-assurance\u002FSKILL.md",[91],{"categoryNo":92,"categoryName":93,"taxonomyType":71,"taxonomyTypeDesc":72},"01JBSEEDCAT000000000000007","代码审查",[95,96,23,97,98,99,100,101,27,102,28],"quality","quality assurance","code review","review","run","validation","qa","session",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":114,"publishedAt":30},"01M6C1TR2SWA481C00S2VQ12DW","python-developer","Python developer umbrella — installs Python coding conventions and bundles companion skills (best practices, testing, dependency management) in a single setup. Use when the user asks to set up Python development conventions, install Python skills, or says \"set up Python development\".","https:\u002F\u002Fgithub.com\u002Fcartaorobbin\u002Fpyramid-temporal\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fpython-developer\u002FSKILL.md",[109],{"categoryNo":110,"categoryName":111,"taxonomyType":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[115,19,116,117,118,27,119,120,28,25,121,122,123,20,124],"developer","python developer","management","development","dependency management","install","testing","python development","setup","SET",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":132,"publishedAt":30},"01M6C1TJEMGMNGNVE4DKWF4TNA","pyramid-library","Library Developer persona: developing standalone Pyramid extensions (own repo, own package) that expose includeme for external consumers. Use when the user builds a reusable Pyramid library, designs includeme for consumers, registers custom directives\u002Ftweens\u002Frequest methods, or tests a library with a proper app.","https:\u002F\u002Fgithub.com\u002Fcartaorobbin\u002Fpyramid-temporal\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fpyramid-library\u002FSKILL.md",[131],{"categoryNo":110,"categoryName":111,"taxonomyType":112,"taxonomyTypeDesc":113},[133,134,135,136,115,137,138,27,28],"pyramid library","library","core","package","persona","repo",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":146,"publishedAt":30},"01M6C1TFT8Z6MCBEAQ7S24XQ77","pyramid-developer","Pyramid framework conventions — configuration\u002Fregistry, module system with includeme, pyramid_services, models, Cornice REST, ACL authorization, and transactions. Use when setting up Pyramid development conventions for a project.","https:\u002F\u002Fgithub.com\u002Fcartaorobbin\u002Fpyramid-temporal\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fpyramid-developer\u002FSKILL.md",[145],{"categoryNo":110,"categoryName":111,"taxonomyType":112,"taxonomyTypeDesc":113},[147,115,148,19,118,149,81,150,151,152,153,154,28,155],"pyramid developer","system","registry","services","ACL","REST","authorization","transactions","micromonolith",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":30},"01M6C1TD7J0P6CTDVGEJH55W1B","pyramid-core","Pyramid framework features reference — request methods, custom directives, events, tweens, exception views, view predicates, view derivers, callbacks, renderers, and static views. Use when the user asks about any Pyramid framework extension point.","https:\u002F\u002Fgithub.com\u002Fcartaorobbin\u002Fpyramid-temporal\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fpyramid-core\u002FSKILL.md",[],[135,163,81,115,164,27,28],"pyramid core","view"]