「eq」の検索結果

Shared Python 3.11+ development rules — type safety and the boundary policy for `Any` (ty, native generics, Protocol, TypeIs, Pydantic), layered architecture and SOLID, error handling, security, performance, identifier naming, PEP 723 script dependencies, Rich/Typer output, tooling defaults (uv, ruff, ty, hatchling, pytest), and testing requirements (behavioral coverage, TDD). Activates when any Python skill or agent needs the shared rules for implementation, code review, refactoring, or test authoring.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a Python task explicitly requires test-driven development, tests-first implementation, or a red-green-refactor workflow.

日本語の概要は準備中です。原文の説明を表示しています。

Applies and teaches Python 3.11+ modernization patterns with PEP citations. Use when reviewing or writing Python code to apply built-in generics (PEP 585), pipe unions (PEP 604), walrus operator (PEP 572), match-case (PEP 634), Self type (PEP 673), exception notes (PEP 678), StrEnum, tomllib, pytest-mock fixtures, Typer Annotated syntax, or Rich terminal output — or when refactoring legacy typing imports or elif chains to modern equivalents.

日本語の概要は準備中です。原文の説明を表示しています。

Use when implementing a Python feature, adding CLI commands, writing pytest suites, reviewing Python code, debugging, or refactoring. The primary Python engineering workflow orchestrator — classifies the task and delegates through this plugin's own specialist agents (architect → implement → test → review), sized to the task. Delegates to python-cli-architect (implementation), python-pytest-architect (tests), code-reviewer (review), python-cli-design-spec (architecture). Triggers on any Python task requiring specialist agent coordination or multi-agent execution.

日本語の概要は準備中です。原文の説明を表示しています。

Use when working with ruff — this skill's ruff policy and required overrides to Astral's official guidance. Pair with `astral:ruff` (if installed) for general usage.

日本語の概要は準備中です。原文の説明を表示しています。

Use when working with uv — this skill's uv policy and required overrides to Astral's official guidance. Pair with `astral:uv` (if installed) for general usage.

日本語の概要は準備中です。原文の説明を表示しています。

Runs structured Python cleanup and modernization — static analysis via prek/ruff, smell investigation to root cause, typed-boundary hardening by inventorying Any usage, and modernization within the project's requires-python lane. Use when refactoring Python code, removing dead code, hardening type boundaries, or running a modernization pass on a file or scope.

日本語の概要は準備中です。原文の説明を表示しています。

Executes a four-phase feature addition workflow (Discovery, Planning, TDD Implementation, Verification) for Python projects. Use when adding a new feature end-to-end — discovering project structure and integration points, drafting a feature spec with MoSCoW-prioritized requirements and BDD acceptance criteria, implementing via test-first TDD cycles, then verifying with ruff lint, ty type checks, and behavior-focused regression and contract coverage.

日本語の概要は準備中です。原文の説明を表示しています。

Use when working with ty — this skill's ty policy and required overrides to Astral's official guidance. Pair with `astral:ty` (if installed) for general usage.

日本語の概要は準備中です。原文の説明を表示しています。

Auto-selects and enforces the strongest valid Python typing lane for the detected Python version and dependencies — no user input required. Use when adding or tightening type annotations, eliminating Any usage in internal code, designing boundary validators or parsers, choosing between stdlib typing (TypedDict, Protocol, dataclasses), Pydantic models, or Hypothesis property tests, addressing ty or mypy failures, or applying version-specific features (TypeIs, ReadOnly, PEP 695 generics, PEP 649 deferred evaluation). Enforces boundary isolation — raw payloads validated immediately at ingress and returned as typed internal objects.

日本語の概要は準備中です。原文の説明を表示しています。

Mermaid diagram syntax reference for all diagram types — flowchart, sequence, class, state, ER, gantt, git graph, mindmap, timeline, user journey, pie, quadrant, XY chart, block, sankey, C4, kanban, and more. Use when constructing or debugging any Mermaid diagram definition.

日本語の概要は準備中です。原文の説明を表示しています。

Validates and corrects Python shebangs and PEP 723 inline script metadata by applying four shebang-selection rules. Use when auditing or fixing shebangs in Python files — choosing between plain python3 and the uv shebang for standalone scripts with external dependencies, adding or removing PEP 723 metadata blocks to match actual import requirements, checking execute bit presence, or avoiding redundant transitive dependencies when typer is declared.

日本語の概要は準備中です。原文の説明を表示しています。

Analyze and improve processes or systems using an explicit semantic model, adaptive instruction resolution, evidence-driven change, and claim-level validation. Use when reviewing process quality, resolving ambiguity or gaps, deciding how much procedural detail is necessary, or validating consequential process behavior.

日本語の概要は準備中です。原文の説明を表示しています。

Audit skill lifecycle by tracing call chains, detecting circular dependencies, finding instruction contradictions, identifying duplicated datasets, analyzing bidirectional coherence, discovering scriptable sequences, and learning patterns. Use when checking skill coherence, validating skill workflow, finding semantic gaps in plugin structure, or auditing plugin before marketplace submission. Generates audit reports to .plugin-creator/audits/ with findings by dimension.

日本語の概要は準備中です。原文の説明を表示しています。

Use when writing delegation instructions to subagents, authoring CLAUDE.md files, rules, skills, or agent definitions, or auditing existing AI-facing content for bloat. Activates on "write a rule for", "add to CLAUDE.md", "create an agent", "update memory", or any request to author AI-facing instruction content. Removes discoverable data, explained-away knowledge, invented constraints, and stale cached facts.

日本語の概要は準備中です。原文の説明を表示しています。

Use when creating a new Claude Code plugin from scratch — orchestrates prerequisite check, user discussion, parallel research, design with verification, atomic implementation, multi-layer validation, documentation, and final verification. For existing plugin improvement, use /plugin-creator:plugin-lifecycle instead.

日本語の概要は準備中です。原文の説明を表示しています。

Format and score completed plugin assessment findings, including whether evidence admits a finding to the requested outcome. Use when a plugin assessment or review needs the standard report structure, scoring criteria, severity breakdown, marketplace-readiness result, or finding admission.

日本語の概要は準備中です。原文の説明を表示しています。

Review existing tests against the software and contracts they actually exercise. Use to assess whether a test has justified unique protection, detects consequential faults, tolerates valid refactors, earns its lifecycle cost, or deserves strengthening, replacement, consolidation, or removal consideration. Reviews are read-only and evidence-backed, including TDD and regression tests.

日本語の概要は準備中です。原文の説明を表示しています。

Rigorous self-assessment checklist before marking any task as complete. Use when about to claim task completion, before final commit, when user asks "is it done?", or when transitioning from implementation to reporting. Prevents premature completion claims by requiring evidence for every assertion.

日本語の概要は準備中です。原文の説明を表示しています。

Discover and run configured quality gates for requested or changed work, preserve diagnostics as evidence, route failures to the appropriate causal/domain capability, and verify corrections. Use for linting, formatting, type-checking, configured hook checks, or pre-completion quality verification.

日本語の概要は準備中です。原文の説明を表示しています。

Validate whether an implementation plan can achieve its stated outcome before execution. Use to check requirement coverage, task contracts, dependencies, data/artifact flow, testability, ownership, impact coverage, and executable ordering without checking whether implementation already exists.

日本語の概要は準備中です。原文の説明を表示しています。

Same reverse-thinking method as dh:rt-ica (see dh:rt-ica or dh-glossary for the definition), but localizes any MISSING input to the affected task only, as a non-blocking information-completeness pre-pass before task decomposition and plan generation. Use when grooming backlog items, generating plans, decomposing tasks under uncertainty, or working in brownfield and refactor scenarios. Produces completeness summary (APPROVED-FOR-PLANNING, APPROVED-WITH-GAPS, or BLOCKED-FOR-PLANNING), missing input report with dependency mapping, required unblock actions, and planning annotations for downstream tasks. Use dh:rt-ica instead at the S2 implementation gate where missing inputs must halt execution.

日本語の概要は準備中です。原文の説明を表示しています。

Use when investigating failing tests or deciding whether to change the test or product. Validate test expectations against authoritative intent, trace product and test boundaries, and require evidence for the correction rather than automatic code fixes or test dismissal.

日本語の概要は準備中です。原文の説明を表示しています。

Verify after implementation that a feature achieved its required user/system outcomes. Use for goal-backward post-implementation verification that tests observable behavior rather than merely checking code existence.

日本語の概要は準備中です。原文の説明を表示しています。