メニュー
Use when auto-generating API endpoint documentation, writing OpenAPI specs, or producing request/response examples for external provider integrations
| name | api-documentation-generator |
| description | Use when auto-generating API endpoint documentation, writing OpenAPI specs, or producing request/response examples for external provider integrations |
For any information that cannot be verified from the current codebase or official documentation, use hedged language:
Never assert version numbers, default values, or error codes that have not been confirmed from the source.
Before writing any documentation, locate the actual implementation:
MessageCommandHandler that calls the endpoint via HttpClientInterface.config/packages/framework.yaml (framework.http_client.scoped_clients).Entity to understand which fields are persisted.Use when analyzing project codebase structure, documenting architecture, mapping domain boundaries, or resolving dependency relationships. Covers Symfony app layout, multi-EntityManager topology, Messenger message flows, and external provider integrations.
Use when explaining how to install, configure, or use an external library in this project. Covers Composer packages, npm packages, Symfony bundles, and infrastructure client libraries. Always verifies compatibility with PHP 8.4, Symfony 8, and existing project conventions before recommending.
Use when reviewing code changes, identifying potential bugs, or suggesting improvements for pull requests. Covers correctness, maintainability, performance, security, and project-specific rule compliance (Symfony 8, PHP 8.4, Doctrine multi-EM, RabbitMQ message flow, Redis cache, API key handling).
Use this skill whenever the user writes, reviews, debugs, or refactors Bash shell scripts on Ubuntu/Linux. Triggers include mentions of '.sh files', 'shell script', 'bash', 'shebang', POSIX compatibility, ShellCheck, cron jobs, systemd timers, or any task involving command-line automation. Also use when fixing common bash pitfalls like quoting issues, exit code handling, IFS, variable expansion, or word splitting — even if the user doesn't explicitly say 'bash'.