4,326 件 ・ 関連度順
概要と使いどころ
Build or resume mathematical-modeling competition work, including CUMCM, MCM/ICM, graduate and regional contests, data challenges, and open-topic statistical modeling. Guide problem framing, modeling, computation, validation, Chinese or English LaTeX writing, and reviewed PDF/source delivery using current official requirements. Not for ordinary paper polishing.
日本語の概要は準備中です。原文の説明を表示しています。
Build documentation websites with Docusaurus. Use when a user asks to create a documentation site, build a developer portal, set up API docs, create a knowledge base, add versioned documentation, build a static docs site with search, create a blog alongside docs, or migrate from GitBook or ReadTheDocs. Covers project setup, docs structure, versioning, custom pages, blog, Algolia search, MDX components, and deployment.
日本語の概要は準備中です。原文の説明を表示しています。
Draft professional emails for various business scenarios with appropriate tone and structure. Use when a user asks to write an email, compose a message, draft a reply, write a follow-up, create an outreach email, respond to a client, write a cold email, or craft any professional correspondence.
日本語の概要は準備中です。原文の説明を表示しています。
Assists with end-to-end testing of web applications using Cypress. Use when writing E2E tests, setting up component testing, configuring CI pipelines with parallelization, or building custom test commands. Trigger words: cypress, e2e testing, end-to-end, cypress run, cy.get, integration testing, browser testing.
日本語の概要は準備中です。原文の説明を表示しています。
Create compelling, personalized cover letters that help you stand out in job applications. Use when a user asks to write a cover letter, draft a job application letter, create a letter of interest, compose a motivation letter, or personalize an application for a specific company and role.
日本語の概要は準備中です。原文の説明を表示しています。
Centrifugo is a self-hosted real-time messaging server: your backend publishes over an HTTP or gRPC API and browsers or mobile apps receive messages over WebSocket, SSE or HTTP streaming. Use when the user wants chat, live notifications, presence ("who is online"), message history with recovery, or any WebSocket pub/sub without writing a socket server.
日本語の概要は準備中です。原文の説明を表示しています。
Build backends with Appwrite — open-source Backend-as-a-Service. Use when a user asks to set up user authentication, manage a database without writing backend code, handle file storage and uploads, add realtime subscriptions, set up cloud functions, build a mobile or web app backend, replace Firebase with an open-source alternative, or self-host a BaaS platform. Covers auth, databases, storage, functions, realtime, and SDK integration for web, mobile, and server-side.
日本語の概要は準備中です。原文の説明を表示しています。
Build AI agents that automate scientific research — hypothesis generation, experiment design, data analysis, and paper writing using agentic tree search. Use when: automating research workflows, generating and testing hypotheses, building AI-powered research assistants.
日本語の概要は準備中です。原文の説明を表示しています。
Generate short-form videos with AI — script writing, text-to-speech narration, stock footage selection, subtitle generation, and video assembly. Use when: creating TikTok/YouTube Shorts/Reels content, automating video production, building content pipelines.
日本語の概要は準備中です。原文の説明を表示しています。
Airtable is a hosted spreadsheet-database; its Web API reads and writes records, table schema, attachments and webhooks over REST. Use when tasks involve reading or writing Airtable data, importing or upserting rows from a CSV or another system, syncing external sources with Airtable bases, reacting to record changes with webhooks, connecting users through Airtable OAuth, or debugging 422 and 429 responses from api.airtable.com.
日本語の概要は準備中です。原文の説明を表示しています。
Build MCP tools that are sticky for vibe coders and powerful for developersUse when "Designing new MCP tools, Improving tool UX or DX, Writing error messages, Planning tool naming, Discussing user onboarding, Making tools "sticky", Vibe coder experience, mcp, product, ux, dx, vibe-coding, onboarding, developer-experience, tool-design" mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
Use when drafting patent applications, writing claims, analyzing prior art, or responding to office actions - covers USPTO practice, claim strategies, and specification requirementsUse when ", " mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
Expert in navigating and manipulating git history. Covers finding bugs with bisect, understanding code evolution, recovering lost work, and rewriting history safely. Understands that git history is your time machine. Use when "git history, git bisect, find when bug introduced, recover deleted, rewrite history, git blame, lost commit, " mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
Kubernetes is the operating system for the cloud. It schedules containers, handles networking, manages storage, and keeps your apps running. But K8s has a steep learning curve - abstractions on abstractions on abstractions. This skill covers the core concepts (Pods, Deployments, Services), production patterns (health checks, resource limits, HPA), and the gotchas that catch everyone (namespace confusion, service discovery, secret management). 2025 reality: You probably don't need to run your own cluster. Use managed K8s (EKS, GKE, AKS) unless you have a very good reason not to. Focus on writing good manifests, not managing etcd. Use when "kubernetes, k8s, kubectl, deployment manifest, helm chart, kustomize, pod, service yaml, ingress, horizontal pod autoscaler, hpa, kubernetes, k8s, containers, orchestration, devops, cloud-native, helm, kustomize" mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
Expert in writing documentation that developers actually read. Covers README craft, API docs, tutorials, and internal docs. Understands that docs are a product—they need UX, marketing, and user empathy. Use when "documentation, readme, write docs, api docs, tutorial, how to document, explain this, " mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
Technical documentation specialist for API docs, tutorials, architecture docs, and developer experienceUse when "documentation, docs, readme, tutorial, api docs, guide, changelog, comments, openapi, documentation, api-docs, tutorials, readme, openapi, swagger, developer-experience, technical-writing, ml-memory" mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
Master the AI tools that generate unlimited content at scale. From stunning images to professional videos, voiceovers to compelling copy - create content that used to require entire teams. Use when "need images, create video, generate content, voiceover, marketing visuals, social media content, ad creative, content, images, video, audio, writing, marketing, creative" mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
Writing maintainable code - readability principles, SOLID patterns applied pragmatically, and the judgment to know when rules should bendUse when "code quality, clean code, readability, naming, SOLID, refactor, code review, best practices, maintainable, how should I structure, clean-code, solid, readability, maintainability, code-review, naming, functions, principles" mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
Tools are how AI agents interact with the world. A well-designed tool is the difference between an agent that works and one that hallucinates, fails silently, or costs 10x more tokens than necessary. This skill covers tool design from schema to error handling. JSON Schema best practices, description writing that actually helps the LLM, validation, and the emerging MCP standard that's becoming the lingua franca for AI tools. Key insight: Tool descriptions are more important than tool implementations. The LLM never sees your code - it only sees the schema and description. Use when "agent tool, function calling, tool schema, tool design, mcp server, mcp tool, tool use, build tool for agent, define function, input_schema, tool_use, tool_result, agents, tools, function-calling, mcp, json-schema, anthropic, openai, llm-tools" mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
Black-box QA audit of slop-guard across MCP, CLI, fit, docs, agent workflows, and writing-effectiveness. Files GitHub issues for real problems found.
日本語の概要は準備中です。原文の説明を表示しています。
De-slop pass for any text. Scans for the statistical fingerprints of AI writing (negative parallelism / "not X but Y", em-dash density, rule-of-three, false ranges, puffery vocabulary, uniform cadence, hedged both-sidesing), rewrites by meaning, then re-scans until the text is clean and sits in the right register for its genre: academic article, tweet, reddit post, email, blog, docs, marketing. Use when the user says "deslopify", "deslop", "de-slop this", "remove the AI tells", "humanize this", "make this not sound like AI", or invokes /deslopify. Also use before publishing any agent-drafted prose.
日本語の概要は準備中です。原文の説明を表示しています。
Authoritative guide for implementing stunning, accessible, performant UI. Synthesizes design engineering philosophy, accessibility standards, animation principles, spatial design, typography, color systems, and component craft into a single actionable reference. Complements the design-system skill (which covers DESIGN.md spec writing) by covering the HOW of implementation. Trigger phrases: "build UI", "create component", "landing page", "make it look good", "frontend", "design", "polish UI", "implement design", "make it beautiful", "UI implementation", "component styling", "animation", "accessibility"
日本語の概要は準備中です。原文の説明を表示しています。
Checkable-ish surface presentation signals a reviewer notices first — duplicate/near-identical tables, leftover pipeline/template strings, too-few or LLM-looking figures, and page-padding. AUXILIARY ONLY and weak by design: a deterministic pass (tools/check_presentation.py — dup-table + pipeline-artifact) plus a fresh cross-model GROSS-cases-only semantic pass (thin-float, LLM-figure, page-padding), every above-info finding span-anchored to the evidence ledger (claims.json). The adjudicator CAPS everything at minor (SURFACE_ONLY_SKILLS + SURFACE_PATTERNS) — these contribute at most SOFT_FLAGS, never a HARD verdict — default false_positive_risk:high. NOTE: the pure AI writing-STYLE impressions (AI-flavor prose, defensive 'not-X-but-Y' hedging, narrative-arc, jargon-stuffing, invented codenames) MOVED to the zero-verdict-weight AIS track — for those use skills/ai-style-impressions, NOT this. Emits presentation-signals.findings.json; NEVER computes the verdict. Triggers: "presentation signals", "surface check", "duplicate tables", "排版信号".
日本語の概要は準備中です。原文の説明を表示しています。
Audits tests for concurrency safety — race conditions, shared mock state, cleanup ordering. Use when writing tests that involve goroutines, async operations, or shared mutable state.
日本語の概要は準備中です。原文の説明を表示しています。