Save this content to: .claude/skills/draft-core-issue/SKILL.md

# Draft an issue for the core

1. Confirm it really is a core concern: reproduce it with core classes only (a minimal PHP snippet, no Symfony). If it reproduces only inside the container, it is a bundle problem.
2. Check existing core issues (`gh issue list -R mtubis/html-translator --search "<keywords>"`) and the drafts in `docs/core-feedback/` of this repo and of the Laravel package — the same need may already be drafted.
3. Write the draft to `docs/core-feedback/<kebab-title>.md` in the core's issue format: `# Title`, `## Context` (what the bundle needs and why; link the bundle issue; mention whether the Laravel package has the same need), `## Scope`, `## Acceptance criteria`, `## Out of scope`. Include the minimal reproduction.
4. Show the draft to the maintainer. Create it on GitHub only when asked: `gh issue create -R mtubis/html-translator --title "…" --body-file docs/core-feedback/<file>.md`.
5. In the package, either wait, or add a temporary workaround marked `// TODO(core#<n>): remove when …` with a test that will fail once the core is fixed (so the workaround is noticed).