Loading...
Loading...
Found 101 Skills
Turn hand-made first-50 traction into self-reinforcing acquisition loops, so the next 5,000 users come from usage, not founder hours. Use when growth stalls the moment the user stops pushing, every signup traces back to a DM or one launch spike, or they're reaching for "more channels" when the real gap is that using the product creates no new users.
Create world-class, accessible, responsive interfaces with sophisticated interactive elements including chat, terminals, code display, and streaming content. Use when building user interfaces that need professional polish and developer-focused features.
Explain English technical documents and text in Japanese with contextual understanding. Not a simple translator — reads the surrounding file or codebase context to provide deeper, more accurate explanations tailored for Japanese-speaking developers. Use when: "explain this English", "この英文を解説", "英語の解説", "en-explainer", "what does this mean", "この英文の意味", "英文を日本語で説明", "ドキュメントを解説", "README解説", "エラーメッセージの意味", "コメントの意味", "API仕様の解説", or when the user pastes English text and asks for explanation in Japanese. Also use when the user provides a file path and asks to explain specific English sections, or when they want to understand English code comments, error messages, config files, or technical documentation.
Search tech blogs, developer forums, and IT media (TechCrunch, Hacker News, 36氪, etc.) for software and hardware industry updates with heat ranking and EN↔CN translation. Use this skill only when the topic is clearly about programming, software, hardware, AI, or IT infrastructure.
Speakeasy integration. Manage data, records, and automate workflows. Use when the user wants to interact with Speakeasy data.
Use when exploring or modifying a codebase and you need a cheap structural map of files, directories, imports, exports, or direct members before reading full source.
Search issues, merged pull requests, READMEs, and documentation. Use when the question is how a library or API behaves, what an error means, or whether a bug was fixed; prefer this over a general web page.
Route to the next skill. Tell it your situation; it names the skill.
Lay the keel of the shipyard harness in any repo — the 4-pillar shared environment (Context, Rules, Tools, Standards) across 5 surfaces (CLAUDE.md, skills, design-system, mcp/cli, shared context) so that every human and agent inherits the same design language and anyone can ship. Run once per repo; re-run with --check to audit drift.
Gamified codebase onboarding through the Spaghetti Code Monster. Use when a developer wants to learn a new codebase through investigation, deep-dive challenges, and the Monster's guidance.
Guide wanderers to the right animal for their journey. Perch, tilt your head, chatter about the forest, present the options, and warble the recommendation. Use when helping users choose which skill to use, discovering capabilities, or navigating the ecosystem.
Disaster recovery drill exercises and security checklists for web application projects (SPA, SSR, full-stack web apps). Focused on solo/indie developers using free-tier infrastructure (Vercel, Supabase, Cloudflare, Netlify, Railway, etc.). Bridges big-tech best practices (NIST, Google SRE DiRT, ISO 22301) to indie scale. Use when the user mentions drills, disaster recovery, security audit, incident simulation, project health check, resilience testing, backup strategies, secret rotation, or incident response for web projects. Not for mobile apps, desktop software, CLI tools, or games.