{"owner":"zauberzeug","repo":"nicegui","hasSkills":true,"hasMcp":false,"mcpConfig":null,"found":["AGENTS.md",".github/copilot-instructions.md"],"skills":{"AGENTS.md":"# AI Agent Guidelines for NiceGUI\n\nThis file gives AI assistants project-specific behavioral guidance. For coding standards, see [CONTRIBUTING.md](CONTRIBUTING.md).\n\n## Pair Programming\n\nWork as a pair programmer, not a silent code generator:\n\n- **Think from first principles**: Don't settle for the first solution; question assumptions about the true nature of the problem.\n- **Requirements first**: Verify requirements before implementing, especially when writing or changing tests.\n- **Research before guessing**: Search the codebase for similar patterns; check online sources for verification.\n- **Discuss before deciding**: When strategy is unclear, present options and trade-offs to the user instead of choosing silently.\n- **Step-by-step for large changes**: Break down significant refactorings and get confirmation along the way.\n- **Challenge assumptions**: If the user states something untrue, correct them directly.\n\n## What to Avoid\n\n- **Overwriting `.env` files** without explicit user confirmation\n- **Creating new files** when editing existing ones would suffice\n- **Global mutable state** in library code\n- **Unnecessary dependencies** — check if existing code suffices first\n- **Reflexive regression tests** — not every bug fix earns a test, and a test coupled to implementation details can be worse than none.\n  Assert observable behavior, not internals: no private attributes, no patched machinery, no fake objects mirroring the code under test.\n  If you catch yourself building scaffolding to observe an internal mechanism, stop — find the user-visible effect to assert on, or skip the test and give the reason in the pull request.\n  Before writing a test, read a recent one in the same file and copy its shape.\n  (Details in [CONTRIBUTING.md](CONTRIBUTING.md#coding-conventions).)\n\n## Before Claiming a Task Complete\n\nRun the project's tests and linters (see [CONTRIBUTING.md](CONTRIBUTING.md)) and review your own diff for unintended scope creep.\n\n## Creating Pull Requests\n\nAlways use the repository's PR template ([`.github/PULL_REQUEST_TEMPLATE.md`](.github/PULL_REQUEST_TEMPLATE.md)) with its **Motivation**, **Implementation**, and **Progress** sections.\nDo not invent alternative formats like \"Summary\" or \"Test plan\".\n\n## Reviewing Pull Requests\n\nFollow [REVIEW.md](REVIEW.md) — it lists what to look for, defines the severity vocabulary, and sets the tone for reviews.\n",".github/copilot-instructions.md":"# GitHub Copilot Instructions for NiceGUI\n\n**Read these files before working:**\n\n1. [README.md](../README.md) - Project overview and setup\n2. [AGENTS.md](../AGENTS.md) - AI agent guidelines\n3. [CONTRIBUTING.md](../CONTRIBUTING.md) - Coding standards and workflow\n"},"files":{"AGENTS.md":"# AI Agent Guidelines for NiceGUI\n\nThis file gives AI assistants project-specific behavioral guidance. For coding standards, see [CONTRIBUTING.md](CONTRIBUTING.md).\n\n## Pair Programming\n\nWork as a pair programmer, not a silent code generator:\n\n- **Think from first principles**: Don't settle for the first solution; question assumptions about the true nature of the problem.\n- **Requirements first**: Verify requirements before implementing, especially when writing or changing tests.\n- **Research before guessing**: Search the codebase for similar patterns; check online sources for verification.\n- **Discuss before deciding**: When strategy is unclear, present options and trade-offs to the user instead of choosing silently.\n- **Step-by-step for large changes**: Break down significant refactorings and get confirmation along the way.\n- **Challenge assumptions**: If the user states something untrue, correct them directly.\n\n## What to Avoid\n\n- **Overwriting `.env` files** without explicit user confirmation\n- **Creating new files** when editing existing ones would suffice\n- **Global mutable state** in library code\n- **Unnecessary dependencies** — check if existing code suffices first\n- **Reflexive regression tests** — not every bug fix earns a test, and a test coupled to implementation details can be worse than none.\n  Assert observable behavior, not internals: no private attributes, no patched machinery, no fake objects mirroring the code under test.\n  If you catch yourself building scaffolding to observe an internal mechanism, stop — find the user-visible effect to assert on, or skip the test and give the reason in the pull request.\n  Before writing a test, read a recent one in the same file and copy its shape.\n  (Details in [CONTRIBUTING.md](CONTRIBUTING.md#coding-conventions).)\n\n## Before Claiming a Task Complete\n\nRun the project's tests and linters (see [CONTRIBUTING.md](CONTRIBUTING.md)) and review your own diff for unintended scope creep.\n\n## Creating Pull Requests\n\nAlways use the repository's PR template ([`.github/PULL_REQUEST_TEMPLATE.md`](.github/PULL_REQUEST_TEMPLATE.md)) with its **Motivation**, **Implementation**, and **Progress** sections.\nDo not invent alternative formats like \"Summary\" or \"Test plan\".\n\n## Reviewing Pull Requests\n\nFollow [REVIEW.md](REVIEW.md) — it lists what to look for, defines the severity vocabulary, and sets the tone for reviews.\n",".github/copilot-instructions.md":"# GitHub Copilot Instructions for NiceGUI\n\n**Read these files before working:**\n\n1. [README.md](../README.md) - Project overview and setup\n2. [AGENTS.md](../AGENTS.md) - AI agent guidelines\n3. [CONTRIBUTING.md](../CONTRIBUTING.md) - Coding standards and workflow\n"},"items":[{"name":"AGENTS.md","path":"AGENTS.md","title":"AGENTS.md","content":"# AI Agent Guidelines for NiceGUI\n\nThis file gives AI assistants project-specific behavioral guidance. For coding standards, see [CONTRIBUTING.md](CONTRIBUTING.md).\n\n## Pair Programming\n\nWork as a pair programmer, not a silent code generator:\n\n- **Think from first principles**: Don't settle for the first solution; question assumptions about the true nature of the problem.\n- **Requirements first**: Verify requirements before implementing, especially when writing or changing tests.\n- **Research before guessing**: Search the codebase for similar patterns; check online sources for verification.\n- **Discuss before deciding**: When strategy is unclear, present options and trade-offs to the user instead of choosing silently.\n- **Step-by-step for large changes**: Break down significant refactorings and get confirmation along the way.\n- **Challenge assumptions**: If the user states something untrue, correct them directly.\n\n## What to Avoid\n\n- **Overwriting `.env` files** without explicit user confirmation\n- **Creating new files** when editing existing ones would suffice\n- **Global mutable state** in library code\n- **Unnecessary dependencies** — check if existing code suffices first\n- **Reflexive regression tests** — not every bug fix earns a test, and a test coupled to implementation details can be worse than none.\n  Assert observable behavior, not internals: no private attributes, no patched machinery, no fake objects mirroring the code under test.\n  If you catch yourself building scaffolding to observe an internal mechanism, stop — find the user-visible effect to assert on, or skip the test and give the reason in the pull request.\n  Before writing a test, read a recent one in the same file and copy its shape.\n  (Details in [CONTRIBUTING.md](CONTRIBUTING.md#coding-conventions).)\n\n## Before Claiming a Task Complete\n\nRun the project's tests and linters (see [CONTRIBUTING.md](CONTRIBUTING.md)) and review your own diff for unintended scope creep.\n\n## Creating Pull Requests\n\nAlways use the repository's PR template ([`.github/PULL_REQUEST_TEMPLATE.md`](.github/PULL_REQUEST_TEMPLATE.md)) with its **Motivation**, **Implementation**, and **Progress** sections.\nDo not invent alternative formats like \"Summary\" or \"Test plan\".\n\n## Reviewing Pull Requests\n\nFollow [REVIEW.md](REVIEW.md) — it lists what to look for, defines the severity vocabulary, and sets the tone for reviews.\n","category":"root","tokens":600},{"name":"copilot-instructions.md","path":".github/copilot-instructions.md","title":"copilot-instructions.md","content":"# GitHub Copilot Instructions for NiceGUI\n\n**Read these files before working:**\n\n1. [README.md](../README.md) - Project overview and setup\n2. [AGENTS.md](../AGENTS.md) - AI agent guidelines\n3. [CONTRIBUTING.md](../CONTRIBUTING.md) - Coding standards and workflow\n","category":".github","tokens":66}]}