메뉴
Check domain name availability across 12 TLDs via direct WHOIS/RDAP lookups. No external service needed. Use when the user asks about domain availability, wants to find a domain name, or mentions registering a domain.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | domain-whois |
| description | Check domain name availability across 12 TLDs via direct WHOIS/RDAP lookups. No external service needed. Use when the user asks about domain availability, wants to find a domain name, or mentions registering a domain. |
| compatibility | Requires bash, whois CLI (built into macOS, install via apt on Linux), and curl. |
| metadata | {"author":"stevederico","version":"1.0"} |
Check domain availability across 12 TLDs via direct WHOIS and RDAP lookups. No API dependency.
Run the bundled script:
scripts/check.sh <domain>
Pass the base name only (no TLD). The script checks all 12 TLDs in parallel:
.com, .net, .org, .io, .dev, .app, .co, .xyz, .ai, .shop, .site, .tech
Pipe-delimited, sorted available first:
example.dev|Available
example.app|Available
example.com|Taken
example.shop|Unknown
Format as a table:
| Domain | Status |
|---|---|
| example.dev | Available |
| example.app | Available |
| example.com | Taken |
Run the script once per name. Can run in parallel:
scripts/check.sh name1 &
scripts/check.sh name2 &
wait
whois -h <server> (port 43 TCP).dev and .app checked via RDAP (HTTP to Google registry)Deep dive into codebase architecture with text explanations. Use when the user says: "explain the architecture", "how does X work", "refresh my memory", "deep dive into", "explain this system", "I forgot how X works", "walk me through".
Node.js/Hono backend development with native-first approach. Also use when the user mentions 'create an API,' 'add an endpoint,' 'build a REST API,' 'database schema,' 'server-side,' 'middleware,' 'route handler,' or 'backend logic.' Use this even if the user just says 'I need an API for...' or 'add a POST route.'
Reduce code complexity, eliminate dead code, consolidate duplicate logic. Also use when the user mentions 'dead code,' 'unused functions,' 'duplicated logic,' 'too complex,' 'simplify this,' 'consolidate,' 'reduce bundle size,' 'clean up,' or 'refactor for maintainability.' Use this even if the user just says 'this feels bloated' or 'there must be dead code in here.'
Systematic error investigation and troubleshooting for React and Node.js. Also use when the user mentions 'error,' 'bug,' 'broken,' 'not working,' 'crash,' 'stack trace,' 'console error,' 'white screen,' 'infinite loop,' 'network error,' or '500 error.' Use this even if the user just says 'something is wrong' or 'it broke.'
Railway platform deployment with optimal configuration and troubleshooting. Also use when the user mentions 'deploy,' 'railway,' 'push to production,' 'environment variables,' 'deployment failed,' 'build error,' 'railway logs,' 'custom domain,' or 'database provisioning.' Use this even if the user just says 'ship it' or 'get it live.'
Minimalist design systems inspired by Vercel and shadcn/ui. Also use when the user mentions 'design system,' 'logo,' 'landing page design,' 'UI design,' 'visual direction,' 'color palette,' 'typography,' 'component design,' 'dark mode design,' or 'make it look like Vercel.' Use this even if the user just says 'design this' or 'it needs a visual refresh.'