website-devtools
Skill Instructions
Purpose
Provide a repeatable way to use browser tools during website work to validate rendering, diagnose layout or CSS issues, and troubleshoot together with the Maintainer.
Hard Rules
Must
- Use the
browser/*tools when diagnosing rendering, layout, or interaction issues. - Capture concrete findings (console errors, computed styles, DOM structure) and summarize them in the PR/issue.
Must Not
- Do not guess at rendering behavior when you can verify it in the browser preview.
Golden Example
Use browser tools to:
- Inspect computed styles and layout for a problematic element
- Check console for errors
More from oocx/tfplan2md
arc42-documentation
Create comprehensive architecture documentation using the arc42 template structure (12 sections covering introduction, constraints, context, solution strategy, building blocks, runtime, deployment, concepts, decisions, quality, risks, and glossary).
83git-rebase-main
Safely rebase the current feature branch on top of the latest origin/main. Use when preparing a branch for PR, UAT, or release.
24website-quality-check
Run a lightweight, repeatable quality checklist for the website (including style guide adherence).
19analyze-chat-export
Export and analyze VS Code Copilot chat logs for retrospective metrics. Extracts model usage, tool invocations, approval patterns, and timing data.
18create-pr-azdo
Create an Azure DevOps pull request using az devops tooling; include the repo’s linear-history merge preference and ask the Maintainer if merge options differ.
17agent-tool-selection
Guide for selecting appropriate VS Code Copilot tools when configuring agents, including environment-specific considerations.
17