メニュー
Review ArtStroy UI code for Web Interface Guidelines compliance. Use when auditing components, pages, or layouts for accessibility, UX best practices, and interface quality. Fetches the latest Vercel Web Interface Guidelines before each review.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Pull weekly traffic data from Plausible Analytics for artstroy.net, produce a structured digest with top articles, category breakdown, referrer mix, and trend signals. Posted to the root company issue weekly.
Cross-post published ArtStroy articles to dev.to and Hashnode with correct canonical URLs, metadata mapping, and formatting. Handles API integration for automated posting and creates manual-assist drafts for platforms without API access.
Scan ArtStroy npm/bun dependencies for known vulnerabilities. Ranks CVEs by CVSS severity, creates vuln-fix issues with deadlines, and verifies fixes post-deploy. Run monthly and on any new dependency addition.
Manage and verify the ArtStroy CI/CD pipeline. Covers the GitHub Actions deploy workflow, SSH-based Hetzner deployment, Docker Compose orchestration, and post-deploy health checks. Used by DevOps Engineer for deploy operations and pipeline maintenance.
Manage ArtStroy's Docker Compose configuration, Hetzner server provisioning, environment variable management, and infrastructure-as-code practices. Used by DevOps Engineer for all infrastructure changes.
Compile new ArtStroy articles into a Markdown newsletter draft ready for Buttondown. Runs weekly; sends draft to human for final review before dispatch.
| name | web-design-guidelines |
| description | Review ArtStroy UI code for Web Interface Guidelines compliance. Use when auditing components, pages, or layouts for accessibility, UX best practices, and interface quality. Fetches the latest Vercel Web Interface Guidelines before each review. |
Review ArtStroy UI files for compliance with Web Interface Guidelines.
file:line formatFetch fresh guidelines before each review using an HTTP GET:
https://raw.githubusercontent.com/vercel-labs/web-interface-guidelines/main/command.md
Do this at the start of every review session — the guidelines evolve and must not be cached between reviews.
The fetched content contains all rules and the required output format. Follow that format exactly.
When given a file path or glob pattern:
If no files are specified, ask which files to review before fetching guidelines.
When reviewing ArtStroy components, apply additional context:
.astro, .tsx, or .mdx<Image> component handles optimization; bare <img> tags for content images are a findingclient:load vs client:visible — flag any client:load that could be client:visibleUse file:line format for every finding:
src/components/ArticleCard.tsx:42 — missing alt text on image element
src/layouts/Base.astro:15 — lang attribute missing on <html>
src/components/Search.tsx:88 — button lacks accessible label
Group findings by severity if the guidelines define severity levels. Follow whatever format the fetched guidelines specify — that document is authoritative.